From: Ben Widawsky <ben@bwidawsk.net>
To: buildroot@busybox.net
Subject: [Buildroot] Clarify the Intel driver related patches in patchwork
Date: Tue, 29 Jul 2014 10:21:10 -0700 [thread overview]
Message-ID: <20140729172109.GA1263@bwidawsk.net> (raw)
In-Reply-To: <20140729092214.539f130e@free-electrons.com>
On Tue, Jul 29, 2014 at 09:22:14AM +0200, Thomas Petazzoni wrote:
> Ben, Bernd,
>
> There are quite a few X.org intel driver related patches in patchwork,
> but it is not clear which one both of you agree with, and therefore
> which ones should be applied. Could you give me an update on:
>
> http://patchwork.ozlabs.org/patch/373074/ (this patch doesn't have a
> proper commit log)
>
> http://patchwork.ozlabs.org/patch/371342/
>
> http://patchwork.ozlabs.org/patch/371343/
>
> http://patchwork.ozlabs.org/patch/370975/
>
> Thanks,
>
> Thomas
A patch (not in that list) to bump to .913 would solve all problems for
me. It seems like Bernd would be okay with this as well, though he sent
that mail only to me, "So updating buildroot to 2.99.914 is ok for me
now." I presume he meant .913.
Feel free to mark all of mine obsolete, and let's see what Bernd's
response to this is. I'd vote for marking them all obsolete and doing
the .913 bump.
I'd be happy to do the .913 package, but I don't want to step on Bernd's
toes. Just let me know if you want it. It will take a day or two for me
to actually test it.
--
Ben Widawsky, Intel Open Source Technology Center
next prev parent reply other threads:[~2014-07-29 17:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-29 7:22 [Buildroot] Clarify the Intel driver related patches in patchwork Thomas Petazzoni
2014-07-29 17:21 ` Ben Widawsky [this message]
2014-07-29 21:38 ` Bernd Kuhls
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=20140729172109.GA1263@bwidawsk.net \
--to=ben@bwidawsk.net \
--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