From: Linus Walleij <linus.walleij@linaro.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Bartosz Golaszewski <brgl@bgdev.pl>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 2/2] gpiolib: Introduce gpio_device_get() and gpio_device_put()
Date: Sat, 3 Dec 2022 23:19:59 +0100 [thread overview]
Message-ID: <CACRpkdYGP4GCHoo_wss4to9Mx-koakh_D9Z0NX+2m0X-o31dpw@mail.gmail.com> (raw)
In-Reply-To: <Y4YbkUX+bTM5ZEGg@smile.fi.intel.com>
On Tue, Nov 29, 2022 at 3:47 PM Andy Shevchenko
<andriy.shevchenko@linux.intel.com> wrote:
> 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.
I usually (A) let it conflict (Torvalds will solve) if it is small and
Rothwell fixed it up in next (B) back-merge some -rcN if is is big
and annoying or as last resort (C) apply the patch to for-next
(git will cope, but not elegant).
Yours,
Linus Walleij
next prev parent reply other threads:[~2022-12-03 22:20 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
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 [this message]
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=CACRpkdYGP4GCHoo_wss4to9Mx-koakh_D9Z0NX+2m0X-o31dpw@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=brgl@bgdev.pl \
--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 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).