All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vinicius Costa Gomes <vinicius.gomes@openbossa.org>
To: Gustavo Padovan <gustavo@padovan.org>
Cc: linux-bluetooth@vger.kernel.org,
	Gustavo Padovan <gustavo.padovan@collabora.co.uk>
Subject: Re: [PATCH 3/4] monitor: add filter support
Date: Tue, 22 May 2012 12:02:39 -0300	[thread overview]
Message-ID: <20120522150239.GA12709@samus> (raw)
In-Reply-To: <1337665227-7228-3-git-send-email-gustavo@padovan.org>

Hi Gustavo,

Here are some nitpicks, feel free to ignore them.

On 02:40 Tue 22 May, Gustavo Padovan wrote:
> From: Gustavo Padovan <gustavo.padovan@collabora.co.uk>

The title "add filter support" is not totally correct, there was some
support for filters, but it was quite basic, right?

> 
> the packet code receives the data parsed from the filter file and apply
> the proper filters to the devices.
> ---
>  monitor/config_file.c |    4 +-
>  monitor/config_file.h |    1 +
>  monitor/main.c        |   21 +++++-----
>  monitor/packet.c      |  108 ++++++++++++++++++++++++++++++++++++++++---------
>  monitor/packet.h      |    4 +-
>  5 files changed, 106 insertions(+), 32 deletions(-)
> 
> diff --git a/monitor/config_file.c b/monitor/config_file.c
> index 6fb50f9..464fe4f 100644
> --- a/monitor/config_file.c
> +++ b/monitor/config_file.c
> @@ -79,7 +79,7 @@ static struct filter_options {
>  
>  struct controller *controller;
>  
> -static void free_controllers_list(struct list *controllers_l)
> +void controllers_list_free(struct list *controllers_l)

This change is somewhat unrelated.

>  {
>  	struct list *l, *tmp;
>  
> @@ -318,7 +318,7 @@ struct list *parse_config(char *file)
>  	return controllers_l;
>  
>  error:


[snip]

>  
>  void packet_hexdump(const unsigned char *buf, uint16_t len);
>  
> -- 
> 1.7.10.1
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


Cheers,
-- 
Vinicius

  parent reply	other threads:[~2012-05-22 15:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-22  5:40 [PATCH 1/4] monitor: add include <stdint.h> Gustavo Padovan
2012-05-22  5:40 ` [PATCH 2/4] monitor: add config_file parser Gustavo Padovan
2012-05-22  5:40   ` [PATCH 3/4] monitor: add filter support Gustavo Padovan
2012-05-22  5:40     ` [PATCH 4/4] monitor: add example filter file Gustavo Padovan
2012-05-22 15:02     ` Vinicius Costa Gomes [this message]
2012-05-22 15:30       ` [PATCH 3/4] monitor: add filter support Gustavo Padovan
  -- strict thread matches above, loose matches on Subject: below --
2012-06-13  2:59 [PATCH 1/4] monitor: add include <stdint.h> Gustavo Padovan
2012-06-13  2:59 ` [PATCH 3/4] monitor: add filter support Gustavo Padovan

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=20120522150239.GA12709@samus \
    --to=vinicius.gomes@openbossa.org \
    --cc=gustavo.padovan@collabora.co.uk \
    --cc=gustavo@padovan.org \
    --cc=linux-bluetooth@vger.kernel.org \
    /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.