public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: kay.sievers@vrfy.org
Cc: wli@holomorphy.com, greg@kroah.com, linux-kernel@vger.kernel.org
Subject: Re: sparc: struct device - replace bus_id with dev_name(), dev_set_name()
Date: Fri, 07 Nov 2008 01:38:33 -0800 (PST)	[thread overview]
Message-ID: <20081107.013833.147302570.davem@davemloft.net> (raw)
In-Reply-To: <ac3eb2510811070033m108d8ed5t499c20ee02b2618f@mail.gmail.com>

From: "Kay Sievers" <kay.sievers@vrfy.org>
Date: Fri, 7 Nov 2008 09:33:16 +0100

> On Fri, Nov 7, 2008 at 08:35, David Miller <davem@davemloft.net> wrote:
> > From: Kay Sievers <kay.sievers@vrfy.org>
> > Date: Fri, 07 Nov 2008 01:43:59 +0100
> >
> >> --- a/arch/sparc64/kernel/vio.c
> >> +++ b/arch/sparc64/kernel/vio.c
> >> @@ -224,7 +224,7 @@ static struct vio_dev *vio_create_one(st
> >>       if (!strcmp(type, "domain-services-port"))
> >>               bus_id_name = "ds";
> >>
> >> -     if (strlen(bus_id_name) >= BUS_ID_SIZE - 4) {
> >> +     if (strlen(bus_id_name) >= 20 - 4) {
> >>               printk(KERN_ERR "VIO: bus_id_name [%s] is too long.\n",
> >>                      bus_id_name);
> >>               return NULL;
> >>
> >>
> >
> > But I don't like this.
> >
> > Could you please keep the macro around until everything is converted?
> > Then you can remove the test entirely.
> >
> > Leaving it with just constants there is inviting confusion, no matter
> > how short amount of time it will be there.
> 
> I can add a SPARC_BUS_ID_SIZE, to that file, or in a sparc header, but
> the core will not provide any such value, and have to, go to catch all
> remaining occurrences across the tree. Where should I add it?

You should keep BUS_ID_SIZE in the device.h header or wherever it is
now.

Then it's a simply grep to kill that off and all the references (and
you have to systematically eliminate these no-longer-needed tests
anyways) in one fell swoop.

Otherwise someone will have to grep for "20" (!!) in order to do that
cleanup.

  reply	other threads:[~2008-11-07  9:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-07  0:43 sparc: struct device - replace bus_id with dev_name(), dev_set_name() Kay Sievers
2008-11-07  7:35 ` David Miller
2008-11-07  8:33   ` Kay Sievers
2008-11-07  9:38     ` David Miller [this message]
2008-11-07  9:58       ` Kay Sievers
2008-11-07 19:36         ` David Miller
2009-03-27 12:21       ` Kay Sievers
2009-03-28  0:27         ` David Miller
2009-04-16 16:21           ` Kay Sievers
2009-04-16 22:56             ` David Miller
2009-05-22 11:42               ` Kay Sievers
2009-05-26  9:30                 ` David Miller

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=20081107.013833.147302570.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=greg@kroah.com \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wli@holomorphy.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