linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: sfr@canb.auug.org.au
Cc: tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com,
	x86@kernel.org, konrad.wilk@oracle.com,
	boris.ostrovsky@oracle.com, david.vrabel@citrix.com,
	anton@enomsg.org, ccross@android.com, keescook@chromium.org,
	tony.luck@intel.com, rjw@rjwysocki.net, lenb@kernel.org,
	kristen@linux.intel.com, viresh.kumar@linaro.org,
	vinod.koul@intel.com, kys@microsoft.com, haiyangz@microsoft.com,
	hiralpat@cisco.com, sramars@cisco.com, buchino@cisco.com,
	JBottomley@odin.com, perex@perex.cz, tiwai@suse.de,
	akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
	xen-devel@lists.xenproject.org, linux-acpi@vger.kernel.org,
	linux-pm@vger.kernel.org, dmaengine@vger.kernel.org,
	devel@linuxdriverproject.org, netdev@vger.kernel.org,
	linux-scsi@vger.kernel.org, alsa-devel@alsa-project.org
Subject: Re: [RFC][PATCH] x86: remove vmalloc.h from asm/io.h
Date: Mon, 01 Jun 2015 15:59:31 -0700 (PDT)	[thread overview]
Message-ID: <20150601.155931.1230241015446814769.davem@davemloft.net> (raw)
In-Reply-To: <20150529191847.2d4cb3a7@canb.auug.org.au>

From: Stephen Rothwell <sfr@canb.auug.org.au>
Date: Fri, 29 May 2015 19:18:47 +1000

> Nothing in asm/io.h uses anything from vmalloc.h, so remove the include
> and fix up the build problems in an allmodconfig (64 bit and 32 bit)
> build.
> 
> This may be the place where x86 builds get vmalloc.h implicitly included
> and that tends to hide places where vmalloc() et al are added to files
> but the include of vmalloc.h is forgotten.
> 
 ...
> Suggested-by: David Miller <davem@davemloft.net>
> Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>

With the follow-on allnoconfig fixes:

Acked-by: David S. Miller <davem@davemloft.net>

Thanks a lot for doing this!

  parent reply	other threads:[~2015-06-01 22:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-29  9:18 [RFC][PATCH] x86: remove vmalloc.h from asm/io.h Stephen Rothwell
2015-05-29  9:21 ` Ingo Molnar
2015-05-29 12:40   ` Stephen Rothwell
2015-05-29 12:43 ` Takashi Iwai
2015-05-29 15:28   ` Stephen Rothwell
2015-06-01 22:59 ` David Miller [this message]
2015-06-02  0:19   ` Stephen Rothwell

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=20150601.155931.1230241015446814769.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=JBottomley@odin.com \
    --cc=akpm@linux-foundation.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=anton@enomsg.org \
    --cc=boris.ostrovsky@oracle.com \
    --cc=buchino@cisco.com \
    --cc=ccross@android.com \
    --cc=david.vrabel@citrix.com \
    --cc=devel@linuxdriverproject.org \
    --cc=dmaengine@vger.kernel.org \
    --cc=haiyangz@microsoft.com \
    --cc=hiralpat@cisco.com \
    --cc=hpa@zytor.com \
    --cc=keescook@chromium.org \
    --cc=konrad.wilk@oracle.com \
    --cc=kristen@linux.intel.com \
    --cc=kys@microsoft.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=rjw@rjwysocki.net \
    --cc=sfr@canb.auug.org.au \
    --cc=sramars@cisco.com \
    --cc=tglx@linutronix.de \
    --cc=tiwai@suse.de \
    --cc=tony.luck@intel.com \
    --cc=vinod.koul@intel.com \
    --cc=viresh.kumar@linaro.org \
    --cc=x86@kernel.org \
    --cc=xen-devel@lists.xenproject.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;
as well as URLs for NNTP newsgroup(s).