All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Juerg Haefliger <juerg.haefliger@canonical.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH v2] shared/shell: Fix --init-script commandline option
Date: Mon, 13 Nov 2023 19:22:17 +0000	[thread overview]
Message-ID: <169990333723.26848.7920910573164487116.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231030065341.8998-1-juerg.haefliger@canonical.com>

Hello:

This patch was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:

On Mon, 30 Oct 2023 07:53:41 +0100 you wrote:
> The newly added option -i/--init-script introduced a short option
> namespace collision with btmgmt's --index, both of which use '-i'.
> 
> As a result, a provided --index is treated as a file name:
> 
> $ sudo btmgmt --index 0 info
> Unable to open 0: No such file or directory (2)
> 
> [...]

Here is the summary with links:
  - [v2] shared/shell: Fix --init-script commandline option
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=303925b28110

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2023-11-13 19:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-26 16:24 bluez: btmgmt --index broken Juerg Haefliger
2023-10-26 16:37 ` bluez.test.bot
2023-10-27  5:54 ` [BlueZ PATCH] shared/shell: Fix --init-script commandline option Juerg Haefliger
2023-10-27  7:29   ` [BlueZ] " bluez.test.bot
2023-10-30  6:53   ` [PATCH v2] " Juerg Haefliger
2023-10-30  8:18     ` [v2] " bluez.test.bot
2023-11-06 16:26     ` [PATCH v2] " Luiz Augusto von Dentz
2023-11-07  8:37       ` Juerg Haefliger
2023-11-13 19:22     ` patchwork-bot+bluetooth [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=169990333723.26848.7920910573164487116.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=juerg.haefliger@canonical.com \
    --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.