All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Sasha Levin <levinsasha928@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>,
	virtualization <virtualization@lists.linux-foundation.org>
Subject: Re: [PULL] lguest fix, virtio documentation
Date: Mon, 22 Aug 2011 09:42:47 +0930	[thread overview]
Message-ID: <87k4a65mo0.fsf@rustcorp.com.au> (raw)
In-Reply-To: <1313419712.3004.1.camel@sasha>

On Mon, 15 Aug 2011 17:48:32 +0300, Sasha Levin <levinsasha928@gmail.com> wrote:
> On Mon, 2011-08-15 at 10:25 +0930, Rusty Russell wrote:
> > [ This adds a text copy of the virtio draft spec to the kernel source,
> >   which should make it easier for people to find and read.  The master
> >   is still the lyx document on my server, so I'll keep it in sync. ]
> > 
> > The following changes since commit 91d85ea6786107aa2837bef3e957165ad7c8b823:
> > 
> >   Merge branch 'hwmon-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/groeck/staging (2011-08-13 18:37:28 -0700)
> > 
> > are available in the git repository at:
> > 
> >   ssh://master.kernel.org/pub/scm/linux/kernel/git/rusty/linux-2.6-for-linus.git master
> > 
> > Rusty Russell (2):
> >       virtio: Add text copy of spec to Documentation/virtual.
> 
> The "Device Status" paragraph says FAILED is 8, while it should be 0x80.

They're 1-based bit numbers.  But since everyone makes this mistake,
I've changed them *all* to values rather than bit numbers.

Thanks!
Rusty.

  parent reply	other threads:[~2011-08-22  2:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-15  0:55 [PULL] lguest fix, virtio documentation Rusty Russell
2011-08-15 14:48 ` Sasha Levin
2011-08-15 14:48 ` Sasha Levin
2011-08-22  0:12   ` Rusty Russell
2011-08-22  0:12   ` Rusty Russell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-08-15  0:55 Rusty Russell

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=87k4a65mo0.fsf@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=levinsasha928@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=virtualization@lists.linux-foundation.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.