public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: Jean-Michel Hautbois <jeanmichel.hautbois@yoseli.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Jiri Slaby <jirislaby@kernel.org>,
	linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
	linux-m68k@lists.linux-m68k.org
Subject: Re: [PATCH] tty: mcf: MCF54418 has 10 UARTS
Date: Thu, 20 Jun 2024 19:01:25 +0200	[thread overview]
Message-ID: <3ca5778e-75fa-4f8c-9bd1-daf5ce4574b9@yoseli.org> (raw)
In-Reply-To: <2024062006-squeezing-traffic-cecb@gregkh>

Hi Greg,

On 20/06/2024 18:58, Greg Kroah-Hartman wrote:
> On Thu, Jun 20, 2024 at 06:29:59PM +0200, Jean-Michel Hautbois wrote:
>> Most of the colfires have up to 5 UARTs but MCF54418 has up-to 10 !
>> Change the maximum value authorized.
>>
>> Signed-off-by: Jean-Michel Hautbois <jeanmichel.hautbois@yoseli.org>
>> ---
>>   drivers/tty/serial/mcf.c | 2 +-
>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/tty/serial/mcf.c b/drivers/tty/serial/mcf.c
>> index b0604d6da025..58858dd352c5 100644
>> --- a/drivers/tty/serial/mcf.c
>> +++ b/drivers/tty/serial/mcf.c
>> @@ -462,7 +462,7 @@ static const struct uart_ops mcf_uart_ops = {
>>   	.verify_port	= mcf_verify_port,
>>   };
>>   
>> -static struct mcf_uart mcf_ports[4];
>> +static struct mcf_uart mcf_ports[10];
> 
> What commit id does this fix?

Sorry about that !
Fixes: 2545cf6e94b4 (m68knommu: allow 4 coldfire serial ports, 2010-03-18)

> 
> thanks,
> 
> greg k-h

      reply	other threads:[~2024-06-20 17:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-20 16:29 [PATCH] tty: mcf: MCF54418 has 10 UARTS Jean-Michel Hautbois
2024-06-20 16:58 ` Greg Kroah-Hartman
2024-06-20 17:01   ` Jean-Michel Hautbois [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=3ca5778e-75fa-4f8c-9bd1-daf5ce4574b9@yoseli.org \
    --to=jeanmichel.hautbois@yoseli.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jirislaby@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@lists.linux-m68k.org \
    --cc=linux-serial@vger.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