From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: [PATCH v2] F2FS support
Date: Thu, 07 May 2015 16:51:46 +0200 [thread overview]
Message-ID: <554B7C02.3000605@gmail.com> (raw)
In-Reply-To: <20150502201545.1ac3fead@opensuse.site>
[-- Attachment #1: Type: text/plain, Size: 239 bytes --]
> grub_uint8_t *addr;
>
> byte = nr >> 3;
> #ifdef WORDS_BIGENDIAN
#ifdef GRUB_CPU_WORDS_BIGENDIAN actually
Also in general it's very good idea to check on big-endian machines.
We don't add __ prefix to function names.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 213 bytes --]
next prev parent reply other threads:[~2015-05-07 14:52 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-24 8:19 [PATCH] F2FS support Jaegeuk Kim
2015-03-28 7:31 ` Andrei Borzenkov
2015-03-28 20:43 ` Jaegeuk Kim
2015-03-28 21:00 ` Andrei Borzenkov
2015-04-03 22:48 ` Jaegeuk Kim
2015-04-03 22:49 ` [PATCH v2] " Jaegeuk Kim
2015-04-29 20:48 ` [f2fs-dev] " Jaegeuk Kim
2015-04-30 3:32 ` Andrei Borzenkov
2015-05-02 17:15 ` Andrei Borzenkov
2015-05-03 6:28 ` Andrei Borzenkov
2015-05-07 14:51 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2015-05-07 14:57 ` Andrei Borzenkov
2015-11-19 21:28 ` [PATCH v3] " Jaegeuk Kim
2015-12-14 8:28 ` Andrei Borzenkov
2015-12-15 0:30 ` [f2fs-dev] " Jaegeuk Kim
2015-12-15 0:34 ` [f2fs-dev] [PATCH v4] " Jaegeuk Kim
2015-12-15 8:34 ` Andrei Borzenkov
2015-12-15 18:08 ` Jaegeuk Kim
2015-12-15 18:14 ` [f2fs-dev] [PATCH v5] " Jaegeuk Kim
2016-01-07 19:37 ` Michael Zimmermann
2016-01-08 19:41 ` [f2fs-dev] [PATCH v6] " Jaegeuk Kim
2016-02-22 9:25 ` Andrei Borzenkov
2016-02-22 18:21 ` Jaegeuk Kim
2016-02-22 18:25 ` [f2fs-dev] [PATCH v7] " Jaegeuk Kim
2016-03-01 19:52 ` [2.02] " Andrei Borzenkov
2016-03-02 23:20 ` Michael Zimmermann
2016-03-03 21:35 ` Jaegeuk Kim
2016-03-03 21:36 ` [2.02] Re: [f2fs-dev] [PATCH v8] " Jaegeuk Kim
2016-08-04 17:06 ` [f2fs-dev] [2.02] " Jaegeuk Kim
2016-08-05 10:57 ` Andrei Borzenkov
2016-08-05 18:07 ` Jaegeuk Kim
2016-08-05 19:17 ` Michael Zimmermann
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=554B7C02.3000605@gmail.com \
--to=phcoder@gmail.com \
--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 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).