All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Walle <michael@walle.cc>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Programmingkid <programmingkidx@gmail.com>,
	"qemu-devel@nongnu.org qemu-devel" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] New documentation for the LatticeMicro32 target
Date: Tue, 09 Jan 2018 18:04:18 +0100	[thread overview]
Message-ID: <286a573eb67773dd93378579ee2499d5@walle.cc> (raw)
In-Reply-To: <CAFEAcA-pjg34=bPe7EiYN6oYC_3xuMCyiucPwZrka2Fxxrk3DQ@mail.gmail.com>

Am 2018-01-09 12:58, schrieb Peter Maydell:
> I just fell over this, it looks like this fix never made it into 
> master.
> 
> Michael, could you submit this as a full patch with a commit message
> and signed-off-by, please? cc: qemu-stable@nongnu.org as well, since
> it fixes a "breaks the board completely" bug.

oops, sorry about that :(

-michael

      parent reply	other threads:[~2018-01-09 17:04 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-09 15:39 [Qemu-devel] New documentation for the LatticeMicro32 target Programmingkid
2017-07-17  5:40 ` Michael Walle
2017-07-17 14:56   ` Programmingkid
2017-07-17 15:18     ` Programmingkid
2017-07-18 11:44       ` Michael Walle
2017-07-18 14:05         ` Programmingkid
2018-01-09 11:58         ` Peter Maydell
2018-01-09 17:01           ` [Qemu-devel] [PATCH] lm32: take BQL before writing IP/IM register Michael Walle
2018-02-01  9:09             ` Michael Walle
2018-05-09 19:45               ` Philippe Mathieu-Daudé
2018-05-10 13:35                 ` Paolo Bonzini
2018-05-10 13:00             ` Alex Bennée
2018-01-09 17:04           ` Michael Walle [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=286a573eb67773dd93378579ee2499d5@walle.cc \
    --to=michael@walle.cc \
    --cc=peter.maydell@linaro.org \
    --cc=programmingkidx@gmail.com \
    --cc=qemu-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.