From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: H Hartley Sweeten <hartleys@visionengravers.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"alan@linux.intel.com" <alan@linux.intel.com>
Subject: Re: linux-next: build failure after merge of drm-next tree
Date: Tue, 1 May 2012 21:12:07 +0100 [thread overview]
Message-ID: <20120501211207.1c565d41@pyramind.ukuu.org.uk> (raw)
In-Reply-To: <ADE657CA350FB648AAC2C43247A983F0020698951E44@AUSP01VMBX24.collaborationhost.net>
On Tue, 1 May 2012 13:16:48 -0500
H Hartley Sweeten <hartleys@visionengravers.com> wrote:
> Hello Alan,
>
> linux-next is getting a build failure:
Yep - and I was beaten to submitting the fix .. should be sorted once the
tree has percolated into -next.
Alan
prev parent reply other threads:[~2012-05-01 20:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-01 18:16 H Hartley Sweeten
2012-05-01 20:12 ` Alan Cox [this message]
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=20120501211207.1c565d41@pyramind.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=alan@linux.intel.com \
--cc=hartleys@visionengravers.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®