From: Riccardo Marotti <riccardo.marotti@gmail.com>
To: gregkh@linuxfoundation.org
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Staging: rtl8192u: ieee80211: ieee80211_module.c: fix style issue
Date: Sun, 7 May 2017 10:49:39 +0200 [thread overview]
Message-ID: <1361b10b-2ba0-13db-8d27-3d31b38ea789@gmail.com> (raw)
In-Reply-To: <20170507064750.3524-1-riccardo.marotti@gmail.com>
On 05/07/2017 08:47 AM, Riccardo Marotti wrote:
> From: Riccardo <riccardo.marotti@gmail.com>
>
> Fixed a brace coding style issue, found via checkpatch.
>
> Signed-off-by: Riccardo Marotti <riccardo.marotti@gmail.com>
> ---
> drivers/staging/rtl8192u/ieee80211/ieee80211_module.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/drivers/staging/rtl8192u/ieee80211/ieee80211_module.c b/drivers/staging/rtl8192u/ieee80211/ieee80211_module.c
> index a791175b86f5..8f236b332a47 100644
> --- a/drivers/staging/rtl8192u/ieee80211/ieee80211_module.c
> +++ b/drivers/staging/rtl8192u/ieee80211/ieee80211_module.c
> @@ -157,8 +157,7 @@ struct net_device *alloc_ieee80211(int sizeof_priv)
> ieee80211_softmac_init(ieee);
>
> ieee->pHTInfo = kzalloc(sizeof(RT_HIGH_THROUGHPUT), GFP_KERNEL);
> - if (ieee->pHTInfo == NULL)
> - {
> + if (ieee->pHTInfo == NULL) {
> IEEE80211_DEBUG(IEEE80211_DL_ERR, "can't alloc memory for HTInfo\n");
> goto failed;
> }
>
I'm really sorry... this was sent by mistake...
next prev parent reply other threads:[~2017-05-07 23:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-07 6:47 [PATCH] Staging: rtl8192u: ieee80211: ieee80211_module.c: fix style issue Riccardo Marotti
2017-05-07 8:49 ` Riccardo Marotti [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-05-04 20:06 Riccardo
[not found] ` <20170507031413.GB30688@kroah.com>
2017-05-07 6:45 ` Riccardo Marotti
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=1361b10b-2ba0-13db-8d27-3d31b38ea789@gmail.com \
--to=riccardo.marotti@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.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).