All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Nam Cao <namcaov@gmail.com>
Cc: Oliver Crumrine <ozlinux@hotmail.com>,
	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 1/6] staging: octeon: clean up the octeon ethernet driver
Date: Mon, 28 Aug 2023 16:45:07 +0200	[thread overview]
Message-ID: <2023082849-crushable-emission-862b@gregkh> (raw)
In-Reply-To: <ZOyxaLDCI81W96/X@nam-dell>

On Mon, Aug 28, 2023 at 04:38:32PM +0200, Nam Cao wrote:
> On Mon, Aug 28, 2023 at 09:39:14AM -0400, Oliver Crumrine wrote:
> > Make the octeon ethernet driver better adhere to the
> > kernel coding standard
> > 
> > Signed-off-by: Oliver Crumrine <ozlinux@hotmail.com>
> > ---
> > v2: Actually send the patch set properly
> > v3: Fixed a bug where I forgot to change all instances of a struct
> > v4: Actually fix that bug (this is my first patch, give me a break)
> 
> Don't give up! You will get it right eventually.
> 
> This is not important, but I prefer you revert the order of the change log.
> The changes compared to the last version is most relevant, so preferably they
> should be put on top.

Either way is fine, this isn't an issue.

What _is_ an issue is that all of these have the identical subject line,
and the identical changelog text _yet_ they do different things.

Oliver, please read read the section entitled "The canonical patch
format" in the kernel file, Documentation/process/submitting-patches.rst
for a description of how to do properly.

thanks,

greg k-h

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

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cover.1693229582.git.ozlinux@hotmail.com>
2023-08-28 13:39 ` [PATCH v4 1/6] staging: octeon: clean up the octeon ethernet driver Oliver Crumrine
2023-08-28 14:23   ` Nam Cao
2023-08-28 14:38   ` Nam Cao
2023-08-28 14:45     ` Greg KH [this message]
2023-08-28 13:39 ` [PATCH v4 2/6] " Oliver Crumrine
2023-08-28 13:39 ` [PATCH v4 3/6] " Oliver Crumrine
2023-08-28 13:39 ` [PATCH v4 4/6] " Oliver Crumrine
2023-08-28 13:39 ` [PATCH v4 5/6] " Oliver Crumrine
2023-08-28 13:39 ` [PATCH v4 6/6] " Oliver Crumrine

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=2023082849-crushable-emission-862b@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=colin.i.king@gmail.com \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=namcaov@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.