From: Jan Kiszka <jan.kiszka@siemens.com>
To: Tim Sander <tim@krieglstein.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu AT24Cxx
Date: Thu, 10 Dec 2015 13:57:47 +0100 [thread overview]
Message-ID: <566976CB.9070307@siemens.com> (raw)
In-Reply-To: <29597206.QFPkAPGnES@dabox>
On 2015-12-10 13:51, Tim Sander wrote:
> Hi Jan
>
> I have seen your patches for AT24Cxx functionality in qemu:
> https://lists.gnu.org/archive/html/qemu-devel/2013-04/msg05714.html
>
> As i am interested in this work i am wondering what happend to this effort?
Internally in heavy use (not sure right now if it is being rebased
frequently, though), but we lost the energy to finally push it upstream.
What was missing was probably "only" some proper qtest unit tests. If
you want to pick up on this, that would be very welcome.
I may have some hours to look into it again as well, though possibly not
this year any more (yeah...).
Thanks,
Jan
--
Siemens AG, Corporate Technology, CT RTC ITP SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2015-12-10 12:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-10 12:51 [Qemu-devel] qemu AT24Cxx Tim Sander
2015-12-10 12:57 ` Jan Kiszka [this message]
2015-12-10 13:05 ` Tim Sander
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=566976CB.9070307@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=qemu-devel@nongnu.org \
--cc=tim@krieglstein.org \
/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;
as well as URLs for NNTP newsgroup(s).