[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <02a401cc6cd2$28ee4e60$7acaeb20$@systemfabricworks.com>
Date: Tue, 6 Sep 2011 15:18:35 -0500
From: "Bob Pearson" <rpearson@...temfabricworks.com>
To: "'Andrew Morton'" <akpm@...ux-foundation.org>,
"'Stephen Rothwell'" <sfr@...b.auug.org.au>
Cc: "'Joakim Tjernlund'" <joakim.tjernlund@...nsmode.se>,
<fzago@...temfabricworks.com>,
"'George Spelvin'" <linux@...izon.com>,
<linux-kernel@...r.kernel.org>
Subject: RE: [PATCH v6 05/10] crc32-misc-cleanup.diff
>
> Yup. lib-crc-add-slice-by-8-algorithm-to-crc32c.patch is dead meat. I
> sometimes keep things like that around to get them a bit of testing
> while reminding myself that there's an open issue to track.
I thought I was getting close until recently someone sent out a patch set
for crc32c.c, the other 32 bit CRC in common use, based on an earlier
version of the changes we have been working on for crc32.c. This has brought
in other interested parties and created a bit of duplicated code. I am at a
loss as to the best way to proceed. Personally I would like to see this
change go upstream and then let the rest of the world figure out how to best
merge things.
The list of needed changes based on recent comments I am aware of are:
- put back in a couple of header files per Andrew
- fix the summary phrases to conform to coding standards per Andrew
- add signed off by for Joakim to patch 04/10 per Joakim
- fix bug in patch 06/10 noted in my email by passing bits as a parameter
to crc32_body
If anyone wants additional changes please let me know and I can put out a
clean version.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists