All of lore.kernel.org
 help / color / mirror / Atom feed
From: Huacai Chen <chenhc@lemote.com>
To: Alexandre Courbot <gnurou@gmail.com>
Cc: Ralf Baechle <ralf@linux-mips.org>,
	"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 09:15:33 +0800	[thread overview]
Message-ID: <CAAhV-H5i+ysaJi1=6ftyY_82yGBZnCqpUmCV2ayMVMDFw0uWVQ@mail.gmail.com> (raw)
In-Reply-To: <CAAVeFuLytDZwo-=Q3DSxS7jLWbr4Jgf8BsBr9VGptBBu4SzZZg@mail.gmail.com>

I think these three patches can go to GPIO tree, because it has no
relationship with others in this series.

Huacai

On Mon, Mar 23, 2015 at 2:29 PM, Alexandre Courbot <gnurou@gmail.com> wrote:
> On Fri, Mar 13, 2015 at 11:26 AM, Huacai Chen <chenhc@lemote.com> wrote:
>> This cleanup is prepare to move the driver to drivers/gpio. Custom
>> definitions of gpio_get_value()/gpio_set_value() are dropped.
>
> I suppose this is starting to look ok, at least patches 3, 4 and 5
> which are of interest for GPIO. I wonder which tree they should be
> merged through, MIPS or GPIO? Not seeing the rest of the series, I
> cannot make a suggestion.
>

  reply	other threads:[~2015-03-25  1:15 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 [this message]
2015-03-25  2:19     ` Alexandre Courbot
2015-03-25  3:12       ` Huacai Chen
2015-03-25 18:09       ` Ralf Baechle
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='CAAhV-H5i+ysaJi1=6ftyY_82yGBZnCqpUmCV2ayMVMDFw0uWVQ@mail.gmail.com' \
    --to=chenhc@lemote.com \
    --cc=Steven.Hill@imgtec.com \
    --cc=gnurou@gmail.com \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@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 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.