mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Eddie James <eajames@linux.ibm.com>
To: Jeremy Kerr <jk@ozlabs.org>, linux-fsi@lists.ozlabs.org
Cc: linux-kernel@vger.kernel.org, alistair@popple.id.au, joel@jms.id.au
Subject: Re: [PATCH] fsi: Add aliased device numbering
Date: Fri, 27 Jan 2023 08:40:57 -0600	[thread overview]
Message-ID: <97f6dc04-8a5f-c518-b804-992c7d46829b@linux.ibm.com> (raw)
In-Reply-To: <8fa108c9dedf884eab6dacaf3e9680b7c66c4202.camel@ozlabs.org>


On 1/26/23 19:03, Jeremy Kerr wrote:
> Hi Eddie,
>
>> The I2C and SPI subsystems can use an aliased name to number the
>> device. Add similar support to the FSI subsystem for any device type.
> Sounds good!
>
> However, the majority of this patch seems to be the change to a (const)
> enum value, which you then convert to a string to generate the
> non-number component of the device name.
>
> Does:
>
>         dev_set_name(&scom->dev, "%s%d", fsi_get_dev_type_name(fsi_dev_scom), didx);
>
> have much of a benefit over:
>
>         dev_set_name(&scom->dev, "scom%d", didx);
>
> ?


Hi Jeremy,

I agree, it's not a benefit but my objective here is to make sure the 
device name is definitely the same as what the alias lookup is looking 
for. Perhaps it doesn't matter so much, and I can drop that part of the 
patch...

Thanks for looking!

Eddie


>
> Cheers,
>
>
> Jeremy

      reply	other threads:[~2023-01-27 14:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-26 22:38 Eddie James
2023-01-27  1:03 ` Jeremy Kerr
2023-01-27 14:40   ` Eddie James [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=97f6dc04-8a5f-c518-b804-992c7d46829b@linux.ibm.com \
    --to=eajames@linux.ibm.com \
    --cc=alistair@popple.id.au \
    --cc=jk@ozlabs.org \
    --cc=joel@jms.id.au \
    --cc=linux-fsi@lists.ozlabs.org \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®