From: Timur Tabi <timur@freescale.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: "gregkh@suse.de" <gregkh@suse.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>,
"Hans J. Koch" <hjk@hansjkoch.de>,
Jiang Kai-B18973 <B18973@freescale.com>
Subject: Re: [PATCH] uio: Support 36-bit physical addresses on 32-bit systems
Date: Thu, 13 Oct 2011 09:35:15 -0500 [thread overview]
Message-ID: <4E96F723.2010304@freescale.com> (raw)
In-Reply-To: <CAMuHMdVYsMj99jTJRj_NJ_dCg+b-39ExnDD1Mhqnv3R6tWf1iQ@mail.gmail.com>
Geert Uytterhoeven wrote:
> You deleted this part:
>
> config PHYS_ADDR_T_64BIT
> def_bool 64BIT || ARCH_PHYS_ADDR_T_64BIT
>
> which enforces that PHYS_ADDR_T_64BIT is enabled if 64BIT is set.
Ok, I didn't catch that before, but it makes sense now. Thanks.
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2011-10-13 14:36 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-12 14:35 [PATCH] uio: Support 36-bit physical addresses on 32-bit systems Kumar Gala
2011-10-12 15:32 ` Hans J. Koch
2011-10-12 16:07 ` Kumar Gala
2011-10-12 16:15 ` Geert Uytterhoeven
2011-10-13 14:10 ` Tabi Timur-B04825
2011-10-13 14:25 ` Geert Uytterhoeven
2011-10-13 14:35 ` Timur Tabi [this message]
2011-10-12 16:16 ` Hans J. Koch
2011-10-12 16:19 ` Hans J. Koch
2011-10-12 18:40 ` Kumar Gala
2011-10-12 20:23 ` Hans J. Koch
2011-10-12 20:58 ` Kumar Gala
-- strict thread matches above, loose matches on Subject: below --
2011-10-13 15:50 Kumar Gala
2011-10-14 18:31 ` Hans J. Koch
2011-10-14 18:36 ` Greg KH
2011-10-14 18:46 ` Hans J. Koch
2011-10-17 16:00 ` Kumar Gala
2011-10-17 17:18 ` Hans J. Koch
2011-10-17 18:03 ` Hans J. Koch
2011-10-17 18:23 ` Greg KH
2011-10-17 18:50 ` Hans J. Koch
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=4E96F723.2010304@freescale.com \
--to=timur@freescale.com \
--cc=B18973@freescale.com \
--cc=geert@linux-m68k.org \
--cc=gregkh@suse.de \
--cc=hjk@hansjkoch.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.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).