From: Louis Bouchard <louis.bouchard@canonical.com>
To: kexec@lists.infradead.org
Subject: Makedumpfile and kernel support
Date: Thu, 21 May 2015 11:23:17 +0200 [thread overview]
Message-ID: <555DA405.1070002@canonical.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hello,
- From time to time, on the distribution side, we get reports that makedumpfile
says the kernel version is not supported with the following message :
"The kernel version is not supported.
The created dumpfile may be incomplete. "
Depending on the kernel and makedumpfile versions, it can be either
disregarded or it requires fixing on the distribution. For instance, with
Kumagai's help, I backported the required commits so makedumpfile on Jessie
(1.5.3) would not complain about Jessie's kernels (3.16).
While we can review each patch to identify those who have specific kernel
requirements, would it be possible to identify a way to highlight those
patches so they become easily identifiable for potential backport ?
Maybe something like "[kernel]" in the git log or specific mention in the
commit log. I would like to avoid going back to upstream to confirm that the
proper patches are being identified.
Any comments, toughts, concerns ?
Kind regards,
...Louis
- --
Louis Bouchard
Software engineer, Cloud & Sustaining eng.
Canonical Ltd
Ubuntu developer Debian Maintainer
GPG : 429D 7A3B DD05 B6F8 AF63 B9C4 8B3D 867C 823E 7A61
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQIcBAEBCAAGBQJVXaQAAAoJEIs9hnyCPnphYbMP/21fhl1pHNcToYH5c2casXTM
D794dqwGzSSgXNWPueTajW/7OyvEEryN6izUfOUQ3ACJ10c0zzv/GQ6mjrIoKLz8
+xhml3gM0Tu3oJsKz5fHDbkKAx9X8604fQSB5Vrsz23Tr/MaNH2ASV000PE7HvY5
uIupEQMsluVV8EeLtjI1NPGNKwk9ZpwgCK4ogKCD0k3Gqn0JGB/bA6T0dpqjPGkm
At+nDUMNpADYkWd6sm9pem1GqgUJMNjgyu9P/vKxGCd++uUvmXolZT0BXXJhebKg
U8BNCxf/l/dhfXx5++GMMVCtD8Po/oDU2/x3C7MefrTaRlZmHTzEAhWr/BPp3I8J
vPK+emrS8b5WcrWY3eq3dvL1gnW0k8ysppUEntgmXF5u1XlDopyoLeDuCXhjrTz8
+y4OHzp2TxX10hZPP6T60YM64AyRsDzJoU1UTk6WMtDxfvy1MW0ynQ5K8jSQHMnO
1GWEPFF2gXmAmMkWh7KxPbjOvBriJurwo4YDjf7kiu9XWCUzSN/o3QV4ywxYS9Nf
Yf8W/zSiEL6z0pODSuNgFis9t610vKdGLPAS97JX3CA2wn1jSfwP7eCXc81Jf1iJ
+O10J4I5/G04iCOaVk0muEywwfeq5GcXsSj0u/YwCZEP1TzWAEhyEZEzn+k4RQJU
6R88MEn7+Zcuz+gvxXBk
=10mW
-----END PGP SIGNATURE-----
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next reply other threads:[~2015-05-21 9:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-21 9:23 Louis Bouchard [this message]
2015-05-22 3:14 ` Makedumpfile and kernel support Atsushi Kumagai
2015-05-27 9:53 ` Louis Bouchard
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=555DA405.1070002@canonical.com \
--to=louis.bouchard@canonical.com \
--cc=kexec@lists.infradead.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