All of lore.kernel.org
 help / color / mirror / Atom feed
From: Romain Naour <romain.naour@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] librtas: bump to version 2.0.1
Date: Sat, 2 Jun 2018 17:44:59 +0200	[thread overview]
Message-ID: <3ceb070b-e676-0ec8-07a5-b1718580c35b@gmail.com> (raw)
In-Reply-To: <CAPi7W815UOMcksm06w0H9x4zm9syEPXJsOheEo9tsog0pQpRgA@mail.gmail.com>

Hi Fabrice,

Le 02/06/2018 ? 17:25, Fabrice Fontaine a ?crit?:
> Dear Romain,
> 
> 2018-06-02 16:56 GMT+02:00 Romain Naour <romain.naour@gmail.com
> <mailto:romain.naour@gmail.com>>:
> 
>     Hi Fabrice,
> 
>     Le 02/06/2018 ? 16:43, Fabrice Fontaine a ?crit?:
>     > - Switch site to github
>     > - Move to autotools infrastructure
>     > - Remove patch (not needed anymore)
>     > - Since version 1.4 (January 2016), license is now LGPL-2.1+
>     > - Add hash for license file
>     > 
>     > Signed-off-by: Fabrice Fontaine <fontaine.fabrice at gmail.com <mailto:fontaine.fabrice@gmail.com>>
> 
>     Did you check if powerpc-utils with rtas still build with this new version ?
> 
> Yes, powerpc-utils still builds with this new version.

Ok, thanks for checking :)

> By the way, this new version of librtas is quite old (July 2016) and
> powerpc-utils is up to date in buildroot (September 2017).

Indeed, there is no activity except one commit in July 2017 in next branch.

Best regards,
Romain

> 
>     IIRC, librtas package has been added by Sam Bobroff to be used with
>     powerpc-utils.
> 
>     Best regards,
>     Romain
> 
> Best Regards,
> 
> Fabrice

  reply	other threads:[~2018-06-02 15:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-02 14:43 [Buildroot] [PATCH 1/1] librtas: bump to version 2.0.1 Fabrice Fontaine
2018-06-02 14:56 ` Romain Naour
2018-06-02 15:25   ` Fabrice Fontaine
2018-06-02 15:44     ` Romain Naour [this message]
2018-06-03 18:30 ` 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=3ceb070b-e676-0ec8-07a5-b1718580c35b@gmail.com \
    --to=romain.naour@gmail.com \
    --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 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.