From: Mark Brown <broonie@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: Tree for Aug 20
Date: Wed, 20 Aug 2014 10:52:22 -0500 [thread overview]
Message-ID: <20140820155222.GA24407@sirena.org.uk> (raw)
In-Reply-To: <20140820061703.6128f99c@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 471 bytes --]
On Wed, Aug 20, 2014 at 06:17:03AM +1000, Stephen Rothwell wrote:
> The sound-asoc tree still had its build failure for which I reverted
> a commit.
Are you sure about this? There's a bunch of updates to the tree
including one that's supposed to have fixed the build failure on PowerPC
which haven't made it into the tree, was there a problem with the fetch
perhaps? I just checked and cgit says I pushed 23 hours ago so it
doesn't look like a problem with the push.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-08-20 16:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-19 20:17 linux-next: Tree for Aug 20 Stephen Rothwell
2014-08-20 15:52 ` Mark Brown [this message]
[not found] ` <5248cecd-03f6-407b-a4a7-1d2989ee0469@email.android.com>
2014-08-21 14:34 ` Stephen Rothwell
2014-08-21 14:52 ` Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2026-08-20 14:37 Mark Brown
2025-08-20 4:34 Stephen Rothwell
2024-08-20 3:55 Stephen Rothwell
2021-08-20 9:26 Stephen Rothwell
2020-08-20 5:55 Stephen Rothwell
2019-08-20 7:09 Stephen Rothwell
2018-08-20 5:25 Stephen Rothwell
2015-08-20 10:37 Stephen Rothwell
2013-08-20 7:36 Stephen Rothwell
2013-08-20 7:36 ` Stephen Rothwell
2012-08-20 9:23 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=20140820155222.GA24407@sirena.org.uk \
--to=broonie@kernel.org \
--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.