All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Nawrocki <michael.nawrocki@gtri.gatech.edu>
To: Paolo Bonzini <pbonzini@redhat.com>,
	qemu-devel@nongnu.org, qemu-block@nongnu.org
Cc: kwolf@redhat.com, peter.maydell@linaro.org, mreitz@redhat.com
Subject: Re: [Qemu-devel] [Qemu-block] [PATCH v2 0/1] Add 8-byte wide AMD flash support, partial interleaving
Date: Mon, 13 Nov 2017 09:27:05 -0500	[thread overview]
Message-ID: <f8b1a08d-5781-70c4-3c16-76927cdbb854@gtri.gatech.edu> (raw)
In-Reply-To: <888aa8cc-25d3-bcc5-9a97-78d59b972c05@redhat.com>

On 11/10/2017 06:12 PM, Paolo Bonzini wrote:
> On 10/11/2017 21:25, Mike Nawrocki wrote:
>> This patch set does a few things. First, it switches the AMD CFI flash MMIO
>> operations from the old MMIO API to the new one. Second, it enables 8-byte wide
>> flash arrays. Finally, it adds flash interleaving using the "device-width" and
>> "max-device-width" properties, using the same interface as pflash_cfi01.c. Much
>> of the code was taken and adapted from that file.
> 
> This unfortunately is not a patch set, it's a patch that does many
> things.  You should split it in three parts, according to the three
> things you've mentioned in the message above.
> 
> Paolo
> 

Sure, no problem. I'll get the split patch set out shortly.

Thanks,
Mike

      reply	other threads:[~2017-11-13 14:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-10 20:25 [Qemu-devel] [PATCH v2 0/1] Add 8-byte wide AMD flash support, partial interleaving Mike Nawrocki
2017-11-10 20:25 ` [Qemu-devel] [PATCH v2 1/1] Add 8-byte access, interleaving to AMD CFI devices Mike Nawrocki
2017-11-10 23:12 ` [Qemu-devel] [Qemu-block] [PATCH v2 0/1] Add 8-byte wide AMD flash support, partial interleaving Paolo Bonzini
2017-11-13 14:27   ` Michael Nawrocki [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=f8b1a08d-5781-70c4-3c16-76927cdbb854@gtri.gatech.edu \
    --to=michael.nawrocki@gtri.gatech.edu \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-block@nongnu.org \
    --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.