public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Adam Sindelar <adam@wowsignal.io>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the mm tree
Date: Tue, 26 Jul 2022 17:02:07 -0700	[thread overview]
Message-ID: <20220726170207.d902aebccf46c855c490b251@linux-foundation.org> (raw)
In-Reply-To: <20220727092329.2a4aade0@canb.auug.org.au>

On Wed, 27 Jul 2022 09:23:29 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:

> In commit
> 
>   1da6684b4930 ("selftests/vm: fix va_128TBswitch.sh permissions")
> 
> Fixes tag
> 
>   Fixes: 1afd01d43efc3 ("selftests/vm: Only run 128TBswitch with 5-level
> 
> has these problem(s):
> 
>   - Subject has leading but no trailing parentheses
>   - Subject has leading but no trailing quotes
> 
> Please do not split Fixes tags over more than one line.  Also keep all
> the commit message tags together at the end of the commit message.
> 
> This commit is also missing a Signed-off-by from its committer.

Bah, thanks.  Fixed&rebased.

  reply	other threads:[~2022-07-27  0:02 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-26 23:23 linux-next: Fixes tag needs some work in the mm tree Stephen Rothwell
2022-07-27  0:02 ` Andrew Morton [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-02-09  6:22 Stephen Rothwell
2024-07-09 22:54 Stephen Rothwell
2024-02-25 21:18 Stephen Rothwell
2024-02-04 21:29 Stephen Rothwell
2023-12-12 20:59 Stephen Rothwell
2023-12-13  1:04 ` Andrew Morton
2023-10-17  4:33 Stephen Rothwell
2023-10-10  5:47 Stephen Rothwell
2023-10-10 15:42 ` Zi Yan
2022-11-23 22:08 Stephen Rothwell
2022-11-23 23:06 ` Jann Horn
2022-11-24  0:13   ` Andrew Morton
2022-11-24 13:37     ` Jann Horn
2022-11-23 22:00 Stephen Rothwell
2022-09-18 22:21 Stephen Rothwell
2022-09-19 14:47 ` Zach O'Keefe
2022-09-19 21:04   ` Andrew Morton
2022-09-21 18:24     ` Zach O'Keefe
2022-06-30  3:37 Stephen Rothwell
2022-06-30 15:28 ` Liam Howlett
2022-06-30 18:16   ` Andrew Morton
2022-06-30  3:32 Stephen Rothwell
2022-06-30 15:20 ` Liam Howlett
2022-05-25  0:27 Stephen Rothwell
2022-05-25  0:36 ` Zi Yan
2022-05-13  6:56 Stephen Rothwell
2022-04-27 22:42 Stephen Rothwell
2022-04-28  2:37 ` Liam Howlett
2022-04-28  3:09   ` 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=20220726170207.d902aebccf46c855c490b251@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=adam@wowsignal.io \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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