From: Carlos Santos <casantos@datacom.ind.br>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 2/2] modem-manager: Update to version 1.7.990
Date: Tue, 20 Feb 2018 12:56:31 -0300 (BRT) [thread overview]
Message-ID: <2048847825.30672.1519142191454.JavaMail.zimbra@datacom.ind.br> (raw)
In-Reply-To: <05fed3b8-01d4-1f66-6de6-0164d6388507@free.fr>
> From: "Julien Boibessot" <julien.boibessot@free.fr>
> To: "Carlos Santos" <casantos@datacom.ind.br>, "Thomas Petazzoni" <thomas.petazzoni@bootlin.com>, "Jared Bents"
> <jared.bents@rockwellcollins.com>
> Cc: "buildroot" <buildroot@buildroot.org>
> Sent: Tuesday, February 20, 2018 11:57:44 AM
> Subject: Re: [Buildroot] [PATCH v2 2/2] modem-manager: Update to version 1.7.990
> Hello,
>
> Thomas, Carlos, Jared,
>
> On 19/02/2018 22:23, Carlos Santos wrote:
>>> From: "Thomas Petazzoni" <thomas.petazzoni@bootlin.com>
>>> To: "Carlos Santos" <casantos@datacom.ind.br>
>>> Cc: "Jared Bents" <jared.bents@rockwellcollins.com>, "buildroot"
>>> <buildroot@buildroot.org>
>>> Sent: Monday, February 19, 2018 5:05:04 AM
>>> Subject: Re: [Buildroot] [PATCH v2 2/2] modem-manager: Update to version 1.7.990
>>> Hello,
>>>
>>> On Sun, 18 Feb 2018 21:03:04 -0300 (BRT), Carlos Santos wrote:
>>>
>>>>> Are you sure 1.7.990 isn't a development version ? Interestingly, their
>>>>> Git repo has no tag with this name:
>>>>> https://cgit.freedesktop.org/ModemManager/ModemManager/refs/tags. It
>>>>> has a 1.8-rc1 version. So it does feel like 1.7.x might be a
>>>>> development version. Could you double check this ?
>>>> It is a development version. That's why I submitted an update to the
>>>> latest release version, which is 1.6.12:
>>>>
>>>> https://patchwork.ozlabs.org/patch/871059/
>>> When is the final 1.8.x version expected ? If it's in the very near
>>> future (i.e before 2018.05-rc1), then we could accept the 1.7.x bump for
>>> now, and move to 1.8.x when it lands. Otherwise, I'd prefer to stick
>>> with 1.6.x for now.
>> The announcement message[1], from Sun Jan 21, informs that 1.7.990
>> corresponds to 1.8-rc1. From the list of 1.5.99x releases, which spans
>> several months, I believe that 1.8 will unlikely be released before
>> the end of February.
>>
>> Notice that I'm sympathetic to upgrading the Buildroot package to
>> 1.7.990, since this release includes the quectel plugin. Currently I
>> need to maintain that change as a local patch in my BR2_LOCAL.
>>
>> 1.
>> https://lists.freedesktop.org/archives/modemmanager-devel/2018-January/006157.html
>>
>
> +1 to bump modemmanager to 1.7.990, as it adds support for Sierra
> EM7565, which I'm using. But for me, beside bump of libqmi to 1.20.0, it
> also requires bump of libmbim to 1.16.0.
It's on the "next" branch, already:
https://git.buildroot.net/buildroot/commit/?id=0a726eab68b4f8c8a760da049fd538fb35f4d201
--
Carlos Santos (Casantos) - DATACOM, P&D
?The greatest triumph that modern PR can offer is the transcendent
success of having your words and actions judged by your reputation,
rather than the other way about.? ? Christopher Hitchens
next prev parent reply other threads:[~2018-02-20 15:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-16 16:38 [Buildroot] [PATCH v2 1/2] libqmi: Update to use libqmi 1.20.0 Jared Bents
2018-02-16 16:38 ` [Buildroot] [PATCH v2 2/2] modem-manager: Update to version 1.7.990 Jared Bents
2018-02-16 20:53 ` Thomas Petazzoni
2018-02-19 0:03 ` Carlos Santos
2018-02-19 8:05 ` Thomas Petazzoni
2018-02-19 21:23 ` Carlos Santos
2018-02-20 14:57 ` Julien Boibessot
2018-02-20 15:56 ` Carlos Santos [this message]
2018-02-23 11:17 ` Aleksander Morgado
2018-04-01 22:52 ` Thomas Petazzoni
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=2048847825.30672.1519142191454.JavaMail.zimbra@datacom.ind.br \
--to=casantos@datacom.ind.br \
--cc=buildroot@busybox.net \
/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