From: Damien Le Moal <damien.lemoal@opensource.wdc.com>
To: Sergey Shtylyov <s.shtylyov@omp.ru>, linux-ide@vger.kernel.org
Subject: Re: [PATCH] ata: pata_hpt37x: merge mode setting methods
Date: Thu, 17 Feb 2022 19:57:36 +0900 [thread overview]
Message-ID: <101340fd-4215-481b-747b-424f9116111f@opensource.wdc.com> (raw)
In-Reply-To: <dbee2241-c540-7f52-1314-9054db292580@omp.ru>
On 2/17/22 18:49, Sergey Shtylyov wrote:
> On 2/16/22 2:29 PM, Damien Le Moal wrote:
>
>>> After commit e0afcf140e6e ("ata: pata_hpt37x: disable fast interrupts in
>>> prereset() method") HPT370's and HPT372+'s PIO/DMA mode setting functions
>>> have become identical -- merge them.
>>>
>>> Signed-off-by: Sergey Shtylyov <s.shtylyov@omp.ru>
>>>
>>> ---
>>> This patch is against the 'for-next' branch of Damien Le Moal's 'libata.git'
>>> repo.
>>>
>>> drivers/ata/pata_hpt37x.c | 71 +++++++---------------------------------------
>>> 1 file changed, 11 insertions(+), 60 deletions(-)
>>>
>>> Index: libata/drivers/ata/pata_hpt37x.c
>>> ===================================================================
>>> --- libata.orig/drivers/ata/pata_hpt37x.c
>>> +++ libata/drivers/ata/pata_hpt37x.c
> [...]
>>> @@ -604,8 +556,7 @@ static struct ata_port_operations hpt370
>>> };
>>>
>>> /*
>>> - * Configuration for HPT371 and HPT302. Slightly different PIO and DMA
>>> - * mode setting functionality.
>>> + * Configuration for HPT371 and HPT302.
>>
>> Shouldn't this be HPT372 ?
>
> No, HPT372 ops are situated below -- they inherit from these.
Yep. Got it (checked the code :)). All good.
>
> [...]
>
> MBR, Sergey
--
Damien Le Moal
Western Digital Research
next prev parent reply other threads:[~2022-02-17 10:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-16 11:24 [PATCH] ata: pata_hpt37x: merge mode setting methods Sergey Shtylyov
2022-02-16 11:29 ` Damien Le Moal
2022-02-17 9:49 ` Sergey Shtylyov
2022-02-17 10:57 ` Damien Le Moal [this message]
2022-02-18 9:35 ` Sergey Shtylyov
2022-02-18 10:15 ` Sergey Shtylyov
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=101340fd-4215-481b-747b-424f9116111f@opensource.wdc.com \
--to=damien.lemoal@opensource.wdc.com \
--cc=linux-ide@vger.kernel.org \
--cc=s.shtylyov@omp.ru \
/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