linux-tegra.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
To: Thierry Reding
	<thierry.reding-RM9K5IK7kjKj5M59NBduVrNAH6kLmebB@public.gmane.org>
Cc: linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 0/3] ARM: tegra: defconfig updates for 3.8
Date: Thu, 15 Nov 2012 15:27:18 -0700	[thread overview]
Message-ID: <50A56C46.6010300@wwwdotorg.org> (raw)
In-Reply-To: <1353015894-20003-1-git-send-email-thierry.reding-RM9K5IK7kjKj5M59NBduVrNAH6kLmebB@public.gmane.org>

On 11/15/2012 02:44 PM, Thierry Reding wrote:
> The following set of patches enables the Tegra DRM driver along with the
> framebuffer console and the PWM backlight driver to light up panels that
> are driven by the DRM driver. A third patch enables SquashFS, which is
> used as the root filesystem on Tamonten-based boards.

Thanks, I have squashed the series into Tegra's for-3.8/defconfig
branch. Squashed rather than applied since there's still a desire to
keep the number of defconfig-related commits minimal.

      parent reply	other threads:[~2012-11-15 22:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-15 21:44 [PATCH 0/3] ARM: tegra: defconfig updates for 3.8 Thierry Reding
     [not found] ` <1353015894-20003-1-git-send-email-thierry.reding-RM9K5IK7kjKj5M59NBduVrNAH6kLmebB@public.gmane.org>
2012-11-15 21:44   ` [PATCH 1/3] ARM: tegra: Update default configuration (backlight) Thierry Reding
2012-11-15 21:44   ` [PATCH 2/3] ARM: tegra: Update default configuration (DRM) Thierry Reding
2012-11-15 21:44   ` [PATCH 3/3] ARM: tegra: Update default configuration (squashfs) Thierry Reding
2012-11-15 22:27   ` Stephen Warren [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=50A56C46.6010300@wwwdotorg.org \
    --to=swarren-3lzwwm7+weoh9zmkesr00q@public.gmane.org \
    --cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=thierry.reding-RM9K5IK7kjKj5M59NBduVrNAH6kLmebB@public.gmane.org \
    /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;
as well as URLs for NNTP newsgroup(s).