[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <AM4PR1001MB137883EF5392EE25ED70A912E0369@AM4PR1001MB1378.EURPRD10.PROD.OUTLOOK.COM>
Date: Thu, 17 Feb 2022 14:03:37 +0000
From: "Starke, Daniel" <daniel.starke@...mens.com>
To: Greg KH <gregkh@...uxfoundation.org>
CC: "linux-serial@...r.kernel.org" <linux-serial@...r.kernel.org>,
"jirislaby@...nel.org" <jirislaby@...nel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH 1/1] tty: n_gsm: fix encoding of control signal octet bit
DV
> > > All of these are patch 1/1, which is odd :(
> > >
> > > Please renumber them properly and resend.
> >
> > All these patches are based on the current version of tty-next and are
> > completely independent from each other. The only common part is the
> > file they apply to. Therefore, this is not a patch series. Would you
> > still suggest to apply a different numbering?
>
> Yes, please send them as a patch series, numbered correctly, as a whole
> series of patches, all listed as 1/1 does not do good things for our
> tools.
I have noticed that all patches have been sent in one thread. This was not
my intention. I see two options here now:
1. Resend all patches one by one as they are completely independent.
2. Create a patch series.
And the following two variants in case of option 2:
a. Just renumber the subjects and resend all (i.e. without a cover letter).
b. Create a patch series from commits that depend on each other. Send this
together with a cover letter.
Please let me know what you prefer.
With best regards,
Daniel Starke
Powered by blists - more mailing lists