All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Amisha Jain <quic_amisjain@quicinc.com>
Cc: linux-bluetooth@vger.kernel.org, quic_mohamull@quicinc.com,
	quic_hbandi@quicinc.com, quic_anubhavg@quicinc.com
Subject: Re: [PATCH v2] obexctl: Enable Map folderlisting operation from obexctl
Date: Mon, 16 Dec 2024 21:50:34 +0000	[thread overview]
Message-ID: <173438583486.361160.18150307733869076812.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241216152330.2579138-1-quic_amisjain@quicinc.com>

Hello:

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

On Mon, 16 Dec 2024 20:53:30 +0530 you wrote:
> This change is required for passing below PTS testcase -
> 
> 1) MAP/MCE/MMB/BV-01-C
> Verify that the MCE can retrieve a Folders Listing on the MSE.
> 
> As of now, user is able to initiate only map messagelisting
> operation with command 'ls <folder_name>' and there is no way to initiate
> folder listing with 'ls' command as second argument <options> is
> set as compulsary.
> In the obexctl code, map folderlisting gets triggered only when there is no
> arguments followed by 'ls' command.
> Therefore in 'ls' command, make the second argument as optional.
> 
> [...]

Here is the summary with links:
  - [v2] obexctl: Enable Map folderlisting operation from obexctl
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=c2caa26a4d62

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



      parent reply	other threads:[~2024-12-16 21:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-16 15:23 [PATCH v2] obexctl: Enable Map folderlisting operation from obexctl Amisha Jain
2024-12-16 16:36 ` [v2] " bluez.test.bot
2024-12-16 21:50 ` 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=173438583486.361160.18150307733869076812.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=quic_amisjain@quicinc.com \
    --cc=quic_anubhavg@quicinc.com \
    --cc=quic_hbandi@quicinc.com \
    --cc=quic_mohamull@quicinc.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.