netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Alex Williamson <alex.williamson@hp.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org
Subject: Re: [PATCH] virtio_net: Fix function name typo
Date: Tue, 5 May 2009 12:52:53 +0930	[thread overview]
Message-ID: <200905051252.53993.rusty@rustcorp.com.au> (raw)
In-Reply-To: <20090427155507.7895.79747.stgit@debian.lart>

On Tue, 28 Apr 2009 01:25:38 am Alex Williamson wrote:
> Signed-off-by: Alex Williamson <alex.williamson@hp.com>

Acked-by: Rusty Russell <rusty@rustcorp.com.au>

I only noticed this in the linux-next error messages, too.  Says bad
things about my review, huh?

Cheers,
Rusty.

      parent reply	other threads:[~2009-05-05  4:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-27 15:55 [PATCH] virtio_net: Fix function name typo Alex Williamson
2009-04-28  9:31 ` David Miller
2009-05-01 22:33 ` David Miller
2009-05-02  3:31   ` Alex Williamson
2009-05-02  4:26     ` David Miller
2009-05-05  3:22 ` Rusty Russell [this message]

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=200905051252.53993.rusty@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=alex.williamson@hp.com \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.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).