From: Darrick J. Wong <darrick.wong@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] The comment should be started with 0x08.
Date: Thu, 24 Mar 2016 23:49:45 -0700 [thread overview]
Message-ID: <20160325064945.GC5812@birch.djwong.org> (raw)
In-Reply-To: <71604351584F6A4EBAE558C676F37CA48294663E@H3CMLB14-EX.srv.huawei-3com.com>
On Fri, Mar 25, 2016 at 02:02:36AM +0000, Guozhonghua wrote:
>
> struct ocfs2_extended_slot {
> /*00*/ __u8 es_valid;
> __u8 es_reserved1[3];
> __le32 es_node_num;
> -/*10*/
> +/*08*/
> };
>
>
> -------------------------------------------------------------------------------------------------------------------------------------
> ????????????????????????????????????????
> ????????????????????????????????????????
> ????????????????????????????????????????
> ???
> This e-mail and its attachments contain confidential information from H3C, which is
No signed-off-by and the message is confidential information too!
See section 11 of SubmittingPatches[1] and try again please.
--D
[1] https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/SubmittingPatches
> intended only for the person or entity whose address is listed above. Any use of the
> information contained herein in any way (including, but not limited to, total or partial
> disclosure, reproduction, or dissemination) by persons other than the intended
> recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender
> by phone or email immediately and delete it!
> _______________________________________________
> Ocfs2-devel mailing list
> Ocfs2-devel at oss.oracle.com
> https://oss.oracle.com/mailman/listinfo/ocfs2-devel
prev parent reply other threads:[~2016-03-25 6:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-25 2:02 [Ocfs2-devel] The comment should be started with 0x08 Guozhonghua
2016-03-25 6:49 ` Darrick J. Wong [this message]
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=20160325064945.GC5812@birch.djwong.org \
--to=darrick.wong@oracle.com \
--cc=ocfs2-devel@oss.oracle.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 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).