From: Joe Perches <joe@perches.com>
To: Sergey Senozhatsky <senozhatsky@chromium.org>,
Andrew Morton <akpm@linux-foundation.org>,
Andy Whitcroft <apw@canonical.com>
Cc: Ricardo Ribalda <ribalda@chromium.org>,
Tomasz Figa <tfiga@chromium.org>,
linux-kernel@vger.kernel.org
Subject: Re: [RESEND][PATCH] checkpatch: make sure fix-up patches have Fixes tag
Date: Wed, 19 Jan 2022 01:42:07 -0800 [thread overview]
Message-ID: <a70570a10026203b544e930eb6dbcf6ad0abb2ad.camel@perches.com> (raw)
In-Reply-To: <20220119074609.4162747-1-senozhatsky@chromium.org>
On Wed, 2022-01-19 at 16:46 +0900, Sergey Senozhatsky wrote:
> If a patch contains "commit hash (commit name)", in other words
> if the patch fixes some particular commit, then require "Fixes:"
> tag.
I do not like this patch as many commits merely reference a
previous patch and do not actually fix anything.
next prev parent reply other threads:[~2022-01-19 9:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-19 7:46 Sergey Senozhatsky
2022-01-19 8:01 ` Sergey Senozhatsky
2022-01-19 9:42 ` Joe Perches [this message]
2022-01-19 9:48 ` Andy Whitcroft
2022-01-26 1:53 ` Andrew Morton
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=a70570a10026203b544e930eb6dbcf6ad0abb2ad.camel@perches.com \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=apw@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ribalda@chromium.org \
--cc=senozhatsky@chromium.org \
--cc=tfiga@chromium.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®