From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4] package/cog: add option for platform DRM.
Date: Mon, 06 Apr 2020 20:18:09 +0300 [thread overview]
Message-ID: <87o8s4edny.fsf@tarshish> (raw)
In-Reply-To: <092c5373232c820c5b730ff21d737b333c3f5dd2.camel@igalia.com>
Hi Charles,
On Mon, Apr 06 2020, Charles Turner wrote:
> Hello,
>
> Thank you for your reviews.
>
> I have commented below. As an aside, I note my patch has been removed
> from the Patchwork interface[1]. My process so far was to find it
> there, copy the message ID, and continue the version bumps. However,
> now that I can't find it there, and that this has become a patch
> *series*, I will be sending new mails.
Your patch is still there:
http://patchwork.ozlabs.org/patch/1265532/
It state has changed to "Changes Requested" so it does not appear in the
default view. You can remove the "State = Action Required" filter to see
your patch listed. You can also search patches by submitter:
http://patchwork.ozlabs.org/project/buildroot/list/?submitter=76614&series=&q=&delegate=&archive=&state=*
You can also do all that from command line using the pwclient utility:
http://patchwork.ozlabs.org/pwclient/
baruch
> On Sun, 2020-04-05 at 01:49 +0300, Adrian Perez de Castro wrote:
>> Hello,
>>
>> I am adding a few comments to Thomas' questions below.
>>
>> On Sat, 4 Apr 2020 23:46:30 +0200, Thomas Petazzoni <
>> thomas.petazzoni at bootlin.com> wrote:
>>
>> > On Thu, 2 Apr 2020 12:34:55 +0100
>> > Charlie Turner <cturner@igalia.com> wrote:
>> >
>> > > diff --git a/package/cog/Config.in b/package/cog/Config.in
>> > > index b25991d4ae..6a7c5668a5 100644
>> > > --- a/package/cog/Config.in
>> > > +++ b/package/cog/Config.in
>> > > @@ -7,7 +7,9 @@ config BR2_PACKAGE_COG
>> > > depends on BR2_PACKAGE_WPEWEBKIT
>> > > depends on BR2_TOOLCHAIN_HAS_THREADS # dbus
>> > > depends on BR2_USE_MMU # dbus
>> > > +
>> >
>> > Why this new empty line?
>
> It was visually pleasing at the time, sorry for introducing an
> inconsistency, I should have checked.
>
>> > Why are you dropping the wayland and wayland-protocols
>> > dependencies?
>> > Overall, it makes sense because cog does not depends/select wayland
>> > or
>> > wayland-protocols. Ditto for wpebackend-fdo.
>>
>> We need those, but only when BR2_PACKAGE_COG_PLATFORM_FDO is enabled.
>
> I slightly diverted here, wayland is needed for both FDO and DRM (FDO
> is a client and DRM is a server). Only FDO registers new protocols, so
> that is platform-specific.
>
> Best,
> Charlie.
>
> [1] https://patchwork.ozlabs.org/project/buildroot/list/
>
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
prev parent reply other threads:[~2020-04-06 17:18 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-10 11:22 [Buildroot] [PATCH 1/2] package/cog: add option for platform DRM Charlie Turner
2020-03-10 11:22 ` [Buildroot] [PATCH 2/2] board/raspberrypi: add post-image option for VC4 overlay Charlie Turner
2020-03-10 12:58 ` Peter Seiderer
2020-03-10 13:42 ` Charles Turner
2020-03-10 12:36 ` [Buildroot] [PATCH 1/2] package/cog: add option for platform DRM Peter Seiderer
2020-03-10 13:49 ` Charles Turner
2020-03-10 14:23 ` Peter Seiderer
2020-03-11 10:30 ` [Buildroot] [PATCH v2 1/1] " Charlie Turner
2020-03-11 12:49 ` Adrian Perez de Castro
2020-03-12 11:03 ` Thomas Petazzoni
2020-03-12 13:11 ` Charles Turner
2020-03-12 13:36 ` Thomas Petazzoni
2020-03-12 19:36 ` Charles Turner
2020-03-12 19:47 ` [Buildroot] [PATCH v3 " Charlie Turner
2020-03-23 13:30 ` Charles Turner
2020-03-31 21:57 ` Adrian Perez de Castro
2020-04-02 11:34 ` [Buildroot] [PATCH v4] " Charlie Turner
2020-04-04 21:46 ` Thomas Petazzoni
2020-04-04 22:49 ` Adrian Perez de Castro
2020-04-06 5:29 ` Thomas Petazzoni
2020-04-06 17:04 ` Charles Turner
2020-04-06 17:18 ` Baruch Siach [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=87o8s4edny.fsf@tarshish \
--to=baruch@tkos.co.il \
--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