From: Zdenek Kabelac <zkabelac@redhat.com>
To: lvm-devel@redhat.com
Subject: [PATCH 0/6] Misc code updates
Date: Wed, 7 Jul 2010 14:29:30 +0200 [thread overview]
Message-ID: <cover.1278505444.git.zkabelac@redhat.com> (raw)
Small patchset contains various bits of code I keep in front of my tree.
First strict-aliasing is a bit contraversional and needs bigger review.
Configure patch basicaly cleanups help strings with the use of
AC_HELP_STRING.
Nextbit patch is tiny code optimization.
Backtrace patch skips printing of backtrace in the log if the situation
is not an error case.
Memlock slightly modifies memory map printing.
Last patch for dmsetup returns '0' exist status when showing option help.
Zdenek Kabelac (6):
Fix compiler warning about strict-aliasing break
configure changes - AC_HELP_STRING, AH_TEMPLATE
nextbit
Do not show backtrace
Better alligned debug message - memlock
Exit status 0 for 'dmsetup -c -o help'
configure | 100 +++++++++++++++++++++------------------------
configure.in | 76 +++++++++++++++++++---------------
lib/activate/activate.c | 6 ++-
lib/device/device.c | 18 ++++----
lib/mm/memlock.c | 7 ++-
libdm/datastruct/bitset.c | 4 +-
tools/dmsetup.c | 1 +
7 files changed, 109 insertions(+), 103 deletions(-)
next reply other threads:[~2010-07-07 12:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-07 12:29 Zdenek Kabelac [this message]
2010-07-07 12:29 ` [PATCH 1/6] Fix compiler warning about strict-aliasing break Zdenek Kabelac
2010-10-06 15:04 ` Petr Rockai
2010-07-07 12:29 ` [PATCH 2/6] configure changes - AC_HELP_STRING, AH_TEMPLATE Zdenek Kabelac
2010-07-07 18:10 ` Alasdair G Kergon
2010-07-07 12:29 ` [PATCH 3/6] nextbit Zdenek Kabelac
2010-07-07 18:49 ` Alasdair G Kergon
2010-07-07 12:29 ` [PATCH 4/6] Do not show backtrace Zdenek Kabelac
2010-07-07 18:54 ` Alasdair G Kergon
2010-07-07 12:29 ` [PATCH 5/6] Better alligned debug message - memlock Zdenek Kabelac
2010-07-07 18:19 ` Alasdair G Kergon
2010-07-07 12:29 ` [PATCH 6/6] Exit status 0 for 'dmsetup -c -o help' Zdenek Kabelac
2010-07-07 18:16 ` Alasdair G Kergon
2010-07-08 15:46 ` Zdenek Kabelac
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=cover.1278505444.git.zkabelac@redhat.com \
--to=zkabelac@redhat.com \
--cc=lvm-devel@redhat.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.