From: Sedat Dilek <sedat.dilek@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: Re: linux-next: Tree for Feb 15
Date: Fri, 15 Feb 2013 11:58:28 +0100 [thread overview]
Message-ID: <CA+icZUWUnnE6=DRuAodY=DS1tK7VZLnFd503rfHgng6CQUMjcw@mail.gmail.com> (raw)
In-Reply-To: <20130215184255.5ba8a085004f4aadb9faf82c@canb.auug.org.au>
On Fri, Feb 15, 2013 at 8:42 AM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi all,
>
> News: Yesterday was the 5th anniversary of linux-next! I can't believe I
> am still doing this :-)
>
So 5-times a happy Quentin Valentino day!
> Changes since 20130214:
>
> New tree: drm-intel
>
More black roses for integrating drm-intel (/me is pulling
drm-intel-nightly after -1 (first "naked") linux-next kernel-build).
- Sedat -
> Dropped tree: drm-intel (build failure)
>
> The pm tree gained a conflict against the pci tree.
>
> The drm-intel tree gained a build failure so I dropped it for today.
>
> The xen-two tree gained a build failure for which I applied a merge fix
> patch.
>
> The driver-core tree gained a conflict against the wireless-next tree.
>
> The akpm tree gained conflicts against the workqueues and net-next trees.
>
> ----------------------------------------------------------------------------
>
next prev parent reply other threads:[~2013-02-15 10:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-15 7:42 linux-next: Tree for Feb 15 Stephen Rothwell
2013-02-15 7:42 ` Stephen Rothwell
2013-02-15 9:24 ` Arend van Spriel
2013-02-15 10:58 ` Sedat Dilek [this message]
2013-02-15 18:51 ` [PATCH -next] i2c: fix i2c-ismt.c printk format warning Randy Dunlap
2013-02-15 19:48 ` Wolfram Sang
-- strict thread matches above, loose matches on Subject: below --
2024-02-15 3:52 linux-next: Tree for Feb 15 Stephen Rothwell
2023-02-15 3:50 Stephen Rothwell
2022-02-15 9:13 Stephen Rothwell
2021-02-15 9:34 Stephen Rothwell
2019-02-15 6:03 Stephen Rothwell
2018-02-15 3:35 Stephen Rothwell
2017-02-15 5:49 Stephen Rothwell
2016-02-15 5:40 Stephen Rothwell
2012-02-15 5:03 Stephen Rothwell
2008-02-15 7:31 Stephen Rothwell
2008-02-15 10:01 ` Andy Whitcroft
2008-02-15 11:09 ` 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='CA+icZUWUnnE6=DRuAodY=DS1tK7VZLnFd503rfHgng6CQUMjcw@mail.gmail.com' \
--to=sedat.dilek@gmail.com \
--cc=daniel.vetter@ffwll.ch \
--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 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.