From: Sergey Shtylyov <s.shtylyov@omp.ru>
To: Damien Le Moal <damien.lemoal@opensource.wdc.com>,
Sergei Shtylyov <sergei.shtylyov@gmail.com>,
<linux-ide@vger.kernel.org>
Subject: Re: [PATCH] ata: libata-transport: fix {dma|pio|xfer}_mode sysfs files
Date: Wed, 8 Jun 2022 20:13:55 +0300 [thread overview]
Message-ID: <82c8076a-444c-e2d2-99d4-b93f97c47709@omp.ru> (raw)
In-Reply-To: <12518fe8-f286-fe20-089b-5055c32312b7@opensource.wdc.com>
On 6/8/22 1:17 PM, Damien Le Moal wrote:
[...]
>>>>>>>> The {dma|pio|xfer}_mode sysfs files are incorrectly handled by the
>>>>>>>> ata_bitfield_name_match() macro which leads to reading such kind of
>>>>>>>> nonsense from them:
>>>>>>>>
>>>>>>>> $ cat /sys/class/ata_device/dev3.0/pio_mode
>>>>>>>> XFER_UDMA_7, XFER_UDMA_6, XFER_UDMA_5, XFER_UDMA_4, XFER_MW_DMA_4,
>>>>>>>> XFER_PIO_6, XFER_PIO_5, XFER_PIO_4, XFER_PIO_3, XFER_PIO_2, XFER_PIO_1,
>>>>>>>> XFER_PIO_0
>>>>>>>>
>>>>>>>> Using the correct ata_bitfield_name_search() macro fixes that:
>>>>>>>>
>>>>>>>> $ cat /sys/class/ata_device/dev3.0/pio_mode
>>>>>>>> XFER_PIO_4
>>>>>>>
>>>>>>> Looks good, but Documentation/ABI/testing/sysfs-ata says:
>>>>>>
>>>>>> Completely forgot that the sysfs files are documented as ABIs... :-(
>>>>>> Hm, shouldn't that file be added to the libata's entry in MAINTAINERS?
>>>>
>>>> So what's your opinion on that idea?
>>
>> ???
>
> Yep, it looks like other subsystems have their doc files listed there. So
OK, you've finally replied, thanks. :-)
> we can add them. Will you send a patch for that ?
Yes, I'll try to...
>>> OK. Then let's do code and doc fixes in one patch, not 2.
>>
>> Doh! Just when I did 2 patches... :-/
>
> Sorry. I replied a little late. Just squash the patches :)
Squashing diffs is simple, the main issue lies in merging the change logs...
MBR, Sergey
prev parent reply other threads:[~2022-06-08 17:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-04 20:53 [PATCH] ata: libata-transport: fix {dma|pio|xfer}_mode sysfs files Sergey Shtylyov
2022-06-06 2:42 ` Damien Le Moal
2022-06-06 20:38 ` Sergey Shtylyov
2022-06-07 0:37 ` Damien Le Moal
2022-06-07 9:49 ` Sergei Shtylyov
2022-06-08 3:14 ` Damien Le Moal
2022-06-08 10:09 ` Sergey Shtylyov
2022-06-08 10:17 ` Damien Le Moal
2022-06-08 17:13 ` Sergey Shtylyov [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=82c8076a-444c-e2d2-99d4-b93f97c47709@omp.ru \
--to=s.shtylyov@omp.ru \
--cc=damien.lemoal@opensource.wdc.com \
--cc=linux-ide@vger.kernel.org \
--cc=sergei.shtylyov@gmail.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