From: Richard Fitzgerald <rf@opensource.wolfsonmicro.com>
To: Vinod Koul <vinod.koul@intel.com>
Cc: alsa-devel@alsa-project.org, patches@opensource.wolfsonmicro.com
Subject: Re: [TINYCOMPRESS][PATCH] crec: support streaming output to stdout
Date: Wed, 4 Mar 2015 16:27:13 +0000 [thread overview]
Message-ID: <20150304162713.GA6218@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20150304125708.GS2613@intel.com>
On Wed, Mar 04, 2015 at 06:27:08PM +0530, Vinod Koul wrote:
> On Wed, Feb 25, 2015 at 03:30:53PM +0000, Richard Fitzgerald wrote:
> > On Tue, Feb 24, 2015 at 10:06:26PM +0530, Vinod Koul wrote:
> > > On Thu, Feb 19, 2015 at 02:55:40PM +0000, Richard Fitzgerald wrote:
> > > > From: Ammar Zahid Ali Syed <aali@opensource.wolfsonmicro.com>
> > > >
> > > > It's useful for testing to be able to stream the captured
> > > > audio to stdout instead of having to go via a file.
> > > This looks okay to me. But it fails to apply, what was it generataed against?
> > >
> >
> > It was generated against the master tinycompress branch.
> > I have just tried to apply it on top of the current head patch
> > "makefile.linux: allow env to override CROSS_COMPILE and CC" and it
> > applies ok for me.
> That is possible as your tree already knew this patch and how to resolve
> this. Anyway I went ahead and have manually applied this one, can you check
> if this is fine
I diffed upstream master against my tree and they are identical.
prev parent reply other threads:[~2015-03-04 16:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-19 14:55 [TINYCOMPRESS][PATCH] crec: support streaming output to stdout Richard Fitzgerald
2015-02-24 16:36 ` Vinod Koul
2015-02-25 15:30 ` Richard Fitzgerald
2015-03-04 12:57 ` Vinod Koul
2015-03-04 16:27 ` Richard Fitzgerald [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=20150304162713.GA6218@opensource.wolfsonmicro.com \
--to=rf@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=patches@opensource.wolfsonmicro.com \
--cc=vinod.koul@intel.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 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.