From: Logan Gunthorpe <logang@deltatee.com>
To: Serge Semin <fancer.lancer@gmail.com>,
jdmason@kudzu.us, dave.jiang@intel.com, Allen.Hubbe@emc.com,
Shyam-sundar.S-k@amd.com, Xiangliang.Yu@amd.com,
gary.hook@amd.com
Cc: Sergey.Semin@t-platforms.ru, linux-ntb@googlegroups.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] NTB: ntb_tool: Add full multi-port NTB API support
Date: Tue, 8 Aug 2017 12:26:23 -0600 [thread overview]
Message-ID: <d1121616-a2f1-7d36-fdee-3076cb6e7db4@deltatee.com> (raw)
In-Reply-To: <20170808101147.24625-1-fancer.lancer@gmail.com>
On 08/08/17 04:11 AM, Serge Semin wrote:
> +static ssize_t tool_db_event_write(struct file *filep,
> + const char __user *ubuf,
> + size_t size, loff_t *offp)
> +{
> + struct tool_ctx *tc = filep->private_data;
> + u64 val;
> + int ret;
> +
> + ret = kstrtou64_from_user(ubuf, size, 0, &val);
> + if (ret)
> + return ret;
> +
> + if (wait_event_interruptible(tc->db_wq, ntb_db_read(tc->ntb) == val))
> + return -ERESTART;
> +
> + return size;
> +}
Also, I like the fact that we are adding a db_event feature, however
this really needs to be a separate commit as it's a completely different
feature and not even mentioned in the commit message. There's a few of
these instances.
Logan
next prev parent reply other threads:[~2017-08-08 18:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-08 10:11 Serge Semin
2017-08-08 18:23 ` Logan Gunthorpe
2017-08-08 18:26 ` Logan Gunthorpe [this message]
2017-11-30 21:37 ` [PATCH v2] " Serge Semin
2017-11-30 22:23 ` Logan Gunthorpe
2017-12-03 9:45 ` kbuild test robot
2017-12-03 9:50 ` kbuild test robot
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=d1121616-a2f1-7d36-fdee-3076cb6e7db4@deltatee.com \
--to=logang@deltatee.com \
--cc=Allen.Hubbe@emc.com \
--cc=Sergey.Semin@t-platforms.ru \
--cc=Shyam-sundar.S-k@amd.com \
--cc=Xiangliang.Yu@amd.com \
--cc=dave.jiang@intel.com \
--cc=fancer.lancer@gmail.com \
--cc=gary.hook@amd.com \
--cc=jdmason@kudzu.us \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-ntb@googlegroups.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®