From: Rusty Russell <rusty@rustcorp.com.au>
To: David Miller <davem@davemloft.net>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org, mst@redhat.com
Subject: Re: [PATCH 1/3] virtio_net: pass well-formed sgs to virtqueue_add_*()
Date: Tue, 16 Sep 2014 10:18:15 +0930 [thread overview]
Message-ID: <87wq94fl0w.fsf@rustcorp.com.au> (raw)
In-Reply-To: <20140913.125341.1440485569100220563.davem@davemloft.net>
David Miller <davem@davemloft.net> writes:
> From: Rusty Russell <rusty@rustcorp.com.au>
> Date: Sat, 13 Sep 2014 15:10:03 +0930
>
>> David Miller <davem@davemloft.net> writes:
>>> Do you guys want me to take this series directly into net-next?
>>
>> Actually, yes. Since I'm going to be travelling, that makes it much
>> easier for me. And no other patches I have depend on it.
>
> Series applied, but can you be more careful when you hand edit patches
> or whatever you are doing that puts space characters at the beginning
> of lines before TAB characters?
>
> GIT flags this immediately, so even if you are hella lazy just feeding
> your patches into "git am" will show this.
Hmm, that was weird, thanks for the warning. This patch is pretty old,
so maybe I did hand-hack it at one stage.
Cheers,
Rusty.
next prev parent reply other threads:[~2014-09-16 2:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-11 0:47 [PATCH 0/3] virtio_net/virtio_ring Rusty Russell
2014-09-11 0:47 ` [PATCH 1/3] virtio_net: pass well-formed sgs to virtqueue_add_*() Rusty Russell
2014-09-12 21:54 ` David Miller
2014-09-13 5:40 ` Rusty Russell
2014-09-13 16:53 ` David Miller
2014-09-16 0:48 ` Rusty Russell [this message]
2014-09-11 0:47 ` [PATCH 2/3] virtio_ring: assume sgs are always well-formed Rusty Russell
2014-09-11 0:47 ` [PATCH 3/3] virtio_ring: unify direct/indirect code paths 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=87wq94fl0w.fsf@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--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