From: Bob Peterson <rpeterso@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH 02/12] trivial: GFS2: inode.c: indent with TABs, not spaces
Date: Fri, 1 May 2015 14:02:04 -0400 (EDT) [thread overview]
Message-ID: <118237089.10849205.1430503324657.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <1430219491-5076-3-git-send-email-ao2@ao2.it>
----- Original Message -----
> Follow the same style used for the other functions in the same file.
>
> Signed-off-by: Antonio Ospite <ao2@ao2.it>
> Cc: Steven Whitehouse <swhiteho@redhat.com>
> Cc: Bob Peterson <rpeterso@redhat.com>
> Cc: cluster-devel at redhat.com
> ---
> fs/gfs2/inode.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/fs/gfs2/inode.c b/fs/gfs2/inode.c
> index 1b3ca7a..efd6bfb 100644
> --- a/fs/gfs2/inode.c
> +++ b/fs/gfs2/inode.c
> @@ -1227,8 +1227,8 @@ static int gfs2_mknod(struct inode *dir, struct dentry
> *dentry, umode_t mode,
> */
>
> static int gfs2_atomic_open(struct inode *dir, struct dentry *dentry,
> - struct file *file, unsigned flags,
> - umode_t mode, int *opened)
> + struct file *file, unsigned flags,
> + umode_t mode, int *opened)
> {
> struct dentry *d;
> bool excl = !!(flags & O_EXCL);
> --
> 2.1.4
Hi,
Thanks. This is now applied to the for-next branch of the linux-gfs2 tree:
https://git.kernel.org/cgit/linux/kernel/git/gfs2/linux-gfs2.git/commit/fs/gfs2?h=for-next&id=86fbca4923f956dae31247e68dc73ffdfd6e5cb0
Regards,
Bob Peterson
Red Hat File Systems
prev parent reply other threads:[~2015-05-01 18:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1430219491-5076-1-git-send-email-ao2@ao2.it>
2015-04-28 11:11 ` [Cluster-devel] [PATCH 02/12] trivial: GFS2: inode.c: indent with TABs, not spaces Antonio Ospite
2015-05-01 18:02 ` Bob Peterson [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=118237089.10849205.1430503324657.JavaMail.zimbra@redhat.com \
--to=rpeterso@redhat.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).