From: "Bob Pearson" <rpearson@systemfabricworks.com>
To: <djwong@us.ibm.com>, "'Herbert Xu'" <herbert@gondor.apana.org.au>
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>
Subject: RE: [PATCH 1/4] crc32: Bolt on crc32c
Date: Tue, 15 Nov 2011 09:38:54 -0600 [thread overview]
Message-ID: <00b001cca3ac$b08c0310$11a40930$@systemfabricworks.com> (raw)
In-Reply-To: <20111115084805.GY12447@tux1.beaverton.ibm.com>
I'd have sent new bits by now. Although the changes are minor and cosmetic.
The problem is that due to getting things ready for SC11 (where I am now) I
have been unable to test anything for the past two weeks.
I can retest everything next week or you can go with the bits that are out
there.
> -----Original Message-----
> From: Darrick J. Wong [mailto:djwong@us.ibm.com]
> Sent: Tuesday, November 15, 2011 2:48 AM
> To: Herbert Xu
> Cc: Andreas Dilger; Theodore Tso; David Miller; Joakim Tjernlund; Bob
> Pearson; linux-kernel; Mingming Cao; linux-crypto; linux-fsdevel; linux-
> ext4@vger.kernel.org
> Subject: Re: [PATCH 1/4] crc32: Bolt on crc32c
>
> 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.
>
> Well... it's been 2.5 weeks since I last asked about this. No reply,
afaict.
> I haven't seen any complaints about Bob's latest patchset, nor any
complaints
> about my set that sits atop his. On the other hand, I'm pretty sure I
haven't
> seen Bob's patches appear in any trees, and Google shows no recent
> progress.
>
> Herbert, would you object to pushing the whole patchset through the crypto
> tree?
>
> --D
> >
> > Cheers,
> > --
> > Email: Herbert Xu <herbert@gondor.apana.org.au>
> > Home Page: http://gondor.apana.org.au/~herbert/
> > PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
> > --
> > 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-11-15 15:38 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 ` Time for a fresh slice-by-8 crc32.c posting? Darrick J. Wong
2011-11-15 8:48 ` [PATCH 1/4] crc32: Bolt on crc32c Darrick J. Wong
2011-11-15 15:38 ` Bob Pearson [this message]
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='00b001cca3ac$b08c0310$11a40930$@systemfabricworks.com' \
--to=rpearson@systemfabricworks.com \
--cc=adilger.kernel@dilger.ca \
--cc=cmm@us.ibm.com \
--cc=davem@davemloft.net \
--cc=djwong@us.ibm.com \
--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=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).