From: Greg KH <gregkh@linuxfoundation.org>
To: Chaitanya Vadrevu <chaitanya.vadrevu@emerson.com>
Cc: jirislaby@kernel.org, linux-serial@vger.kernel.org,
linux-kernel@vger.kernel.org, kernel test robot <lkp@intel.com>,
Jason Smith <jason.smith@emerson.com>,
Gratian Crisan <gratian.crisan@emerson.com>
Subject: Re: [PATCH] serial: 8250_ni: Fix build warning
Date: Sat, 12 Jul 2025 08:49:10 +0200 [thread overview]
Message-ID: <2025071249-curdle-predator-05ed@gregkh> (raw)
In-Reply-To: <2025071206-grip-overblown-bf53@gregkh>
On Sat, Jul 12, 2025 at 08:47:42AM +0200, Greg KH wrote:
> Ah, you are right, sorry, I always get that one wrong. I'll just take
> this as-is, no need to redo it.
You already sent v2, thanks, I'll take that.
greg k-h
prev parent reply other threads:[~2025-07-12 6:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-10 22:38 [PATCH] serial: 8250_ni: Fix build warning Chaitanya Vadrevu
2025-07-11 5:03 ` Jiri Slaby
2025-07-11 5:50 ` Greg KH
2025-07-11 19:27 ` Chaitanya Vadrevu
2025-07-12 6:47 ` Greg KH
2025-07-12 6:49 ` Greg KH [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=2025071249-curdle-predator-05ed@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=chaitanya.vadrevu@emerson.com \
--cc=gratian.crisan@emerson.com \
--cc=jason.smith@emerson.com \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=lkp@intel.com \
/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).