public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: DJ Delorie <dj@redhat.com>
To: "Tang\, Jun" <juntangc@amazon.com>
Cc: carlos@redhat.com, libc-alpha@sourceware.org
Subject: Re: revised patch for hp-timing.h
Date: Tue, 31 Jan 2023 18:14:39 -0500	[thread overview]
Message-ID: <xncz6ue1pc.fsf@greed.delorie.com> (raw)
In-Reply-To: <cf9eebc3af244c78b4779644560883a8@amazon.com>


Something was stripping leading spaces off the "context" lines.  The
attached-as-file patch was unaffected.  However, because this was a
"Re:" email, it wasn't considered as a new patch in patchwork, but
instead attached to the corrupted patch's series.

So please re-send as a new message to the list, without the "Re:" or
Reply-to headers, with the patch attached as a file, and it should work.

If not, we'll keep trying to make it work :-)

"Tang, Jun" <juntangc@amazon.com> writes:
>> diff --git a/sysdeps/aarch64/hp-timing.h b/sysdeps/aarch64/hp-timing.h 
>> index f7f7ac7cae..c699effe6a 100644
>> --- a/sysdeps/aarch64/hp-timing.h
>> +++ b/sysdeps/aarch64/hp-timing.h
>> @@ -41,7 +41,7 @@ typedef uint64_t hp_timing_t;
>> #define HP_TIMING_DIFF(Diff, Start, End)                       \
>> ({  hp_timing_t freq;                                          \
>>      __asm__ __volatile__ ("mrs %0, cntfrq_el0" : "=r" (freq)); \
>> -   (Diff) = ((End) - (Start)) * (UINT64_C(1000000000) / freq); \
>> +   (Diff) = (((End) - (Start)) * UINT64_C(1000000000)) / freq; \
>> })
>>  #endif /* hp-timing.h */


  reply	other threads:[~2023-01-31 23:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-31 17:19 Tang, Jun
2023-01-31 22:38 ` Carlos O'Donell
2023-01-31 22:50   ` Tang, Jun
2023-01-31 23:14     ` DJ Delorie [this message]
2023-01-31 23:16       ` Tang, Jun

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xncz6ue1pc.fsf@greed.delorie.com \
    --to=dj@redhat.com \
    --cc=carlos@redhat.com \
    --cc=juntangc@amazon.com \
    --cc=libc-alpha@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).