linux-mmc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ulf Hansson <ulf.hansson@linaro.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Christoph Hellwig <hch@lst.de>,
	Linus Walleij <linus.walleij@linaro.org>,
	Russell King <linux@armlinux.org.uk>,
	Shawn Lin <shawn.lin@rock-chips.com>,
	Allen <allen.lkml@gmail.com>,
	"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mmc: mxmmc: include linux/highmem.h
Date: Tue, 29 May 2018 12:35:52 +0200	[thread overview]
Message-ID: <CAPDyKFo2b9biWkmJ1tM4QU1RbGvF6SOOpTxpYFuUchkhZKXnug@mail.gmail.com> (raw)
In-Reply-To: <20180529103057.1378025-1-arnd@arndb.de>

On 29 May 2018 at 12:30, Arnd Bergmann <arnd@arndb.de> wrote:
> The highmem conversion caused a build error in some configurations:
>
> drivers/mmc/host/mxcmmc.c: In function 'mxcmci_transfer_data':
> drivers/mmc/host/mxcmmc.c:622:10: error: implicit declaration of function 'kmap_atomic'; did you mean 'in_atomic'? [-Werror=implicit-function-declaration]
>
> This includes the correct header file.
>
> Fixes: b189e7589f6d ("mmc: mxcmmc: handle highmem pages")
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>

Thanks, applied for next!

Kind regards
Uffe

> ---
>  drivers/mmc/host/mxcmmc.c | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/drivers/mmc/host/mxcmmc.c b/drivers/mmc/host/mxcmmc.c
> index 150fbdba777d..d62bf7efce13 100644
> --- a/drivers/mmc/host/mxcmmc.c
> +++ b/drivers/mmc/host/mxcmmc.c
> @@ -21,6 +21,7 @@
>  #include <linux/init.h>
>  #include <linux/ioport.h>
>  #include <linux/platform_device.h>
> +#include <linux/highmem.h>
>  #include <linux/interrupt.h>
>  #include <linux/irq.h>
>  #include <linux/blkdev.h>
> --
> 2.9.0
>

      reply	other threads:[~2018-05-29 10:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-29 10:30 [PATCH] mmc: mxmmc: include linux/highmem.h Arnd Bergmann
2018-05-29 10:35 ` Ulf Hansson [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=CAPDyKFo2b9biWkmJ1tM4QU1RbGvF6SOOpTxpYFuUchkhZKXnug@mail.gmail.com \
    --to=ulf.hansson@linaro.org \
    --cc=allen.lkml@gmail.com \
    --cc=arnd@arndb.de \
    --cc=hch@lst.de \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=shawn.lin@rock-chips.com \
    /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).