From: Ralf Baechle <ralf@linux-mips.org>
To: Paul Walmsley <paul@pwsan.com>
Cc: "Rafał Miłecki" <zajec5@gmail.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"linux-mips@linux-mips.org" <linux-mips@linux-mips.org>,
"Hauke Mehrtens" <hauke@hauke-m.de>,
"Kumar Gala" <galak@codeaurora.org>,
"Olof Johansson" <olof@lixom.net>,
"Arnd Bergmann" <arnd@arndb.de>,
"Sandeep Nair" <sandeep_n@ti.com>,
linux-soc@vger.kernel.org,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V3] MIPS: BCM47XX: Move NVRAM driver to the drivers/soc/
Date: Fri, 28 Nov 2014 18:16:39 +0100 [thread overview]
Message-ID: <20141128171639.GC30648@linux-mips.org> (raw)
In-Reply-To: <alpine.DEB.2.02.1411281659190.1406@utopia.booyaka.com>
On Fri, Nov 28, 2014 at 05:07:12PM +0000, Paul Walmsley wrote:
> If I were in your shoes, I would suggest either
>
> 1. asking Ralf to merge your patches that touch drivers/firmware, since
> he'll also presumably be merging the parts that touch arch/mips
>
> or
>
> 2. asking Greg KH to merge those patches
>
> And of course it would not hurt to collect some Reviewed-By:s from other
> folks. (See below...)
I surely can carry this patch.
Ralf
next prev parent reply other threads:[~2014-11-28 17:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1416736241-12723-1-git-send-email-zajec5@gmail.com>
[not found] ` <1416778509-31502-1-git-send-email-zajec5@gmail.com>
[not found] ` <alpine.DEB.2.02.1411240910100.16047@utopia.booyaka.com>
[not found] ` <CACna6rxwwn5_e86278TAiOFZ3sVu_Exfm2x94vN2KiTJfsFujQ@mail.gmail.com>
[not found] ` <alpine.DEB.2.02.1411251407290.16047@utopia.booyaka.com>
[not found] ` <CACna6rxj8=V8me1_L8SxhV3=kgYRyKeBHkxShSMZa4kbcHimLg@mail.gmail.com>
2014-11-27 19:56 ` [PATCH V3] MIPS: BCM47XX: Move NVRAM driver to the drivers/soc/ Paul Walmsley
2014-11-27 22:36 ` Rafał Miłecki
2014-11-28 17:07 ` Paul Walmsley
2014-11-28 17:16 ` Ralf Baechle [this message]
2014-12-04 6:43 ` Paul Walmsley
2014-12-04 7:28 ` Rafał Miłecki
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=20141128171639.GC30648@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=arnd@arndb.de \
--cc=galak@codeaurora.org \
--cc=gregkh@linuxfoundation.org \
--cc=hauke@hauke-m.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-soc@vger.kernel.org \
--cc=olof@lixom.net \
--cc=paul@pwsan.com \
--cc=sandeep_n@ti.com \
--cc=zajec5@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