From: Michael Tokarev <mjt@tls.msk.ru>
To: Peter Crosthwaite <peter.crosthwaite@xilinx.com>
Cc: qemu-trivial@nongnu.org, Ed Maste <emaste@freebsd.org>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Qemu-trivial] [PATCH] block/m25p80: Update Micron entries
Date: Fri, 28 Jun 2013 14:37:20 +0400 [thread overview]
Message-ID: <51CD6760.30901@msgid.tls.msk.ru> (raw)
In-Reply-To: <51B5F378.70804@msgid.tls.msk.ru>
10.06.2013 19:40, Michael Tokarev wrote:
> 07.06.2013 07:51, Peter Crosthwaite wrote:
> []
>> Id like to give it a few days to see what they say before we merge
>> this. Ideally we have agreement between the two source trees, so we
>> can continue the copy-paste based update strategy.
>
> Do we have any agreement yet? :)
Ping^2 ?
Should I apply the initial patch?
Thanks,
/mjt
next prev parent reply other threads:[~2013-06-28 10:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-04 15:59 [Qemu-devel] [PATCH] block/m25p80: Update Micron entries Ed Maste
2013-06-07 3:51 ` Peter Crosthwaite
2013-06-10 15:40 ` [Qemu-devel] [Qemu-trivial] " Michael Tokarev
2013-06-28 10:37 ` Michael Tokarev [this message]
2013-07-16 17:56 ` Michael Tokarev
2013-07-17 0:06 ` Peter Crosthwaite
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=51CD6760.30901@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=emaste@freebsd.org \
--cc=peter.crosthwaite@xilinx.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.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).