From: Larry Finger <Larry.Finger@lwfinger.net>
To: Jagan Teki <jteki@openedev.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
devel@driverdev.osuosl.org,
Florian Schilhabel <florian.c.schilhabel@googlemail.com>,
Dan Carpenter <dan.carpenter@oracle.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH v3] staging: rtl8712: Use ether_addr_copy() instead of memcpy()
Date: Wed, 20 May 2015 14:57:31 -0500 [thread overview]
Message-ID: <555CE72B.5060402@lwfinger.net> (raw)
In-Reply-To: <CAD6G_RTekex0t7gJfbLtVf3mEcSzCiyE9sL8LMpQo4X0Z68cyg@mail.gmail.com>
On 05/20/2015 02:46 PM, Jagan Teki wrote:
> On 21 May 2015 at 01:10, Larry Finger <Larry.Finger@lwfinger.net> wrote:
>> On 05/20/2015 01:41 PM, Jagan Teki wrote:
>>>
>>> On 18 May 2015 at 22:02, Jagan Teki <jteki@openedev.com> wrote:
>>>>
>>>> Fixes Warning encounter this by applying checkpatch.pl against this file:
>>>> Prefer ether_addr_copy() over memcpy() if the Ethernet addresses
>>>> are __aligned(2)
>>>>
>>>> pahole output for respective structures:
>>>> - addr->sa_data
>>>> struct sockaddr {
>>>> sa_family_t sa_family; /* 0 2
>>>> */
>>>> char sa_data[14]; /* 2 14
>>>> */
>>>>
>>>> /* size: 16, cachelines: 1, members: 2 */
>>>> /* last cacheline: 16 bytes */
>>>> };
>>>>
>>>> - pnetdev->dev_addr
>>>> dev_addr is interface address infor from generic net_device structure
>>>> which is properly aligned and have some patches with this change as well.
>>>> "staging: rtl8712: fix Prefer ether_addr_copy() over memcpy()"
>>>> (sha1: 36e4d8826b317080e283e4edd08bf8d5ac706f38)
>>>>
>>>> Signed-off-by: Jagan Teki <jteki@openedev.com>
>>>> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>>>> Cc: Larry Finger <Larry.Finger@lwfinger.net>
>>>> Cc: Florian Schilhabel <florian.c.schilhabel@googlemail.com>
>>>> ---
>>>> Changes for v3:
>>>> - Removed unaligned conversions
>>>> Changes for v2:
>>>> - Describe a changelog, to prove address are aligned
>>>>
>>>> drivers/staging/rtl8712/os_intfs.c | 2 +-
>>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>>
>>>> diff --git a/drivers/staging/rtl8712/os_intfs.c
>>>> b/drivers/staging/rtl8712/os_intfs.c
>>>> index 6e776e5..d5f4c4d 100644
>>>> --- a/drivers/staging/rtl8712/os_intfs.c
>>>> +++ b/drivers/staging/rtl8712/os_intfs.c
>>>> @@ -181,7 +181,7 @@ static int r871x_net_set_mac_address(struct
>>>> net_device *pnetdev, void *p)
>>>> struct sockaddr *addr = p;
>>>>
>>>> if (padapter->bup == false)
>>>> - memcpy(pnetdev->dev_addr, addr->sa_data, ETH_ALEN);
>>>> + ether_addr_copy(pnetdev->dev_addr, addr->sa_data);
>>>> return 0;
>>>> }
>>>>
>>>> --
>>>
>>>
>>> Ping!
>>
>>
>> Ah. Not only are you ignorant, but you are also rude! The patch was not
>> NACKed, thus it will be picked up in good time.
>
> What are these statements, sending a patch with valid proofs implies rudeness?
> Does this patch still have changes..?
No, that patch (V3) is OK. Sending a ping after 2 days is most certainly rude.
That implies that no one has anything better to do than cater to your
submissions. As Greg told you, wait for a while.
Larry
prev parent reply other threads:[~2015-05-20 19:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-18 16:32 Jagan Teki
2015-05-20 18:41 ` Jagan Teki
2015-05-20 19:31 ` Dan Carpenter
2015-05-20 19:40 ` Larry Finger
2015-05-20 19:46 ` Jagan Teki
2015-05-20 19:57 ` Larry Finger [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=555CE72B.5060402@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=florian.c.schilhabel@googlemail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jteki@openedev.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