From: poza@codeaurora.org
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Oza Pawandeep <oza.pawandeep@gmail.com>,
Sinan Kaya <okaya@codeaurora.org>,
Keith Busch <keith.busch@intel.com>,
Bjorn Helgaas <bhelgaas@google.com>,
Linux PCI <linux-pci@vger.kernel.org>,
linux-pci-owner@vger.kernel.org
Subject: Re: [PATCH 2/6] PCI/DPC: Leave interrupts enabled while handling event
Date: Wed, 31 Jan 2018 10:53:18 +0530 [thread overview]
Message-ID: <751f22485ba10c4a732831787c4ea2d6@codeaurora.org> (raw)
In-Reply-To: <20180130183046.GG232763@bhelgaas-glaptop.roam.corp.google.com>
On 2018-01-31 00:00, Bjorn Helgaas wrote:
> On Tue, Jan 30, 2018 at 12:04:44PM +0530, poza@codeaurora.org wrote:
>> Bjorn: Can you please help to review my AER/DPC series of patches so
>> that I do not have to keep rebasing and do manual merge ?
>
> They're in the queue and I'll get to them this cycle.
>
> You don't need to rebase them unless you change your patches to
> actually require something from another branch. If there are
> conflicts with other patches that are in-flight, I'll resolve those
> myself.
>
> Since your patches will probably land in the v4.17 merge, it *will* be
> nice if you rebase them when I update the pci/master branch, which
> will probably be to v4.16-rc1. But unless you *depend* on features in
> another branch, it's easiest if you base them on pci/master, which
> generally stays the same throughout the cycle.
>
> Bjorn
sure, will rebase them on top of pci/master.
Regards,
Oza.
next prev parent reply other threads:[~2018-01-31 5:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-29 21:31 [PATCH 1/6] PCI/DPC: Defer all event handling to work queue Keith Busch
2018-01-29 21:31 ` [PATCH 2/6] PCI/DPC: Leave interrupts enabled while handling event Keith Busch
2018-01-30 2:11 ` Sinan Kaya
2018-01-30 6:29 ` Oza Pawandeep
2018-01-30 6:34 ` poza
2018-01-30 6:40 ` poza
2018-01-30 18:17 ` Keith Busch
2018-01-31 5:21 ` poza
2018-01-30 18:30 ` Bjorn Helgaas
2018-01-31 5:23 ` poza [this message]
2018-01-29 21:31 ` [PATCH 3/6] PCI/DPC: Remove rp_pio_status from dpc struct Keith Busch
2018-01-29 21:31 ` [PATCH 4/6] PCI/DPC: Cleanup declarations Keith Busch
2018-01-29 21:31 ` [PATCH 5/6] PCI/DPC: Enable ERR_COR Keith Busch
2018-01-29 21:31 ` [PATCH 6/6] PCI/DPC: Print AER status in DPC event handling Keith Busch
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=751f22485ba10c4a732831787c4ea2d6@codeaurora.org \
--to=poza@codeaurora.org \
--cc=bhelgaas@google.com \
--cc=helgaas@kernel.org \
--cc=keith.busch@intel.com \
--cc=linux-pci-owner@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=okaya@codeaurora.org \
--cc=oza.pawandeep@gmail.com \
/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.