From: Greg KH <gregkh@linuxfoundation.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Weijie Gao <hackpascal@gmail.com>,
"open list:STAGING SUBSYSTEM" <devel@driverdev.osuosl.org>,
Jason Yan <yanaijie@huawei.com>
Subject: Re: [PATCH] staging: mt7621-pinctrl: stop using the deprecated 'pinctrl_add_gpio_range'
Date: Mon, 7 Dec 2020 16:50:31 +0100 [thread overview]
Message-ID: <X85PR+MHeoKm2b6b@kroah.com> (raw)
In-Reply-To: <CACRpkdafXZJ5W9Z0LJv3p7htP12o2mULgHhFa8kmnT+LWJhh0A@mail.gmail.com>
On Mon, Dec 07, 2020 at 04:40:06PM +0100, Linus Walleij wrote:
> On Mon, Dec 7, 2020 at 2:57 PM Sergio Paracuellos
> <sergio.paracuellos@gmail.com> wrote:
> > On Mon, Dec 7, 2020 at 2:05 PM Linus Walleij <linus.walleij@linaro.org> wrote:
>
> > > After this I think the driver looks good and can graduate from staging.
> > > Can you send a patch to move this to drivers/pinctrl next
> > >
> > > I think drivers/pinctrl/pinctrl-rt2880.c since we don't expect a lot
> > > more of them.
> >
> > Perfect, let me write the bindings yaml file and send the patch moving this.
> >
> > What git tree do you prefer the patch to be rebased onto?
>
> I suppose Gregs since he has some changes to it that it need to
> be based on. After v5.11-rc1 it could be the pinctrl tree as well.
> I don't know if Greg has a favourite way to de-stage drivers?
It all depends on what the subsystem maintainer wants to do.
Sometimes we just do a "add a new driver to the real spot" that goes
through the subsystem tree, and when that is accepted, I delete the
driver in the staging tree. This is most often in networking.
Or you can wait until -rc1 and do a move in your tree, or just tell me
to do the move in my tree with an ack, and I can handle it all.
Whatever is easier for you is fine with me, I'm flexible :)
thanks,
greg k-h
_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
next prev parent reply other threads:[~2020-12-07 15:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-06 10:53 [PATCH] staging: mt7621-pinctrl: stop using the deprecated 'pinctrl_add_gpio_range' Sergio Paracuellos
2020-12-07 13:05 ` Linus Walleij
2020-12-07 13:57 ` Sergio Paracuellos
2020-12-07 15:40 ` Linus Walleij
2020-12-07 15:50 ` Greg KH [this message]
2020-12-07 21:43 ` Linus Walleij
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=X85PR+MHeoKm2b6b@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=devel@driverdev.osuosl.org \
--cc=hackpascal@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=yanaijie@huawei.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).