All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Amitkumar Karwar <akarwar@marvell.com>,
	Zhaoyang Liu <liuzy@marvell.com>,
	Avinash Patil <patila@marvell.com>,
	linux-wireless@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: mwifiex: missing curly braces in mwifiex_write_data_complete()
Date: Fri, 20 Mar 2015 07:00:19 +0000	[thread overview]
Message-ID: <20150320070019.9A289140DB9@smtp.codeaurora.org> (raw)
In-Reply-To: <20150318082235.GC10434@mwanda>
In-Reply-To: <20150318082235.GC10434@mwanda>


> It's clear from the indenting that curly braces were intended here.
> 
> Fixes: e35000ead491 ('mwifiex: preprocess packets from TX queue')
> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>

Thanks, applied to wireless-drivers-next.git.

Kalle Valo

WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@codeaurora.org>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Amitkumar Karwar <akarwar@marvell.com>,
	Zhaoyang Liu <liuzy@marvell.com>,
	Avinash Patil <patila@marvell.com>,
	linux-wireless@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: mwifiex: missing curly braces in mwifiex_write_data_complete()
Date: Fri, 20 Mar 2015 07:00:19 +0000 (UTC)	[thread overview]
Message-ID: <20150320070019.9A289140DB9@smtp.codeaurora.org> (raw)
In-Reply-To: <20150318082235.GC10434@mwanda>


> It's clear from the indenting that curly braces were intended here.
> 
> Fixes: e35000ead491 ('mwifiex: preprocess packets from TX queue')
> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>

Thanks, applied to wireless-drivers-next.git.

Kalle Valo

  reply	other threads:[~2015-03-20  7:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-18  8:22 [patch] mwifiex: missing curly braces in mwifiex_write_data_complete() Dan Carpenter
2015-03-18  8:22 ` Dan Carpenter
2015-03-20  7:00 ` Kalle Valo [this message]
2015-03-20  7:00   ` Kalle Valo

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=20150320070019.9A289140DB9@smtp.codeaurora.org \
    --to=kvalo@codeaurora.org \
    --cc=akarwar@marvell.com \
    --cc=dan.carpenter@oracle.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=liuzy@marvell.com \
    --cc=patila@marvell.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.