linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
To: luokai <454728735@qq.com>
Cc: "linux-bluetooth@vger.kernel.org"
	<linux-bluetooth@vger.kernel.org>, luokai <luokai@uniontech.com>
Subject: Re: [PATCH BlueZ 1/1] src/agent.c : parse_io_capability Function optimization
Date: Mon, 27 Jul 2020 16:21:40 -0700	[thread overview]
Message-ID: <CABBYNZ+7DuiuNZQ8AZnvSoGPQXD8pG0sVMqwy=xoGp2EWYQLPw@mail.gmail.com> (raw)
In-Reply-To: <20200724122507.27671-1-454728735@qq.com>

Hi,

On Fri, Jul 24, 2020 at 5:27 AM luokai <454728735@qq.com> wrote:
>
> From: luokai <luokai@uniontech.com>
>
> ---
>  src/agent.c | 28 ++++++++++++++++------------
>  1 file changed, 16 insertions(+), 12 deletions(-)
>
> diff --git a/src/agent.c b/src/agent.c
> index e0ffcd22f..82baf608f 100644
> --- a/src/agent.c
> +++ b/src/agent.c
> @@ -957,20 +957,24 @@ static void agent_destroy(gpointer data)
>         agent_unref(agent);
>  }
>
> +static struct capability g_cap[]  = {
> +       {"", IO_CAPABILITY_KEYBOARDDISPLAY},
> +       {"DisplayOnly", IO_CAPABILITY_DISPLAYONLY},
> +       {"DisplayYesNo", IO_CAPABILITY_DISPLAYYESNO},
> +       {"KeyboardOnly", IO_CAPABILITY_KEYBOARDONLY},
> +       {"NoInputNoOutput", IO_CAPABILITY_NOINPUTNOOUTPUT},
> +       {"KeyboardDisplay", IO_CAPABILITY_KEYBOARDDISPLAY}

We usually spaces after { and before }.

> +};
> +
>  static uint8_t parse_io_capability(const char *capability)
>  {
> -       if (g_str_equal(capability, ""))
> -               return IO_CAPABILITY_KEYBOARDDISPLAY;
> -       if (g_str_equal(capability, "DisplayOnly"))
> -               return IO_CAPABILITY_DISPLAYONLY;
> -       if (g_str_equal(capability, "DisplayYesNo"))
> -               return IO_CAPABILITY_DISPLAYYESNO;
> -       if (g_str_equal(capability, "KeyboardOnly"))
> -               return IO_CAPABILITY_KEYBOARDONLY;
> -       if (g_str_equal(capability, "NoInputNoOutput"))
> -               return IO_CAPABILITY_NOINPUTNOOUTPUT;
> -       if (g_str_equal(capability, "KeyboardDisplay"))
> -               return IO_CAPABILITY_KEYBOARDDISPLAY;
> +       size_t count = sizeof(g_cap) / sizeof(g_cap[0]);

If I recall correctly we do have macros for ARRAY_SIZE, check
src/shared/util.h, btw there also seems to be a problem with the
formatting on the above line:

Applying: src/agent.c : parse_io_capability Function optimization
.git/rebase-apply/patch:36: trailing whitespace.
size_t count = sizeof(g_cap) / sizeof(g_cap[0]);
error: 1 line adds whitespace errors.


> +       for (size_t i = 0; i < count; i++)
> +       {
> +               if(g_str_equal(capability, g_cap[i].cap)) {
> +                       return g_cap[i].parse_capability;
> +               }
> +       }
>         return IO_CAPABILITY_INVALID;
>  }
>
> --
> 2.20.1
>
>
>


-- 
Luiz Augusto von Dentz

      reply	other threads:[~2020-07-27 23:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-24 12:25 [PATCH BlueZ 1/1] src/agent.c : parse_io_capability Function optimization luokai
2020-07-27 23:21 ` Luiz Augusto von Dentz [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='CABBYNZ+7DuiuNZQ8AZnvSoGPQXD8pG0sVMqwy=xoGp2EWYQLPw@mail.gmail.com' \
    --to=luiz.dentz@gmail.com \
    --cc=454728735@qq.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luokai@uniontech.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).