linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Nathan Lynch <nathanl@linux.ibm.com>
To: linuxppc-dev@lists.ozlabs.org
Cc: aik@ozlabs.ru, tyreld@linux.ibm.com, cheloha@linux.ibm.com,
	ldufour@linux.ibm.com, ajd@linux.ibm.com
Subject: Re: [PATCH v2 1/2] powerpc/rtas: rtas_busy_delay() improvements
Date: Wed, 17 Nov 2021 00:13:11 -0600	[thread overview]
Message-ID: <87pmqzia2w.fsf@linux.ibm.com> (raw)
In-Reply-To: <20211117060259.957178-2-nathanl@linux.ibm.com>

Nathan Lynch <nathanl@linux.ibm.com> writes:
>
> Signed-off-by: Nathan Lynch <nathanl@linux.ibm.com>
> ---
>
> Notes:
>     This could be considered a sequel to:
>     
>     https://lore.kernel.org/linuxppc-dev/20210504030358.1715034-1-nathanl@linux.ibm.com/
>     
>     which tried to address both the suboptimal delay behavior as well as naming
>     issues. The present change achieves the performance improvement and leaves
>     the matter of naming for another time.
>     
>     I've incorporated Alexey's feedback from that series to avoid division when
>     calculating the arguments to usleep_range().

Oops, this part is redundant with information in the cover. Git should
discard it if/when applied, though.

  reply	other threads:[~2021-11-17  6:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-17  6:02 [PATCH v2 0/2] powerpc/rtas: improved busy and extended delay status handling Nathan Lynch
2021-11-17  6:02 ` [PATCH v2 1/2] powerpc/rtas: rtas_busy_delay() improvements Nathan Lynch
2021-11-17  6:13   ` Nathan Lynch [this message]
2021-11-17  6:02 ` [PATCH v2 2/2] powerpc/rtas: rtas_busy_delay_time() kernel-doc Nathan Lynch
2021-11-25  9:36 ` [PATCH v2 0/2] powerpc/rtas: improved busy and extended delay status handling Michael Ellerman

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=87pmqzia2w.fsf@linux.ibm.com \
    --to=nathanl@linux.ibm.com \
    --cc=aik@ozlabs.ru \
    --cc=ajd@linux.ibm.com \
    --cc=cheloha@linux.ibm.com \
    --cc=ldufour@linux.ibm.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=tyreld@linux.ibm.com \
    /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 NNTP newsgroup(s).