All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2] /dev/mem: use phys_addr_t for physical addresses
Date: Wed, 12 Sep 2012 18:15:03 +0000	[thread overview]
Message-ID: <20120912181503.GB12840@kroah.com> (raw)
In-Reply-To: <1347473158-7219-1-git-send-email-cyril@ti.com>

On Wed, Sep 12, 2012 at 02:05:58PM -0400, Cyril Chemparathy wrote:
> This patch fixes the /dev/mem driver to use phys_addr_t for physical
> addresses.  This is required on PAE systems, especially those that run
> entirely out of >4G physical memory space.

What is the symptom if this patch is not applied?  Does it need to be
backported to older kernels?  If so, which ones?

thanks,

greg k-h

WARNING: multiple messages have this Message-ID (diff)
From: gregkh@linuxfoundation.org (Greg KH)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] /dev/mem: use phys_addr_t for physical addresses
Date: Wed, 12 Sep 2012 11:15:03 -0700	[thread overview]
Message-ID: <20120912181503.GB12840@kroah.com> (raw)
In-Reply-To: <1347473158-7219-1-git-send-email-cyril@ti.com>

On Wed, Sep 12, 2012 at 02:05:58PM -0400, Cyril Chemparathy wrote:
> This patch fixes the /dev/mem driver to use phys_addr_t for physical
> addresses.  This is required on PAE systems, especially those that run
> entirely out of >4G physical memory space.

What is the symptom if this patch is not applied?  Does it need to be
backported to older kernels?  If so, which ones?

thanks,

greg k-h

WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <gregkh@linuxfoundation.org>
To: Cyril Chemparathy <cyril@ti.com>
Cc: linux-arm-kernel@lists.infradead.org, linux-ia64@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-sh@vger.kernel.org,
	arnd@arndb.de, dhowells@redhat.com, fenghua.yu@intel.com,
	lethal@linux-sh.org, linux@arm.linux.org.uk, nico@linaro.org,
	rob.herring@calxeda.com, tony.luck@intel.com, tony@atomide.com,
	will.deacon@arm.com
Subject: Re: [PATCH v2] /dev/mem: use phys_addr_t for physical addresses
Date: Wed, 12 Sep 2012 11:15:03 -0700	[thread overview]
Message-ID: <20120912181503.GB12840@kroah.com> (raw)
In-Reply-To: <1347473158-7219-1-git-send-email-cyril@ti.com>

On Wed, Sep 12, 2012 at 02:05:58PM -0400, Cyril Chemparathy wrote:
> This patch fixes the /dev/mem driver to use phys_addr_t for physical
> addresses.  This is required on PAE systems, especially those that run
> entirely out of >4G physical memory space.

What is the symptom if this patch is not applied?  Does it need to be
backported to older kernels?  If so, which ones?

thanks,

greg k-h

  reply	other threads:[~2012-09-12 18:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-12 18:05 [PATCH v2] /dev/mem: use phys_addr_t for physical addresses Cyril Chemparathy
2012-09-12 18:05 ` Cyril Chemparathy
2012-09-12 18:05 ` Cyril Chemparathy
2012-09-12 18:15 ` Greg KH [this message]
2012-09-12 18:15   ` Greg KH
2012-09-12 18:15   ` Greg KH
2012-09-12 22:54   ` Cyril Chemparathy
2012-09-12 22:54     ` Cyril Chemparathy
2012-09-12 22:54     ` Cyril Chemparathy

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=20120912181503.GB12840@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.