From: Greg Kroah-Hartman <gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org>
To: James Hogan <james.hogan-1AXoQHu6uovQT0dZR+AlfA@public.gmane.org>
Cc: Stephen Rothwell <sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>,
linux-metag-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-next-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Abhilash Kesavan
<a.kesavan-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
Subject: Re: [PATCH -next] metag: Fix ioremap_wc/ioremap_cached build errors
Date: Wed, 25 Mar 2015 11:30:41 +0100 [thread overview]
Message-ID: <20150325103041.GA32429@kroah.com> (raw)
In-Reply-To: <55117FDE.1030904-1AXoQHu6uovQT0dZR+AlfA@public.gmane.org>
On Tue, Mar 24, 2015 at 03:16:46PM +0000, James Hogan wrote:
> On 23/03/15 21:02, Stephen Rothwell wrote:
> > Hi Greg,
> >
> > On Mon, 23 Mar 2015 20:54:01 +0100 Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:
> >>
> >> On Mon, Mar 23, 2015 at 12:26:15PM +0000, James Hogan wrote:
> >>> When ioremap_wc() or ioremap_cached() are used without first including
> >>> asm/pgtable.h, the _PAGE_CACHEABLE or _PAGE_WR_COMBINE definitions
> >>> aren't found, resulting in build errors like the following (in
> >>> next-20150323 due to "lib: devres: add a helper function for
> >>> ioremap_wc"):
> >>>
> >>> lib/devres.c: In function ‘devm_ioremap_wc’:
> >>> lib/devres.c:91: error: ‘_PAGE_WR_COMBINE’ undeclared
> >>>
> >>> We can't easily include asm/pgtable.h in asm/io.h due to dependency
> >>> problems, so split out the _PAGE_* definitions from asm/pgtable.h into a
> >>> separate asm/pgtable-bits.h header (as a couple of other architectures
> >>> already do), and include that in io.h instead.
> >>>
> >>> Signed-off-by: James Hogan <james.hogan-1AXoQHu6uovQT0dZR+AlfA@public.gmane.org>
> >>> Cc: linux-metag-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> >>> Cc: Abhilash Kesavan <a.kesavan-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
> >>> Cc: Greg Kroah-Hartman <gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org>
> >>> ---
> >>> GregKH: I can apply this patch to the metag tree for 4.0. However commit
> >>> 34644524bce9 "lib: devres: add a helper function for ioremap_wc" in
> >>> your char-misc-next branch in next-20150323 will still break the metag
> >>> build until the two changes merge. How do you want to handle that?
> >>
> >> I don't know, I can't pull that into 4.0-final as it's not 4.0-final
> >> material. So there's nothing I can do from my end, sorry.
> >
> > Am I missing something? Why can't you just put that commit in your
> > char-misc-next branch along with the commit that causes the need for
> > that commit? If James put it in it's own (non rebasing) branch, you
> > could even both merge it into your trees ...
>
> Greg: I've pushed a fix_ioremap_wc branch to:
> git://git.kernel.org/pub/scm/linux/kernel/git/jhogan/metag.git
>
> based on v4.0-rc3, with just this patch. Feel free to merge it if you're
> happy to do so.
I've now done this, thanks.
greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-metag" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2015-03-25 10:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-23 12:26 [PATCH -next] metag: Fix ioremap_wc/ioremap_cached build errors James Hogan
[not found] ` <1427113575-29222-1-git-send-email-james.hogan-1AXoQHu6uovQT0dZR+AlfA@public.gmane.org>
2015-03-23 19:54 ` Greg Kroah-Hartman
2015-03-23 21:02 ` Stephen Rothwell
[not found] ` <20150324080238.222953d5-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2015-03-24 15:16 ` James Hogan
[not found] ` <55117FDE.1030904-1AXoQHu6uovQT0dZR+AlfA@public.gmane.org>
2015-03-25 10:30 ` Greg Kroah-Hartman [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=20150325103041.GA32429@kroah.com \
--to=gregkh-hqyy1w1ycw8ekmwlsbkhg0b+6bgklq7r@public.gmane.org \
--cc=a.kesavan-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org \
--cc=james.hogan-1AXoQHu6uovQT0dZR+AlfA@public.gmane.org \
--cc=linux-metag-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-next-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.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