public inbox for linux-staging@lists.linux.dev
 help / color / mirror / Atom feed
From: Nam Cao <namcaov@gmail.com>
To: Oliver Crumrine <ozlinux@hotmail.com>
Cc: gregkh@linuxfoundation.org, colin.i.king@gmail.com,
	sumitraartsy@gmail.com, u.kleine-koenig@pengutronix.de,
	geert@linux-m68k.org, linux-kernel@vger.kernel.org,
	linux-staging@lists.linux.dev
Subject: Re: [PATCH v4 0/6] staging: octeon: clean up the octeon ethernet driver
Date: Mon, 28 Aug 2023 16:17:16 +0200	[thread overview]
Message-ID: <ZOysbIihBA5ZMGc9@nam-dell> (raw)
In-Reply-To: <PH7PR11MB7643280D48E45D2B660F5B6CBCE0A@PH7PR11MB7643.namprd11.prod.outlook.com>

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 

  reply	other threads:[~2023-08-28 14:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-28 13:39 [PATCH v4 0/6] staging: octeon: clean up the octeon ethernet driver Oliver Crumrine
2023-08-28 14:17 ` Nam Cao [this message]
2023-08-28 14:44   ` ozlinux
2023-08-28 14:57     ` Nam Cao
2023-08-29 13:58     ` Nam Cao

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=ZOysbIihBA5ZMGc9@nam-dell \
    --to=namcaov@gmail.com \
    --cc=colin.i.king@gmail.com \
    --cc=geert@linux-m68k.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=ozlinux@hotmail.com \
    --cc=sumitraartsy@gmail.com \
    --cc=u.kleine-koenig@pengutronix.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox