public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org, linux-input@vger.kernel.org
Subject: Re: [git pull] Input updates for 3.5-rc0
Date: Fri, 25 May 2012 10:39:17 +0900	[thread overview]
Message-ID: <20120525013917.GA22260@kroah.com> (raw)
In-Reply-To: <CA+55aFxYQQRpw0CDJn8bRLQJ2EYNhxf4Ra6=Hd9hOw=1q11pXA@mail.gmail.com>

On Thu, May 24, 2012 at 03:05:09PM -0700, Linus Torvalds wrote:
> On Thu, May 24, 2012 at 3:01 PM, Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
> >
> > I'm open to ideas on what to change it to.  A full sysfs path?
> 
> A full sysfs path really looks pretty ugly, partly because we'd have
> to really change all our naming (look at PCI devices now: they end up
> looking like
> 
>     pci0000:00/0000:00:1a.0
> 
> where that "0000:00" is duplicated because we wanted to make
> dev_name() look nice).
> 
> I think Dmitry's idea to stop when we hit the actual "physical" device
> might just work in practice. So we'd show the dev_name() of the actual
> piece of hardware, and then perhaps one or two "layering" details on
> top of it. And it wouldn't change anything for the current common case
> where people tend to pass in the physical device as-is.

Ok, the "trick" is going to be to figure out where the "physical" device
is in the parent chain (look at the scsi craziness for an example of
that.)

I'm on the road for the next week or so, with lots of international
plane rides with time to kill, so I'll try to figure something out on
them and post it.

thanks,

greg k-h

  reply	other threads:[~2012-05-25  1:39 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-24  8:32 [git pull] Input updates for 3.5-rc0 Dmitry Torokhov
2012-05-24 17:33 ` Linus Torvalds
2012-05-24 18:01   ` Dmitry Torokhov
2012-05-24 18:21     ` Linus Torvalds
2012-05-24 19:58       ` Dmitry Torokhov
2012-05-24 20:11         ` Linus Torvalds
2012-05-24 20:36           ` Dmitry Torokhov
2012-05-24 20:48             ` Linus Torvalds
2012-05-24 20:59               ` Dmitry Torokhov
2012-05-24 21:07                 ` Linus Torvalds
2012-05-24 21:38                   ` Dmitry Torokhov
2012-05-24 21:56                     ` Linus Torvalds
2012-05-24 21:44                   ` Linus Torvalds
2012-05-24 21:56                     ` Dmitry Torokhov
2012-05-24 21:59                       ` Linus Torvalds
2012-05-24 22:01                     ` Greg Kroah-Hartman
2012-05-24 22:05                       ` Linus Torvalds
2012-05-25  1:39                         ` Greg Kroah-Hartman [this message]
2012-05-25 19:05         ` Mark Lord
2012-05-24 21:26   ` Greg Kroah-Hartman

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=20120525013917.GA22260@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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