linux-kernel - Re: hid: struct device - replace bus_id with dev_name(), dev_set

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: <ac3eb2510810301616n271102fcred30bc1eef6a8dba@mail.gmail.com>
Date:	Fri, 31 Oct 2008 00:16:01 +0100
From:	"Kay Sievers" <kay.sievers@...y.org>
To:	"Jiri Kosina" <jkosina@...e.cz>
Cc:	"Jiri Slaby" <jirislaby@...il.com>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	"Greg KH" <greg@...ah.com>
Subject: Re: hid: struct device - replace bus_id with dev_name(), dev_set_name()

On Fri, Oct 31, 2008 at 00:10, Jiri Kosina <jkosina@...e.cz> wrote:
> On Thu, 30 Oct 2008, Kay Sievers wrote:
>
>> > > switch over to the new api, which will remove the 20 bytes array
>> > > and does no longer have a size limitation.
>> > Cool!
>> > Could you left the comment above to remind us about removing this ugly hack
>> > later when the new non-limited api will be used?
>> Sure!
>> From: Kay Sievers <kay.sievers@...y.org>
>> Subject: hid: struct device - replace bus_id with dev_name(), dev_set_name()
>
> Hi Kay,
>
> thanks for this cleanup. What is the timeframe the bus_id will be removed
> from struct device?

Hmm, not sure. We will put the remaining pieces into Greg's tree, wait
for -next to carry most of it, and convert the rest. Maybe we can do
it for the next kernel, but we might get sidetracked again, and it
might take longer.

Thanks,
Kay
--
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/