From: Liam Girdwood <liam.r.girdwood@linux.intel.com>
To: Vinod Koul <vinod.koul@intel.com>
Cc: Takashi Iwai <tiwai@suse.de>,
ALSA development <alsa-devel@alsa-project.org>
Subject: Re: 1.1.3 release?
Date: Fri, 16 Dec 2016 16:17:02 +0000 [thread overview]
Message-ID: <1481905022.14684.244.camel@loki> (raw)
In-Reply-To: <20161216081850.GP25795@localhost>
On Fri, 2016-12-16 at 13:48 +0530, Vinod Koul wrote:
> On Fri, Dec 16, 2016 at 09:02:59AM +0100, Jaroslav Kysela wrote:
> > Dne 16.12.2016 v 08:47 Vinod Koul napsal(a):
> > > On Wed, Dec 14, 2016 at 04:36:21PM +0100, Jaroslav Kysela wrote:
> > >> Dne 14.12.2016 v 16:00 Takashi Iwai napsal(a):
> > >>> Hi Jaroslav,
> > >>>
> > >>> shall we release v1.1.3 now?
> > >>> We've gathered quite a lot of changes since the last release.
> > >>
> > >> Hi,
> > >>
> > >> a good idea. I will release packages in next few days.
> > >
> > > Hi Jaroslav,
> > >
> > > I have updated tuncompress with couple of patches. In case you have already
> > > prepared the package would it be too much hassle to update the tinycompress
> > > ones again?
> >
> > I have not added the tags to the repos yet, so if you commit your
> > changes now, it is fine.
>
> Great, I have pushed.
>
> One more question, will the 1.1.3 release also contain open-firmware?
>
Do you mean sound-open-firmware ? If so, SOF is on a separate schedule,
and I'll be tagging a new release before the holidays.
Thanks
Liam
prev parent reply other threads:[~2016-12-16 16:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-14 15:00 1.1.3 release? Takashi Iwai
2016-12-14 15:36 ` Jaroslav Kysela
2016-12-16 7:47 ` Vinod Koul
2016-12-16 8:02 ` Jaroslav Kysela
2016-12-16 8:18 ` Vinod Koul
2016-12-16 16:17 ` Liam Girdwood [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=1481905022.14684.244.camel@loki \
--to=liam.r.girdwood@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=tiwai@suse.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox