From: Al Viro <viro@ftp.linux.org.uk>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Re: [PATCH 1/2] GFS2: struct gfs2_rindex vs char buf[] cleanup
Date: Mon, 13 Nov 2006 21:32:17 +0000 [thread overview]
Message-ID: <20061113213217.GU29920@ftp.linux.org.uk> (raw)
In-Reply-To: <20061113205531.GB4971@martell.zuzino.mipt.ru>
On Mon, Nov 13, 2006 at 11:55:31PM +0300, Alexey Dobriyan wrote:
> Looks like the following code is needed to just save a cast:
>
> char buf[sizeof(struct gfs2_rindex)];
>
> Name things by their names. Also, patch will make endian annotations
> more complete.
Is that against mainline or against gfs2 tree? The later has a pile
of endianness annotations in it...
WARNING: multiple messages have this Message-ID (diff)
From: Al Viro <viro@ftp.linux.org.uk>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: Steven Whitehouse <swhiteho@redhat.com>,
cluster-devel@redhat.com, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 1/2] GFS2: struct gfs2_rindex vs char buf[] cleanup
Date: Mon, 13 Nov 2006 21:32:17 +0000 [thread overview]
Message-ID: <20061113213217.GU29920@ftp.linux.org.uk> (raw)
In-Reply-To: <20061113205531.GB4971@martell.zuzino.mipt.ru>
On Mon, Nov 13, 2006 at 11:55:31PM +0300, Alexey Dobriyan wrote:
> Looks like the following code is needed to just save a cast:
>
> char buf[sizeof(struct gfs2_rindex)];
>
> Name things by their names. Also, patch will make endian annotations
> more complete.
Is that against mainline or against gfs2 tree? The later has a pile
of endianness annotations in it...
next prev parent reply other threads:[~2006-11-13 21:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-13 20:55 [Cluster-devel] [PATCH 1/2] GFS2: struct gfs2_rindex vs char buf[] cleanup Alexey Dobriyan
2006-11-13 20:55 ` Alexey Dobriyan
2006-11-13 21:32 ` Al Viro [this message]
2006-11-13 21:32 ` Al Viro
2006-11-13 21:42 ` [Cluster-devel] " Alexey Dobriyan
2006-11-13 21:42 ` Alexey Dobriyan
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=20061113213217.GU29920@ftp.linux.org.uk \
--to=viro@ftp.linux.org.uk \
/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.