mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sherry Sun <sherry.sun@nxp.com>
To: sudeep.dutt@intel.com, ashutosh.dixit@intel.com, arnd@arndb.de,
	gregkh@linuxfoundation.org
Cc: linux-kernel@vger.kernel.org, linux-imx@nxp.com
Subject: [PATCH V2 0/4] Fix some bugs of the vop driver and mpssd user space tool
Date: Tue, 29 Sep 2020 17:11:02 +0800	[thread overview]
Message-ID: <20200929091106.24624-1-sherry.sun@nxp.com> (raw)

Changes in V2:
1. Change the way of copy data from ubuf to dbuf in patch4. Reuse the allocated
vvr->buf as the temp buffer and add a loop for multiple copies if there are too
much data.

This patchset fix some bugs about the vop driver and Intel MIC user space tool.

Sherry Sun (4):
  samples: mpssd: fix the build errors when enable DEBUG in mpssd.c
  misc: vop: build VOP based on CONFIG_VOP
  misc: vop: add round_up(x,4) for vring_size to avoid kernel panic
  mic: vop: copy data to kernel space then write to io memory

 drivers/misc/mic/vop/Makefile     |  2 +-
 drivers/misc/mic/vop/vop_main.c   |  2 +-
 drivers/misc/mic/vop/vop_vringh.c | 24 ++++++++++++++++--------
 samples/mic/mpssd/mpssd.c         | 24 ++++++++++++------------
 4 files changed, 30 insertions(+), 22 deletions(-)

-- 
2.17.1


             reply	other threads:[~2020-09-29  9:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-29  9:11 Sherry Sun [this message]
2020-09-29  9:11 ` [PATCH V2 1/4] samples: mpssd: fix the build errors when enable DEBUG Sherry Sun
2020-09-29  9:11 ` [PATCH V2 2/4] misc: vop: build VOP based on CONFIG_VOP Sherry Sun
2020-09-29  9:11 ` [PATCH V2 3/4] misc: vop: add round_up(x,4) for vring_size to avoid kernel panic Sherry Sun
2020-09-29  9:11 ` [PATCH V2 4/4] mic: vop: copy data to kernel space then write to io memory Sherry Sun

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=20200929091106.24624-1-sherry.sun@nxp.com \
    --to=sherry.sun@nxp.com \
    --cc=arnd@arndb.de \
    --cc=ashutosh.dixit@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sudeep.dutt@intel.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

all inboxes | Powered by JetHome®