From: Andrew Morton <akpm@linux-foundation.org>
To: Chereji Marian-Cornel-R27762 <R27762@freescale.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Grigore Sebastian-SGRIGOR1 <sgrigor1@freescale.com>,
Schmitt Richard-B43082 <B43082@freescale.com>,
Fleming Andy-AFLEMING <afleming@freescale.com>
Subject: Re: [PATCH] lib: Add CRC64 ECMA module
Date: Mon, 29 Jul 2013 15:22:47 -0700 [thread overview]
Message-ID: <20130729152247.6c00ed3e6de57bb3e7addca9@linux-foundation.org> (raw)
In-Reply-To: <4B6ACA9E2957BC4EBAA02AF13568C81B03CA7BC4@039-SN2MPN1-021.039d.mgd.msft.net>
On Mon, 29 Jul 2013 11:49:31 +0000 Chereji Marian-Cornel-R27762 <R27762@freescale.com> wrote:
> -----Original Message-----
> From: Andrew Morton [mailto:akpm@linux-foundation.org]
> Sent: Saturday, July 27, 2013 1:01 AM
> To: Chereji Marian-Cornel-R27762
> Cc: linux-kernel@vger.kernel.org; Grigore Sebastian-SGRIGOR1; Schmitt Richard-B43082; Fleming Andy-AFLEMING
> Subject: Re: [PATCH] lib: Add CRC64 ECMA module
>
> On Fri, 12 Jul 2013 11:56:26 +0300 Marian Chereji <marian.chereji@freescale.com> wrote:
>
> > Added implementation of CRC64 ECMA checksum.
> >
> > Signed-off-by: Marian Chereji <marian.chereji@freescale.com>
> > Reviewed-by: Varvara Andrei-B21317 <andrei.varvara@freescale.com>
> > Reviewed-by: Fleming Andrew-AFLEMING <AFLEMING@freescale.com>
> > ---
> > include/linux/crc64_ecma.h | 56 +++++++
> > lib/Kconfig | 7 +
> > lib/Makefile | 1 +
> > lib/crc64_ecma.c | 341 ++++++++++++++++++++++++++++++++++++++++++++
> >
> > Presumably you have some code which will need this library feature?
> >
> > What code is that, and what is its status?
> >
>
> Hi Andrew,
>
> we have an IP Acceleration driver for Freescale network processors
> which is using this CRC64. However, it still needs some work in
> order for it to become upstreamable.
>
> Thought this CRC64 could helps others in the meantime since it doesn't
> have anything specific to do with our driver.
Please don't top-post - it makes it very hard to conduct a conversation.
I don't think it's generally desirable to put code into lib/ unless we
have an in-kernel user: it consumes resources and is untestable. From
a quick grep I don't see any current in-kernel code which might use
this.
So I'd propose that I keep this patch in -mm to get a bit of exposure
and compilation testing and wait until the first user comes along, OK?
next prev parent reply other threads:[~2013-07-29 22:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-12 8:56 Marian Chereji
2013-07-26 22:00 ` Andrew Morton
2013-07-29 11:49 ` Chereji Marian-Cornel-R27762
2013-07-29 22:22 ` Andrew Morton [this message]
2013-07-30 7:29 ` Chereji Marian-Cornel-R27762
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=20130729152247.6c00ed3e6de57bb3e7addca9@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=B43082@freescale.com \
--cc=R27762@freescale.com \
--cc=afleming@freescale.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sgrigor1@freescale.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
Powered by JetHome