linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Sergio Paracuellos <sergio.paracuellos@gmail.com>
Cc: neil@brown.name, linux-gpio@vger.kernel.org,
	linus.walleij@linaro.org, driverdev-devel@linuxdriverproject.org
Subject: Re: [PATCH] staging: mt7621-gpio: move out of staging
Date: Fri, 1 Jun 2018 20:13:47 +0200	[thread overview]
Message-ID: <20180601181347.GA27486@kroah.com> (raw)
In-Reply-To: <1527854570-17200-1-git-send-email-sergio.paracuellos@gmail.com>

On Fri, Jun 01, 2018 at 02:02:50PM +0200, Sergio Paracuellos wrote:
> Move the mt7621-gpio driver out of staging and into mainline
> 
> Signed-off-by: Sergio Paracuellos <sergio.paracuellos@gmail.com>
> ---
>  .../devicetree/bindings/gpio}/mediatek,mt7621-gpio.txt             | 0
>  drivers/gpio/Kconfig                                               | 7 +++++++
>  drivers/gpio/Makefile                                              | 1 +
>  drivers/{staging/mt7621-gpio => gpio}/gpio-mt7621.c                | 0
>  drivers/staging/Kconfig                                            | 2 --
>  drivers/staging/Makefile                                           | 1 -
>  drivers/staging/mt7621-gpio/Kconfig                                | 6 ------
>  drivers/staging/mt7621-gpio/Makefile                               | 3 ---
>  drivers/staging/mt7621-gpio/TODO                                   | 3 ---

I suggest you submit this as a new driver to the gpio maintainer and
developers and then if/when it is merged into that tree, we can then
delete the staging tree version.  That makes it easier for the gpio
developers to review it and makes any cross-tree merge issues go away.

thanks,

greg k-h

  reply	other threads:[~2018-06-01 18:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-01 12:02 [PATCH] staging: mt7621-gpio: move out of staging Sergio Paracuellos
2018-06-01 18:13 ` Greg KH [this message]
2018-06-01 19:02   ` Sergio Paracuellos
2018-06-01 23:30     ` NeilBrown
2018-06-02  7:33       ` Sergio Paracuellos
2018-06-04  9:09 ` Dan Carpenter
2018-06-05 11:19   ` Sergio Paracuellos

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=20180601181347.GA27486@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=driverdev-devel@linuxdriverproject.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=neil@brown.name \
    --cc=sergio.paracuellos@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).