From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Bartosz Golaszewski <brgl@bgdev.pl>,
Linus Walleij <linus.walleij@linaro.org>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-acpi@vger.kernel.org
Subject: Re: [PATCH v4 0/6] Add support for software nodes to gpiolib
Date: Wed, 16 Nov 2022 10:08:02 +0200 [thread overview]
Message-ID: <Y3SaYsepJ2sEt2CD@smile.fi.intel.com> (raw)
In-Reply-To: <Y3QedBxErvjc+YHi@google.com>
On Tue, Nov 15, 2022 at 03:19:16PM -0800, Dmitry Torokhov wrote:
> On Tue, Nov 15, 2022 at 11:28:17AM +0100, Bartosz Golaszewski wrote:
> > On Fri, Nov 11, 2022 at 11:19 PM Dmitry Torokhov
> > <dmitry.torokhov@gmail.com> wrote:
...
> > I still had some fuzz when applying, can you for the future rebase on
> > top of the GPIO for-next branch?
>
> OK, I will, but I thought it is feeding into the next tree?
It has ~2-3 days latency usually.
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2022-11-16 8:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-11 22:19 [PATCH v4 0/6] Add support for software nodes to gpiolib Dmitry Torokhov
2022-11-11 22:19 ` [PATCH v4 1/6] gpiolib: of: change of_find_gpio() to accept device node Dmitry Torokhov
2022-11-11 22:19 ` [PATCH v4 2/6] gpiolib: acpi: change acpi_find_gpio() to accept firmware node Dmitry Torokhov
2022-11-11 22:19 ` [PATCH v4 3/6] gpiolib: acpi: teach acpi_find_gpio() to handle data-only nodes Dmitry Torokhov
2022-11-11 22:19 ` [PATCH v4 4/6] gpiolib: acpi: avoid leaking ACPI details into upper gpiolib layers Dmitry Torokhov
2022-11-11 22:19 ` [PATCH v4 5/6] gpiolib: consolidate GPIO lookups Dmitry Torokhov
2022-11-13 13:07 ` Andy Shevchenko
2022-11-15 10:26 ` Bartosz Golaszewski
2022-11-11 22:19 ` [PATCH v4 6/6] gpiolib: add support for software nodes Dmitry Torokhov
2022-11-15 10:28 ` [PATCH v4 0/6] Add support for software nodes to gpiolib Bartosz Golaszewski
2022-11-15 23:19 ` Dmitry Torokhov
2022-11-16 8:08 ` Andy Shevchenko [this message]
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=Y3SaYsepJ2sEt2CD@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=brgl@bgdev.pl \
--cc=dmitry.torokhov@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-acpi@vger.kernel.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.