Kexec Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Liu Tao <ltao@redhat.com>
Cc: Greg KH <gregkh@linuxfoundation.org>, Baoquan He <bhe@redhat.com>,
	Patrick Sung <patricksung@gmail.com>,
	sashal@kernel.org, kexec@lists.infradead.org,
	RuiRui Yang <dyoung@redhat.com>,
	horms@verge.net.au
Subject: Re: kexec does not work for kernel version with patch level >= 256
Date: Thu, 01 Apr 2021 12:50:19 -0500	[thread overview]
Message-ID: <m1mtuhq4h0.fsf@fess.ebiederm.org> (raw)
In-Reply-To: <CAO7dBbWPcjOTcugLkpV9S9uOEhetCg=MiW=xDbAX4EAotBMOHg@mail.gmail.com> (Liu Tao's message of "Thu, 1 Apr 2021 15:11:56 +0800")

Liu Tao <ltao@redhat.com> writes:

> Hello Eric,
>
> I'd like to have a try on this issue.
> Since I'm not very familiar with the related code, maybe I need to spend a
> little more time on it.

Please give it a shot.

Getting rid of explicit kernel version checks would be wonderful and
prevent future problems as well.

Eric

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

  parent reply	other threads:[~2021-04-01 17:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-24  4:28 kexec does not work for kernel version with patch level >= 256 Patrick Sung
2021-03-31  2:47 ` Baoquan He
2021-03-31  3:04   ` Patrick Sung
2021-03-31  3:48     ` Baoquan He
2021-03-31  8:03       ` Baoquan He
2021-03-31  8:10         ` Greg KH
2021-03-31 14:05           ` Eric W. Biederman
     [not found]             ` <CAO7dBbWPcjOTcugLkpV9S9uOEhetCg=MiW=xDbAX4EAotBMOHg@mail.gmail.com>
2021-04-01 17:50               ` Eric W. Biederman [this message]
     [not found]                 ` <CAO7dBbU=Q7yMKv-Hp8cUxgPffE=vxtKYvfP7NLKejf-Q8x+H=w@mail.gmail.com>
2021-04-07 17:23                   ` Eric W. Biederman

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=m1mtuhq4h0.fsf@fess.ebiederm.org \
    --to=ebiederm@xmission.com \
    --cc=bhe@redhat.com \
    --cc=dyoung@redhat.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=horms@verge.net.au \
    --cc=kexec@lists.infradead.org \
    --cc=ltao@redhat.com \
    --cc=patricksung@gmail.com \
    --cc=sashal@kernel.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