linux-kernel - Re: [git pull] Input updates for 3.5-rc0

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20120525013917.GA22260@kroah.com>
Date:	Fri, 25 May 2012 10:39:17 +0900
From:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Dmitry Torokhov <dmitry.torokhov@...il.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, linux-input@...r.kernel.org
Subject: Re: [git pull] Input updates for 3.5-rc0

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@...uxfoundation.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/