From: Paul Bolle <pebolle@tiscali.nl>
To: Steven Miao <realmz6@gmail.com>
Cc: adi-buildroot-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Blackfin: remove "config IP_CHECKSUM_L1"
Date: Thu, 13 Feb 2014 10:50:28 +0100 [thread overview]
Message-ID: <1392285028.30853.24.camel@x220> (raw)
In-Reply-To: <1363899006.1390.157.camel@x61.thuisdomein>
[Replaced previous maintainer and list with current maintainer and
list.]
On Thu, 2013-03-21 at 21:50 +0100, Paul Bolle wrote:
> The only user of Kconfig symbol IP_CHECKSUM_L1 got removed in v2.6.33,
> with commit ddf9ddacef0989fdeb22e182212a232488f0f3ad ("Blackfin: convert
> to generic checksum code"). We can remove the Kconfig entry for this
> unused symbol now.
>
> Signed-off-by: Paul Bolle <pebolle@tiscali.nl>
Has someone ever looked at this trivial patch? The Kconfig entry for
this symbol is still present in v3.14-rc2.
> Untested.
>
> arch/blackfin/Kconfig | 8 --------
> 1 file changed, 8 deletions(-)
>
> diff --git a/arch/blackfin/Kconfig b/arch/blackfin/Kconfig
> index c3f2e0b..a8acb1d 100644
> --- a/arch/blackfin/Kconfig
> +++ b/arch/blackfin/Kconfig
> @@ -866,14 +866,6 @@ config SYS_BFIN_SPINLOCK_L1
> If enabled, sys_bfin_spinlock function is linked
> into L1 instruction memory. (less latency)
>
> -config IP_CHECKSUM_L1
> - bool "Locate IP Checksum function in L1 Memory"
> - default n
> - depends on !SMP
> - help
> - If enabled, the IP Checksum function is linked
> - into L1 instruction memory. (less latency)
> -
> config CACHELINE_ALIGNED_L1
> bool "Locate cacheline_aligned data to L1 Data Memory"
> default y if !BF54x
Paul Bolle
prev parent reply other threads:[~2014-02-13 9:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-21 20:50 [PATCH] Blackfin: remove "config IP_CHECKSUM_L1" Paul Bolle
2014-02-13 9:50 ` Paul Bolle [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=1392285028.30853.24.camel@x220 \
--to=pebolle@tiscali.nl \
--cc=adi-buildroot-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=realmz6@gmail.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