linux-kernel - Re: [alsa-devel] [PATCH] aoa: remove driver

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: <s5hoctyu6m4.wl%tiwai@suse.de>
Date:	Tue, 12 May 2009 09:23:47 +0200
From:	Takashi Iwai <tiwai@...e.de>
To:	Greg KH <gregkh@...e.de>
Cc:	Roel Kluin <roel.kluin@...il.com>, johannes@...solutions.net,
	linuxppc-dev@...abs.org, alsa-devel@...a-project.org,
	lkml <linux-kernel@...r.kernel.org>
Subject: Re: [alsa-devel] [PATCH] aoa: remove driver_data direct access of	struct device

At Mon, 11 May 2009 23:57:43 -0700,
Greg KH wrote:
> 
> On Tue, May 12, 2009 at 08:40:05AM +0200, Takashi Iwai wrote:
> > At Mon, 11 May 2009 21:54:51 +0200,
> > Roel Kluin wrote:
> > > 
> > > To avoid direct access to the driver_data pointer in struct device, the
> > > functions dev_get_drvdata() and dev_set_drvdata() should be used.
> > > 
> > > Signed-off-by: Roel Kluin <roel.kluin@...il.com>
> > 
> > The same fix has been already in Greg's tree (and thus in linux-next).
> > 
> > Greg, is it OK that I take over your patch to sound git tree?
> 
> Yes, please do, no objection from me at all.

OK, will do.

BTW, should it be pushed to 2.6.30?  If "the near future" you
mentioned in the patch means 2.6.31, it'll be better to merge that fix
now.  Otherwise, I'm going to apply the patch as a 2.6.31 material.


thanks,

Takashi
--
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/