Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Alexandre Courbot <gnurou@gmail.com>
Cc: Huacai Chen <chenhc@lemote.com>,
	"Steven J. Hill" <Steven.Hill@imgtec.com>,
	linux-mips <linux-mips@linux-mips.org>,
	Fuxin Zhang <zhangfx@lemote.com>,
	Zhangjin Wu <wuzhangjin@gmail.com>,
	"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>
Subject: Re: [PATCH V8 3/8] MIPS: Cleanup Loongson-2F's gpio driver
Date: Wed, 25 Mar 2015 19:09:27 +0100	[thread overview]
Message-ID: <20150325180927.GI1385@linux-mips.org> (raw)
In-Reply-To: <CAAVeFuLF7tHgqXbX1MAikM67DwSu729eG0JcBiipSAG=AeBfOQ@mail.gmail.com>

On Wed, Mar 25, 2015 at 11:19:01AM +0900, Alexandre Courbot wrote:

> On Wed, Mar 25, 2015 at 10:15 AM, Huacai Chen <chenhc@lemote.com> wrote:
> > I think these three patches can go to GPIO tree, because it has no
> > relationship with others in this series.
> 
> In that case we would need a ack from the MIPS maintainers to move the
> code into drivers/gpio/.

Yes, please.  For all three patches:

Acked-by: Ralf Baechle <ralf@linux-mips.org>

  Ralf

  parent reply	other threads:[~2015-03-25 18:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-13  2:26 [PATCH V8 3/8] MIPS: Cleanup Loongson-2F's gpio driver Huacai Chen
2015-03-13  2:26 ` [PATCH V8 4/8] MIPS: Move Loongson GPIO driver to drivers/gpio Huacai Chen
2015-03-13  2:26   ` Huacai Chen
2015-03-13  2:26 ` [PATCH V8 5/8] GPIO: Add Loongson-3A/3B GPIO driver support Huacai Chen
2015-03-23  6:29 ` [PATCH V8 3/8] MIPS: Cleanup Loongson-2F's gpio driver Alexandre Courbot
2015-03-25  1:15   ` Huacai Chen
2015-03-25  2:19     ` Alexandre Courbot
2015-03-25  3:12       ` Huacai Chen
2015-03-25 18:09       ` Ralf Baechle [this message]
2015-03-26  2:12         ` Alexandre Courbot

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=20150325180927.GI1385@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=Steven.Hill@imgtec.com \
    --cc=chenhc@lemote.com \
    --cc=gnurou@gmail.com \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=wuzhangjin@gmail.com \
    --cc=zhangfx@lemote.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