linux-kernel - Re: [patch 2.6.21-rc5 1/3] parport->dev driver model support

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 for Android: free password hash cracker in your pocket

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

Message-Id: <200703261525.56731.david-b@pacbell.net>
Date:	Mon, 26 Mar 2007 15:25:56 -0700
From:	David Brownell <david-b@...bell.net>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Linux Kernel list <linux-kernel@...r.kernel.org>,
	Jean Delvare <khali@...ux-fr.org>
Subject: Re: [patch 2.6.21-rc5 1/3] parport->dev driver model support

On Monday 26 March 2007 2:59 pm, Andrew Morton wrote:
> On Mon, 26 Mar 2007 09:06:19 -0700
> David Brownell <david-b@...bell.net> wrote:
> 
> > Currently a parport_driver can't get a handle on the device node for the
> > underlying parport (PNPACPI, PCI, etc).  That prevents correct placement
> > of sysfs child nodes, which can affect things like power management.
> > 
> > This patch adds a field to "struct parport" pointing to that device node,
> > and updates non-legacy port drivers to initialize that device pointer.
> > That field replaces the analagous PCI-only support in parport_pc.
> > 
> > Signed-off-by: David Brownell <dbrownell@...rs.sourceforge.net>
> > ---
> > NOTE this depends on an earlier patch to make pnp devices set up DMA,
> > parport is the primary user of legacy i8237 dma infrastructure.
> 
> Confusion reigns.
> 
> To which "earlier patch" do you refer?

The one named "init-dma-masks-in-pnp_dev.patch" in 2.6.21-rc4-mm1 ...

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