public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: dhowells@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: On patch "Remove all #inclusions of asm/system.h"
Date: Sun, 01 Apr 2012 02:46:31 +0100	[thread overview]
Message-ID: <5679.1333244791@redhat.com> (raw)
In-Reply-To: <20120331224452.1862a2b4@stein>

Stefan Richter <stefanr@s5r6.in-berlin.de> wrote:

> It's not a problem; they now get barrier.h via spinlock.h.  I just
> wondered whether absence of #include <asm/barrier.h> in those files had a
> deeper non-obvious meaning.  Since it doesn't I will just put that include
> in them next time around when I do some housekeeping there.

I suspect they should #include asm/barrier.h directly rather than relying on
spinlock.h.  There's no guarantee that on every arch spinlock.h will pull in
asm/barrier.h, I think...

David

      reply	other threads:[~2012-04-01  1:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-29 13:34 On patch "Remove all #inclusions of asm/system.h" Stefan Richter
2012-03-31 19:31 ` David Howells
2012-03-31 20:44   ` Stefan Richter
2012-04-01  1:46     ` 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=5679.1333244791@redhat.com \
    --to=dhowells@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stefanr@s5r6.in-berlin.de \
    /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