From: Thomas Renninger <trenn@suse.de>
To: lkundrak@v3.sk, kexec@lists.infradead.org
Subject: The kernel version is not supported
Date: Tue, 12 Nov 2013 17:23:25 +0100 [thread overview]
Message-ID: <2415548.dh2jmZ1ojx@skinner> (raw)
Hi,
there was a patch recently from Lubomir, title:
dump-dmesg: Understand >= v3.11-rc4 dmesg
But in makedumpfile.h the latest supported version still is:
#define LATEST_VERSION KERNEL_VERSION(3, 9, 6)/* linux-3.9.6 */
resulting in:
The kernel version is not supported.
The created dumpfile may be incomplete.
messages.
I wonder whether there are other known issues with latest
kernels which are the reason LATEST_VERSION did not get increased
and which are those?
I also wonder what the concept of LATEST_VERSION is.
One does not know in advance which change in a newer kernel version
might break things?
So this one needs to be increased with every new kernel version?
Thanks for any hints,
Thomas
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next reply other threads:[~2013-11-12 16:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-12 16:23 Thomas Renninger [this message]
2013-11-19 1:58 ` The kernel version is not supported Atsushi Kumagai
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=2415548.dh2jmZ1ojx@skinner \
--to=trenn@suse.de \
--cc=kexec@lists.infradead.org \
--cc=lkundrak@v3.sk \
/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