From: <Rengarajan.S@microchip.com>
To: <jirislaby@kernel.org>, <gregkh@linuxfoundation.org>
Cc: <linux-serial@vger.kernel.org>, <UNGLinuxDriver@microchip.com>,
<Kumaravel.Thiagarajan@microchip.com>,
<linux-kernel@vger.kernel.org>,
<Tharunkumar.Pasumarthi@microchip.com>
Subject: Re: [PATCH v1 tty] 8250: microchip: pci1xxxx: Add Burst mode transmission support in uart driver for reading from FIFO
Date: Tue, 13 Feb 2024 09:31:21 +0000 [thread overview]
Message-ID: <0fdcb9c4fea657b7d29c2b8fe356c544b4b50a35.camel@microchip.com> (raw)
In-Reply-To: <2024020916-barrette-okay-60f7@gregkh>
Hi Greg,
Since, Most of the comments were alignment related and no
functionalities were affected, the current patch can be merged in the
next window. Will share another patch with the suggested incremental
changes shortly. Thanks!!
On Fri, 2024-02-09 at 10:20 +0000, Greg KH wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you
> know the content is safe
>
> On Fri, Feb 09, 2024 at 07:38:49AM +0100, Jiri Slaby wrote:
> > On 09. 02. 24, 5:52, Rengarajan.S@microchip.com wrote:
> > > Hi Jiri Slaby,
> > >
> > > The patch has been accepted and added in the tty-git tree and
> > > will be
> > > merged during the next merged window. Should the changes be given
> > > as a
> > > seperate incremental patch or should we re-submit this patch
> > > again.
> >
> > Hi,
> >
> > as you write, you cannot change the patch as it is already queued.
> > PLease
> > submit changes on top.
>
> Or, if the original is so bad, we can revert them now and wait for
> new
> ones later, just let me know.
>
> thanks,
>
> greg k-h
next prev parent reply other threads:[~2024-02-13 9:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-25 10:00 [PATCH v1 tty] 8250: microchip: pci1xxxx: Add Burst mode transmission support in uart driver for reading from FIFO Rengarajan S
2024-02-05 7:56 ` Jiri Slaby
2024-02-08 2:49 ` Rengarajan.S
2024-02-09 4:52 ` Rengarajan.S
2024-02-09 6:38 ` Jiri Slaby
2024-02-09 10:20 ` Greg KH
2024-02-13 9:31 ` Rengarajan.S [this message]
2024-02-15 9:30 ` Rengarajan.S
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=0fdcb9c4fea657b7d29c2b8fe356c544b4b50a35.camel@microchip.com \
--to=rengarajan.s@microchip.com \
--cc=Kumaravel.Thiagarajan@microchip.com \
--cc=Tharunkumar.Pasumarthi@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.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