From: Juan Quintela <quintela@redhat.com>
To: Amit Shah <amit.shah@redhat.com>
Cc: Virtualization List <virtualization@lists.linux-foundation.org>
Subject: Re: [PULL] virtio console fixes, abi change
Date: Wed, 14 Apr 2010 09:25:36 +0200 [thread overview]
Message-ID: <m3633ulclr.fsf@trasno.mitica> (raw)
In-Reply-To: <20100414053557.GA4442@amit-x200.redhat.com> (Amit Shah's message of "Wed, 14 Apr 2010 11:05:57 +0530")
Amit Shah <amit.shah@redhat.com> wrote:
> Hello Rusty,
>
> To avoid sending the same patches again, this time I'm trying a git pull
> request.
>
> Please pull from
>
> git://git.kernel.org/pub/scm/linux/kernel/git/amit/vs-kernel.git for-rusty
>
> to get the patches that I've sent to the list previously, with a couple
> of fixes:
>
> - Create a console port when not using multiport (fix was sent as a
> reply to prev. series)
>
> - Add hunk that got inadvertently reverted during git rebase operations
> (thanks Juan).
>
> The diff to the v6 version is attached below:
Acked-by: Juan Quintela <quintela@redhat.com>
prev parent reply other threads:[~2010-04-14 7:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-14 5:35 [PULL] virtio console fixes, abi change Amit Shah
2010-04-14 7:25 ` Juan Quintela [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=m3633ulclr.fsf@trasno.mitica \
--to=quintela@redhat.com \
--cc=amit.shah@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox