From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Linus Torvalds <torvalds@linux-foundation•org>
Cc: Christian Borntraeger <borntraeger@de•ibm.com>,
linux-next <linux-next@vger•kernel.org>,
LKML <linux-kernel@vger•kernel.org>
Subject: Re: linux-next: missing merge fix for the access_once tree
Date: Tue, 23 Dec 2014 17:34:18 +1100 [thread overview]
Message-ID: <20141223173418.59e8556f@canb.auug.org.au> (raw)
In-Reply-To: <CA+55aFxjeunxnfc8L1r=GWCBUf5uU=bcnDeu6VygMbsCxVgB0Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 806 bytes --]
Hi Linus,
On Mon, 22 Dec 2014 20:12:22 -0800 Linus Torvalds <torvalds@linux-foundation•org> wrote:
>
> On Mon, Dec 22, 2014 at 6:17 PM, Stephen Rothwell <sfr@canb•auug.org.au> wrote:
> >
> > I have been carrying this merge fix patch for some time. It should
> > have gone into the merge of the access_once tree.
>
> No, you had a different tree that got merged into linux-next, that
> made it an error to do ACCESS_ONCE() on a structure.
>
> The thing I merged didn't actually have that final commit, exactly so
> that things wouldn't break from missing conversions.
>
> So that patch isn't wrong, but it also isn't exactly a required fix
> until the next merge window..
True, so "should" was a bit strong.
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-12-23 6:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-23 2:17 linux-next: missing merge fix for the access_once tree Stephen Rothwell
2014-12-23 4:12 ` Linus Torvalds
2014-12-23 6:34 ` Stephen Rothwell [this message]
2014-12-28 8:38 ` Christian Borntraeger
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=20141223173418.59e8556f@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=borntraeger@de$(echo .)ibm.com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=torvalds@linux-foundation$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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