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 1/3] virtio: console: Add emergency writeonly register to config space
Date: Thu, 16 May 2013 18:07:46 +0530	[thread overview]
Message-ID: <20130516123746.GA4744@amit.redhat.com> (raw)
In-Reply-To: <1367842791-30285-2-git-send-email-pranavkumar@linaro.org>

On (Mon) 06 May 2013 [17:49:49], Pranavkumar Sawargaonkar wrote:
> This patch adds an emerg_wr register (writeonly) in config space
> of virtio console device which can be used for debugging.
> 
> Signed-off-by: Pranavkumar Sawargaonkar <pranavkumar@linaro.org>
> Signed-off-by: Anup Patel <anup.patel@linaro.org>
> Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>

OK, this change by itself looks harmless.

Acked-by: Amit Shah <amit.shah@redhat.com>

		Amit

  reply	other threads:[~2013-05-16 12:37 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 [this message]
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
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=20130516123746.GA4744@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).