From: Jens Axboe <jens.axboe@oracle.com>
To: H Hartley Sweeten <hartleys@visionengravers.com>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] fs/bio.c: move EXPORT* macros to line after function
Date: Sat, 26 Sep 2009 16:15:21 +0200 [thread overview]
Message-ID: <20090926141521.GZ23126@kernel.dk> (raw)
In-Reply-To: <BD79186B4FD85F4B8E60E381CAEE190901D4276C@mi8nycmail19.Mi8.com>
On Fri, Sep 25 2009, H Hartley Sweeten wrote:
> As mentioned in Documentation/CodingStyle, move EXPORT* macro's
> to the line immediately after the closing function brace line.
>
> Signed-off-by: H Hartley Sweeten <hsweeten@visionengravers.com>
> Cc: Jens Axboe <jens.axboe@oracle.com>
Thanks, applied.
--
Jens Axboe
prev parent reply other threads:[~2009-09-26 14:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-25 23:10 [PATCH] fs/bio.c: move EXPORT* macros to line after function H Hartley Sweeten
2009-09-26 14:15 ` Jens Axboe [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=20090926141521.GZ23126@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=hartleys@visionengravers.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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).