From: Scott Wood <oss@buserror.net>
To: Wang Wenhu <wenhu.wang@vivo.com>,
gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org
Cc: kernel@vivo.com, robh@kernel.org
Subject: Re: [PATCH] drivers: uio: new driver uio_fsl_85xx_cache_sram
Date: Fri, 17 Apr 2020 18:02:12 -0500 [thread overview]
Message-ID: <1f05e37b5aa52aad44d4310edfdc6b36894cb964.camel@buserror.net> (raw)
In-Reply-To: <20200417172130.14287-1-wenhu.wang@vivo.com>
On Fri, 2020-04-17 at 10:21 -0700, Wang Wenhu wrote:
> Implements a new uio driver for freescale 85xx platforms to access
> the Cache-Sram form user level. It is extremely helpful for the user
> space applications that require high performance memory accesses.
>
> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Cc: Christophe Leroy <christophe.leroy@c-s.fr>
> Cc: Scott Wood <oss@buserror.net>
> Cc: Michael Ellerman <mpe@ellerman.id.au>
> Cc: linuxppc-dev@lists.ozlabs.org
> Signed-off-by: Wang Wenhu <wenhu.wang@vivo.com>
> ---
> drivers/uio/Kconfig | 8 +
> drivers/uio/Makefile | 1 +
> drivers/uio/uio_fsl_85xx_cache_sram.c | 407 ++++++++++++++++++++++++++
> 3 files changed, 416 insertions(+)
> create mode 100644 drivers/uio/uio_fsl_85xx_cache_sram.c
NACK, we don't need two copies of this code in the kernel. Please just wait a
bit and I'll send a patch to have the existing driver expose a dynamic
allocation interface to userspace.
-Scott
prev parent reply other threads:[~2020-04-17 23:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-17 17:21 [PATCH] drivers: uio: new driver uio_fsl_85xx_cache_sram Wang Wenhu
2020-04-17 17:39 ` Randy Dunlap
2020-04-17 23:02 ` Scott Wood [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=1f05e37b5aa52aad44d4310edfdc6b36894cb964.camel@buserror.net \
--to=oss@buserror.net \
--cc=gregkh@linuxfoundation.org \
--cc=kernel@vivo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=robh@kernel.org \
--cc=wenhu.wang@vivo.com \
/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).