From: cov@codeaurora.org (Christopher Covington)
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: Mon, 13 May 2013 13:36:59 -0400 [thread overview]
Message-ID: <519124BB.9030709@codeaurora.org> (raw)
In-Reply-To: <CAAHg+Hi6BHqwOznnC9qxkc5pBWz7r5qpz9Nhh=EeNenhjhHohg@mail.gmail.com>
Hi Pranavkumar,
On 05/13/2013 02:56 AM, Pranavkumar Sawargaonkar wrote:
> 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)
You seem to have omitted copying virtualization at lists.linux-foundation.org,
the mailing list documented in the MAINTAINERS file as appropriate for changes
relating to the virtio console driver.
[...]
Christopher
--
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by the Linux Foundation.
WARNING: multiple messages have this Message-ID (diff)
From: Christopher Covington <cov@codeaurora.org>
To: Pranavkumar Sawargaonkar <pranavkumar@linaro.org>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
"linaro-kernel@lists.linaro.org" <linaro-kernel@lists.linaro.org>,
Anup Patel <anup.patel@linaro.org>,
Patch Tracking <patches@linaro.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Amit Shah <amit.shah@redhat.com>,
"kvmarm@lists.cs.columbia.edu" <kvmarm@lists.cs.columbia.edu>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH V2 2/3] Documentation: virtio: Add emergency write (emerg_wr) config register in virtio console.
Date: Mon, 13 May 2013 13:36:59 -0400 [thread overview]
Message-ID: <519124BB.9030709@codeaurora.org> (raw)
In-Reply-To: <CAAHg+Hi6BHqwOznnC9qxkc5pBWz7r5qpz9Nhh=EeNenhjhHohg@mail.gmail.com>
Hi Pranavkumar,
On 05/13/2013 02:56 AM, Pranavkumar Sawargaonkar wrote:
> 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)
You seem to have omitted copying virtualization@lists.linux-foundation.org,
the mailing list documented in the MAINTAINERS file as appropriate for changes
relating to the virtio console driver.
[...]
Christopher
--
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by the Linux Foundation.
next prev parent reply other threads:[~2013-05-13 17:36 UTC|newest]
Thread overview: 28+ 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 ` Pranavkumar Sawargaonkar
2013-05-06 12:19 ` [PATCH V2 1/3] virtio: console: Add emergency writeonly register to config space Pranavkumar Sawargaonkar
2013-05-06 12:19 ` Pranavkumar Sawargaonkar
2013-05-16 12:37 ` Amit Shah
2013-05-16 12:37 ` Amit Shah
2013-05-16 23:52 ` Rusty Russell
2013-05-16 23:52 ` Rusty Russell
2013-05-17 6:00 ` Pranavkumar Sawargaonkar
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-06 12:19 ` Pranavkumar Sawargaonkar
2013-05-07 5:02 ` Rob Landley
2013-05-07 5:02 ` Rob Landley
2013-05-13 1:16 ` Rusty Russell
2013-05-13 1:16 ` Rusty Russell
2013-05-13 2:52 ` Rusty Russell
2013-05-13 2:52 ` Rusty Russell
2013-05-13 6:56 ` Pranavkumar Sawargaonkar
2013-05-13 6:56 ` Pranavkumar Sawargaonkar
2013-05-13 17:36 ` Christopher Covington [this message]
2013-05-13 17:36 ` Christopher Covington
2013-05-15 4:29 ` Rusty Russell
2013-05-15 4:29 ` Rusty Russell
2013-05-15 5:30 ` Amit Shah
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
2013-05-06 12:19 ` 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=519124BB.9030709@codeaurora.org \
--to=cov@codeaurora.org \
--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 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.