linux-kernel - Re: [PATCH] PCI: make pci_name use dev

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] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 3 Jul 2008 13:33:56 -0700
From:	Jesse Barnes <jbarnes@...tuousgeek.org>
To:	Greg KH <greg@...ah.com>
Cc:	Greg KH <gregkh@...e.de>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Kay Sievers <kay.sievers@...y.org>,
	linux-kernel@...r.kernel.org, linux-pci@...r.kernel.org,
	davem@...emloft.net
Subject: Re: [PATCH] PCI: make pci_name use dev_name

On Thursday, July 03, 2008 1:24 pm Greg KH wrote:
> On Thu, Jul 03, 2008 at 12:37:30PM -0700, Jesse Barnes wrote:
> > On Wednesday, July 02, 2008 1:22 pm Greg KH wrote:
> > > On Wed, Jul 02, 2008 at 09:04:22AM -0700, Greg KH wrote:
> > > > Well, it's only used in 837 different places, so it might take me a
> > > > few hours to ensure I catch all the usages :(
> > >
> > > Ok, here are 4 patches that fix the few places that this pci change
> > > caused problems.
> > >
> > > Jesse, do you want to add these to your tree?  I can take the single
> > > USB one if you want, or you can take all 4, it's fine with me.
> >
> > I'd rather just take the PCI patch (which I'm doing now).  The other
> > stuff can come in through the appropriate tree.
>
> Fair enough, I'll make sure they don't get dropped.

Cool thanks.  I assume you'll only push the pci_name change once all or most 
of the compiler warnings have been fixed up?

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