linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Mark Brown <broonie@kernel.org>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: build failure after merge of the spi tree
Date: Mon, 29 Jul 2013 16:48:20 +1000	[thread overview]
Message-ID: <20130729164820.38c47ee56d98d67debc77f97@canb.auug.org.au> (raw)
In-Reply-To: <20130729064028.GR9858@sirena.org.uk>

[-- Attachment #1: Type: text/plain, Size: 759 bytes --]

Hi Mark,

On Mon, 29 Jul 2013 07:40:28 +0100 Mark Brown <broonie@kernel.org> wrote:
>
> Yeah, unfortunately those issues are a good proportion of what gets
> caught by this sort of testing that wouldn't get caught in normal
> development so it doesn't seem worth doing something that won't at least
> give a linking kernel.

The problem is that you are impacting on other people's testing.  Even if
this stuff builds for me, it may well break for people using other
arches/configs.  These changes (adding dependencies on
CONFIG_COMPILE_TEST for devices that are currently only built for
particular platforms) are adding very little, but impacting on my time (at
least).

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2013-07-29  6:48 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-29  3:42 linux-next: build failure after merge of the spi tree Stephen Rothwell
2013-07-29  5:00 ` Mark Brown
2013-07-29  5:56   ` Stephen Rothwell
2013-07-29  6:40     ` Mark Brown
2013-07-29  6:48       ` Stephen Rothwell [this message]
2013-07-29  8:00         ` Mark Brown
  -- strict thread matches above, loose matches on Subject: below --
2022-02-16  5:17 Stephen Rothwell
2022-02-16 12:20 ` André Almeida
2022-02-16 13:07   ` André Almeida
2022-02-16 16:08     ` Mark Brown
2022-02-16 16:13       ` André Almeida
2022-02-16 16:07   ` Mark Brown
2022-02-15  2:08 Stephen Rothwell
2022-02-15  7:33 ` Uwe Kleine-König
2022-01-27  4:57 Stephen Rothwell
2018-08-29  0:33 Stephen Rothwell
2018-08-29  1:29 ` Baolin Wang
2017-12-22  2:18 Stephen Rothwell
2017-12-22  7:39 ` Rasmus Villemoes
2017-12-22 15:51   ` Mark Brown
2017-07-10  3:26 Stephen Rothwell
2017-07-03  3:41 Stephen Rothwell
2017-05-24  1:08 Stephen Rothwell
2017-05-24  3:29 ` Jiada Wang
2016-12-09  2:32 Stephen Rothwell
2016-12-12  2:24 ` Stephen Rothwell
2016-05-16  2:08 Stephen Rothwell
2016-05-16 10:23 ` Mark Brown
2016-01-06  3:34 Stephen Rothwell
2015-08-21  4:10 Stephen Rothwell
2015-05-12  3:14 Stephen Rothwell
2015-04-07  6:49 Stephen Rothwell
2015-01-30  3:02 Stephen Rothwell
2015-01-30  5:43 ` Ricardo Ribalda Delgado
2014-12-08 12:05 Stephen Rothwell
2014-12-08 12:13 ` Mark Brown
2014-12-08 12:54   ` Lee Jones
2014-12-08 12:58     ` Mark Brown
2014-12-08 13:56 ` Laurentiu Palcu
2014-04-15  2:17 Stephen Rothwell
2014-04-15  4:35 ` Harini Katakam
2014-02-24  3:45 Stephen Rothwell
2014-02-24  6:00 ` Mark Brown
2014-01-06  7:03 Stephen Rothwell
2014-01-06  7:09 ` Baruch Siach
2013-08-27  6:15 Stephen Rothwell
2013-08-27  7:20 ` Sourav Poddar
2011-06-07  2:53 Stephen Rothwell
2011-06-07 16:51 ` Grant Likely
2010-10-14  1:55 Stephen Rothwell
2010-10-14  1:58 ` Grant Likely
2010-06-29  3:29 Stephen Rothwell
2010-06-29  5:02 ` Grant Likely

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=20130729164820.38c47ee56d98d67debc77f97@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=broonie@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.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).