From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: Andrew Morton <akpm@linux-foundation.org>,
Joe Perches <joe@perches.com>, Andy Whitcroft <apw@canonical.com>
Cc: Ricardo Ribalda <ribalda@chromium.org>,
Tomasz Figa <tfiga@chromium.org>,
linux-kernel@vger.kernel.org,
Sergey Senozhatsky <senozhatsky@chromium.org>
Subject: Re: [RESEND][PATCH] checkpatch: make sure fix-up patches have Fixes tag
Date: Wed, 19 Jan 2022 17:01:46 +0900 [thread overview]
Message-ID: <YefFapMkddSWHXRE@google.com> (raw)
In-Reply-To: <20220119074609.4162747-1-senozhatsky@chromium.org>
On (22/01/19 16:46), Sergey Senozhatsky wrote:
>
> Change-Id: I066ae0e607a67ac83c6ba0ff8d883f7e7a4a73e0
>
It was not supposed to be there, but it's there (spotted by Tomasz).
Let me know if I need to re-send.
next prev parent reply other threads:[~2022-01-19 8:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-19 7:46 [RESEND][PATCH] checkpatch: make sure fix-up patches have Fixes tag Sergey Senozhatsky
2022-01-19 8:01 ` Sergey Senozhatsky [this message]
2022-01-19 9:42 ` Joe Perches
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=YefFapMkddSWHXRE@google.com \
--to=senozhatsky@chromium.org \
--cc=akpm@linux-foundation.org \
--cc=apw@canonical.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ribalda@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;
as well as URLs for NNTP newsgroup(s).