From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: R Veera Kumar <vkor@vkten.in>
Cc: outreachy-kernel <outreachy-kernel@googlegroups.com>
Subject: Re: [PATCH v2 2/2] staging: rtl8723bs: os_dep: Remove whitespace characters in code line
Date: Fri, 20 Mar 2020 15:06:35 +0100 [thread overview]
Message-ID: <20200320140635.GD643325@kroah.com> (raw)
In-Reply-To: <7cf2a33375608b6c00713ba55234c9686af499a4.1584668433.git.vkor@vkten.in>
On Fri, Mar 20, 2020 at 07:17:30AM +0530, R Veera Kumar wrote:
> Remove five leading whitespace characters in code line.
>
> Signed-off-by: R Veera Kumar <vkor@vkten.in>
> ---
> drivers/staging/rtl8723bs/os_dep/recv_linux.c | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/staging/rtl8723bs/os_dep/recv_linux.c b/drivers/staging/rtl8723bs/os_dep/recv_linux.c
> index 87090af7d776..1502477e48bb 100644
> --- a/drivers/staging/rtl8723bs/os_dep/recv_linux.c
> +++ b/drivers/staging/rtl8723bs/os_dep/recv_linux.c
> @@ -79,8 +79,8 @@ _pkt *rtw_os_alloc_msdu_pkt(union recv_frame *prframe, u16 nSubframe_Length, u8
>
> if (sub_skb->len >= 8 &&
> ((!memcmp(sub_skb->data, rtw_rfc1042_header, SNAP_SIZE) &&
> - eth_type != ETH_P_AARP && eth_type != ETH_P_IPX) ||
> - !memcmp(sub_skb->data, rtw_bridge_tunnel_header, SNAP_SIZE))) {
> + eth_type != ETH_P_AARP && eth_type != ETH_P_IPX) ||
> + !memcmp(sub_skb->data, rtw_bridge_tunnel_header, SNAP_SIZE))) {
Again, this is just fine.
prev parent reply other threads:[~2020-03-20 14:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-20 1:47 [PATCH v2 0/2] staging: rtl8723bs: os_dep: Correct long line comments and remove whitespace in code R Veera Kumar
2020-03-20 1:47 ` [PATCH v2 1/2] staging: rtl8723bs: os_dep: Correct long line comments R Veera Kumar
2020-03-20 14:06 ` Greg Kroah-Hartman
2020-03-20 1:47 ` [PATCH v2 2/2] staging: rtl8723bs: os_dep: Remove whitespace characters in code line R Veera Kumar
2020-03-20 14:06 ` Greg Kroah-Hartman [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=20200320140635.GD643325@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=outreachy-kernel@googlegroups.com \
--cc=vkor@vkten.in \
/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.