From: Jisheng Zhang <jszhang@marvell.com>
To: David Miller <davem@davemloft.net>
Cc: <thomas.petazzoni@free-electrons.com>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] net: mvneta: replace MVNETA_CPU_D_CACHE_LINE_SIZE with L1_CACHE_BYTES
Date: Fri, 1 Apr 2016 15:15:32 +0800 [thread overview]
Message-ID: <20160401151532.3c596206@xhacker> (raw)
In-Reply-To: <20160331.164710.1998871529914699937.davem@davemloft.net>
Hi David, Thomas,
On Thu, 31 Mar 2016 16:47:10 -0400 David Miller wrote:
> From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> Date: Thu, 31 Mar 2016 22:37:35 +0200
>
> > Hello,
> >
> > On Thu, 31 Mar 2016 15:15:47 -0400 (EDT), David Miller wrote:
> >> From: Jisheng Zhang <jszhang@marvell.com>
> >> Date: Wed, 30 Mar 2016 19:55:21 +0800
> >>
> >> > The mvneta is also used in some Marvell berlin family SoCs which may
> >> > have 64bytes cacheline size. Replace the MVNETA_CPU_D_CACHE_LINE_SIZE
> >> > usage with L1_CACHE_BYTES.
> >> >
> >> > And since dma_alloc_coherent() is always cacheline size aligned, so
> >> > remove the align checks.
> >> >
> >> > Signed-off-by: Jisheng Zhang <jszhang@marvell.com>
> >>
> >> Applied.
> >
> > A new version of the patch was sent, which more rightfully uses
> > cache_line_size(), see:
> >
> > "[PATCH v2] net: mvneta: replace MVNETA_CPU_D_CACHE_LINE_SIZE with cache_line_size"
>
> Sorry about that.
>
> Send me a realtive fixup patch if you like.
>
Sorry about inconvenience, I'll send out fixup patch.
Thanks,
Jisheng
prev parent reply other threads:[~2016-04-01 7:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-30 11:55 [PATCH] net: mvneta: replace MVNETA_CPU_D_CACHE_LINE_SIZE with L1_CACHE_BYTES Jisheng Zhang
2016-03-31 19:15 ` David Miller
2016-03-31 20:37 ` Thomas Petazzoni
2016-03-31 20:47 ` David Miller
2016-04-01 7:15 ` Jisheng Zhang [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=20160401151532.3c596206@xhacker \
--to=jszhang@marvell.com \
--cc=davem@davemloft.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=thomas.petazzoni@free-electrons.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;
as well as URLs for NNTP newsgroup(s).