linux-kernel - Re: [RFC PATCH 3/4] PLATFORM: Introduce async platform

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: <20110313174811.GA11504@kroah.com>
Date:	Sun, 13 Mar 2011 10:48:11 -0700
From:	Greg KH <greg@...ah.com>
To:	andy.green@...aro.org
Cc:	"Rafael J. Wysocki" <rjw@...k.pl>, linux-usb@...r.kernel.org,
	linux-kernel@...r.kernel.org, patches@...aro.org
Subject: Re: [RFC PATCH 3/4] PLATFORM: Introduce async platform_data attach
 api

On Sun, Mar 13, 2011 at 05:13:31PM +0000, Andy Green wrote:
> So when there's a bit more of Device Tree in evidence, are you going
> to accept Device-tree based patches in usbnet etc along these lines,
> or does that trigger the "do it in userspace" response, in which
> case we are both wasting each others' time continuing to discuss
> this at all?

As mentioned numerous times before, network naming stuff happens in
userspace, not in the kernel, so no matter what infrastructure is added,
insisting on naming the network device 'eth0' is not going to happen
within the kernel.  Please use the tools we have today to do this with
no kernel changes.

As for other changes, it all depends on what you need to accomplish,
right?  Those will be gladly reviewed on a case-by-case basis.

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/