All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2/next 3/4] webkitgtk: update to version 2.20.0
Date: Tue, 10 Apr 2018 17:57:38 +0200	[thread overview]
Message-ID: <20180410175738.40345498@windsurf> (raw)
In-Reply-To: <20180410165409.GD19381@momiji>

Hello,

On Tue, 10 Apr 2018 16:54:09 +0100, Adrian Perez de Castro wrote:

> The change for AArch64 is just listing BR2_aarch64 in WEBKITGTK_ARCH_SUPPORTS,
> the addition is in the first patch.

Then the following paragraph that you wrote:

   This series starts with the same three patches as the previous
   submission, and adds on top three additional commits to make
   WebKitGTK+ available on AArch64 (it's a platform we support
   upstream), and adds a couple of patches which are already merged in
   the upstream repository, but are not in the release and are worth
   applying.

is a bit unclear. You're saying "adds on top three additional commits
to make WebKitGTK+ available on AArch6". What those three additional
commits ?

For the record, your patch series was:

  brotli: new package
  woff2: new package
  webkitgtk: update to version 2.20.0
  webkitgtk: Add upstream patch for better memory monitoring

> Anyway, I was waiting a bit until the 2.20.1 release, which just happened:
> 
>   https://webkitgtk.org/2018/04/10/webkitgtk2.20.1-released.html
> 
> Updating to 2.20.1 directly is IMHO better because it includes the fix for
> building with multimedia disabled, and a fix to improve memory consumption
> on devices with smaller amounts of memory ? which is particularly welcome
> for embedded :-)
> 
> I'm making a test build with 2.20.1 as I wrote this mail, if all goes well
> the new patch set will supersede this one.

OK, thanks. Some clarification about the above would be nice. Perhaps
it was just a mistake in your cover letter ?

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2018-04-10 15:57 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-23 18:59 [Buildroot] [PATCH v2/next 0/4] Update WebKitGTK+ to 2.20.0 Adrian Perez de Castro
2018-03-23 18:59 ` [Buildroot] [PATCH v2/next 1/4] brotli: new package Adrian Perez de Castro
2018-03-24 10:45   ` Peter Korsgaard
2018-04-02 20:25   ` Thomas Petazzoni
2018-04-02 22:07     ` Adrian Perez de Castro
2018-04-02 22:30       ` Peter Korsgaard
2018-04-03 17:15         ` Adrian Perez de Castro
2018-03-23 18:59 ` [Buildroot] [PATCH v2/next 2/4] woff2: " Adrian Perez de Castro
2018-03-24 10:48   ` Peter Korsgaard
2018-05-09  8:54   ` Thomas Petazzoni
2018-03-23 18:59 ` [Buildroot] [PATCH v2/next 3/4] webkitgtk: update to version 2.20.0 Adrian Perez de Castro
2018-03-24 10:51   ` Peter Korsgaard
2018-04-10  7:53     ` Thomas Petazzoni
2018-04-10 15:54       ` Adrian Perez de Castro
2018-04-10 15:57         ` Thomas Petazzoni [this message]
2018-04-10 16:18           ` Adrian Perez de Castro
2018-04-10 18:55             ` Thomas Petazzoni
2018-04-10 19:18               ` Adrian Perez de Castro
2018-04-10 21:22                 ` Thomas Petazzoni
2018-04-10 22:06                   ` Adrian Perez de Castro
2018-03-23 18:59 ` [Buildroot] [PATCH v2/next 4/4] webkitgtk: Add upstream patch for better memory monitoring Adrian Perez de Castro
2018-05-02  7:23 ` [Buildroot] [PATCH v2/next 0/4] Update WebKitGTK+ to 2.20.0 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=20180410175738.40345498@windsurf \
    --to=thomas.petazzoni@bootlin.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.