public inbox for linux-tegra@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: stable@vger.kernel.org, linux-tegra@vger.kernel.org,
	Paul Walmsley <pwalmsley@nvidia.com>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH stable] ARM: tegra: unify Tegra's Kconfig a bit more
Date: Sat, 5 Oct 2013 16:38:33 -0700	[thread overview]
Message-ID: <20131005233833.GA18223@kroah.com> (raw)
In-Reply-To: <1380917411-25869-1-git-send-email-swarren@wwwdotorg.org>

On Fri, Oct 04, 2013 at 02:10:11PM -0600, Stephen Warren wrote:
> From: Stephen Warren <swarren@nvidia.com>
> 
> Move all common select clauses from ARCH_TEGRA_*_SOC to ARCH_TEGRA to
> eliminate duplication. The USB-related selects all should have been
> common too, but were missing from Tegra114 previously. Move these to
> ARCH_TEGRA too. The latter fixes a build break when only Tegra114
> support was enabled, but not Tegra20 or Tegra30 support.
> 
> This is 20984c44b5a08620778ea14fa5807489170fd5ca in v3.12-rc1.
> 
> Signed-off-by: Stephen Warren <swarren@nvidia.com>
> Reported-by: Paul Walmsley <pwalmsley@nvidia.com>
> [auto-builders for 3.11.x are failing due to this]

What autobuilders?  I haven't heard of this before.

> Cc: stable # v3.11
> ---
>  arch/arm/mach-tegra/Kconfig | 21 ++++++---------------
>  1 file changed, 6 insertions(+), 15 deletions(-)

This fails to apply to the 3.11-stable tree, if you want it there, can
you provide a version that actually does apply, and that you have tested
to work properly?

thanks,

greg k-h

  reply	other threads:[~2013-10-05 23:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-04 20:10 [PATCH stable] ARM: tegra: unify Tegra's Kconfig a bit more Stephen Warren
2013-10-05 23:38 ` Greg KH [this message]
2013-10-07  6:18   ` Paul Walmsley
     [not found]     ` <52525247.9060609-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-10-08  6:00       ` Paul Walmsley
     [not found]         ` <52539F98.2030307-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-10-10 23:11           ` Greg KH
     [not found]             ` <20131010231135.GF4301-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2013-10-14 18:00               ` Kevin Hilman
     [not found]                 ` <87bo2r91hg.fsf-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2013-10-14 18:20                   ` Greg KH
2013-10-14 18:11               ` Paul Walmsley
     [not found]                 ` <525C33D1.4080509-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-10-14 18:20                   ` Greg KH
     [not found]   ` <20131005233833.GA18223-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2013-10-07 16:47     ` Stephen Warren

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=20131005233833.GA18223@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=pwalmsley@nvidia.com \
    --cc=stable@vger.kernel.org \
    --cc=swarren@wwwdotorg.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