Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Clarify the Intel driver related patches in patchwork
Date: Tue, 29 Jul 2014 09:22:14 +0200	[thread overview]
Message-ID: <20140729092214.539f130e@free-electrons.com> (raw)

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
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

             reply	other threads:[~2014-07-29  7:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-29  7:22 Thomas Petazzoni [this message]
2014-07-29 17:21 ` [Buildroot] Clarify the Intel driver related patches in patchwork Ben Widawsky
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=20140729092214.539f130e@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox