All of lore.kernel.org
 help / color / mirror / Atom feed
From: Laszlo Ersek <lersek-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Rob Herring <robherring2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: "devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	Rob Herring <rob.herring-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
	Peter Maydell
	<peter.maydell-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
	Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>,
	Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>,
	drjones-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
	Paolo Bonzini <pbonzini-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
	Alexander Graf <agraf-l3A5Bk7waGM@public.gmane.org>
Subject: Re: [PATCH v4 0/2] devicetree: document ARM bindings for QEMU's Firmware Config interface
Date: Wed, 07 Jan 2015 17:33:03 +0100	[thread overview]
Message-ID: <54AD5FBF.3080108@redhat.com> (raw)
In-Reply-To: <CAL_JsqL+ued8mZj_MONKf0j2MO0zmE+H=mahQC30aV8vki0mvQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

On 01/07/15 16:43, Rob Herring wrote:
> On Wed, Dec 17, 2014 at 2:49 PM, Laszlo Ersek <lersek-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> wrote:
>> The qemu patchset has been turned upside down on qemu-devel during
>> review (many thanks for that!); one outcome is that now both the
>> selector and the data registers are big endian. This series has been
>> updated accordingly.
> 
> I'm assuming this is now settled on the QEMU side and will apply.

Actually I have a small update for this text file. I thought people
forgot about it and I didn't want to make more noise. If you're still
willing to apply it, then I can post an incremental patch or a new version.

Thanks!
Laszlo

--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2015-01-07 16:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-17 20:49 [PATCH v4 0/2] devicetree: document ARM bindings for QEMU's Firmware Config interface Laszlo Ersek
     [not found] ` <1418849386-25857-1-git-send-email-lersek-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2014-12-17 20:49   ` [PATCH v4 1/2] devicetree: document the "qemu" and "virtio" vendor prefixes Laszlo Ersek
2014-12-17 20:49   ` [PATCH v4 2/2] devicetree: document ARM bindings for QEMU's Firmware Config interface Laszlo Ersek
2014-12-17 21:48   ` [PATCH v4 0/2] " Arnd Bergmann
2015-01-07 15:43   ` Rob Herring
     [not found]     ` <CAL_JsqL+ued8mZj_MONKf0j2MO0zmE+H=mahQC30aV8vki0mvQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-01-07 16:33       ` Laszlo Ersek [this message]
     [not found]         ` <54AD5FBF.3080108-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-01-07 17:12           ` Rob Herring

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=54AD5FBF.3080108@redhat.com \
    --to=lersek-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=agraf-l3A5Bk7waGM@public.gmane.org \
    --cc=arnd-r2nGTMty4D4@public.gmane.org \
    --cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=drjones-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=mark.rutland-5wv7dgnIgG8@public.gmane.org \
    --cc=pbonzini-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=peter.maydell-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
    --cc=rob.herring-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
    --cc=robherring2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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.