From: Randy Dunlap <rdunlap@infradead.org>
To: Nick Krause <xerofoify@gmail.com>,
Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>
Subject: Re: Fwd: linux-next: Tree for Jul 9
Date: Wed, 09 Jul 2014 10:11:40 -0700 [thread overview]
Message-ID: <53BD77CC.9060606@infradead.org> (raw)
In-Reply-To: <CAPDOMVjAMHOhuzfcJRL_JQ1jSKOeE7PEhppZJKJKbtR2-ixi-A@mail.gmail.com>
On 07/09/2014 10:07 AM, Nick Krause wrote:
> ---------- Forwarded message ----------
> From: Stephen Rothwell wrote on Wed, Jul 9, 2014 at 4:31 AM
> Subject: linux-next: Tree for Jul 9
> To: linux-next@vger.kernel.org
> Cc: linux-kernel@vger.kernel.org
>
>
> Hi all,
>
> Changes since 20140708:
>
>
> --
> Cheers,
> Stephen Rothwell sfr@canb.auug.org.au
>
> Hey Stephen,
>
> A lot of your builds that are failing seem to build for me. Please try
> a compiler toolchain
> newer then gcc 4.6.3 to see if this is why your builds are failing.
> Since all the arm builds
> you have failing build for me.
> Cheers Nick
>
Hey Nick,
Does your email client interface have a "Reply All" or "Reply to All" button
or selection that you can use? Please use that instead of Forwarding each message.
That will make it easier to read the email threading.
Thanks.
--
~Randy
next prev parent reply other threads:[~2014-07-09 17:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-09 8:31 linux-next: Tree for Jul 9 Stephen Rothwell
2014-07-09 17:07 ` Fwd: " Nick Krause
2014-07-09 17:11 ` Randy Dunlap [this message]
2014-07-09 17:13 ` Nick Krause
2014-07-09 18:47 ` Guenter Roeck
2014-07-09 18:53 ` Randy Dunlap
2014-07-09 18:56 ` Nick Krause
2014-07-09 19:22 ` Randy Dunlap
2014-07-09 20:54 ` Nick Krause
2014-07-10 9:43 ` Bernd Petrovitsch
2014-07-10 17:08 ` Nick Krause
[not found] ` <53BDBC22.7050009@infradead.org>
2014-07-10 17:10 ` Nick Krause
2014-07-11 5:19 ` Nick Krause
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=53BD77CC.9060606@infradead.org \
--to=rdunlap@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=xerofoify@gmail.com \
/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