From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Martin Schwidefsky <schwidefsky@de•ibm.com>,
Heiko Carstens <heiko.carstens@de•ibm.com>
Cc: Linux Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Philipp Rudo <prudo@linux•ibm.com>
Subject: linux-next: Fixes tag needs some work in the s390 tree
Date: Sun, 28 Apr 2019 17:07:13 +1000 [thread overview]
Message-ID: <20190428170713.770e1bfc@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 347 bytes --]
Hi all,
In commit
2875248b5e1a ("s390/kexec_file: Fix potential segment overlap in ELF loader")
Fixes tag
Fixes: 91a05d9e1d6b ("s390/kexec_file: Add ELF loader")
has these problem(s):
- Target SHA1 does not exist
Did you mean
Fixes: 8be018827154 ("s390/kexec_file: Add ELF loader")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2019-04-28 7:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-28 7:07 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-02-18 20:38 linux-next: Fixes tag needs some work in the s390 tree Stephen Rothwell
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=20190428170713.770e1bfc@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=heiko.carstens@de$(echo .)ibm.com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=prudo@linux$(echo .)ibm.com \
--cc=schwidefsky@de$(echo .)ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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