From: Greg KH <gregkh@linuxfoundation.org>
To: Janani Sankara Babu <jananis37@gmail.com>
Cc: insafonov@gmail.com, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V5] staging:rtl8188eu:core Rename CamelCase variables
Date: Fri, 1 Sep 2017 19:09:54 +0200 [thread overview]
Message-ID: <20170901170954.GA25866@kroah.com> (raw)
In-Reply-To: <1504249859-8861-1-git-send-email-jananis37@gmail.com>
On Fri, Sep 01, 2017 at 12:40:59PM +0530, Janani Sankara Babu wrote:
> This patch is created to solve the CamelCase issue. The members 'IEs'
> and 'IELength' of struct wlan_bssid_ex are being modified to 'ie' and
> 'ie_length' to solve the issue. And the places where these variables
> are referenced inside rtl8188eu driver are also changed.
>
> Signed-off-by: Janani Sankara Babu <jananis37@gmail.com>
> ---
> Changelog
> [Patch 1/2] : Replace 'IELength' and 'IEs' of struct wlan_bssid_ex with
> 'ie_length' and 'ies'
> [Patch 2/2] : Remove wrongly commented out lines from the code and rename
> 'ies' to 'ie' as per suggestions
> V3 : Merge all changes into single patch
> V4 : Rebased the patch
> V5 : Added the changelog
I have no idea what you rebased this against, but it still does not
apply:
checking file drivers/staging/rtl8188eu/core/rtw_ap.c
Hunk #4 FAILED at 119.
Hunk #5 FAILED at 129.
Hunk #13 FAILED at 583.
Hunk #26 FAILED at 1043.
Hunk #32 FAILED at 1719.
Hunk #33 FAILED at 1754.
Hunk #34 FAILED at 1763.
7 out of 34 hunks FAILED
checking file drivers/staging/rtl8188eu/core/rtw_cmd.c
checking file drivers/staging/rtl8188eu/core/rtw_ieee80211.c
checking file drivers/staging/rtl8188eu/core/rtw_ioctl_set.c
checking file drivers/staging/rtl8188eu/core/rtw_mlme.c
Hunk #9 succeeded at 1662 (offset -3 lines).
Hunk #10 succeeded at 1686 (offset -3 lines).
Hunk #11 succeeded at 1744 (offset -8 lines).
Hunk #12 succeeded at 1758 (offset -8 lines).
Hunk #13 succeeded at 1767 (offset -8 lines).
Hunk #14 succeeded at 1858 (offset -8 lines).
checking file drivers/staging/rtl8188eu/core/rtw_mlme_ext.c
Hunk #23 succeeded at 4953 (offset 2 lines).
Hunk #24 succeeded at 5012 (offset 2 lines).
Hunk #25 succeeded at 5390 (offset 2 lines).
checking file drivers/staging/rtl8188eu/core/rtw_wlan_util.c
checking file drivers/staging/rtl8188eu/hal/rtl8188e_cmd.c
checking file drivers/staging/rtl8188eu/include/wlan_bssdef.h
checking file drivers/staging/rtl8188eu/os_dep/ioctl_linux.c
prev parent reply other threads:[~2017-09-01 17:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-01 7:10 Janani Sankara Babu
2017-09-01 17:09 ` Greg KH [this message]
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=20170901170954.GA25866@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=devel@driverdev.osuosl.org \
--cc=insafonov@gmail.com \
--cc=jananis37@gmail.com \
--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
Powered by JetHome