linux-serial.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yanteng Si <si.yanteng@linux.dev>
To: Yanteng Si <siyanteng@cqsoftware.com.cn>,
	linux@armlinux.org.uk, gregkh@linuxfoundation.org,
	jirislaby@kernel.org, alan@linux.intel.com
Cc: 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: Sat, 12 Oct 2024 11:10:05 +0800	[thread overview]
Message-ID: <6b5d548b-82ab-4bf3-90da-173928968fb9@linux.dev> (raw)
In-Reply-To: <20240920053423.1373354-1-siyanteng@cqsoftware.com.cn>

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?


Thanks,
Yanteng
>
> Signed-off-by: Yanteng Si <siyanteng@cqsoftware.com.cn>
> ---
>   include/linux/platform_data/sa11x0-serial.h | 1 -
>   1 file changed, 1 deletion(-)
>
> diff --git a/include/linux/platform_data/sa11x0-serial.h b/include/linux/platform_data/sa11x0-serial.h
> index 8b79ab08af45..a88096bc74e4 100644
> --- a/include/linux/platform_data/sa11x0-serial.h
> +++ b/include/linux/platform_data/sa11x0-serial.h
> @@ -10,7 +10,6 @@
>   #define SA11X0_SERIAL_H
>   
>   struct uart_port;
> -struct uart_info;
>   
>   /*
>    * This is a temporary structure for registering these


  parent reply	other threads:[~2024-10-12  3:10 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 [this message]
2024-10-12  7:57   ` Greg KH
2024-10-14  1:46     ` Yanteng Si

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=6b5d548b-82ab-4bf3-90da-173928968fb9@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).