linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnaud Lacombe <lacombar@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Greg KH <greg@kroah.com>,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: build failure after merge of the final tree (tty tree related)
Date: Fri, 26 Aug 2011 11:47:40 -0400	[thread overview]
Message-ID: <CACqU3MVbKJw5VVqnz+gfLDnQEDu9Lv4xV+7RvdD4ZbetGu79WQ@mail.gmail.com> (raw)
In-Reply-To: <20110826103932.1626f1c5542b660bcd1b24aa@canb.auug.org.au>

Hi,

[Removed PPC folks from the CC list, the conversation drifted.]

On Thu, Aug 25, 2011 at 8:39 PM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi Arnaud,
>
> On Thu, 25 Aug 2011 12:09:20 -0400 Arnaud Lacombe <lacombar@gmail.com> wrote:
>>
>> If you could provide an exhaustive list of them, I'd be interested. Do
>> you account/reference them in the report you make on each new -next
>> tree ?
>
> I don't refer to them at all :-(
>
> If you are not just referring to powerpc ones, then an x86_64
> allmodconfig is a good place to start, there are several in there.
>
> Otherwise, I will send you the results of some of my builds this evening.
>
Couldn't all the error log be public, rotated over a 7 iteration
period ? That would be fair to everyone.

Thanks,
 - Arnaud

  reply	other threads:[~2011-08-26 15:47 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-25  6:18 linux-next: build failure after merge of the final tree (tty tree related) Stephen Rothwell
2011-08-25 14:08 ` Greg KH
2011-08-25 14:28   ` Timur Tabi
2011-08-25 15:22   ` Timur Tabi
2011-08-25 15:51     ` Stephen Rothwell
2011-08-25 16:09       ` Arnaud Lacombe
2011-08-26  0:39         ` Stephen Rothwell
2011-08-26 15:47           ` Arnaud Lacombe [this message]
2011-09-11  4:23             ` Stephen Rothwell
2011-09-11  9:05               ` Geert Uytterhoeven
  -- strict thread matches above, loose matches on Subject: below --
2013-10-28 14:33 Stephen Rothwell
2013-10-28 14:49 ` Michal Simek
2013-10-28 16:05 ` Sören Brinkmann
2013-10-28 16:33   ` Greg KH
2013-10-29  7:04     ` Stephen Rothwell
2013-09-27  8:21 Stephen Rothwell
2013-09-28  1:04 ` Greg KH
2013-04-02  7:57 Stephen Rothwell
2012-11-26 13:49 Stephen Rothwell
2012-11-26 14:35 ` Steven Rostedt
2012-11-26 23:05   ` Stephen Rothwell
2012-12-13 23:32     ` Stephen Rothwell
2012-12-13 23:38       ` Greg KH
2012-12-14  0:11         ` Steven Rostedt
2012-09-24 14:36 Stephen Rothwell
2012-09-25 22:41 ` Greg KH
2012-07-20  5:02 Stephen Rothwell
2012-07-25 22:47 ` Greg KH
2012-07-26  0:23   ` Alan Cox
2012-07-25 22:52 ` Stephen Rothwell
2010-12-17  6:11 Stephen Rothwell
2010-12-17  7:04 ` Greg KH
2010-12-17 10:16   ` Thomas Gleixner
2011-01-06  3:27     ` Stephen Rothwell
2011-01-06 18:45       ` Greg KH
2010-11-12  1:57 Stephen Rothwell
2010-11-12 10:44 ` Alan Cox

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=CACqU3MVbKJw5VVqnz+gfLDnQEDu9Lv4xV+7RvdD4ZbetGu79WQ@mail.gmail.com \
    --to=lacombar@gmail.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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).