From: Bjorn Helgaas <bhelgaas@google.com>
To: Valentine <valentine.barshak@cogentembedded.com>
Cc: Simon Horman <horms@verge.net.au>,
Jingoo Han <jg1.han@samsung.com>,
Wei Yongjun <weiyj.lk@gmail.com>,
Wei Yongjun <yongjun_wei@trendmicro.com.cn>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
Magnus Damm <magnus.damm@gmail.com>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
linux-sh@vger.kernel.org
Subject: Re: [PATCH] PCI: rcar: fix return value check in rcar_pci_probe()
Date: Fri, 13 Dec 2013 17:00:03 +0000 [thread overview]
Message-ID: <CAErSpo72MYGvg9p2-2YCdvhzK4Mvp6j81P77sQPno34bKZPtuw@mail.gmail.com> (raw)
In-Reply-To: <52AAF85E.80206@cogentembedded.com>
On Fri, Dec 13, 2013 at 5:06 AM, Valentine
<valentine.barshak@cogentembedded.com> wrote:
> On 12/11/2013 06:30 AM, Simon Horman wrote:
>>
>> On Mon, Dec 09, 2013 at 10:46:17AM +0900, Jingoo Han wrote:
>>>
>>> On Sunday, December 08, 2013 7:50 AM, Bjorn Helgaas wrote:
>>>> For drivers/pci/host/*, I normally look for an ack from the responsible
>>>> person, but this patch is trivial enough that I'm fine taking it
>>>> without
>>>> that. But for more significant changes, I don't have any notes about
>>>> who
>>>> should own pci-rcar-gen2.c. Valentine could be a candidate since he
>>>> added
>>>> it in the first place? Or Jingoo?
>
>
> Sorry, I didn't ack since I thought it was not really needed for a trivial
> change like this one that had already been reviewed by Jingoo.
To be honest, I'm just trying to save myself some work by looking for
an ack. I want to have an indication that at least one person besides
the author approves, and if nobody else looks at it, I have to do it
myself :)
>> I will let Valentine volunteer himself if he wants to.
>
>
> I'll try to track the e-mails related to this driver as well.
>
> Not sure if I want myself in the MAINTAINERS though, since it would probably
> mean that "try to" should be changed to "have to" in my statement above.
Fair enough, thanks! Let me know if anything changes here.
Bjorn
prev parent reply other threads:[~2013-12-13 17:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAPgLHd-XTnQXdK7H2uLbGW1ftxNB_nHwzcNCoiCjpXsB5X3HnA@mail.gmail.com>
[not found] ` <20131207225012.GC7901@google.com>
2013-12-09 1:46 ` [PATCH] PCI: rcar: fix return value check in rcar_pci_probe() Jingoo Han
2013-12-11 2:30 ` Simon Horman
2013-12-13 12:06 ` Valentine
2013-12-13 17:00 ` 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=CAErSpo72MYGvg9p2-2YCdvhzK4Mvp6j81P77sQPno34bKZPtuw@mail.gmail.com \
--to=bhelgaas@google.com \
--cc=horms@verge.net.au \
--cc=jg1.han@samsung.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-pci@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=valentine.barshak@cogentembedded.com \
--cc=weiyj.lk@gmail.com \
--cc=yongjun_wei@trendmicro.com.cn \
/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).