From: Mike Rapoport <rppt@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Guenter Roeck <linux@roeck-us.net>,
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 memblock-fixes tree
Date: Tue, 6 Jul 2021 09:10:10 +0300 [thread overview]
Message-ID: <YOPzwg7DeU1gobIr@kernel.org> (raw)
In-Reply-To: <20210706080621.5d497973@canb.auug.org.au>
Hi Stephen,
On Tue, Jul 06, 2021 at 08:06:21AM +1000, Stephen Rothwell wrote:
> Hi all,
>
> In commit
>
> 24caecffab46 ("arm: ioremap: don't abuse pfn_valid() to check if pfn is in RAM")
>
> Fixes tag
>
> Fixes: 30603c5a0c9a ("arm: ioremap: don't abuse pfn_valid() to check if pfn
>
> has these problem(s):
>
> - Target SHA1 does not exist
>
> I could not easily find the actual commit that was meant.
>
> Also, please do not split Fixes tags over more than one line.
Should be fixed now.
--
Sincerely yours,
Mike.
prev parent reply other threads:[~2021-07-06 6:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-05 22:06 linux-next: Fixes tag needs some work in the memblock-fixes tree Stephen Rothwell
2021-07-06 6:10 ` Mike Rapoport [this message]
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=YOPzwg7DeU1gobIr@kernel.org \
--to=rppt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux@roeck-us.net \
--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 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.