From: Dan Carpenter <dan.carpenter@oracle.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Benedict Boerger <benedict.boerger@cs.tu-dortmund.de>,
matlackdavid@gmail.com, devel@driverdev.osuosl.org,
peter.p.waskiewicz.jr@intel.com, linux-kernel@vger.kernel.org,
liodot@gmail.com, charrer@alacritech.com,
Joe Perches <joe@perches.com>
Subject: Re: [PATCH] staging: slicoss: Fix coding style issue
Date: Mon, 16 Jun 2014 11:13:50 +0300 [thread overview]
Message-ID: <20140616081350.GC5500@mwanda> (raw)
In-Reply-To: <20140613170435.GA18608@kroah.com>
On Fri, Jun 13, 2014 at 10:04:35AM -0700, Greg KH wrote:
> On Fri, Jun 13, 2014 at 05:52:33PM +0200, Benedict Boerger wrote:
> > Fix a coding style issue found by checkpatch.pl.
> > Use ether_addr_copy instead of memcpy.
> >
> > Done to complete a eudyptula task.
> >
> > Signed-off-by: Benedict Boerger <benedict.boerger@cs.tu-dortmund.de>
> >
> > ---
> > drivers/staging/slicoss/slicoss.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/staging/slicoss/slicoss.c b/drivers/staging/slicoss/slicoss.c
> > index 48841e7..02807a3 100644
> > --- a/drivers/staging/slicoss/slicoss.c
> > +++ b/drivers/staging/slicoss/slicoss.c
> > @@ -1790,7 +1790,7 @@ static int slic_mcast_add_list(struct adapter *adapter, char *address)
> > if (mcaddr == NULL)
> > return 1;
> >
> > - memcpy(mcaddr->address, address, ETH_ALEN);
> > + ether_addr_copy(mcaddr->address, address);
> >
> > mcaddr->next = adapter->mcastaddrs;
> > adapter->mcastaddrs = mcaddr;
>
> Are you sure this is correct? It's not always a one-to-one replacement
> from what I have been told.
I hate this checkpatch.pl warning because it just encourages people to
add bugs.
regards,
dan carpenter
prev parent reply other threads:[~2014-06-16 8:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-13 15:52 [PATCH] staging: slicoss: Fix coding style issue Benedict Boerger
2014-06-13 17:04 ` Greg KH
2014-06-16 8:13 ` Dan Carpenter [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=20140616081350.GC5500@mwanda \
--to=dan.carpenter@oracle.com \
--cc=benedict.boerger@cs.tu-dortmund.de \
--cc=charrer@alacritech.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=liodot@gmail.com \
--cc=matlackdavid@gmail.com \
--cc=peter.p.waskiewicz.jr@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox