From: Karel Zak <kzak@redhat.com>
To: Heiko Carstens <heiko.carstens@de.ibm.com>
Cc: util-linux@vger.kernel.org
Subject: Re: [PATCH 0/5] various small fixes and changes
Date: Sat, 10 Sep 2011 00:10:42 +0200 [thread overview]
Message-ID: <20110909220903.GF4204@nb> (raw)
In-Reply-To: <1315559974-26863-1-git-send-email-heiko.carstens@de.ibm.com>
On Fri, Sep 09, 2011 at 11:19:29AM +0200, Heiko Carstens wrote:
> just another bunch of small patches which are supposed to improve or
> fix some small things.
Merged, thanks!
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
prev parent reply other threads:[~2011-09-09 22:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-09 9:19 [PATCH 0/5] various small fixes and changes Heiko Carstens
2011-09-09 9:19 ` [PATCH 1/5] lib,cpuset: fix comments for cpu mask/list functions Heiko Carstens
2011-09-09 9:19 ` [PATCH 2/5] lib,cpuset: fix odd placed braces in cpulist_parse() Heiko Carstens
2011-09-09 9:19 ` [PATCH 3/5] lib,cpuset: fix stride handling " Heiko Carstens
2011-09-09 9:19 ` [PATCH 4/5] lib,cpuset: enforce stricter parsing of cpu lists Heiko Carstens
2011-09-09 9:19 ` [PATCH 5/5] chcpu,cpuset: reduce code duplication for cpu list parsing Heiko Carstens
2011-09-09 22:10 ` Karel Zak [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=20110909220903.GF4204@nb \
--to=kzak@redhat.com \
--cc=heiko.carstens@de.ibm.com \
--cc=util-linux@vger.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