From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: "Hans J. Koch" <hjk@hansjkoch.de>,
linux-kernel@vger.kernel.org, kernel@pengutronix.de
Subject: Re: [PATCH v2 1/2] uio: provide vm access to UIO_MEM_PHYS maps
Date: Mon, 29 Jul 2013 13:09:14 -0700 [thread overview]
Message-ID: <20130729200914.GA6146@kroah.com> (raw)
In-Reply-To: <1374962978-1860-1-git-send-email-u.kleine-koenig@pengutronix.de>
On Sun, Jul 28, 2013 at 12:09:37AM +0200, Uwe Kleine-König wrote:
> This makes it possible to let gdb access mappings of the process that is
> being debugged.
>
> uio_mmap_logical was moved and uio_vm_ops renamed to group related code
> and differentiate to new stuff.
>
> Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
> ---
> Changes since v1:
> - only use generic_access_phys ifdef CONFIG_HAVE_IOREMAP_PROT
> - fix all users of renamed struct
I still get a build error with this patch:
MODPOST 384 modules
ERROR: "generic_access_phys" [drivers/uio/uio.ko] undefined!
So something isn't quite right.
greg k-h
next prev parent reply other threads:[~2013-07-29 20:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-16 17:21 [PATCH 0/2] Resend of two uio patches Uwe Kleine-König
2013-07-16 17:21 ` [PATCH 1/2] uio: provide vm access to UIO_MEM_PHYS maps Uwe Kleine-König
2013-07-27 0:58 ` Greg Kroah-Hartman
2013-07-27 21:49 ` Uwe Kleine-König
2013-07-27 22:09 ` [PATCH v2 " Uwe Kleine-König
2013-07-27 22:09 ` [PATCH v2 2/2] uio: drop unused vma_count member in uio_device struct Uwe Kleine-König
2013-07-29 20:09 ` Greg Kroah-Hartman [this message]
2013-07-30 7:52 ` [PATCH v2 1/2] uio: provide vm access to UIO_MEM_PHYS maps Uwe Kleine-König
2013-07-30 13:49 ` Greg Kroah-Hartman
2013-07-30 14:32 ` Uwe Kleine-König
2013-07-30 14:38 ` Greg Kroah-Hartman
2013-07-16 17:21 ` [PATCH 2/2] uio: drop unused vma_count member in uio_device struct Uwe Kleine-König
2013-07-16 17:25 ` [PATCH 0/2] Resend of two uio patches Greg Kroah-Hartman
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=20130729200914.GA6146@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=hjk@hansjkoch.de \
--cc=kernel@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=u.kleine-koenig@pengutronix.de \
/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