From: Sergey Shtylyov <s.shtylyov@omp.ru>
To: Damien Le Moal <damien.lemoal@opensource.wdc.com>,
<linux-ide@vger.kernel.org>
Subject: [PATCH 0/2] Fix sloppy typing in the fast drain logic
Date: Thu, 16 Jun 2022 23:51:47 +0300 [thread overview]
Message-ID: <20220616205149.16157-1-s.shtylyov@omp.ru> (raw)
Here are 2 patches against the 'for-next' branch of Damien Le Moal's
'libata.git' repo.
The libata's fast drain logic unfortunately boasts of some sloppy typing --
unify it by using *unsigned int* everyhere...
Sergey Shtylyov (2):
ata: libata-eh: fix sloppy result type of ata_eh_nr_in_flight()
ata: make ata_port::fastdrain_cnt *unsigned int*
drivers/ata/libata-eh.c | 8 ++++----
include/linux/libata.h | 2 +-
2 files changed, 5 insertions(+), 5 deletions(-)
--
2.26.3
next reply other threads:[~2022-06-16 20:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-16 20:51 Sergey Shtylyov [this message]
2022-06-16 20:51 ` [PATCH 1/2] ata: libata-eh: fix sloppy result type of ata_eh_nr_in_flight() Sergey Shtylyov
2022-06-17 18:16 ` Sergey Shtylyov
2022-06-19 23:15 ` Damien Le Moal
2022-06-16 20:51 ` [PATCH 2/2] ata: make ata_port::fastdrain_cnt *unsigned int* Sergey Shtylyov
2022-06-17 7:48 ` [PATCH 0/2] Fix sloppy typing in the fast drain logic Damien Le Moal
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=20220616205149.16157-1-s.shtylyov@omp.ru \
--to=s.shtylyov@omp.ru \
--cc=damien.lemoal@opensource.wdc.com \
--cc=linux-ide@vger.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