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] [day] [month] [year] [list]
Message-ID: <20080201050818.GA23207@kroah.com>
Date:	Thu, 31 Jan 2008 21:08:18 -0800
From:	Greg KH <greg@...ah.com>
To:	Andrew Vasquez <andrew.vasquez@...gic.com>
Cc:	James Bottomley <james.bottomley@...eleye.com>,
	Benjamin Herrenschmidt <benh@...nel.crashing.org>,
	linux-pci@...ey.karlin.mff.cuni.cz, linux-kernel@...r.kernel.org,
	ink@...assic.park.msu.ru, Alan Cox <alan@...hat.com>,
	james.smart@...lex.com, linux-driver@...gic.com,
	Bartlomiej Zolnierkiewicz <bzolnier@...il.com>
Subject: Re: [PATCH 2/3] pci: Remove users of pci_enable_device_bars()

On Thu, Jan 31, 2008 at 04:14:45PM -0800, Andrew Vasquez wrote:
> On Tue, 08 Jan 2008, Benjamin Herrenschmidt wrote:
> 
> > On Mon, 2008-01-07 at 11:42 -0800, Andrew Vasquez wrote:
> > > That's fine.  I take it these patches will be funneled via
> > > gregkh/pci-2.6.git.  There's some qla2xxx updates which are queued for
> > > post-2.6.24 consumption in jejb/scsi-misc-2.6.git which don't appear
> > > to have any conflicts.
> > > 
> > > I do though have a series of patches which I'll hold off on submitting
> > > to linux-scsi until these PCI changes are merged, as there's some
> > > minor conflicts merging the three branches.  James B, will that be
> > > fine?
> > > 
> > > The patches themselves appear to be working fine within several of our
> > > test rings.  I hold off on some of the cleanup post-merge time...
> > 
> > Thanks for testing ! They should be queued with Greg indeed.
> 
> Just curious, this patch-set hasn't made it upstream to linux-2.6.git,
> will the work be deferred to 2.6.26??

It's less than one week into the merge window, and people are getting
worried, sheesh :)

Yes, this is queued up to go to Linus, been busy working on other issues
at the moment, don't worry, I'll make the window.  Hopefully get them
all out tomorrow...

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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ