From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH v1 2/2] gpiolib: Introduce gpio_device_get() and gpio_device_put()
Date: Tue, 29 Nov 2022 16:47:45 +0200 [thread overview]
Message-ID: <Y4YbkUX+bTM5ZEGg@smile.fi.intel.com> (raw)
In-Reply-To: <CAMRc=Mf14Q7_gMXaK+hZ8PdV2U5GiL97QRc3SGKLPqmEuSyDxA@mail.gmail.com>
On Tue, Nov 29, 2022 at 02:54:10PM +0100, Bartosz Golaszewski wrote:
> On Fri, Nov 25, 2022 at 7:11 PM Andy Shevchenko
> <andriy.shevchenko@linux.intel.com> wrote:
> >
> > Introduce gpio_device_get() and gpio_device_put() helpers
> > and convert existing users.
> This doesn't apply to my for-next branch, can you rebase and resend
> (just this one, the other is applied).
The problem is that you don't merge or cherry-pick fixes into your
for-next branch and they are getting diverged.
In PDx86 subsystem we decided to cherry-pick the fixes into for-next.
Some other subsystems are doing back-merges (but I remember that Linus
T. complained about back merges, although I dunno if it's still
the case). Some subsystems merges their fixes into for-next, dunno
if it's the best practice either.
That said, this can be submitted after v6.2-rc1 is out.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2022-11-29 14:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-25 18:11 [PATCH v1 1/2] gpiolib: Provide to_gpio_device() helper Andy Shevchenko
2022-11-25 18:11 ` [PATCH v1 2/2] gpiolib: Introduce gpio_device_get() and gpio_device_put() Andy Shevchenko
2022-11-28 20:27 ` Linus Walleij
2022-11-29 13:54 ` Bartosz Golaszewski
2022-11-29 14:47 ` Andy Shevchenko [this message]
2022-11-29 15:49 ` Bartosz Golaszewski
2022-11-29 16:21 ` Andy Shevchenko
2022-11-29 16:48 ` Andy Shevchenko
2022-12-03 22:19 ` Linus Walleij
2022-11-28 18:04 ` [PATCH v1 1/2] gpiolib: Provide to_gpio_device() helper Bartosz Golaszewski
2022-11-28 19:01 ` Andy Shevchenko
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=Y4YbkUX+bTM5ZEGg@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=brgl@bgdev.pl \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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.