From: Niklas Cassel <cassel@kernel.org>
To: Haoyu Lu <hechushiguitu666@gmail.com>
Cc: Viresh Kumar <vireshk@kernel.org>,
Damien Le Moal <dlemoal@kernel.org>,
linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] ata: pata_arasan_cf: fix missing newline in dev_err() messages
Date: Thu, 2 Apr 2026 11:10:14 +0200 [thread overview]
Message-ID: <ac4ydu1CKrPb0f0g@ryzen> (raw)
In-Reply-To: <20260402090612.2236-1-hechushiguitu666@gmail.com>
Hello Haoyu,
This patch is still appears to be based on a downstream kernel.
(Which downstream kernel are you using btw?)
Please use a mainline kernel:
git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
or
git clone git://git.kernel.org/pub/scm/linux/kernel/git/libata/linux.git
Also, Viresh provided an Acked-by, not a Reviewed-by:
https://lore.kernel.org/linux-ide/ac4ojZl_qe3NXwwi@ryzen/T/#mb2b5ed70f1b4256fe3c675b539c1791249e08d22
Kind regards,
Niklas
prev parent reply other threads:[~2026-04-02 9:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-02 9:06 [PATCH v2] ata: pata_arasan_cf: fix missing newline in dev_err() messages Haoyu Lu
2026-04-02 9:10 ` 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=ac4ydu1CKrPb0f0g@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