From: Karel Zak <kzak@redhat.com>
To: Davidlohr Bueso <dave@gnu.org>
Cc: util-linux <util-linux@vger.kernel.org>
Subject: Re: [PATCH 3/5] sfdisk: do not depend on arch for packed attribute
Date: Thu, 5 Jan 2012 17:29:34 +0100 [thread overview]
Message-ID: <20120105162934.GC11073@x2.net.home> (raw)
In-Reply-To: <1325718131.7056.6.camel@offbook> <1325718126.7056.5.camel@offbook> <1325716139.7056.1.camel@offbook> <1324994959-24298-1-git-send-email-gaowanlong@cn.fujitsu.com> <1324388527.3316.10.camel@offbook> <1324388525.3316.9.camel@offbook>
On Tue, Dec 20, 2011 at 02:42:05PM +0100, Davidlohr Bueso wrote:
> fdisk/sfdisk.c | 9 ---------
> include/c.h | 3 +++
> 2 files changed, 3 insertions(+), 9 deletions(-)
On Tue, Dec 20, 2011 at 02:42:07PM +0100, Davidlohr Bueso wrote:
> fdisk/fdisk.h | 6 ------
> 1 files changed, 0 insertions(+), 6 deletions(-)
I have removed the PACKED macro at all and used __attribute__
keyword in the code.
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2012-01-05 16:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-04 23:02 [PATCH 2/2] sfdisk: use is_blkdev Davidlohr Bueso
2012-01-04 23:02 ` [PATCH 1/2] blkdev: add is_blkdev function Davidlohr Bueso
2012-01-04 22:28 ` [PATCH] lscpu: fix compiler warnings Davidlohr Bueso
[not found] ` <1324994959-24298-1-git-send-email-gaowanlong@cn.fujitsu.com>
2011-12-20 13:42 ` [PATCH 4/5] fdisk: remove packed definitions Davidlohr Bueso
2011-12-20 13:42 ` [PATCH 3/5] sfdisk: do not depend on arch for packed attribute Davidlohr Bueso
2012-01-05 16:29 ` Karel Zak [this message]
2011-12-22 2:33 ` [PATCH 4/5] fdisk: remove packed definitions Guillem Jover
2012-01-05 16:30 ` [PATCH] lscpu: fix compiler warnings Karel Zak
2012-01-05 16:31 ` [PATCH 1/2] blkdev: add is_blkdev function Karel Zak
2012-01-05 16:31 ` [PATCH 2/2] sfdisk: use is_blkdev Karel Zak
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=20120105162934.GC11073@x2.net.home \
--to=kzak@redhat.com \
--cc=dave@gnu.org \
--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;
as well as URLs for NNTP newsgroup(s).