Re: [PATCH v4 0/6] staging: octeon: clean up the octeon ethernet driver

[Nam Cao]

On Mon, Aug 28, 2023 at 10:44:42AM -0400, ozlinux@xxxxxxxxxxx wrote:
> On Mon, Aug 28, 2023 at 04:17:16PM +0200, Nam Cao wrote:
> > On Mon, Aug 28, 2023 at 09:39:13AM -0400, Oliver Crumrine wrote:
> > > Make the octeon ethernet driver better conform to the linux kernel coding standards
> > > 
> > > Oliver Crumrine (6):
> > >   staging: octeon: clean up the octeon ethernet driver
> > >   staging: octeon: clean up the octeon ethernet driver
> > >   staging: octeon: clean up the octeon ethernet driver
> > >   staging: octeon: clean up the octeon ethernet driver
> > >   staging: octeon: clean up the octeon ethernet driver
> > >   staging: octeon: clean up the octeon ethernet driver
> > > 
> > >  drivers/staging/octeon/ethernet.c     |  6 ++--
> > >  drivers/staging/octeon/octeon-stubs.h | 50 +++++++++++++--------------
> > >  2 files changed, 28 insertions(+), 28 deletions(-)
> > > 
> > > -- 
> > > 2.39.3
> > >
> > 
> > The patches themselves should also be sent with this cover letter. Instead they
> > are sent in a different thread :(
> > 
> > Best regards,
> > Nam 
> 
> Looking at the what I sent, all the patches should be in reply to 
> <cover.1693229582.git.ozlinux@xxxxxxxxxxx>, both according to the patch
> that was created by git format-patch, and Outlook. If in-reply-to and
> the thread are 2 different things, please let me know, and instruct me on 
> how I should put the patches in the same thread.

(keep in mind I know little of emails, I am just guessing here)

It seems that your email client or email provider changed your message ID. See:
https://lore.kernel.org/linux-staging/PH7PR11MB7643280D48E45D2B660F5B6CBCE0A@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx/raw
that "Message-ID" is not what git-format patch generates. Your original email
ID is instead in "X-Microsoft-Original-Message-ID". So your patches have
"In-Reply-To" that refers to an ID that has been removed, so the email thread
is broken.

So perhaps try to change your email settings to stop this from happening, or
change your email client / email provider.

If you figure out what is the problem, consider sending a patch to
Documentation/process/email-clients.rst documenting this.

Best regards,
Nam