All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: joe@perches.com
Cc: kuba@kernel.org, netdev@vger.kernel.org, andrew@lunn.ch,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v3] checkpatch: warn about uses of ENOTSUPP
Date: Mon, 11 May 2020 13:43:09 -0700 (PDT)	[thread overview]
Message-ID: <20200511.134309.870356538874716906.davem@davemloft.net> (raw)
In-Reply-To: <c4c6fee41ceb2eb4b583df37ad0d659357cd81d8.camel@perches.com>

From: Joe Perches <joe@perches.com>
Date: Mon, 11 May 2020 10:16:34 -0700

> No worries here and it's not worth a respin, but
> typically the patch changelog goes below the --- line.

I ask people explicitly to keep the changelog in the commit message
proper, the more information we have in the GIT history the better.

  reply	other threads:[~2020-05-11 20:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-11 17:08 [PATCH net-next v3] checkpatch: warn about uses of ENOTSUPP Jakub Kicinski
2020-05-11 17:16 ` Joe Perches
2020-05-11 20:43   ` David Miller [this message]
2020-05-12  0:00 ` David Miller

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=20200511.134309.870356538874716906.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=andrew@lunn.ch \
    --cc=joe@perches.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    /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.