From: Greg KH <gregkh@linuxfoundation.org>
To: Osama Abdelkader <osama.abdelkader@gmail.com>
Cc: jirislaby@kernel.org, ilpo.jarvinen@linux.intel.com,
mingo@kernel.org, john.ogness@linutronix.de, tglx@linutronix.de,
linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org
Subject: Re: [PATCH v2] serial: 8250_core: fix coding style issue
Date: Fri, 22 Aug 2025 11:49:19 +0200 [thread overview]
Message-ID: <2025082212-crunchy-crewless-7eab@gregkh> (raw)
In-Reply-To: <6503f380-1566-4efc-913d-125d316787d1@gmail.com>
On Fri, Aug 22, 2025 at 11:42:55AM +0200, Osama Abdelkader wrote:
>
> On 8/22/25 10:45 AM, Greg KH wrote:
> > On Fri, Aug 22, 2025 at 10:23:10AM +0200, Osama Abdelkader wrote:
> >> Fix a coding style issue in 8250_core.c:
> >>
> >> - Remove redundant NULL initialization of a global pointer
> >>
> >> Signed-off-by: Osama Abdelkader <osama.abdelkader@gmail.com>
> >> ---
> >> drivers/tty/serial/8250/8250_core.c | 2 +-
> >> 1 file changed, 1 insertion(+), 1 deletion(-)
> >>
> >> diff --git a/drivers/tty/serial/8250/8250_core.c b/drivers/tty/serial/8250/8250_core.c
> >> index feb920c5b2e8..225bb7e4b89c 100644
> >> --- a/drivers/tty/serial/8250/8250_core.c
> >> +++ b/drivers/tty/serial/8250/8250_core.c
> >> @@ -307,7 +307,7 @@ static void univ8250_release_irq(struct uart_8250_port *up)
> >> serial_unlink_irq_chain(up);
> >> }
> >>
> >> -const struct uart_ops *univ8250_port_base_ops = NULL;
> >> +const struct uart_ops *univ8250_port_base_ops;
> >> struct uart_ops univ8250_port_ops;
> >>
> >> static const struct uart_8250_ops univ8250_driver_ops = {
> >> --
> >> 2.43.0
> >>
> >>
> >
> > Hi,
> >
> > This is the friendly patch-bot of Greg Kroah-Hartman. You have sent him
> > a patch that has triggered this response. He used to manually respond
> > to these common problems, but in order to save his sanity (he kept
> > writing the same thing over and over, yet to different people), I was
> > created. Hopefully you will not take offence and will fix the problem
> > in your patch and resubmit it so that it can be accepted into the Linux
> > kernel tree.
> >
> > You are receiving this message because of the following common error(s)
> > as indicated below:
> >
> > - This looks like a new version of a previously submitted patch, but you
> > did not list below the --- line any changes from the previous version.
> > Please read the section entitled "The canonical patch format" in the
> > kernel file, Documentation/process/submitting-patches.rst for what
> > needs to be done here to properly describe this.
> >
> > If you wish to discuss this problem further, or you have questions about
> > how to resolve this issue, please feel free to respond to this email and
> > Greg will reply once he has dug out from the pending patches received
> > from other developers.
> >
> > thanks,
> >
> > greg k-h's patch email bot
>
> Hi All,
>
> I forgot to include the changelog in v2.
>
> v2:
>
> - Dropped extra blank line after gpios declaration
Please send a v3 with that.
prev parent reply other threads:[~2025-08-22 9:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-22 8:23 [PATCH v2] serial: 8250_core: fix coding style issue Osama Abdelkader
2025-08-22 8:45 ` Greg KH
2025-08-22 9:42 ` Osama Abdelkader
2025-08-22 9:49 ` 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=2025082212-crunchy-crewless-7eab@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jirislaby@kernel.org \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=osama.abdelkader@gmail.com \
--cc=tglx@linutronix.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