From: Artem Bityutskiy <dedekind1@gmail.com>
To: Seunghun Lee <waydi1@gmail.com>
Cc: adrian.hunter@intel.com, linux-mtd@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] UBIFS: fix some comments
Date: Tue, 01 Jul 2014 17:57:14 +0300 [thread overview]
Message-ID: <1404226634.6841.121.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <1404225925-3347-1-git-send-email-waydi1@gmail.com>
On Tue, 2014-07-01 at 23:45 +0900, Seunghun Lee wrote:
> This patch fixes some comments about return type.
>
> Signed-off-by: Seunghun Lee <waydi1@gmail.com>
Pushed to linux-ubifs.git, thanks!
--
Best Regards,
Artem Bityutskiy
next prev parent reply other threads:[~2014-07-01 14:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-01 14:45 [PATCH] UBIFS: fix some comments Seunghun Lee
2014-07-01 14:57 ` Artem Bityutskiy [this message]
2014-07-01 15:27 ` Randy Dunlap
2014-07-01 15:31 ` Artem Bityutskiy
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=1404226634.6841.121.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=adrian.hunter@intel.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=waydi1@gmail.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).