All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: Damien Le Moal <damien.lemoal@opensource.wdc.com>,
	Damien LeMoal <damien.lemoal@wdc.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: [RFC PATCH] libata: sysfs naming option
Date: Wed, 5 Jan 2022 08:41:29 +0100	[thread overview]
Message-ID: <8cc29e34-2d26-5976-9176-dbeac8d602b3@suse.de> (raw)
In-Reply-To: <e48f13f0-f79a-e8a9-d8c2-cf53657d8072@opensource.wdc.com>

On 1/5/22 07:18, Damien Le Moal wrote:
> On 1/3/22 18:09, Hannes Reinecke wrote:
>> This patch adds a config option ATA_SYSFS_NAMING to align the libata
>> device names in sysfs with those in the kernel message log.
>> It adds a new dummy bus 'ata', which collects all ata device objects
>> like ata_port, ata_link, and ata_dev, and adds an 'ata' prefix to the
>> message log.
>> For consistency the 'ata_dev' name has been changed from 'ata' to 'dev';
>> as this induces a sysfs change the config option is disabled per default.
>>
>> Patch is relative to the 'for-5.17-logging' branch from Damien.
> 
> FYI, I queued the logging series in for-5.17, minus this patch.
> Everything is in for-next too to check that nothing is broken.
> 
> For this patch, as I commented, I think we can keep a backward
> compatible naming using sysfs symlinks. But I am not entirely sure if
> that can work with port-multiplier setups. Let's work on that for the
> next cycle ?
> 
Well, I'm not terribly happy about the current port multiplier 
implementation, either.
Currently they are named 'ataX.Y.0', making them the only ata objects 
with three levels. Personally I would take the PATA master/slave thingie 
as an example, and just increase the last number (such that we would 
have ata1.0, ata1.1, ata1.2 etc).
Reasoning here is that PMP is pretty much an SATA thing, and 'slave' 
drives is a PATA thing. So they'll never clash.

As for the 'ataX.Y' link; that'll require even more sysfs trickery.
Let's see if I can come up with something.
So yeah, let's hold off the patch for now.

First I need to get a PMP cable to test things out :-)

Cheers,

Hannes
-- 
Dr. Hannes Reinecke                Kernel Storage Architect
hare@suse.de                              +49 911 74053 688
SUSE Software Solutions GmbH, Maxfeldstr. 5, 90409 Nürnberg
HRB 36809 (AG Nürnberg), Geschäftsführer: Felix Imendörffer

  reply	other threads:[~2022-01-05  7:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-03  9:09 [RFC PATCH] libata: sysfs naming option Hannes Reinecke
2022-01-04  8:26 ` Damien Le Moal
2022-01-05  6:18 ` Damien Le Moal
2022-01-05  7:41   ` Hannes Reinecke [this message]
2022-01-05  7:58     ` 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=8cc29e34-2d26-5976-9176-dbeac8d602b3@suse.de \
    --to=hare@suse.de \
    --cc=damien.lemoal@opensource.wdc.com \
    --cc=damien.lemoal@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.