[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20090603170506.a10cc38f.akpm@linux-foundation.org>
Date: Wed, 3 Jun 2009 17:05:06 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Dmitry Eremin-Solenikov <dbaryshkov@...il.com>
Cc: linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
linux-wireless@...r.kernel.org, slapin@...fans.org,
maxim.osipov@...mens.com, dmitry.baryshkov@...mens.com,
oliver.fendt@...mens.com, linux@...mustbejoking.demon.co.uk
Subject: Re: [PATCH 01/10] crc-itu-t: add bit-reversed calculation
On Mon, 1 Jun 2009 18:54:42 +0400
Dmitry Eremin-Solenikov <dbaryshkov@...il.com> wrote:
> From: Darren Salt <linux@...mustbejoking.demon.co.uk>
>
> ..
>
> static inline u16 crc_itu_t_byte(u16 crc, const u8 data)
> {
> return (crc << 8) ^ crc_itu_t_table[((crc >> 8) ^ data) & 0xff];
> }
>
> +static inline u16 crc_itu_t_bitreversed_byte(u16 crc, const u8 data)
> +{
> + return (crc << 8) ^ crc_itu_t_table[((crc >> 8) ^ bitrev8(data)) & 0xff];
> +}
I suspect that inlining these was a mistake, but one which we make often.
> #endif /* CRC_ITU_T_H */
>
> diff --git a/lib/crc-itu-t.c b/lib/crc-itu-t.c
> index a63472b..5562fdd 100644
> --- a/lib/crc-itu-t.c
> +++ b/lib/crc-itu-t.c
> @@ -64,6 +64,24 @@ u16 crc_itu_t(u16 crc, const u8 *buffer, size_t len)
> }
> EXPORT_SYMBOL(crc_itu_t);
>
> +/**
> + * crc_itu_t_bitreversed - Compute the CRC-ITU-T for the data buffer;
> + * the buffer content is assumed to be bit-reversed
kerneldoc doesn't support the breaking of this information across
multiple lines. It'll need to be done as a single 120-column line.
> + * @crc: previous CRC value
> + * @buffer: data pointer
> + * @len: number of bytes in the buffer
> + *
> + * Returns the updated CRC value
> + */
> +u16 crc_itu_t_bitreversed(u16 crc, const u8 *buffer, size_t len)
> +{
> + while (len--)
> + crc = crc_itu_t_bitreversed_byte(crc, *buffer++);
> + return crc;
> +}
> +EXPORT_SYMBOL(crc_itu_t_bitreversed);
--
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