public inbox for linux-ide@vger.kernel.org
 help / color / mirror / Atom feed
From: Niklas Cassel <cassel@kernel.org>
To: Haoyu Lu <hechushiguitu666@gmail.com>
Cc: Damien Le Moal <dlemoal@kernel.org>,
	Viresh Kumar <vireshk@kernel.org>,
	linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ata: pata_arasan_cf: fix missing newline in dev_err messages
Date: Thu, 2 Apr 2026 10:27:57 +0200	[thread overview]
Message-ID: <ac4ojZl_qe3NXwwi@ryzen> (raw)
In-Reply-To: <CAEZ4rQ_c9m=3Ksp15706xq7TtH-9SxF8vaNNZoNj_dBgP7EuNw@mail.gmail.com>

Hello Haoyu,

On Thu, Apr 02, 2026 at 03:48:42PM +0800, Haoyu Lu wrote:
> Hi Damien,
> 
> Sorry for the mistake!
> I didn't realize libata patches need to be based on libata/for-next,
> not mainline.

This patch was not based on either libata/for-next or Linus's tree.


> I see the driver has been refactored and the newlines are already fixed.
> I'll drop this patch and follow the correct branch for future changes.
> Thanks for the clarification!

There has not been any newlines added upstream, your fix is still valid.

However, the function has not been refactored, you must have based your
patch on some downstream kernel.

While the patch does apply, and I could theoretically apply it, please:

-Send a V2 based on libata/for-next or Linus's tree
-Pick up the tag from Viresh
-Change the subject from
 ata: pata_arasan_cf: fix missing newline in dev_err messages
 to
 ata: pata_arasan_cf: fix missing newline in dev_err() messages


If only to give you experience working with upstream kernels.


Kind regards,
Niklas

      reply	other threads:[~2026-04-02  8:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-02  2:10 [PATCH] ata: pata_arasan_cf: fix missing newline in dev_err messages Haoyu Lu
2026-04-02  3:00 ` Viresh Kumar
2026-04-02  5:35 ` Damien Le Moal
2026-04-02  7:11   ` Owens James
2026-04-02  7:38     ` Damien Le Moal
2026-04-02  7:48       ` Haoyu Lu
2026-04-02  8:27         ` 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=ac4ojZl_qe3NXwwi@ryzen \
    --to=cassel@kernel.org \
    --cc=dlemoal@kernel.org \
    --cc=hechushiguitu666@gmail.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vireshk@kernel.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