From: Damien Le Moal <damien.lemoal@opensource.wdc.com>
To: Sergey Shtylyov <s.shtylyov@omp.ru>, linux-ide@vger.kernel.org
Subject: Re: [PATCH 0/2] Refactor the accessors for the ATA device control and alternate status registers
Date: Wed, 16 Feb 2022 16:20:12 +0900 [thread overview]
Message-ID: <e6f18dc7-35c8-1792-28c6-dc8b15181b71@opensource.wdc.com> (raw)
In-Reply-To: <20220213151032.4694-1-s.shtylyov@omp.ru>
On 2/14/22 00:10, Sergey Shtylyov wrote:
> Here are 2 patches against the 'for-next' branch of Damien Le Moal's
> 'libata.git' repo. Refactor the accessors for the device control and
> alternate status registers moving the prerequeiste checks done now around
> the calls into the functionas themselves and make them return a 'bool'
> result indicating if a respective register exists or not...
>
> Sergey Shtylyov (2):
> ata: libata-sff: refactor ata_sff_set_devctl()
> ata: libata-sff: refactor ata_sff_altstatus()
>
> drivers/ata/libata-sff.c | 86 +++++++++++++++++++++-------------------
> 1 file changed, 46 insertions(+), 40 deletions(-)
>
Applied to for-5.18. Thanks !
--
Damien Le Moal
Western Digital Research
next prev parent reply other threads:[~2022-02-16 7:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-13 15:10 [PATCH 0/2] Refactor the accessors for the ATA device control and alternate status registers Sergey Shtylyov
2022-02-13 15:10 ` [PATCH v2 1/2] ata: libata-sff: refactor ata_sff_set_devctl() Sergey Shtylyov
2022-02-13 23:25 ` Damien Le Moal
2022-02-14 8:37 ` Sergey Shtylyov
2022-02-13 15:10 ` [PATCH v2 2/2] ata: libata-sff: refactor ata_sff_altstatus() Sergey Shtylyov
2022-02-17 12:12 ` Dan Carpenter
2022-02-17 16:02 ` Sergey Shtylyov
2022-02-18 22:58 ` Damien Le Moal
2022-02-18 22:59 ` Damien Le Moal
2022-02-16 7:20 ` Damien Le Moal [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-02-13 15:09 [PATCH 0/2] Refactor the accessors for the ATA device control and alternate status registers 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=e6f18dc7-35c8-1792-28c6-dc8b15181b71@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