All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brian King <brking@linux.vnet.ibm.com>
To: ebiederm@xmission.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: Mon, 04 Aug 2014 09:21:25 -0500	[thread overview]
Message-ID: <53DF96E5.7000601@linux.vnet.ibm.com> (raw)
In-Reply-To: <53D6B270.5020403@linux.vnet.ibm.com>

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?

Thanks!

Brian


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

WARNING: multiple messages have this Message-ID (diff)
From: Brian King <brking@linux.vnet.ibm.com>
To: ebiederm@xmission.com
Cc: "James E.J. Bottomley" <JBottomley@parallels.com>,
	linux-scsi <linux-scsi@vger.kernel.org>,
	Wendy Xiong <wenxiong@linux.vnet.ibm.com>,
	kexec@lists.infradead.org
Subject: Re: [PATCH 2/5] kexec: Export kexec_in_progress
Date: Mon, 04 Aug 2014 09:21:25 -0500	[thread overview]
Message-ID: <53DF96E5.7000601@linux.vnet.ibm.com> (raw)
In-Reply-To: <53D6B270.5020403@linux.vnet.ibm.com>

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?

Thanks!

Brian


  reply	other threads:[~2014-08-04 14:21 UTC|newest]

Thread overview: 10+ 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-07-28 20:28 ` Brian King
2014-08-04 14:21 ` Brian King [this message]
2014-08-04 14:21   ` Brian King
2014-08-29 15:38   ` Brian King
2014-08-29 15:38     ` Brian King
2014-08-30 20:02     ` Eric W. Biederman
2014-08-30 20:02       ` Eric W. Biederman
2014-09-02 19:46       ` Brian King
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=53DF96E5.7000601@linux.vnet.ibm.com \
    --to=brking@linux.vnet.ibm.com \
    --cc=JBottomley@parallels.com \
    --cc=ebiederm@xmission.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.