All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@xenotime.net>
To: sedat.dilek@gmail.com
Cc: Sedat Dilek <sedat.dilek@googlemail.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	Stephen Boyd <sboyd@codeaurora.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: linux-next: Tree for Aug 1
Date: Mon, 1 Aug 2011 14:54:22 -0700	[thread overview]
Message-ID: <20110801145422.cccff7aa.rdunlap@xenotime.net> (raw)
In-Reply-To: <CA+icZUXq9V6h6kJrjckpeDXQAbQ-skiKLwTjD7Luhz1mTqSM1w@mail.gmail.com>

On Mon, 1 Aug 2011 09:01:21 +0200 Sedat Dilek wrote:

> On Mon, Aug 1, 2011 at 6:47 AM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> > Hi all,
> >
> > Just in case anyone needs reminding:  Please do not add anything destined
> > for v3.2 into linux-next included trees until after v3.1-rc1.
> >
> > The powerpc allyesconfig build (at least) fails today.
> >
> > Changes since 20110729:
> >
> > Linus' tree still lost its build failure.
> >
> > The v4l-dvb tree lost its conflicts.
> >
> > The kgdb tree gained a build failure for which I reverted 3 commits.
> >
> > The moduleh tree gained a conflict against the slabe-dma tree but lost
> > its build failures (except for a few remaining merge fixups).
> >
> > ----------------------------------------------------------------------------
> >
> 
> Just FYI: mmotm-tree still misses the fixup-patch from [1].
> 
> - Sedat -
> 
> [1] https://patchwork.kernel.org/patch/1021602/

Yes, I am applying this patch daily (among others).  :(

Acked-by: Randy Dunlap <rdunlap@xenotime.net>

---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

  reply	other threads:[~2011-08-01 21:54 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-01  4:47 linux-next: Tree for Aug 1 Stephen Rothwell
2011-08-01  7:01 ` Sedat Dilek
2011-08-01 21:54   ` Randy Dunlap [this message]
2011-08-02  1:29     ` Stephen Rothwell
2011-08-02 10:38       ` Sedat Dilek
2011-08-01 21:52 ` linux-next: Tree for Aug 1 (wireless/rt2x00) Randy Dunlap
2013-08-01  7:25 linux-next: Tree for Aug 1 Stephen Rothwell
2013-08-01  7:25 ` Stephen Rothwell
2013-08-01  7:50 ` Sedat Dilek
2014-08-01  9:14 Stephen Rothwell
2016-08-01  4:02 Stephen Rothwell
2017-08-01  7:37 Stephen Rothwell
2017-08-01 12:42 ` Sergey Senozhatsky
2017-08-01 13:20   ` Arnd Bergmann
2017-08-01 13:28     ` Arnd Bergmann
2017-08-01 23:55       ` Sergey Senozhatsky
2017-08-02 11:13         ` Arnd Bergmann
2018-08-01  7:58 Stephen Rothwell
2018-08-01 22:48 ` Guenter Roeck
2018-08-01 22:52   ` James Bottomley
2018-08-01 23:00     ` James Bottomley
2018-08-02  0:05       ` Stephen Rothwell
2018-08-02  1:19         ` Guenter Roeck
2018-08-01 23:47     ` Guenter Roeck
2018-08-01 23:57       ` Ming Lei
2018-08-02  0:03         ` James Bottomley
2018-08-02  0:20           ` Guenter Roeck
2018-08-02  4:58           ` Guenter Roeck
2018-08-02  5:04             ` Bart Van Assche
2018-08-02  5:04               ` Bart Van Assche
2018-08-02 12:46               ` Guenter Roeck
2018-08-02 12:46                 ` Guenter Roeck
2018-08-02 12:51                 ` Johannes Thumshirn
2018-08-02 12:51                   ` Johannes Thumshirn
2018-08-02 13:00                   ` Guenter Roeck
2018-08-02 13:00                     ` Guenter Roeck
2018-08-02 13:06                     ` Johannes Thumshirn
2018-08-02 13:06                       ` Johannes Thumshirn
2018-08-02 11:35             ` Ming Lei
2018-08-02 13:05               ` Guenter Roeck
2018-08-02 16:27                 ` Ming Lei
2018-08-02 16:40                   ` Bart Van Assche
2018-08-02 16:40                     ` Bart Van Assche
2018-08-02 16:50                     ` Ming Lei
2018-08-02 16:50                       ` Ming Lei
2018-08-02 16:57                       ` Bart Van Assche
2018-08-02 16:57                         ` Bart Van Assche
2018-08-02  0:12         ` Guenter Roeck
2019-08-01  6:14 Stephen Rothwell
2023-08-01  5:19 Stephen Rothwell

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=20110801145422.cccff7aa.rdunlap@xenotime.net \
    --to=rdunlap@xenotime.net \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sboyd@codeaurora.org \
    --cc=sedat.dilek@gmail.com \
    --cc=sedat.dilek@googlemail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.