public inbox for linux-ide@vger.kernel.org
 help / color / mirror / Atom feed
From: Niklas Cassel <cassel@kernel.org>
To: Niklas Cassel <Niklas.Cassel@wdc.com>
Cc: Tomas Henzl <thenzl@redhat.com>,
	Damien Le Moal <dlemoal@kernel.org>,
	"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Subject: Re: [PATCH V3] ata: ahci: simplify init function
Date: Tue, 18 Mar 2025 09:01:10 +0100	[thread overview]
Message-ID: <Z9koRvxBwzwfjQ81@ryzen> (raw)
In-Reply-To: <Z9gxiFiKsfXXyOkp@ryzen>

Hello Tomas,

On Mon, Mar 17, 2025 at 02:28:25PM +0000, Niklas Cassel wrote:
> On Mon, Mar 17, 2025 at 03:00:46PM +0100, Tomas Henzl wrote:
> > Hi Damien,
> > 
> > the V3  patch applies to the for-6.15 branch with just an offset.
> > Can you take it as it is or do you want me to resend?
> > 
> > Regards,
> > Tomas
> 
> Please rebase and send a v4 with an improved commit log.
> 
> -Remove the double newlines.
> 
> -Use paragraphs (with an empty line between paragraphs).
>  (There can be multiple sentences in one paragraph.)
> 
> -Improve the motivation. I.e. "removing a few lines" doesn't make sense,
>  you are actually adding lines:
>  1 file changed, 12 insertions(+), 11 deletions(-)
> 
>  You are however moving all the IRQ vector allocations into a single
>  place/function, instead of having the allocations spread out over
>  two separate call sites, so your refactoring does make sense, since
>  it improves code readability.

If you want this patch to be queued up for 6.15, please send a new version
this week, because after this week, it will instead be queued up for 6.16.


Kind regards,
Niklas

      reply	other threads:[~2025-03-18  8:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-14 18:29 [PATCH V3] ata: ahci: simplify init function Tomas Henzl
2025-01-15  2:30 ` Damien Le Moal
2025-01-15 15:08   ` Tomas Henzl
2025-03-17 14:00     ` Tomas Henzl
2025-03-17 14:28       ` Niklas Cassel
2025-03-18  8:01         ` Niklas Cassel [this message]

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=Z9koRvxBwzwfjQ81@ryzen \
    --to=cassel@kernel.org \
    --cc=Niklas.Cassel@wdc.com \
    --cc=dlemoal@kernel.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=thenzl@redhat.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