Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Romain Naour <romain.naour@openwide.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC 00/37] efl bump to 1.14.2
Date: Mon, 28 Sep 2015 23:00:48 +0200	[thread overview]
Message-ID: <5609AA80.6040106@openwide.fr> (raw)
In-Reply-To: <CAAMcf8DcwuJvASF1A12hLSTKsyK3553CL5hv9dnPT+vrMwo9sA@mail.gmail.com>

Hi Vicente,

Le 27/09/2015 02:37, vj a ?crit :
> Hello Romain,
> this weekend I had some time to spend on this, sorry for the delay.

That's ok, I guess you're working on your free time :)

> 
> I've posted the EFL issue:
> http://sourceforge.net/p/enlightenment/mailman/message/34493376

Glad to see you had some help on your error on framebuffer support.
If you send me a git formated patch that fixes your issue, be sure it'll be part
of the next efl series. (I hope, in the meantime, a patch will be applied
upstream and backported to 1.15 stable branch before the 1.15.2 release).

> 
> And tested your efl-1.15.1-v1 branch from
> git://github.com/RomainNaour/buildroot.git
> Aside from the EFL workaround (-fvisibility=default) the only
> remaining issue is that when audio is disabled it fails to build
> because of bae9cf8354208bdad7780e0d11e5b4c8cf1b1f3e.
> I think it should be safe to just revert it because multisense is
> already enabled by default and (as an audio-related feature) it only
> makes sense when audio is also enabled.

Thanks for the testing and the feedback!
The last patches from efl-1.15.1-v1 branch are WIP and won't be included yet in
the next Buildroot series. I'll take a closer look to multisense stuff.

> 
> Regards,
>   Vicente.
> 
> Tested-by: Vicente Bergas <vicencb@gmail.com>
> 

I already added your tested-by tag in the commit that bump efl for the target.
https://github.com/RomainNaour/buildroot/commit/04b24bc4e9b9c21209cbdb1110d0ae41991f838d

Also, tags are not taken into account by patchwork when you reply to a cover
letter. You can send several tags on a specific patch on the series by replying
to the email.

Best regards,
Romain

  reply	other threads:[~2015-09-28 21:00 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-21  0:30 [Buildroot] [RFC 00/37] efl bump to 1.14.2 vj
2015-08-21  9:51 ` Romain Naour
2015-08-21 10:18   ` Romain Naour
2015-08-21 17:56   ` vj
2015-08-24 21:42     ` Romain Naour
2015-08-24 22:09       ` vj
2015-09-05 14:55         ` Romain Naour
2015-09-27  0:37           ` vj
2015-09-28 21:00             ` Romain Naour [this message]
2015-10-05 19:41               ` [Buildroot] efl: fix framebuffer support Vicente Bergas
2015-10-05 19:41                 ` Vicente Bergas
2015-10-09 21:32                   ` Romain Naour
2015-10-09 21:04                 ` Romain Naour
  -- strict thread matches above, loose matches on Subject: below --
2015-08-03 18:55 [Buildroot] [RFC 00/37] efl bump to 1.14.2 vj
2015-08-03 23:10 ` Romain Naour
2015-07-26 18:55 Romain Naour
2015-08-06  8:45 ` Romain Naour

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=5609AA80.6040106@openwide.fr \
    --to=romain.naour@openwide.fr \
    --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