From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
To: Matt Ranostay <matt.ranostay@konsulko.com>
Cc: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Re: [PATCH RESEND] obex: report notification status on incoming message
Date: Tue, 11 Feb 2020 13:01:42 -0800 [thread overview]
Message-ID: <CABBYNZJVeugUw-s7XDzjSknGwHKyg2w2UXd_PUHoRmMZ9GXk4g@mail.gmail.com> (raw)
In-Reply-To: <20200207050856.9249-1-matt.ranostay@konsulko.com>
Hi Matt.
On Thu, Feb 6, 2020 at 9:12 PM Matt Ranostay <matt.ranostay@konsulko.com> wrote:
>
> To match doc/obex.txt on incoming message notification the respective
> Status field should be set.
> ---
> obexd/client/map.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/obexd/client/map.c b/obexd/client/map.c
> index 550c5afb4..23be2d6b2 100644
> --- a/obexd/client/map.c
> +++ b/obexd/client/map.c
> @@ -1914,6 +1914,7 @@ static void map_handle_notification(struct map_event *event, void *user_data)
> switch (event->type) {
> case MAP_ET_NEW_MESSAGE:
> map_handle_new_message(map, event);
> + map_handle_status_changed(map, event, "notification");
> break;
> case MAP_ET_DELIVERY_SUCCESS:
> map_handle_status_changed(map, event, "delivery-success");
> --
> 2.20.1
Applied, thanks.
--
Luiz Augusto von Dentz
next prev parent reply other threads:[~2020-02-11 21:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-07 5:08 [PATCH RESEND] obex: report notification status on incoming message Matt Ranostay
2020-02-11 21:01 ` Luiz Augusto von Dentz [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-08-29 19:38 Matt Ranostay
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=CABBYNZJVeugUw-s7XDzjSknGwHKyg2w2UXd_PUHoRmMZ9GXk4g@mail.gmail.com \
--to=luiz.dentz@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=matt.ranostay@konsulko.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).