linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Szymon Janc <szymon.janc@tieto.com>
To: Lukasz Rymanowski <lukasz.rymanowski@tieto.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH v2 1/5] monitor: Allow to modify epoll even events are the same
Date: Wed, 05 Mar 2014 14:24:25 +0100	[thread overview]
Message-ID: <8771068.vOHNjRSlbZ@uw000953> (raw)
In-Reply-To: <1394011361-9469-1-git-send-email-lukasz.rymanowski@tieto.com>

Hi Łukasz,

On Wednesday 05 of March 2014 10:22:37 Lukasz Rymanowski wrote:
> This is epsecially needed when we want to modify timer.
> ---
>  monitor/mainloop.c | 3 ---
>  1 file changed, 3 deletions(-)
> 
> diff --git a/monitor/mainloop.c b/monitor/mainloop.c
> index 8c94bfe..7f97e65 100644
> --- a/monitor/mainloop.c
> +++ b/monitor/mainloop.c
> @@ -222,9 +222,6 @@ int mainloop_modify_fd(int fd, uint32_t events)
>  	if (!data)
>  		return -ENXIO;
>  
> -	if (data->events == events)
> -		return 0;
> -
>  	memset(&ev, 0, sizeof(ev));
>  	ev.events = events;
>  	ev.data.ptr = data;
> 

All patches applied. Thanks.

-- 
Best regards, 
Szymon Janc

      parent reply	other threads:[~2014-03-05 13:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-05  9:22 [PATCH v2 1/5] monitor: Allow to modify epoll even events are the same Lukasz Rymanowski
2014-03-05  9:22 ` [PATCH v2 2/5] monitor: Use miliseconds instead of seconds in the timeout Lukasz Rymanowski
2014-03-05 13:39   ` Anderson Lizardo
2014-03-05  9:22 ` [PATCH v2 3/5] shared: Add header for timeout abstraction Lukasz Rymanowski
2014-03-05  9:22 ` [PATCH v2 4/5] shared: Add timeout handling with Glib support Lukasz Rymanowski
2014-03-05  9:22 ` [PATCH v2 5/5] shared: Add timeout handling with mainloop support Lukasz Rymanowski
2014-03-05 13:24 ` Szymon Janc [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=8771068.vOHNjRSlbZ@uw000953 \
    --to=szymon.janc@tieto.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=lukasz.rymanowski@tieto.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).