From: Greg KH <gregkh@linuxfoundation.org>
To: Himanshu Jha <himanshujha199640@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drivers: staging: rtl8192e: make const qualified argument
Date: Tue, 22 Aug 2017 18:36:03 -0700 [thread overview]
Message-ID: <20170823013603.GC3319@kroah.com> (raw)
In-Reply-To: <1503415862-16551-1-git-send-email-himanshujha199640@gmail.com>
On Tue, Aug 22, 2017 at 09:01:02PM +0530, Himanshu Jha wrote:
> The ether_addr_copy expects const u8* as its second argument, therefore
> pass const qualified argument instead of non-const argument.
Huh, why?
>
> Signed-off-by: Himanshu Jha <himanshujha199640@gmail.com>
> ---
> drivers/staging/rtl8192e/rtl819x_BAProc.c | 13 ++++++-------
> 1 file changed, 6 insertions(+), 7 deletions(-)
Always use scripts/get_maintainer.pl on your patch to know who to send
it to, and what lists as well.
>
> diff --git a/drivers/staging/rtl8192e/rtl819x_BAProc.c b/drivers/staging/rtl8192e/rtl819x_BAProc.c
> index 1720e1b..f34a4ee 100644
> --- a/drivers/staging/rtl8192e/rtl819x_BAProc.c
> +++ b/drivers/staging/rtl8192e/rtl819x_BAProc.c
> @@ -97,10 +97,9 @@ static struct sk_buff *rtllib_ADDBA(struct rtllib_device *ieee, u8 *Dst,
>
> BAReq = skb_put(skb, sizeof(struct rtllib_hdr_3addr));
>
> - ether_addr_copy(BAReq->addr1, Dst);
> - ether_addr_copy(BAReq->addr2, ieee->dev->dev_addr);
> -
> - ether_addr_copy(BAReq->addr3, ieee->current_network.bssid);
> + ether_addr_copy(BAReq->addr1, (const u8 *)Dst);
> + ether_addr_copy(BAReq->addr2, (const u8 *)ieee->dev->dev_addr);
> + ether_addr_copy(BAReq->addr3, (const u8 *)ieee->current_network.bssid);
I don't understand what this patch "solves"...
thanks,
greg k-h
prev parent reply other threads:[~2017-08-23 1:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-22 15:31 [PATCH] drivers: staging: rtl8192e: make const qualified argument Himanshu Jha
2017-08-23 1:36 ` 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=20170823013603.GC3319@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=himanshujha199640@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