From: ebiederm@xmission.com (Eric W. Biederman)
To: Brian King <brking@linux.vnet.ibm.com>
Cc: kexec@lists.infradead.org,
Wendy Xiong <wenxiong@linux.vnet.ibm.com>,
linux-scsi <linux-scsi@vger.kernel.org>,
"James E.J. Bottomley" <JBottomley@parallels.com>
Subject: Re: [PATCH 2/5] kexec: Export kexec_in_progress
Date: Sat, 30 Aug 2014 15:02:10 -0500 [thread overview]
Message-ID: <87wq9piw59.fsf@x220.int.ebiederm.org> (raw)
In-Reply-To: <54009E8A.4070809@linux.vnet.ibm.com> (Brian King's message of "Fri, 29 Aug 2014 10:38:50 -0500")
Brian King <brking@linux.vnet.ibm.com> writes:
> On 08/04/2014 09:21 AM, Brian King wrote:
>> On 07/28/2014 03:28 PM, Brian King wrote:
>>>
>>> Export kexec_in_progress for use by device drivers and other modules
>>> to optimize kexec boot.
>>>
>>> Signed-off-by: Brian King <brking@linux.vnet.ibm.com>
>>> ---
>>>
>>> kernel/kexec.c | 2 ++
>>> 1 file changed, 2 insertions(+)
>>>
>>> diff -puN kernel/kexec.c~kexec_export_in_prog kernel/kexec.c
>>> --- linux/kernel/kexec.c~kexec_export_in_prog 2014-07-23 17:05:24.851887935 -0500
>>> +++ linux-bjking1/kernel/kexec.c 2014-07-23 17:05:24.856887970 -0500
>>> @@ -1716,3 +1716,5 @@ int kernel_kexec(void)
>>> mutex_unlock(&kexec_mutex);
>>> return error;
>>> }
>>> +
>>> +EXPORT_SYMBOL_GPL(kexec_in_progress);
>>
>> Eric,
>>
>> Can I get an ack on this so we can take this entire series through the SCSI tree?
>
> Eric,
>
> Any issues with this patch?
No huge issues except that patch description is largely uniformitive and
actually wrong. kexec_in_progress is never set at boot/kernel startup.
Eric
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2014-08-30 20:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-28 20:28 [PATCH 2/5] kexec: Export kexec_in_progress Brian King
2014-08-04 14:21 ` Brian King
2014-08-29 15:38 ` Brian King
2014-08-30 20:02 ` Eric W. Biederman [this message]
2014-09-02 19:46 ` Brian King
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=87wq9piw59.fsf@x220.int.ebiederm.org \
--to=ebiederm@xmission.com \
--cc=JBottomley@parallels.com \
--cc=brking@linux.vnet.ibm.com \
--cc=kexec@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=wenxiong@linux.vnet.ibm.com \
/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