From: Roman Storozhenko <romeusmeister@gmail.com>
To: lustre-devel@lists.lustre.org
Subject: [lustre-devel] [PATCH v3] staging: lustre: Replace 'uint32_t' with 'u32' and 'uint64_t' with 'u64'
Date: Tue, 5 Dec 2017 16:48:01 +0300 [thread overview]
Message-ID: <20171205134801.GA707@home> (raw)
In-Reply-To: <20171204195823.yiwitsbbhcywwa3m@mwanda>
On Mon, Dec 04, 2017 at 10:58:23PM +0300, Dan Carpenter wrote:
> On Wed, Nov 29, 2017 at 07:46:21PM +0300, Roman Storozhenko wrote:
> > There are two reasons for that:
>
> What I'm asking is there are two reasons for what? Where is the first
> part of that paragraph?
Hello, Dan!
Now I understand what did you mean. I shouldn't have written reason in
the subject line and reference to it as 'that' in the body.
Thanks for you mentioned that. In the following patches I will avoid
such types of mistakes.
Regards,
Romans Storozhenko
>
> regards,
> dan carpenter
>
prev parent reply other threads:[~2017-12-05 13:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-29 16:46 [lustre-devel] [PATCH v3] staging: lustre: Replace 'uint32_t' with 'u32' and 'uint64_t' with 'u64' Roman Storozhenko
2017-11-30 6:08 ` Dan Carpenter
2017-12-04 19:45 ` Roman Storozhenko
2017-12-04 20:01 ` Dan Carpenter
2017-12-04 19:58 ` Dan Carpenter
2017-12-05 13:48 ` Roman Storozhenko [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=20171205134801.GA707@home \
--to=romeusmeister@gmail.com \
--cc=lustre-devel@lists.lustre.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.