All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Ioana Ciornei <ciorneiioana@gmail.com>
Cc: outreachy-kernel@googlegroups.com
Subject: Re: [Outreachy kernel] [PATCH v3] staging: p80211conv: Replace memcpy with ether_addr_copy
Date: Fri, 20 Mar 2015 13:21:58 +0100	[thread overview]
Message-ID: <20150320122158.GA4519@kroah.com> (raw)
In-Reply-To: <1426686607-11608-1-git-send-email-ciorneiioana@gmail.com>

On Wed, Mar 18, 2015 at 03:50:07PM +0200, Ioana Ciornei wrote:
> Replace memcpy() with ether_addr_copy() since addresses are __aligned(2).
> The 2 structures are aligned to u16:
> 
> struct p80211_hdr_a3 {
>         __le16 fc;              /* 0    2 */
>         u16 dur;                /* 2    2 */
>         u8 a1[ETH_ALEN];        /* 4    6 */
>         u8 a2[ETH_ALEN];        /* 10   6 */
>         u8 a3[ETH_ALEN];        /* 16   6 */
>         u16 seq;                /* 22   2 */
> } __packed;
> 
> Total size: 24
> 
> struct wlan_ethhdr {
>         u8 daddr[WLAN_ETHADDR_LEN];     /* 0    6 */
>         u8 saddr[WLAN_ETHADDR_LEN];     /* 6    6 */
>         u16 type;                       /* 12   2 */
> } __packed;
> 
> Total size: 14
> 
> Signed-off-by: Ioana Ciornei <ciorneiioana@gmail.com>
> ---
> 
> Changes in v3:
> 	- fixed corrupted patch

Please resend this again, after fixing the obvious build errors with it
:(

ALWAYS test build your patches, to not do so annoys the people you send
them to, as it breaks their workflow, and is a bit rude.

thanks,

greg k-h


  reply	other threads:[~2015-03-20 14:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-18 13:50 [PATCH v3] staging: p80211conv: Replace memcpy with ether_addr_copy Ioana Ciornei
2015-03-20 12:21 ` Greg KH [this message]
2015-03-20 22:16   ` [Outreachy kernel] " Ioana Ciornei

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=20150320122158.GA4519@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=ciorneiioana@gmail.com \
    --cc=outreachy-kernel@googlegroups.com \
    /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.