From: Greg KH <gregkh@linuxfoundation.org>
To: Jaya Durga <jayad@cdac.in>
Cc: devel@driverdev.osuosl.org, florian.c.schilhabel@googlemail.com,
driverdev-devel@linuxdriverproject.org,
linux-kernel@vger.kernel.org, Larry.Finger@lwfinger.net
Subject: Re: [PATCH 9/9] Staging: rtl8712: ieee80211: fixed camelcase coding style issue
Date: Tue, 13 Jun 2017 14:57:12 +0200 [thread overview]
Message-ID: <20170613125712.GC14290@kroah.com> (raw)
In-Reply-To: <1497205677-19665-3-git-send-email-jayad@cdac.in>
On Sun, Jun 11, 2017 at 11:57:57PM +0530, Jaya Durga wrote:
> Fixed coding style issue
>
> Renamed Ssid to ssid
> Renamed Ssid_Length to ssid_length
>
> Signed-off-by: Jaya Durga <jayad@cdac.in>
Where are patches 1-8 of this series?
next prev parent reply other threads:[~2017-06-13 12:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-11 18:27 [PATCH 7/9] Staging: rtl8712: ieee80211: fixed camelcase coding style issue Jaya Durga
2017-06-11 18:27 ` [PATCH 8/9] " Jaya Durga
2017-06-11 18:27 ` [PATCH 9/9] " Jaya Durga
2017-06-13 12:57 ` Greg KH [this message]
2017-06-13 12:57 ` [PATCH 7/9] " Greg KH
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=20170613125712.GC14290@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Larry.Finger@lwfinger.net \
--cc=devel@driverdev.osuosl.org \
--cc=driverdev-devel@linuxdriverproject.org \
--cc=florian.c.schilhabel@googlemail.com \
--cc=jayad@cdac.in \
--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