From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: LKML <linux-kernel@vger.kernel.org>,
Linux PM list <linux-pm@vger.kernel.org>
Subject: Re: [PATCH] Documentation: Fix typo in freezer-subsystem.txt
Date: Sun, 6 Nov 2011 22:03:52 +0100 [thread overview]
Message-ID: <201111062203.52842.rjw@sisk.pl> (raw)
In-Reply-To: <4EB6B7FB.3080005@xenotime.net>
On Sunday, November 06, 2011, Randy Dunlap wrote:
> On 11/05/2011 05:12 PM, Rafael J. Wysocki wrote:
> > From: Rafael J. Wysocki <rjw@sisk.pl>
> >
> > Fix a typo in Documentation/cgroups/freezer-subsystem.txt.
> >
> > Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
>
> Acked-by: Randy Dunlap <rdunlap@xenotime.net>
>
> You are welcome to merge this with PM patches.. or did you want
> me to merge it?
Well, I can do that. :-)
Thanks,
Rafael
> > ---
> > Documentation/cgroups/freezer-subsystem.txt | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > Index: linux-3.0-SLE11-SP2/Documentation/cgroups/freezer-subsystem.txt
> > ===================================================================
> > --- linux-3.0-SLE11-SP2.orig/Documentation/cgroups/freezer-subsystem.txt
> > +++ linux-3.0-SLE11-SP2/Documentation/cgroups/freezer-subsystem.txt
> > @@ -33,9 +33,9 @@ demonstrate this problem using nested ba
> >
> > From a second, unrelated bash shell:
> > $ kill -SIGSTOP 16690
> > - $ kill -SIGCONT 16990
> > + $ kill -SIGCONT 16690
> >
> > - <at this point 16990 exits and causes 16644 to exit too>
> > + <at this point 16690 exits and causes 16644 to exit too>
> >
> > This happens because bash can observe both signals and choose how it
> > responds to them.
> > --
>
>
>
prev parent reply other threads:[~2011-11-06 21:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-06 0:12 [PATCH] Documentation: Fix typo in freezer-subsystem.txt Rafael J. Wysocki
2011-11-06 9:40 ` Srivatsa S. Bhat
2011-11-06 16:38 ` Randy Dunlap
2011-11-06 21:03 ` Rafael J. Wysocki [this message]
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=201111062203.52842.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/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