From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Andrew Vasquez <andrew.vasquez@qlogic.com>
Cc: James Bottomley <james.bottomley@steeleye.com>,
Greg Kroah-Hartman <greg@kroah.com>,
linux-pci@atrey.karlin.mff.cuni.cz, linux-kernel@vger.kernel.org,
ink@jurassic.park.msu.ru, Alan Cox <alan@redhat.com>,
james.smart@emulex.com, linux-driver@qlogic.com,
Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Subject: Re: [PATCH 2/3] pci: Remove users of pci_enable_device_bars()
Date: Tue, 08 Jan 2008 07:48:27 +1100 [thread overview]
Message-ID: <1199738907.6734.11.camel@pasglop> (raw)
In-Reply-To: <20080107194225.GE13518@plap3.qlogic.org>
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.
Cheers,
Ben.
next prev parent reply other threads:[~2008-01-07 20:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-20 4:28 [PATCH 2/3] pci: Remove users of pci_enable_device_bars() Benjamin Herrenschmidt
2007-12-21 2:59 ` patch pci-remove-users-of-pci_enable_device_bars.patch added to gregkh-2.6 tree gregkh
2008-01-07 19:42 ` [PATCH 2/3] pci: Remove users of pci_enable_device_bars() Andrew Vasquez
2008-01-07 20:48 ` Benjamin Herrenschmidt [this message]
2008-02-01 0:14 ` Andrew Vasquez
2008-02-01 5:08 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1199738907.6734.11.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=alan@redhat.com \
--cc=andrew.vasquez@qlogic.com \
--cc=bzolnier@gmail.com \
--cc=greg@kroah.com \
--cc=ink@jurassic.park.msu.ru \
--cc=james.bottomley@steeleye.com \
--cc=james.smart@emulex.com \
--cc=linux-driver@qlogic.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.