linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: amit.shah@redhat.com (Amit Shah)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2 2/3] Documentation: virtio: Add emergency write (emerg_wr) config register in virtio console.
Date: Wed, 15 May 2013 11:00:32 +0530	[thread overview]
Message-ID: <20130515053032.GA32133@amit.redhat.com> (raw)
In-Reply-To: <87hai427di.fsf@rustcorp.com.au>

On (Wed) 15 May 2013 [13:59:29], Rusty Russell wrote:
> Pranavkumar Sawargaonkar <pranavkumar@linaro.org> writes:
> > Hi Rusty,
> >
> > On 13 May 2013 08:22, Rusty Russell <rusty@rustcorp.com.au> wrote:
> >> Pranavkumar Sawargaonkar <pranavkumar@linaro.org> writes:
> >>> Signed-off-by: Pranavkumar Sawargaonkar <pranavkumar@linaro.org>
> >>> Signed-off-by: Anup Patel <anup.patel@linaro.org>
> >>> ---
> >>>  Documentation/virtual/virtio-spec.txt |    8 +++++++-
> >>>  1 file changed, 7 insertions(+), 1 deletion(-)
> >>
> >> OK, I applied this to the lyx master, with three changes:
> >> 1) Changed "filed" to "field".
> >> 2) Added ", or even acknowledging the feature" after "without
> >>    initializing virtio queues".
> >> 3) Added an initial point to the Device Initialization section:
> >>
> >>    1. If the VIRTIO_CONSOLE_F_EMERG_WRITE feature is offered, the
> >>    emerg_wr field of the configuration can be written at any time. Thus
> >>    it should work for very early boot debugging output as well as
> >>    catastophic OS failures (eg. virtio ring corruption).
> >
> > Thanks for applying this patch.
> > Have you also applied first patch ([PATCH V2 1/3] virtio: console: Add
> > emergency writeonly register to config space)
> > with this?  (https://lkml.org/lkml/2013/5/6/169)
> 
> Would like Amit's Ack, since he's de-facto console maintainer.

I've been away, and am reviewing the discussions here.  Expect a
response later today.

Thanks,

		Amit

  reply	other threads:[~2013-05-15  5:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-06 12:19 [PATCH V2 0/3] Emergency write support for virtio console devices Pranavkumar Sawargaonkar
2013-05-06 12:19 ` [PATCH V2 1/3] virtio: console: Add emergency writeonly register to config space Pranavkumar Sawargaonkar
2013-05-16 12:37   ` Amit Shah
2013-05-16 23:52     ` Rusty Russell
2013-05-17  6:00       ` Pranavkumar Sawargaonkar
2013-05-06 12:19 ` [PATCH V2 2/3] Documentation: virtio: Add emergency write (emerg_wr) config register in virtio console Pranavkumar Sawargaonkar
2013-05-07  5:02   ` Rob Landley
2013-05-13  1:16     ` Rusty Russell
2013-05-13  2:52   ` Rusty Russell
2013-05-13  6:56     ` Pranavkumar Sawargaonkar
2013-05-13 17:36       ` Christopher Covington
2013-05-15  4:29       ` Rusty Russell
2013-05-15  5:30         ` Amit Shah [this message]
2013-05-06 12:19 ` [PATCH V2 3/3] arm64: earlyprintk support for virtio-mmio console Pranavkumar Sawargaonkar

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=20130515053032.GA32133@amit.redhat.com \
    --to=amit.shah@redhat.com \
    --cc=linux-arm-kernel@lists.infradead.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).