From: Pavel Roskin <proski@gnu.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] Split big and little endian BeFS and AtheFS
Date: Thu, 20 Aug 2009 18:16:24 -0400 [thread overview]
Message-ID: <1250806584.2668.61.camel@mj> (raw)
In-Reply-To: <d7ead6de0908190305o39906fbo3ac31665d050ca75@mail.gmail.com>
On Wed, 2009-08-19 at 12:05 +0200, Vladimir 'phcoder' Serbinenko wrote:
> > I'm fine with the split, but please use something more descriptive than
> > U16, U32 and U64. Maybe fs_to_cpu16() etc.
> >
> U* was here before me but here is a patch w/o them
Sorry, I didn't realize that. Then maybe it would be better to apply
that part separately after the split.
Please define macros with arguments. It makes the code more readable.
Please don't introduce excessively long lines in *.rmk files. Newlines
are cheap :-)
I don't think we should rename "byte_order" to "unused". Just because
we doesn't use it now to determine the endianess, it doesn't mean that
the field becomes meaningless. We may want to check it in the future.
There are other fields in the superblock that we don't use, such as
"flags", yet we don't rename them to "unusedN".
Apart from that, I'm fine with the patch.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2009-08-20 22:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-14 20:53 [PATCH] Split big and little endian BeFS and AtheFS Vladimir 'phcoder' Serbinenko
2009-08-14 22:00 ` Pavel Roskin
2009-08-19 10:05 ` Vladimir 'phcoder' Serbinenko
2009-08-20 22:16 ` Pavel Roskin [this message]
2009-08-20 22:47 ` Vladimir 'phcoder' Serbinenko
2009-08-23 10:40 ` Robert Millan
2009-08-23 11:04 ` Vladimir 'phcoder' Serbinenko
2009-08-23 23:09 ` Robert Millan
2009-08-28 13:02 ` Vladimir 'phcoder' Serbinenko
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=1250806584.2668.61.camel@mj \
--to=proski@gnu.org \
--cc=grub-devel@gnu.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 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.