From: "Darrick J. Wong" <djwong@us.ibm.com>
To: Bob Pearson <rpearson@systemfabricworks.com>
Cc: Andreas Dilger <adilger.kernel@dilger.ca>,
Theodore Tso <tytso@mit.edu>, David Miller <davem@davemloft.net>,
Joakim Tjernlund <joakim.tjernlund@transmode.se>,
linux-kernel <linux-kernel@vger.kernel.org>,
Mingming Cao <cmm@us.ibm.com>,
linux-crypto <linux-crypto@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-ext4@vger.kernel.org,
Herbert Xu <herbert@gondor.apana.org.au>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Time for a fresh slice-by-8 crc32.c posting?
Date: Thu, 27 Oct 2011 11:32:21 -0700 [thread overview]
Message-ID: <20111027183221.GV12447@tux1.beaverton.ibm.com> (raw)
In-Reply-To: <20111026171556.GU12447@tux1.beaverton.ibm.com>
Hi Bob,
Would you mind posting your current crc32 patches to lkml again? A couple of
months have gone by, and it sure would be nice to replace the circa-July patch
in -next with a newer one. I recall that there were requests for some code
changes even in Bob's 8/31 submission, so it'd be nice to have a fresh set from
you with your latest changes.
I'd also like to freshen my crc32c refactor patches and send them along too.
To clarify, I tried the new crc32{,c} on my ppc32 and it passed the self test.
--D
On Wed, Oct 26, 2011 at 10:16:10AM -0700, Darrick J. Wong wrote:
> On Fri, Oct 21, 2011 at 09:15:14PM +0200, Herbert Xu wrote:
> > On Fri, Oct 21, 2011 at 09:57:03AM -0700, Darrick J. Wong wrote:
> > >
> > > My patchset builds upon Bob Pearson's crc32 patchset from early September. Do
> > > my patches fail to apply after applying his patchset?
> > >
> > > Or, to speed things along, should I simply repost both Bob's and my patches as
> > > one big series?
> > >
> > > Bob, have you sent out a new iteration of your patches since September 6th?
> >
> > I'm fine with you pushing this through whichever tree that Bob's
> > patches are going through.
>
> Bob,
>
> Which tree (if any) are your patches going through?
>
> --D
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-10-27 18:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-04 23:53 [PATCH v5 0/4] crc32c: Add faster algorithm and self-test code Darrick J. Wong
2011-10-04 23:54 ` [PATCH 1/4] crc32: Bolt on crc32c Darrick J. Wong
2011-10-21 12:28 ` Herbert Xu
2011-10-21 16:57 ` Darrick J. Wong
2011-10-21 19:15 ` Herbert Xu
2011-10-26 17:16 ` Darrick J. Wong
2011-10-27 18:32 ` Darrick J. Wong [this message]
2011-11-15 8:48 ` Darrick J. Wong
2011-11-15 15:38 ` Bob Pearson
2011-10-04 23:54 ` [PATCH 2/4] crypto: crc32c should use library implementation Darrick J. Wong
2011-10-04 23:54 ` [PATCH 3/4] crc32: Add self-test code for crc32c Darrick J. Wong
2011-10-04 23:54 ` [PATCH 4/4] crc32: Select an algorithm via kconfig Darrick J. Wong
2011-10-08 7:42 ` [PATCH v5.1 " Darrick J. Wong
2011-10-06 20:20 ` [PATCH v5 0/4] crc32c: Add faster algorithm and self-test code Darrick J. Wong
2011-10-07 7:38 ` Joakim Tjernlund
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=20111027183221.GV12447@tux1.beaverton.ibm.com \
--to=djwong@us.ibm.com \
--cc=adilger.kernel@dilger.ca \
--cc=akpm@linux-foundation.org \
--cc=cmm@us.ibm.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=joakim.tjernlund@transmode.se \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rpearson@systemfabricworks.com \
--cc=tytso@mit.edu \
/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).