From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <47ED372B.8040501@domain.hid> Date: Fri, 28 Mar 2008 19:21:31 +0100 From: Jan Kiszka MIME-Version: 1.0 References: <47CA8934.3060405@domain.hid> <18378.50046.906228.646119@domain.hid> <47CACD33.5000107@domain.hid> <2ff1a98a0803030206j52d5c1eeja568e346fe058213@domain.hid> In-Reply-To: <2ff1a98a0803030206j52d5c1eeja568e346fe058213@domain.hid> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigA3C6670E7BED438E179A949F" Sender: jan.kiszka@domain.hid Subject: Re: [Xenomai-core] [PATCH 0/6] Fix, refactor, and optimize xnlock services, v2 List-Id: "Xenomai life and development \(bug reports, patches, discussions\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Philippe Gerum Cc: Xenomai-core@domain.hid This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigA3C6670E7BED438E179A949F Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Philippe, I noticed that you merged patch 1-4. What are the plans for (or concerns = about) the ticket xnlock and the UP debugging changes? Jan --------------enigA3C6670E7BED438E179A949F Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFH7TcrniDOoMHTA+kRAlg5AJ4mG0ffWefzgHqhudieR0ZebyLK0QCeNN8+ lC38xLxJFG3h/IvrlXy3v2Y= =Iw+7 -----END PGP SIGNATURE----- --------------enigA3C6670E7BED438E179A949F--