From: Wolfram Sang <wsa@the-dreams.de>
To: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
David Airlie <airlied@linux.ie>, Ben Skeggs <bskeggs@redhat.com>,
linux-i2c@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: linux-next: Tree for Mar 14
Date: Tue, 15 Mar 2016 07:43:19 +0100 [thread overview]
Message-ID: <20160315064318.GA1385@katana> (raw)
In-Reply-To: <20160315003029.GA2126@swordfish>
[-- Attachment #1: Type: text/plain, Size: 760 bytes --]
On Tue, Mar 15, 2016 at 09:30:29AM +0900, Sergey Senozhatsky wrote:
> On (03/14/16 17:40), Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20160311:
> >
> > The vfs tree gained a conflict against Linus' tree. I also applied a
> > patch for a known runtime bug.
> >
> > The tip tree gained a conflict against the mips tree.
> >
> > The aio tree still had a build failure so I removed several commits
> > from it. It also gained a conflict against the vfs tree.
> >
> > Non-merge commits (relative to Linus' tree): 11202
> > 8646 files changed, 426680 insertions(+), 211740 deletions(-)
>
>
> Hello,
>
> I'm seeing a bunch of warnings and errors
I pushed the fix to my for-next branch yesterday. Sorry for the fuzz!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-03-15 6:43 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-14 6:40 linux-next: Tree for Mar 14 Stephen Rothwell
2016-03-14 14:37 ` Guenter Roeck
2016-03-14 16:51 ` James Morse
2016-03-14 19:18 ` Guenter Roeck
2016-03-14 23:55 ` Michael Ellerman
2016-03-15 2:31 ` Guenter Roeck
2016-03-15 5:26 ` linux-next: Tree for Mar 14 (mips qemu failure bisected) Guenter Roeck
2016-03-15 21:55 ` Qais Yousef
2016-03-16 0:17 ` Guenter Roeck
2016-03-16 13:22 ` Guenter Roeck
2016-03-16 20:27 ` Qais Yousef
2016-03-16 22:17 ` Qais Yousef
2016-03-16 22:17 ` Qais Yousef
2016-03-17 2:10 ` Guenter Roeck
2016-03-17 2:36 ` Guenter Roeck
[not found] ` <CA+mqd+5AUfGSh1WvLa5bOt-HQM=eA+BmLeb7_xZo+-tswLcqiQ@mail.gmail.com>
2016-03-17 12:43 ` Guenter Roeck
2016-03-15 0:30 ` linux-next: Tree for Mar 14 Sergey Senozhatsky
2016-03-15 6:43 ` Wolfram Sang [this message]
2016-03-15 6:52 ` Sergey Senozhatsky
-- strict thread matches above, loose matches on Subject: below --
2025-03-14 7:04 Stephen Rothwell
2024-03-14 3:22 Stephen Rothwell
2023-03-14 3:24 Stephen Rothwell
2018-03-14 6:27 Stephen Rothwell
2014-03-14 19:32 Mark Brown
2013-03-14 7:06 Stephen Rothwell
2013-03-14 7:06 ` Stephen Rothwell
2012-03-14 7: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=20160315064318.GA1385@katana \
--to=wsa@the-dreams.de \
--cc=airlied@linux.ie \
--cc=bskeggs@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sergey.senozhatsky.work@gmail.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.