All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Jiri Slaby <jirislaby@kernel.org>
Cc: Rengarajan.S@microchip.com, linux-serial@vger.kernel.org,
	Kumaravel.Thiagarajan@microchip.com,
	linux-kernel@vger.kernel.org,
	Tharunkumar.Pasumarthi@microchip.com,
	UNGLinuxDriver@microchip.com
Subject: Re: [PATCH v1 tty] 8250: microchip: pci1xxxx: Add Burst mode transmission support in uart driver for reading from FIFO
Date: Fri, 9 Feb 2024 10:20:36 +0000	[thread overview]
Message-ID: <2024020916-barrette-okay-60f7@gregkh> (raw)
In-Reply-To: <0c1e8d38-4b00-4738-bd05-7e36ce736681@kernel.org>

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

  reply	other threads:[~2024-02-09 10:20 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 [this message]
2024-02-13  9:31           ` Rengarajan.S
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=2024020916-barrette-okay-60f7@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=Kumaravel.Thiagarajan@microchip.com \
    --cc=Rengarajan.S@microchip.com \
    --cc=Tharunkumar.Pasumarthi@microchip.com \
    --cc=UNGLinuxDriver@microchip.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.