From: David Howells <dhowells@redhat.com>
To: Nicolas Pitre <nico@fluxnic.net>
Cc: dhowells@redhat.com,
Linus Torvalds <torvalds@linux-foundation.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] clarify a usage constraint for cnt32_to_63()
Date: Mon, 20 Dec 2010 16:51:30 +0000 [thread overview]
Message-ID: <21293.1292863890@redhat.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1012200017280.10437@xanadu.home>
Nicolas Pitre <nico@fluxnic.net> wrote:
> The cnt32_to_63 algorithm relies on proper counter data evaluation
> ordering to work properly. This was missing from the provided
> documentation.
>
> Let's augment the documentation with the missing usage constraint and
> fix the only instance that got it wrong.
>
> Signed-off-by: Nicolas Pitre <nico@fluxnic.net>
> Cc: David Howells <dhowells@redhat.com>
Seems to work on my ASB2305.
Acked-by: David Howells <dhowells@redhat.com>
prev parent reply other threads:[~2010-12-20 16:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-15 3:44 [PATCH] clarify a usage constraint for cnt32_to_63() Nicolas Pitre
2010-12-19 21:19 ` Linus Torvalds
2010-12-20 5:29 ` Nicolas Pitre
2010-12-20 16:51 ` David Howells [this message]
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=21293.1292863890@redhat.com \
--to=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nico@fluxnic.net \
--cc=torvalds@linux-foundation.org \
/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