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] [thread-next>] [day] [month] [year] [list]

Message-ID: <PH7PR11MB7643DE405C5FBBE0B0E63313BCE0A@PH7PR11MB7643.namprd11.prod.outlook.com>
Date:   Mon, 28 Aug 2023 10:44:42 -0400
From:   <ozlinux@...mail.com>
To:     Nam Cao <namcaov@...il.com>
Cc:     gregkh@...uxfoundation.org, colin.i.king@...il.com,
        sumitraartsy@...il.com, u.kleine-koenig@...gutronix.de,
        geert@...ux-m68k.org, linux-kernel@...r.kernel.org,
        linux-staging@...ts.linux.dev
Subject: Re: [PATCH v4 0/6] staging: octeon: clean up the octeon ethernet
 driver

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. 

As per your second email, I will be more specific in my description for
each patch.

As per your third email, I will make sure to invert the changelog.

Thanks for all the feedback, 
Oliver