mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Jiri Slaby <jirislaby@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH v1 1/1] serial: 8250: Move CE4100 quirks to a module under 8250 driver
Date: Mon, 30 Jun 2025 15:38:00 +0300	[thread overview]
Message-ID: <aGKFKOWv1xTDlhnD@smile.fi.intel.com> (raw)
In-Reply-To: <a7f162cf-b7ba-472c-b13a-e3a5cd722bab@kernel.org>

On Mon, Jun 30, 2025 at 01:27:10PM +0200, Jiri Slaby wrote:
> On 27. 06. 25, 20:25, Andy Shevchenko wrote:
> > There is inconvenient for maintainers and maintainership to have
> > some quirks under architectural code. Move it to the specific quirk
> > file like other 8250-compatible drivers do.
> > 
> > Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> 
> Nice.
> 
> Reviewed-by: Jiri Slaby <jirislaby@kernel.org>

Thanks, but it seems a bit late :-)

> Just two nits (one suggestion actually) below. Ignore if you won't resubmit
> for some other reasons...

Sure, see above.

...

> > +static inline void sdv_serial_fixup(void) {};
> 
> Superfluous ;.

Indeed. But I don't want to update just this (as it now may require
a separate change for x86).

...

> > -static u32 ce4100_mem_serial_in(struct uart_port *p, unsigned int offset)
> > -{
> > -	u32 ret, ier, lsr;
> > -
> > -	if (offset != UART_IIR)
> > -		return mem_serial_in(p, offset);
> > -
> > -	offset <<= p->regshift;
> > -
> > -	ret = readl(p->membase + offset);
> 
> Just noticed: why the two above lines are not one:
> ret = mem_serial_in()?
> 
> Or in fact the whole function intro:
> ret = mem_serial_in(p, offset);
> if (offset != UART_IIR)
>   return ret;

Hmm... Sounds like an equivalent. I probably can send a followup for this
suggestion.

-- 
With Best Regards,
Andy Shevchenko



      reply	other threads:[~2025-06-30 12:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-27 18:25 Andy Shevchenko
2025-06-30 11:27 ` Jiri Slaby
2025-06-30 12:38   ` Andy Shevchenko [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=aGKFKOWv1xTDlhnD@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hpa@zytor.com \
    --cc=jirislaby@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=x86@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

all inboxes | Powered by JetHome®