From: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Linus Torvalds <torvalds@osdl.org>,
Nick Piggin <nickpiggin@yahoo.com.au>,
Russell King <rmk+lkml@arm.linux.org.uk>,
David Howells <dhowells@redhat.com>,
Andrew Morton <akpm@osdl.org>,
"David S. Miller" <davem@davemloft.net>,
matthew@wil.cx,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-arch@vger.kernel.org
Subject: Re: [PATCH 1/2] WorkStruct: Add assign_bits() to give an atomic-bitops safe assignment
Date: Mon, 18 Dec 2006 12:05:45 +0300 [thread overview]
Message-ID: <20061218090545.GC21778@2ka.mipt.ru> (raw)
In-Reply-To: <1166432184.25827.8.camel@pmac.infradead.org>
On Mon, Dec 18, 2006 at 08:56:24AM +0000, David Woodhouse (dwmw2@infradead.org) wrote:
> On Fri, 2006-12-15 at 14:45 -0800, Linus Torvalds wrote:
> > This uses "atomic_long_t" for the workstruct "data" field, which shares
> > the per-cpu pointer and the workstruct flag bits in one field.
>
> This fixes drivers/connector/connector.c to cope...
>
> Signed-off-by: David Woodhouse <dwmw2@infradead.org>
Yep, there are already four different patches to fix it.
Proper one will be pushed through David Miller's netdev tree splitted into
fix and delayed work removal.
Thanks David.
> --
> dwmw2
--
Evgeniy Polyakov
next prev parent reply other threads:[~2006-12-18 9:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-12 20:11 [PATCH 1/2] WorkStruct: Add assign_bits() to give an atomic-bitops safe assignment David Howells
2006-12-12 20:11 ` [PATCH 2/2] WorkStruct: Use bitops-safe direct assignment David Howells
2006-12-12 22:54 ` [PATCH 1/2] WorkStruct: Add assign_bits() to give an atomic-bitops safe assignment Russell King
2006-12-12 23:03 ` Paul Mackerras
2006-12-12 23:17 ` David Howells
2006-12-13 1:36 ` Linus Torvalds
2006-12-13 2:07 ` Nick Piggin
2006-12-13 2:30 ` Linus Torvalds
2006-12-15 22:45 ` Linus Torvalds
2006-12-18 8:56 ` David Woodhouse
2006-12-18 9:05 ` Evgeniy Polyakov [this message]
2006-12-18 9:10 ` David Miller
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=20061218090545.GC21778@2ka.mipt.ru \
--to=johnpol@2ka.mipt.ru \
--cc=akpm@osdl.org \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=dwmw2@infradead.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=nickpiggin@yahoo.com.au \
--cc=rmk+lkml@arm.linux.org.uk \
--cc=torvalds@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.