All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Simon Horman <horms@verge.net.au>
Cc: Chris Mason <clm@fb.com>, kexec@lists.infradead.org
Subject: Re: [PATCH 2/2] kexec: remove ordering constraints from -x (--no-ifdown) and -y (--no-sync)
Date: Mon, 13 Apr 2015 13:01:56 -0400	[thread overview]
Message-ID: <20150413170156.GH2596@htj.duckdns.org> (raw)
In-Reply-To: <20150326191644.GF1953@htj.duckdns.org>

On Thu, Mar 26, 2015 at 03:16:44PM -0400, Tejun Heo wrote:
> From 81b5889b49f0f2448c3e9543c5c936d52348910c Mon Sep 17 00:00:00 2001
> From: Tejun Heo <tj@kernel.org>
> Date: Thu, 26 Mar 2015 15:11:09 -0400
> 
> Currently, the two options must be the last ones to be honored;
> otherwise, they can get silently ignored and both the manpage and help
> text point it out.  This is error-prone and trivial to fix.  There
> isn't much point in pointing something out in documentation when the
> peculiarity can be removed with four lines of extra code.
> 
> Update option handling so that the two arguments are honored
> regardless of their positions.
> 
> Signed-off-by: Tejun Heo <tj@kernel.org>

Ping?

Thanks.

-- 
tejun

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

  reply	other threads:[~2015-04-13 17:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-26 19:16 [PATCH 1/2] kexec: implement -y (--no-sync) option Tejun Heo
2015-03-26 19:16 ` [PATCH 2/2] kexec: remove ordering constraints from -x (--no-ifdown) and -y (--no-sync) Tejun Heo
2015-04-13 17:01   ` Tejun Heo [this message]
2015-04-14  0:29     ` Simon Horman
2015-04-14 12:15       ` [PATCH REPOST 1/2] kexec: implement -y (--no-sync) option Tejun Heo
2015-04-14 12:16         ` [PATCH REPOST 2/2] kexec: remove ordering constraints from -x (--no-ifdown) and -y (--no-sync) Tejun Heo
2015-04-15  1:09         ` [PATCH REPOST 1/2] kexec: implement -y (--no-sync) option Simon Horman
2015-04-15  2:42           ` Tejun Heo

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=20150413170156.GH2596@htj.duckdns.org \
    --to=tj@kernel.org \
    --cc=clm@fb.com \
    --cc=horms@verge.net.au \
    --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 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.