From: Yanteng Si <si.yanteng@linux.dev>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Yanteng Si <siyanteng@cqsoftware.com.cn>,
linux@armlinux.org.uk, jirislaby@kernel.org,
alan@linux.intel.com, bartosz.golaszewski@linaro.org,
andriy.shevchenko@linux.intel.com, arnd@arndb.de,
u.kleine-koenig@pengutronix.de, mengdewei@cqsoftware.com.cn,
linux-serial@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] serial: clean up uart_info
Date: Mon, 14 Oct 2024 09:46:46 +0800 [thread overview]
Message-ID: <3aee5864-2e2b-4ce4-b814-6864deaa9d79@linux.dev> (raw)
In-Reply-To: <2024101206-stench-eraser-e479@gregkh>
在 2024/10/12 15:57, Greg KH 写道:
> On Sat, Oct 12, 2024 at 11:10:05AM +0800, Yanteng Si wrote:
>> Hi all,
>>
>>
>> 在 2024/9/20 13:34, Yanteng Si 写道:
>>> Since commit ebd2c8f6d2ec ("serial: kill off uart_info") has
>>> removed uart_info, the uart_info declaration looks lonely,
>>> let it go.
>> Could someone pick up my patch? Or give me some hints on what else I need to
>> do?
> I picked it up yesterday, you should have gotten an email for it, it is
> commit 483c5c2bc6b1 ("serial: clean up uart_info") in my tree. Do you
> not see it there?
Oh yeah! I've already seen this email!
Sorry, I forgot that my patch was generated during working hours,
so I used my company email. My company email has received your
email. Thank you!
Thanks,
Yanteng
>
> thanks,
>
> greg k-h
prev parent reply other threads:[~2024-10-14 1:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-20 5:34 [PATCH] serial: clean up uart_info Yanteng Si
2024-09-20 14:18 ` Andy Shevchenko
2024-10-12 3:10 ` Yanteng Si
2024-10-12 7:57 ` Greg KH
2024-10-14 1:46 ` Yanteng Si [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=3aee5864-2e2b-4ce4-b814-6864deaa9d79@linux.dev \
--to=si.yanteng@linux.dev \
--cc=alan@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=arnd@arndb.de \
--cc=bartosz.golaszewski@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mengdewei@cqsoftware.com.cn \
--cc=siyanteng@cqsoftware.com.cn \
--cc=u.kleine-koenig@pengutronix.de \
/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).