linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: u.kleine-koenig@pengutronix.de (Uwe Kleine-König)
To: linux-arm-kernel@lists.infradead.org
Subject: Remove unused default configurations
Date: Wed, 6 Oct 2010 15:03:38 +0200	[thread overview]
Message-ID: <20101006130338.GH29673@pengutronix.de> (raw)
In-Reply-To: <AANLkTi==1Rj2W8QPuiZdoGHCZ5Q0dJ-_j0xogURQ6nPt@mail.gmail.com>

On Wed, Oct 06, 2010 at 10:46:48AM +0300, Amit Kucheria wrote:
> On Mon, Sep 13, 2010 at 6:13 PM, Vincent Sanders <vince@kyllikki.org> wrote:
> >
> > Several default configurations have failed to build for the entire
> > 2.6.36 cycle. There are several causes to these faliures. The exact
> > issues can be tracked on http://armlinux.simtec.co.uk/kautobuild/
> >
> > Obviously the maintainers are not using these default configurations
> > because if they were they would have fixed the build issues by now.
> >
> > As Linus has made it very clear the number of default configurations
> > must be reduced as much as possible I have come up with the following
> > series which will remove these nine unused configurations. This will
> > reduce our build coverage by ten machines as all but one are a single
> > config per machine.
> >
> > ?msm_defconfig ? ? ? ? ? ? ? | ? 72 ------------------
> > ?mx1_defconfig ? ? ? ? ? ? ? | ? 90 -----------------------
> > ?mx51_defconfig ? ? ? ? ? ? ?| ?171 --------------------------------------------
> 
> Could we please keep mx51?
> 
> I'll attempt to fix the problems.
No need to hurry, the problems are already solved in Linus' and Sascha's
trees. :-)

Best regards
Uwe

-- 
Pengutronix e.K.                           | Uwe Kleine-K?nig            |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

      reply	other threads:[~2010-10-06 13:03 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-13 15:13 Remove unused default configurations Vincent Sanders
2010-09-13 15:13 ` [PATCH 1/9] Remove unused default configuration Vincent Sanders
2010-09-13 15:13 ` [PATCH 2/9] " Vincent Sanders
2010-09-14 14:05   ` Uwe Kleine-König
2010-09-13 15:13 ` [PATCH 3/9] " Vincent Sanders
2010-09-13 15:13 ` [PATCH 4/9] Remove unused n8x0 " Vincent Sanders
2010-09-13 15:13 ` [PATCH 5/9] Remove unused omap generic 2420 " Vincent Sanders
2010-09-13 15:13 ` [PATCH 6/9] Remove unused pxa3xx " Vincent Sanders
2010-09-14  6:15   ` Haojian Zhuang
2010-09-14  6:51   ` Eric Miao
2010-09-13 15:13 ` [PATCH 7/9] Remove unused qil-a9260 " Vincent Sanders
2010-09-13 15:13 ` [PATCH 8/9] Remove unused usb-a9260 " Vincent Sanders
2010-09-13 15:13 ` [PATCH 9/9] Remove unused usb-a9263 " Vincent Sanders
2010-09-13 15:27   ` Jean-Christophe PLAGNIOL-VILLARD
2010-09-13 15:56     ` Vincent Sanders
2010-09-13 15:43   ` Thomas Petazzoni
2010-09-13 16:00     ` Vincent Sanders
2010-09-13 18:08   ` avictor.za at gmail.com
2010-09-13 18:24     ` Russell King - ARM Linux
2010-09-13 17:24 ` Remove unused default configurations Daniel Walker
2010-09-14  7:20   ` Eric Miao
2010-10-06  7:46 ` Amit Kucheria
2010-10-06 13:03   ` Uwe Kleine-König [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=20101006130338.GH29673@pengutronix.de \
    --to=u.kleine-koenig@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.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).