From: Greg KH <gregkh@linuxfoundation.org>
To: Xiaolong Ye <yexl@marvell.com>
Cc: hjk@hansjkoch.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] uio: add uio_event_sync interface
Date: Wed, 14 Aug 2013 11:34:57 -0700 [thread overview]
Message-ID: <20130814183457.GA25715@kroah.com> (raw)
In-Reply-To: <1376483423-603-2-git-send-email-yexl@marvell.com>
On Wed, Aug 14, 2013 at 08:30:23PM +0800, Xiaolong Ye wrote:
> This interface is called to sync listener->event_count and device
> event count in multi-instances case.
>
> Change-Id: Ibb1e4888ce55b4993394b61e4bcd6dce8b8291f0
What is this for? (hint, it should never be in a kernel patch...)
> Signed-off-by: Xiaolong Ye <yexl@marvell.com>
> ---
> drivers/uio/uio.c | 12 ++++++++++++
> include/linux/uio_driver.h | 1 +
> 2 files changed, 13 insertions(+)
>
> diff --git a/drivers/uio/uio.c b/drivers/uio/uio.c
> index ba47563..95d559f 100644
> --- a/drivers/uio/uio.c
> +++ b/drivers/uio/uio.c
> @@ -408,6 +408,18 @@ void uio_event_notify(struct uio_info *info)
> EXPORT_SYMBOL_GPL(uio_event_notify);
>
> /**
> + * uio_event_sync - sync listener's event count with UIO device
> + * @listener: uio_listener structure
> + */
> +void uio_event_sync(struct uio_listener *listener)
> +{
> + struct uio_device *idev = listener->dev;
> +
> + listener->event_count = atomic_read(&idev->event);
What prevents that count from changing right after you call this
function?
> +}
> +EXPORT_SYMBOL_GPL(uio_event_sync);
You are exporting a symbol, yet never using it, which means I can't
accept this patch, sorry.
greg k-h
next prev parent reply other threads:[~2013-08-14 18:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-14 12:30 [PATCH] Add uio_sync_event interface to support mulit-instances case in UIO framework Xiaolong Ye
2013-08-14 12:30 ` [PATCH] uio: add uio_event_sync interface Xiaolong Ye
2013-08-14 18:34 ` Greg KH [this message]
2013-08-14 18:36 ` [PATCH] Add uio_sync_event interface to support mulit-instances case in UIO framework Greg KH
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=20130814183457.GA25715@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=hjk@hansjkoch.de \
--cc=linux-kernel@vger.kernel.org \
--cc=yexl@marvell.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 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.