From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Lucas De Marchi <lucas.demarchi@profusion.mobi>
Subject: Re: linux-next: manual merge of the sound tree with Linus' tree
Date: Sun, 10 Apr 2011 11:29:16 -0700 [thread overview]
Message-ID: <20110410182916.GB10486@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <s5hoc4ee88p.wl%tiwai@suse.de>
On Sun, Apr 10, 2011 at 12:00:38PM +0200, Takashi Iwai wrote:
> It'd be helpful if you can resolve in your tree.
I'll do so whenever the next -rc comes out - I know Linus isn't fond of
people pulling random untagged commits.
> I've been sick and can't work much since days ago.
Oh dear, get well soon :(
next prev parent reply other threads:[~2011-04-10 18:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-08 4:38 linux-next: manual merge of the sound tree with Linus' tree Stephen Rothwell
2011-04-08 6:16 ` Mark Brown
2011-04-10 10:00 ` Takashi Iwai
2011-04-10 18:29 ` Mark Brown [this message]
2011-04-11 9:05 ` Takashi Iwai
-- strict thread matches above, loose matches on Subject: below --
2010-04-07 3:18 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=20110410182916.GB10486@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lucas.demarchi@profusion.mobi \
--cc=sfr@canb.auug.org.au \
--cc=tiwai@suse.de \
/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