From: Bjorn Helgaas <helgaas@kernel.org>
To: Lukas Wunner <lukas@wunner.de>
Cc: Stuart Hayes <stuart.w.hayes@gmail.com>,
Austin Bolen <austin_bolen@dell.com>,
keith.busch@intel.com, Alexandru Gagniuc <mr.nuke.me@gmail.com>,
"Rafael J . Wysocki" <rafael.j.wysocki@intel.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
Sinan Kaya <okaya@kernel.org>,
Oza Pawandeep <poza@codeaurora.org>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
Enzo Matsumiya <ematsumiya@suse.de>
Subject: Re: [PATCH v2] PCI: pciehp: Make sure pciehp_isr clears interrupt events
Date: Mon, 10 Feb 2020 17:21:18 -0600 [thread overview]
Message-ID: <20200210232118.GA82108@google.com> (raw)
In-Reply-To: <20200209125543.k7u5y6omptbpmwo6@wunner.de>
On Sun, Feb 09, 2020 at 01:55:43PM +0100, Lukas Wunner wrote:
> On Tue, Jan 28, 2020 at 06:51:51PM -0600, Bjorn Helgaas wrote:
> > I see that Lukas took a look at this earlier; I'd really like to have
> > his reviewed-by, since he's the expert on this code.
>
> Hm, should we add an entry for pciehp to MAINTAINERS and list me as R: or M:?
That'd be great. I would certainly apply a patch like that, but I don't
want to presume by generating it myself.
Bjorn
prev parent reply other threads:[~2020-02-10 23:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-20 22:20 [PATCH v2] PCI: pciehp: Make sure pciehp_isr clears interrupt events Stuart Hayes
2020-01-20 16:10 ` Stuart Hayes
2020-01-28 21:51 ` Enzo Matsumiya
2020-01-29 0:51 ` Bjorn Helgaas
2020-01-29 21:55 ` Stuart Hayes
2020-02-09 13:08 ` Lukas Wunner
2020-02-09 12:55 ` Lukas Wunner
2020-02-10 23:21 ` Bjorn Helgaas [this message]
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=20200210232118.GA82108@google.com \
--to=helgaas@kernel.org \
--cc=andy.shevchenko@gmail.com \
--cc=austin_bolen@dell.com \
--cc=ematsumiya@suse.de \
--cc=keith.busch@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=mika.westerberg@linux.intel.com \
--cc=mr.nuke.me@gmail.com \
--cc=okaya@kernel.org \
--cc=poza@codeaurora.org \
--cc=rafael.j.wysocki@intel.com \
--cc=stuart.w.hayes@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).