linux-kernel - Re: chris: 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: <20081117225359.GB10377@kroah.com>
Date:	Mon, 17 Nov 2008 14:53:59 -0800
From:	Greg KH <greg@...ah.com>
To:	Jesper Nilsson <Jesper.Nilsson@...s.com>
Cc:	Kay Sievers <kay.sievers@...y.org>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: chris: struct device - replace bus_id with dev_name(),
	dev_set_name()

On Fri, Nov 07, 2008 at 01:01:36PM +0100, Jesper Nilsson wrote:
> On Fri, Nov 07, 2008 at 01:38:40AM +0100, Kay Sievers wrote:
> > This patch is part of a larger patch series which will remove
> > the "char bus_id[20]" name string from struct device. The device
> > name is managed in the kobject anyway, and without any size
> > limitation, and just needlessly copied into "struct device".
> 
> Thanks, but I think that since this driver has been broken a long time
> it is high time to fix it, and I think the fix removes the need for your patch.
> 
> Greg, could you please look this patch over?
> 
> 
> [CRISv32] Fix IOP fw-loader to use platform_device.
> 
> Change IOP fw-loader to use platform_device instead of
> raw device, which should be more correct usage.
> 
> Signed-off-by: Stefan Andersson <stefan.andersson@...s.com>
> Signed-off-by: Jesper Nilsson <jesper.nilsson@...s.com>

Looks sane to me.  Want me to take it through my tree, or will you be
submitting 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/