From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Ryan Case <ryandcase@chromium.org>
Cc: Jiri Slaby <jslaby@suse.com>, Evan Green <evgreen@chromium.org>,
Doug Anderson <dianders@chromium.org>,
linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
Stephen Boyd <swboyd@chromium.org>
Subject: Re: [PATCH 4/4] tty: serial: qcom_geni_serial: Use u32 for register variables
Date: Fri, 4 Jan 2019 09:45:11 +0100 [thread overview]
Message-ID: <20190104084511.GA17997@kroah.com> (raw)
In-Reply-To: <20190102213636.40866-5-ryandcase@chromium.org>
On Wed, Jan 02, 2019 at 01:36:36PM -0800, Ryan Case wrote:
> Signed-off-by: Ryan Case <ryandcase@chromium.org>
> ---
>
> drivers/tty/serial/qcom_geni_serial.c | 22 +++++++++++-----------
> 1 file changed, 11 insertions(+), 11 deletions(-)
I can not take patches without any changelog text, sorry.
greg k-h
next prev parent reply other threads:[~2019-01-04 8:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-02 21:36 [PATCH 0/4] tty: serial: qcom_geni_serial: Assorted cleanups Ryan Case
2019-01-02 21:36 ` [PATCH 1/4] tty: serial: qcom_geni_serial: Remove use of *_relaxed() and mb() Ryan Case
2019-01-04 19:03 ` Evan Green
2019-01-02 21:36 ` [PATCH 2/4] tty: serial: qcom_geni_serial: Remove set_rfr_wm() and related variables Ryan Case
2019-01-04 19:04 ` Evan Green
2019-01-02 21:36 ` [PATCH 3/4] tty: serial: qcom_geni_serial: Remove xfer_mode variable Ryan Case
2019-01-04 19:04 ` Evan Green
2019-01-02 21:36 ` [PATCH 4/4] tty: serial: qcom_geni_serial: Use u32 for register variables Ryan Case
2019-01-03 21:22 ` Stephen Boyd
2019-01-04 8:45 ` Greg Kroah-Hartman [this message]
2019-01-04 19:05 ` Evan Green
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=20190104084511.GA17997@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=dianders@chromium.org \
--cc=evgreen@chromium.org \
--cc=jslaby@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=ryandcase@chromium.org \
--cc=swboyd@chromium.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).