netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Shyam Saini <mayhs11saini@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: Yuval.Mintz@cavium.com, Ariel.Elior@cavium.com,
	everest-linux-l2@cavium.com, netdev@vger.kernel.org
Subject: Re: [PATCH] qed: Replace memset with eth_zero_addr
Date: Tue, 17 Jan 2017 09:03:05 +0530	[thread overview]
Message-ID: <20170117033305.GB4055@mystictot> (raw)
In-Reply-To: <20170116.145819.115892553691222296.davem@davemloft.net>

On Mon, Jan 16, 2017 at 02:58:19PM -0500, David Miller wrote:
> From: Shyam Saini <mayhs11saini@gmail.com>
> Date: Tue, 17 Jan 2017 00:21:38 +0530
> 
> > Use eth_zero_addr to assign zero address to the given address array
> > instead of memset when the second argument in memset is address
> > of zero. Also, it makes the code clearer
> > 
> > Signed-off-by: Shyam Saini <mayhs11saini@gmail.com>
> 
> This patch does not apply cleanly to the net-next tree.

I always send patches from linux-next tree and that caused this mistake

I apologize for this.

> Please state if you don't understand what that means instead of
> submitting this patch over and over again against the wrong source
> tree.

Now sent from net-next tree

Thanks a lot,
Shyam

  reply	other threads:[~2017-01-17  3:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-16 18:51 [PATCH] qed: Replace memset with eth_zero_addr Shyam Saini
2017-01-16 19:58 ` David Miller
2017-01-17  3:33   ` Shyam Saini [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-01-17  2:05 Shyam Saini
2017-01-17 20:24 ` David Miller
2017-01-16 18:03 Shyam Saini
2017-01-16 18:25 ` David Miller

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=20170117033305.GB4055@mystictot \
    --to=mayhs11saini@gmail.com \
    --cc=Ariel.Elior@cavium.com \
    --cc=Yuval.Mintz@cavium.com \
    --cc=davem@davemloft.net \
    --cc=everest-linux-l2@cavium.com \
    --cc=netdev@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;
as well as URLs for NNTP newsgroup(s).