All of lore.kernel.org
 help / color / mirror / Atom feed
From: Aya Mahfouz <mahfouz.saif.elyazal@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: outreachy-kernel@googlegroups.com
Subject: Re: [Outreachy kernel] [PATCH] staging: vt6656: replace memcpy by ether_addr_copy
Date: Fri, 27 Feb 2015 03:59:43 +0200	[thread overview]
Message-ID: <20150227015943.GA15393@waves> (raw)
In-Reply-To: <20150227015512.GA29726@kroah.com>

On Thu, Feb 26, 2015 at 05:55:12PM -0800, Greg KH wrote:
> On Fri, Feb 27, 2015 at 03:32:51AM +0200, Aya Mahfouz wrote:
> > On Thu, Feb 26, 2015 at 12:59:30PM -0800, Greg KH wrote:
> > > On Thu, Feb 26, 2015 at 10:32:44PM +0200, Aya Mahfouz wrote:
> > > > On Thu, Feb 26, 2015 at 10:28:27AM -0800, Greg KH wrote:
> > > > > On Tue, Feb 17, 2015 at 10:00:55PM +0200, Aya Mahfouz wrote:
> > > > > > This patch fixes the following checkpatch.pl warning:
> > > > > > 
> > > > > > Prefer ether_addr_copy() over memcpy() if the Ethernet addresses are
> > > > > > __aligned(2)
> > > > > > 
> > > > > > The changes were applied using the following coccinelle
> > > > > > rule: 
> > > > > > @@ expression e1, e2; @@
> > > > > > - memcpy(e1, e2, ETH_ALEN);
> > > > > > + ether_addr_copy(e1, e2); 
> > > > > > 
> > > > > > All variables defined in vnt_mac_set_key start at even offsets
> > > > > > making the variables aligned to the u16 datatype.
> > > > > > 
> > > > > > Signed-off-by: Aya Mahfouz <mahfouz.saif.elyazal@gmail.com>
> > > > > > ---
> > > > > >  drivers/staging/vt6656/mac.c | 2 +-
> > > > > >  1 file changed, 1 insertion(+), 1 deletion(-)
> > > > > > 
> > > > > > diff --git a/drivers/staging/vt6656/mac.c b/drivers/staging/vt6656/mac.c
> > > > > > index bb37e33..5958ecf 100644
> > > > > > --- a/drivers/staging/vt6656/mac.c
> > > > > > +++ b/drivers/staging/vt6656/mac.c
> > > > > > @@ -126,7 +126,7 @@ void vnt_mac_set_keyentry(struct vnt_private *priv, u16 key_ctl, u32 entry_idx,
> > > > > >  	offset += (entry_idx * MISCFIFO_KEYENTRYSIZE);
> > > > > >  
> > > > > >  	set_key.u.write.key_ctl = cpu_to_le16(key_ctl);
> > > > > > -	memcpy(set_key.u.write.addr, addr, ETH_ALEN);
> > > > > > +	ether_addr_copy(set_key.u.write.addr, addr);
> > > > > >  
> > > > > >  	/* swap over swap[0] and swap[1] to get correct write order */
> > > > > >  	swap(set_key.u.swap[0], set_key.u.swap[1]);
> > > > > 
> > > > > This patch breaks the build, please _always_ test build your patches :(
> > > > > 
> > > > > thanks,
> > > > > 
> > > > > greg k-h
> > > > 
> > > > Hello Greg,
> > > > 
> > > > I always do and I didn't get any warnings or erros when building it
> > > > before sending. If you have the time, please let me know what is the
> > > > error. 
> > > 
> > > The compiler does not know what ether_addr_copy() is.
> > > 
> > > > It also seems to be that you compile all warnings as errors, it would be
> > > > kind of you if you let me know your build settings.
> > > 
> > > I am building a "normal" x86-64 kernel with this driver enabled.  And
> > > no, I am not treating warnings as errors, but your patches should never
> > > be adding build warnings, that is not allowed either.
> > >
> > 
> > Yes, concerning warnings, you told me that before. It seems to me that
> > I'm compiling the modules in a wrong way. I usually use one of the
> > following commands, if compiling a module:
> > 
> > make -C $pwd SUBDIRS=drivers/staging/xxx modules
> > make M=drivers/staging/xxx
> 
> Both of those should work.
> 
> > The .o files were generated only after I broke the whole kernel build,
> > otherwise nothing is generated.
> > 
> > Any remedies?
> 
> I don't understand, what exactly was the errors?
> 
> It's usually just easiest to build the whole tree, you can do it quicker
> by doing:
> 	make -j16
> 
> replace the number with 2x the number of cpus you have, and you should
> be fine.
> 
> good luck,
> 
> greg k-h

ok, Thanks!
-- 
Kind Regards,
Aya Saif El-yazal Mahfouz


  reply	other threads:[~2015-02-27  1:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-17 20:00 [PATCH] staging: vt6656: replace memcpy by ether_addr_copy Aya Mahfouz
2015-02-26 18:28 ` [Outreachy kernel] " Greg KH
2015-02-26 20:32   ` Aya Mahfouz
2015-02-26 20:35     ` Julia Lawall
2015-02-26 20:41       ` Aya Mahfouz
2015-02-26 20:59     ` Greg KH
2015-02-27  1:32       ` Aya Mahfouz
2015-02-27  1:55         ` Greg KH
2015-02-27  1:59           ` Aya Mahfouz [this message]
2015-02-27  5:45             ` Julia Lawall
2015-02-27  5:53               ` Aya Mahfouz
2015-02-27  8:53                 ` Arnd Bergmann
2015-02-27 10:23                   ` Aya Mahfouz
  -- strict thread matches above, loose matches on Subject: below --
2015-02-21 11:32 [PATCH] Staging: " Yeliz Taneroglu
2015-02-21 14:22 ` [Outreachy kernel] " Julia Lawall

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=20150227015943.GA15393@waves \
    --to=mahfouz.saif.elyazal@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --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.