linux-serial.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Mihai.Sain@microchip.com
Cc: richard.genoud@bootlin.com, jirislaby@kernel.org,
	Nicolas.Ferre@microchip.com, alexandre.belloni@bootlin.com,
	claudiu.beznea@tuxon.dev, linux-kernel@vger.kernel.org,
	linux-serial@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC PATCH] tty: atmel_serial: Use devm_platform_ioremap_resource()
Date: Mon, 21 Oct 2024 09:24:57 +0200	[thread overview]
Message-ID: <2024102148-stamp-isolation-ae90@gregkh> (raw)
In-Reply-To: <PH8PR11MB6804FADFEFEA51A8B35F894482432@PH8PR11MB6804.namprd11.prod.outlook.com>

On Mon, Oct 21, 2024 at 07:16:31AM +0000, Mihai.Sain@microchip.com wrote:
> > From: Greg KH <gregkh@linuxfoundation.org>
> > Sent: Monday, October 21, 2024 10:00 AM
> > To: Mihai Sain - M19926 <Mihai.Sain@microchip.com>
> > Cc: richard.genoud@bootlin.com; jirislaby@kernel.org; Nicolas Ferre - M43238
> > <Nicolas.Ferre@microchip.com>; alexandre.belloni@bootlin.com;
> > claudiu.beznea@tuxon.dev; linux-kernel@vger.kernel.org; linux-
> > serial@vger.kernel.org; linux-arm-kernel@lists.infradead.org
> > Subject: Re: [RFC PATCH] tty: atmel_serial: Use
> > devm_platform_ioremap_resource()
> > 
> > On Mon, Oct 21, 2024 at 09:43:21AM +0300, Mihai Sain wrote:
> > > Simplify the request port function by using a single call to
> > > devm_platform_ioremap_resource().
> > >
> > > This will also enhance the printing from /proc/iomem:
> > >
> > > cat /proc/iomem | grep flexcom ; cat /proc/iomem | grep serial
> > >
> > > f0004000-f00041ff : f0004000.flexcom flexcom@f0004000
> > > f8020000-f80201ff : f8020000.flexcom flexcom@f8020000
> > > f0004200-f00043ff : f0004200.serial serial@200 f8020200-f80203ff :
> > > f8020200.serial serial@200 fffff200-fffff3ff : fffff200.serial
> > > serial@fffff200
> > >
> > > Signed-off-by: Mihai Sain <mihai.sain@microchip.com>
> > > ---
> > >  drivers/tty/serial/atmel_serial.c | 12 +++---------
> > >  1 file changed, 3 insertions(+), 9 deletions(-)
> > 
> > Why is this a rfc?  What needs to be done before you want it merged?
> 
> I used the rfc tag in order to get the feedback from you and all stakeholders.

You need to ask for the feedback you are looking for, we don't know what
you feel is wrong here.

> If the modifications are OK for you I will send a new patch without rfc tag.

As we are drowning in real patches to review, I almost always just
ignore RFC patches as I know that means that the submitter feels there
is still more work to be done.  So please always take that in mind.
Please ask for reviews from other developers in your company if you feel
it is not ready for our review.

thanks,

greg k-h

      reply	other threads:[~2024-10-21  7:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-21  6:43 [RFC PATCH] tty: atmel_serial: Use devm_platform_ioremap_resource() Mihai Sain
2024-10-21  6:59 ` Greg KH
2024-10-21  7:16   ` Mihai.Sain
2024-10-21  7:24     ` 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=2024102148-stamp-isolation-ae90@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=Mihai.Sain@microchip.com \
    --cc=Nicolas.Ferre@microchip.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=claudiu.beznea@tuxon.dev \
    --cc=jirislaby@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=richard.genoud@bootlin.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).