From: "Arend van Spriel" <arend@broadcom.com>
To: "George Spelvin" <linux@horizon.com>
Cc: "akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"error27@gmail.com" <error27@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"linville@tuxdriver.com" <linville@tuxdriver.com>
Subject: Re: [RFC] lib: crc8: add new library module providing crc8 algorithm
Date: Wed, 25 May 2011 08:49:19 +0200 [thread overview]
Message-ID: <4DDCA66F.1080007@broadcom.com> (raw)
In-Reply-To: <20110525054634.5033.qmail@science.horizon.com>
On 05/25/2011 07:46 AM, George Spelvin wrote:
> Since you are obviously being ironic in your phrasing, I hope I did not
> give serious offense. What I wrote is a fairly accurate description of
> my reflex reaction, but I could have phrased it more diplomatically.
No offense. I am not keen on politics anyway so blunt in fine with me ;-)
>> If callers use the specific function they can not specify a bit order so
>> no compile-time error.
> What I meant was, the bit order is specified by the function name.
> An invalid bit order translates to an invalid function name, which the
> linker will complain about.
Than we mean the same thing.
> If you feel ambitious, you can fold the crc7 code into yours. Its an
> msbit-first CRC. The resultant table will be left-justified rather
> than the current right-justified, but if you look at all the call sites,
> you'll notice that they all shift the result left 1 bit!
We are ambitious, but the focus is on getting our wireless driver in
shape. The crc8 library function is related to that. So folding the crc7
will get a low priority for now.
I noticed the whole table changed in the patch you posted in the bug
report. So that is because of the shift, right?
Gr. AvS
--
Almost nobody dances sober, unless they happen to be insane.
-- H.P. Lovecraft --
next prev parent reply other threads:[~2011-05-25 6:49 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-24 20:23 [RFC] lib: crc8: add new library module providing crc8 algorithm Arend van Spriel
2011-05-24 22:52 ` George Spelvin
2011-05-25 5:21 ` Arend van Spriel
2011-05-25 5:46 ` George Spelvin
2011-05-25 6:49 ` Arend van Spriel [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-05-22 8:08 Arend van Spriel
2011-05-22 8:59 ` Nicolas Kaiser
2011-05-22 12:49 ` Arend van Spriel
2011-05-21 20:49 Arend van Spriel
2011-05-21 22:37 ` Johannes Berg
2011-05-22 8:23 ` Arend van Spriel
2011-05-22 11:23 ` Alan Cox
2011-05-22 12:47 ` Arend van Spriel
[not found] ` <20110522151959.7fd6e87e@lxorguk.ukuu.org.uk>
2011-05-22 15:38 ` Arend van Spriel
2011-05-24 7:45 ` Arend van Spriel
2011-05-24 8:30 ` Arend van Spriel
2011-05-24 9:44 ` Alan Cox
2011-05-24 10:01 ` Arend van Spriel
2011-05-24 10:25 ` Rafał Miłecki
2011-05-24 10:40 ` Arend van Spriel
2011-05-24 10:27 ` Alan Cox
2011-05-24 10:38 ` Arend van Spriel
2011-05-24 12:57 ` Alan Cox
2011-05-24 17:00 ` Arend van Spriel
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=4DDCA66F.1080007@broadcom.com \
--to=arend@broadcom.com \
--cc=akpm@linux-foundation.org \
--cc=error27@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linux@horizon.com \
--cc=linville@tuxdriver.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;
as well as URLs for NNTP newsgroup(s).