From: Damien Le Moal <dlemoal@kernel.org>
To: Yahu Gao <yahu.gao@outlook.com>
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
Yahu Gao <gaoyh12@lenovo.com>
Subject: Re: [PATCH v3] ata: libata-core: Simplies if condition
Date: Fri, 19 May 2023 08:17:43 +0900 [thread overview]
Message-ID: <ce4ee43c-8acd-6ad8-3a18-bf4bdfe48f9c@kernel.org> (raw)
In-Reply-To: <OS3P286MB0632EC8F4BE2127EF092F59B9E789@OS3P286MB0632.JPNP286.PROD.OUTLOOK.COM>
On 5/15/23 11:36, Yahu Gao wrote:
> From: Yahu Gao <gaoyh12@lenovo.com>
>
> Simplify the condition used in ata_dev_revalidate() to not
> issue identify commands to port multiplier devices.
>
> Signed-off-by: Yahu Gao <gaoyh12@lenovo.com>
Applied to for-6.5 with a fixed up commit title (typo... please run
scripts/checkpatch.pl next time). Thanks !
> ---
> drivers/ata/libata-core.c | 6 +-----
> 1 file changed, 1 insertion(+), 5 deletions(-)
>
> Changes since V1:
> 1. Update the subject
> 2. Add more descriptive
> 3. Remove review-by without email
> 4. keep "ata_class_enabled(new_class) &&" condition
>
> diff --git a/drivers/ata/libata-core.c b/drivers/ata/libata-core.c
> index 14c17c3bda4e..2c9472b00f17 100644
> --- a/drivers/ata/libata-core.c
> +++ b/drivers/ata/libata-core.c
> @@ -3802,11 +3802,7 @@ int ata_dev_revalidate(struct ata_device *dev, unsigned int new_class,
> return -ENODEV;
>
> /* fail early if !ATA && !ATAPI to avoid issuing [P]IDENTIFY to PMP */
> - if (ata_class_enabled(new_class) &&
> - new_class != ATA_DEV_ATA &&
> - new_class != ATA_DEV_ATAPI &&
> - new_class != ATA_DEV_ZAC &&
> - new_class != ATA_DEV_SEMB) {
> + if (ata_class_enabled(new_class) && new_class == ATA_DEV_PMP) {
> ata_dev_info(dev, "class mismatch %u != %u\n",
> dev->class, new_class);
> rc = -ENODEV;
--
Damien Le Moal
Western Digital Research
prev parent reply other threads:[~2023-05-18 23:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-15 2:36 Yahu Gao
2023-05-18 23:17 ` Damien Le Moal [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=ce4ee43c-8acd-6ad8-3a18-bf4bdfe48f9c@kernel.org \
--to=dlemoal@kernel.org \
--cc=gaoyh12@lenovo.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yahu.gao@outlook.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
all inboxes | Powered by JetHome®