mirror of https://lore.kernel.org/lkml/
 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 11:36:45 -0800 (PST)	[thread overview]
Message-ID: <20081107.113645.46315945.davem@davemloft.net> (raw)
In-Reply-To: <ac3eb2510811070158i40ea64adq93511426e5c86ab7@mail.gmail.com>

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

> Yeah, but the thing is, that _I_ don't want to remove any checks or
> limits from subsystem code. While touching hundreds of files the last
> days, there are several instances which could break if I remove any
> limits. And most of the stuff I can not even compile.
> 
> I can let the BUS_ID_SIZE in the header, but I rather have the people
> who understand the code to change the behavior.

That's right.  My main point is that if you don't keep the key
in there to grep for, nobody is likely to make the cleanups.
Nobody is going to grep for "20".

> Anyway, care to apply the first hunk, and skip the "20" part? I'll
> remove the "20" part from the net/ patch too and resend it.

Sure.

  reply	other threads:[~2008-11-07 19:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-07  0:43 Kay Sievers
2008-11-07  7:35 ` David Miller
2008-11-07  8:33   ` Kay Sievers
2008-11-07  9:38     ` David Miller
2008-11-07  9:58       ` Kay Sievers
2008-11-07 19:36         ` David Miller [this message]
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.113645.46315945.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

all inboxes | Powered by JetHome®