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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <PH7PR11MB7643ABC9DDDEF7423218EA37BCE7A@PH7PR11MB7643.namprd11.prod.outlook.com>
Date:   Tue, 29 Aug 2023 10:48:29 -0400
From:   <ozlinux@...mail.com>
To:     Nam Cao <namcaov@...il.com>
Cc:     linux-kernel@...r.kernel.org
Subject: Re: [PATCH v4 0/6] staging: octeon: clean up the octeon ethernet
 driver

On Tue, Aug 29, 2023 at 03:58:48PM +0200, Nam Cao wrote:
> On Mon, Aug 28, 2023 at 10:44:42AM -0400, ozlinux@...mail.com 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@...mail.com>, 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@PH7PR11MB7643.namprd11.prod.outlook.com/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

Okay, makes sense. I'll try to figure out what Microsoft is doing to
my email.

Oliver