linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Quigley <sqawesome99@gmail.com>
To: Philippe Loctaux <phil@philippeloctaux.com>, clm@fb.com
Cc: jbacik@fb.com, dsterba@suse.com, linux-btrfs@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Btrfs: async: fixed a brace coding style issue
Date: Sun, 21 Feb 2016 15:08:02 -0600	[thread overview]
Message-ID: <56CA2732.7020106@gmail.com> (raw)
In-Reply-To: <1456087842-29045-1-git-send-email-phil@philippeloctaux.com>



On 02/21/2016 02:50 PM, Philippe Loctaux wrote:
> Fixed a coding style issue.
>
> Signed-off-by: Philippe Loctaux <phil@philippeloctaux.com>
> ---
>   fs/btrfs/async-thread.c | 4 ++--
>   1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/fs/btrfs/async-thread.c b/fs/btrfs/async-thread.c
> index 5fb60ea..7914dd2 100644
> --- a/fs/btrfs/async-thread.c
> +++ b/fs/btrfs/async-thread.c
> @@ -227,9 +227,9 @@ static inline void thresh_exec_hook(struct __btrfs_workqueue *wq)
>   out:
>   	spin_unlock(&wq->thres_lock);
>   
> -	if (need_change) {
> +	if (need_change)
>   		workqueue_set_max_active(wq->normal_wq, wq->current_active);
> -	}
> +
>   }
>   
>   static void run_ordered_work(struct __btrfs_workqueue *wq)
I thought I proposed this exact patch...hmm...

  reply	other threads:[~2016-02-21 21:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-21 20:50 [PATCH] Btrfs: async: fixed a brace coding style issue Philippe Loctaux
2016-02-21 21:08 ` Simon Quigley [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-02-21 21:52 Philippe Loctaux

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=56CA2732.7020106@gmail.com \
    --to=sqawesome99@gmail.com \
    --cc=clm@fb.com \
    --cc=dsterba@suse.com \
    --cc=jbacik@fb.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=phil@philippeloctaux.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).