All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Chris Mason <clm@fb.com>,
	Nikolay Borisov <n.borisov.lkml@gmail.com>,
	Josef Bacik <jbacik@fb.com>,
	kernel-janitors@vger.kernel.org, linux-btrfs@vger.kernel.org
Subject: Re: [patch] btrfs: white space cleanup in btrfs_log_inode()
Date: Thu, 26 Jan 2017 09:40:59 +0100	[thread overview]
Message-ID: <20170126084059.GB11951@suse.cz> (raw)
In-Reply-To: <20170125151126.GA27572@mwanda>

On Wed, Jan 25, 2017 at 06:11:26PM +0300, Dan Carpenter wrote:
> We accidentally deleted a new line in commit 0921910aa6fe ("btrfs: Make
> btrfs_log_inode take btrfs_inode")

Thanks, I've folded the change to the patch that introduced it.

WARNING: multiple messages have this Message-ID (diff)
From: David Sterba <dsterba@suse.cz>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Chris Mason <clm@fb.com>,
	Nikolay Borisov <n.borisov.lkml@gmail.com>,
	Josef Bacik <jbacik@fb.com>,
	kernel-janitors@vger.kernel.org, linux-btrfs@vger.kernel.org
Subject: Re: [patch] btrfs: white space cleanup in btrfs_log_inode()
Date: Thu, 26 Jan 2017 08:40:59 +0000	[thread overview]
Message-ID: <20170126084059.GB11951@suse.cz> (raw)
In-Reply-To: <20170125151126.GA27572@mwanda>

On Wed, Jan 25, 2017 at 06:11:26PM +0300, Dan Carpenter wrote:
> We accidentally deleted a new line in commit 0921910aa6fe ("btrfs: Make
> btrfs_log_inode take btrfs_inode")

Thanks, I've folded the change to the patch that introduced it.

  reply	other threads:[~2017-01-26  8:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-25 15:11 [patch] btrfs: white space cleanup in btrfs_log_inode() Dan Carpenter
2017-01-25 15:11 ` Dan Carpenter
2017-01-26  8:40 ` David Sterba [this message]
2017-01-26  8:40   ` David Sterba

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=20170126084059.GB11951@suse.cz \
    --to=dsterba@suse.cz \
    --cc=clm@fb.com \
    --cc=dan.carpenter@oracle.com \
    --cc=jbacik@fb.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=n.borisov.lkml@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 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.