All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Andrew Morton <akpm@osdl.org>,
	Linux Kernel list <linux-kernel@vger.kernel.org>,
	linux-pci <linux-pci@atrey.karlin.mff.cuni.cz>,
	linuxppc64-dev <linuxppc64-dev@ozlabs.org>
Subject: Re: [PATCH] ppc/ppc64: Fix pci mmap via sysfs
Date: Tue, 28 Jun 2005 00:51:40 -0700	[thread overview]
Message-ID: <20050628075140.GF3577@kroah.com> (raw)
In-Reply-To: <1119838264.5133.76.camel@gaston>

On Mon, Jun 27, 2005 at 12:11:03PM +1000, Benjamin Herrenschmidt wrote:
> On Sun, 2005-06-26 at 18:57 -0700, Andrew Morton wrote:
> > Benjamin Herrenschmidt <benh@kernel.crashing.org> wrote:
> > >
> > > Hi !
> > > 
> > > This implement the change to /proc and sysfs PCI mmap functions that we
> > > discussed a while ago, that is adding an arch optional
> > > pci_resource_to_user() to allow munging on the exposed value of PCI
> > > resources to userland and thus hiding kernel internal values. It also
> > > implements using of that callback to sanitize exposed values on ppc an
> > > ppc64, thus fixing mmap of PCI devices via /proc and sysfs.
> > > 
> > 
> > You sure you want all those printks in there?
> 
> One quilt ref later ... :)
> 
> Hi !
> 
> This implement the change to /proc and sysfs PCI mmap functions that we
> discussed a while ago, that is adding an arch optional
> pci_resource_to_user() to allow munging on the exposed value of PCI
> resources to userland and thus hiding kernel internal values. It also
> implements using of that callback to sanitize exposed values on ppc an
> ppc64, thus fixing mmap of PCI devices via /proc and sysfs.

Hm, did I just send the right one to Linus?

thanks,

greg k-h

  reply	other threads:[~2005-06-28  8:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-27  1:36 [PATCH] ppc/ppc64: Fix pci mmap via sysfs Benjamin Herrenschmidt
     [not found] ` <20050626185727.0ce92772.akpm@osdl.org>
2005-06-27  2:11   ` Benjamin Herrenschmidt
2005-06-28  7:51     ` Greg KH [this message]
2005-06-28 23:53       ` Benjamin Herrenschmidt
2005-06-28 21:19     ` Jesse Barnes

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=20050628075140.GF3577@kroah.com \
    --to=greg@kroah.com \
    --cc=akpm@osdl.org \
    --cc=benh@kernel.crashing.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@atrey.karlin.mff.cuni.cz \
    --cc=linuxppc64-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 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.