Arnd Bergmann <[email protected]> wrote: > You could write it as > > bounce-$(CONFIG_MMU) += bounce.o > obj-$(CONFIG_BLOCK) += $(bounce-y) I could, yes, but why? What does it buy? I think this: ifeq ($(CONFIG_MMU)$(CONFIG_BLOCK),yy) obj-y += bounce.o endif is clearer. David - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- References:
- Re: [PATCH 04/18] [PATCH] BLOCK: Separate the bounce buffering code from the highmem code [try #4]
- From: Arnd Bergmann <[email protected]>
- Re: [PATCH 04/18] [PATCH] BLOCK: Separate the bounce buffering code from the highmem code [try #4]
- From: Sam Ravnborg <[email protected]>
- [PATCH 04/18] [PATCH] BLOCK: Separate the bounce buffering code from the highmem code [try #4]
- From: David Howells <[email protected]>
- Re: [PATCH 04/18] [PATCH] BLOCK: Separate the bounce buffering code from the highmem code [try #4]
- From: David Howells <[email protected]>
- Re: [PATCH 04/18] [PATCH] BLOCK: Separate the bounce buffering code from the highmem code [try #4]
- Prev by Date: vmsplice can't work well
- Next by Date: Re: [PATCH 2.6.18-rc4-mm2] fs/jfs: Conversion to generic boolean
- Previous by thread: Re: [PATCH 04/18] [PATCH] BLOCK: Separate the bounce buffering code from the highmem code [try #4]
- Next by thread: Re: [PATCH 04/18] [PATCH] BLOCK: Separate the bounce buffering code from the highmem code [try #4]
- Index(es):
 |