From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: [PATCH] gprs: Fix allocation of context id read from settings
Date: Tue, 02 Apr 2019 10:41:34 -0500 [thread overview]
Message-ID: <dec32406-2bd4-6c27-fa20-4958cdedbdc8@gmail.com> (raw)
In-Reply-To: <20190402072853.7793-1-richard.rojfors@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 582 bytes --]
Hi Richard,
On 04/02/2019 02:28 AM, richard.rojfors(a)gmail.com wrote:
> From: Richard Röjfors <richard@puffinpack.se>
>
> This fix is similar to the one in the following commit,
> but fixes allocation for context ids after ap's are
> read from settings.
>
> commit c3fdf6a7c567a7507c3558a27006b6f9559493d6
> Author: Denis Kenzior <denkenz@gmail.com>
> Date: Thu Jan 3 17:17:21 2019 -0600
>
> gprs: Fix allocation of context id
> ---
> src/gprs.c | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
Applied, thanks.
Regards,
-Denis
prev parent reply other threads:[~2019-04-02 15:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-02 7:28 [PATCH] gprs: Fix allocation of context id read from settings richard.rojfors
2019-04-02 15:41 ` Denis Kenzior [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=dec32406-2bd4-6c27-fa20-4958cdedbdc8@gmail.com \
--to=denkenz@gmail.com \
--cc=ofono@ofono.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox