From mboxrd@z Thu Jan  1 00:00:00 1970
From: Mark Brown <broonie@kernel.org>
Subject: Re: [PATCH v2 0/13] topology support for alsa-lib
Date: Wed, 1 Jul 2015 18:25:34 +0100
Message-ID: <20150701172534.GV11162@sirena.org.uk>
References: <1435758316.29665.23.camel@loki> <s5hh9pnlw2s.wl-tiwai@suse.de>
 <1435767232.29665.30.camel@loki>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============2731269980425555563=="
Return-path: <alsa-devel-bounces@alsa-project.org>
Received: from mezzanine.sirena.org.uk (mezzanine.sirena.org.uk
 [106.187.55.193])
 by alsa0.perex.cz (Postfix) with ESMTP id 9962F26154E
 for <alsa-devel@alsa-project.org>; Wed,  1 Jul 2015 19:25:44 +0200 (CEST)
In-Reply-To: <1435767232.29665.30.camel@loki>
List-Unsubscribe: <http://mailman.alsa-project.org/mailman/options/alsa-devel>,
 <mailto:alsa-devel-request@alsa-project.org?subject=unsubscribe>
List-Archive: <http://mailman.alsa-project.org/pipermail/alsa-devel/>
List-Post: <mailto:alsa-devel@alsa-project.org>
List-Help: <mailto:alsa-devel-request@alsa-project.org?subject=help>
List-Subscribe: <http://mailman.alsa-project.org/mailman/listinfo/alsa-devel>,
 <mailto:alsa-devel-request@alsa-project.org?subject=subscribe>
Errors-To: alsa-devel-bounces@alsa-project.org
Sender: alsa-devel-bounces@alsa-project.org
To: Liam Girdwood <liam.r.girdwood@linux.intel.com>
Cc: Takashi Iwai <tiwai@suse.de>, "Koul, Vinod" <vinod.koul@intel.com>, "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
List-Id: alsa-devel@alsa-project.org


--===============2731269980425555563==
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="jfWagoTHmfL/c8Ax"
Content-Disposition: inline


--jfWagoTHmfL/c8Ax
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Wed, Jul 01, 2015 at 05:13:52PM +0100, Liam Girdwood wrote:
> On Wed, 2015-07-01 at 17:46 +0200, Takashi Iwai wrote:

> > You can manage such a cover letter better with --cover-letter option
> > of git-format-patch or git-send-email.

> I know, I guess I'm set in my ways ;) Will do it next time.

Youi can also just supply the message ID for threading directly in git
send-email (which is what I tend to do) but you do need to look it up
after you send the cover letter if you're going to do that.

--jfWagoTHmfL/c8Ax
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJVlCKNAAoJECTWi3JdVIfQb4gH/A5JVoCBvTwCAQsJ3T8asoau
GUQeZTiEq8pCNsKmDYsbLSkAIt5m1SUr+8giXdH2CzhSWy7N+BK0YZeAt/491jId
FLwjAq1fbqCFR6s5scOdQqJthwtU+E+f94HEcQCeYY5VZmBsezVkmCwfymv3RFs7
JSOfc5+Ex7A6a26KMVu9bPJkyOu/szIDivVSR0PyAOhmmrikdPqcP4Wc5OhRnUk7
yH8PDTXjP91ZvTsUUb3GpEO0cqI6aLHqDPVK4ccG2jzlC/IExcntNbx5aE3swTnJ
A1wd/GkoYiH0i8qvufFBBboA+B+ZCIzTEAM8a8TB7AGFva+x8onMpvdh2iH+qXk=
=G1T6
-----END PGP SIGNATURE-----

--jfWagoTHmfL/c8Ax--

--===============2731269980425555563==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline


--===============2731269980425555563==--