mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Jens Axboe <jens.axboe@oracle.com>,
	linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: -tip: block, mm: Fix build error in mm/memcontrol.c
Date: Sat, 11 Jul 2009 21:03:03 +0200	[thread overview]
Message-ID: <20090711190303.GB15163@elte.hu> (raw)
In-Reply-To: <alpine.LFD.2.01.0907111125030.3552@localhost.localdomain>


* Linus Torvalds <torvalds@linux-foundation.org> wrote:

> On Sat, 11 Jul 2009, Ingo Molnar wrote:
> > 
> > Today's upstream tree build (x86, 64-bit, allyesconfig) failed 
> > with this build error:
> 
> I merged a better fix from Trond, which should make all of this 
> unnecessary (just move BLK_RW_[A]SYNC to the header file that 
> people need anyway).

ok, that's better. I think if in addition to that we also did what i 
suggested:

> Fix it the simplest way for now, by moving the definitions early 
> in blkdev.h (this cannot break anything), but the real fix would 
> be to split up blkdev.h into blkdev-types.h and blkdev-api.h and 
> make only the API definitions/declarations dependent on 
> CONFIG_BLOCK.

would be one step cleaner.

We could then include blkdev-types.h in backing-dev.h so that it 
picks up the constants. Right now having BLK_RW_[A]SYNC in 
backing-dev.h looks a bit weird. No strong opinion though.

	Ingo

      reply	other threads:[~2009-07-11 19:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-11  6:51 Ingo Molnar
2009-07-11 18:25 ` Linus Torvalds
2009-07-11 19:03   ` Ingo Molnar [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=20090711190303.GB15163@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@linux-foundation.org \
    --cc=jens.axboe@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --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

all inboxes | Powered by JetHome®