From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Maximilian Luz <luzmaximilian@gmail.com>,
Lee Jones <lee.jones@linaro.org>,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
Mark Gross <mgross@linux.intel.com>,
Rob Herring <robh@kernel.org>, Jiri Slaby <jirislaby@kernel.org>
Subject: Re: [PATCH v3 1/2] serdev: Split and export serdev_acpi_get_uart_resource()
Date: Fri, 13 Aug 2021 09:13:36 +0200 [thread overview]
Message-ID: <YRYboAR9g/193T48@kroah.com> (raw)
In-Reply-To: <a955083a-a985-0b7d-460f-af196c5113c5@redhat.com>
On Fri, Aug 06, 2021 at 02:08:42PM +0200, Hans de Goede wrote:
> Hi,
>
> On 8/6/21 1:17 PM, Andy Shevchenko wrote:
> > The same as for I²C Serial Bus resource split and export
> > serdev_acpi_get_uart_resource(). We have already a few users
> > one of which is converted here.
> >
> > Rationale of this is to consolidate parsing UART Serial Bus
> > resource in one place as it's done, e.g., for I²C Serial Bus.
> >
> > Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> > Reviewed-by: Hans de Goede <hdegoede@redhat.com>
>
> As mentioned before I believe it is best if this series is
> merged in its entirety through to the tty tree, here is my
> ack for patch 2/2 for that:
>
> Acked-by: Hans de Goede <hdegoede@redhat.com>
>
> Greg, can you pickup the entire series please?
Now picked up, thanks.
greg k-h
prev parent reply other threads:[~2021-08-13 7:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-06 11:17 [PATCH v3 1/2] serdev: Split and export serdev_acpi_get_uart_resource() Andy Shevchenko
2021-08-06 11:17 ` [PATCH v3 2/2] platform/surface: aggregator: Use serdev_acpi_get_uart_resource() helper Andy Shevchenko
2021-08-06 12:08 ` [PATCH v3 1/2] serdev: Split and export serdev_acpi_get_uart_resource() Hans de Goede
2021-08-13 7:13 ` Greg Kroah-Hartman [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=YRYboAR9g/193T48@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=hdegoede@redhat.com \
--cc=jirislaby@kernel.org \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=luzmaximilian@gmail.com \
--cc=mgross@linux.intel.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=robh@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).