From: Grant Likely <grant.likely@secretlab.ca>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Thomas Abraham <thomas.abraham@linaro.org>
Subject: Re: linux-next: build failure after merge of the final tree (devicetree tree related)
Date: Thu, 19 Apr 2012 16:12:33 -0600 [thread overview]
Message-ID: <20120419221233.E1BCF3E0700@localhost> (raw)
In-Reply-To: <20120418104819.289b5bd6ec0c8575fbeeb5be@canb.auug.org.au>
On Wed, 18 Apr 2012 10:48:19 +1000, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi Grant,
>
> On Tue, 17 Apr 2012 16:39:16 -0600 Grant Likely <grant.likely@secretlab.ca> wrote:
> >
> > Should be fixed now.
>
> Did you forget to push it out?
Apparantly so. Pushed out now.
g.
next prev parent reply other threads:[~2012-04-19 22:12 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-11 5:11 linux-next: build failure after merge of the final tree (devicetree tree related) Stephen Rothwell
2012-04-11 13:35 ` David Miller
2012-04-12 0:31 ` Stephen Rothwell
2012-04-12 0:35 ` Grant Likely
2012-04-12 0:44 ` Stephen Rothwell
2012-04-17 3:23 ` Stephen Rothwell
2012-04-17 3:39 ` Grant Likely
2012-04-17 22:39 ` Grant Likely
2012-04-18 0:48 ` Stephen Rothwell
2012-04-19 22:12 ` Grant Likely [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-08-04 4:28 Stephen Rothwell
2011-08-04 6:36 ` Stephen Rothwell
2011-08-04 6:59 ` Grant Likely
2011-08-04 7:13 ` David Miller
2011-08-04 8:17 ` David Miller
2011-08-04 9:41 ` Grant Likely
2011-03-01 6:54 Stephen Rothwell
2011-03-01 16:41 ` Grant Likely
2010-05-18 7:47 Stephen Rothwell
2010-05-18 11:52 ` Grant Likely
2010-05-18 11:52 ` Grant Likely
2010-05-18 22:16 ` Grant Likely
2010-05-18 22:16 ` Grant Likely
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=20120419221233.E1BCF3E0700@localhost \
--to=grant.likely@secretlab.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=thomas.abraham@linaro.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 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.