public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: YueHaibing <yuehaibing@huawei.com>, davem@davemloft.net
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	jcliburn@gmail.com, chris.snook@gmail.com, benve@cisco.com,
	jdmason@kudzu.us, chessman@tux.org, jes@trained-monkey.org,
	rahul.verma@cavium.com
Subject: Re: [PATCH net-next 4/6] netxen_nic: use pci_zalloc_consistent
Date: Wed, 6 Jun 2018 12:56:55 +0300	[thread overview]
Message-ID: <9a40ee2d-cb01-d469-602e-c4b79e6d41cf@cogentembedded.com> (raw)
In-Reply-To: <20180605122851.23912-5-yuehaibing@huawei.com>

On 6/5/2018 3:28 PM, YueHaibing wrote:

> use pci_zalloc_consistent to remove unnecessary memset.
> Also remove a local intermediate pointer 'void *addr'.

    AAgain, don't do 2 things with 1 patch.

> Signed-off-by: YueHaibing <yuehaibing@huawei.com>
[...]

MBR, Sergei

  reply	other threads:[~2018-06-06  9:57 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-05 12:28 [PATCH net-next 0/6] use pci_zalloc_consistent YueHaibing
2018-06-05 12:28 ` [PATCH net-next 1/6] net: hippi: " YueHaibing
2018-06-06  9:53   ` Sergei Shtylyov
2018-06-06 15:04   ` kbuild test robot
2018-06-05 12:28 ` [PATCH net-next 2/6] net: atheros: " YueHaibing
2018-06-05 12:28 ` [PATCH net-next 3/6] net: neterion: " YueHaibing
2018-06-05 12:28 ` [PATCH net-next 4/6] netxen_nic: " YueHaibing
2018-06-06  9:56   ` Sergei Shtylyov [this message]
2018-06-05 12:28 ` [PATCH net-next 5/6] net: tlan: " YueHaibing
2018-06-05 12:28 ` [PATCH net-next 6/6] enic: " YueHaibing
2018-06-05 12:39 ` [PATCH net-next 0/6] " Andy Shevchenko
2018-06-05 12:49   ` Christoph Hellwig
2018-06-05 12:46     ` Andy Shevchenko
2018-06-05 13:04       ` YueHaibing
2018-06-05 13:00     ` 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=9a40ee2d-cb01-d469-602e-c4b79e6d41cf@cogentembedded.com \
    --to=sergei.shtylyov@cogentembedded.com \
    --cc=benve@cisco.com \
    --cc=chessman@tux.org \
    --cc=chris.snook@gmail.com \
    --cc=davem@davemloft.net \
    --cc=jcliburn@gmail.com \
    --cc=jdmason@kudzu.us \
    --cc=jes@trained-monkey.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=rahul.verma@cavium.com \
    --cc=yuehaibing@huawei.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