From: David Miller <davem@davemloft.net>
To: stephen@networkplumber.org
Cc: netdev@vger.kernel.org
Subject: Re: pull-request vxlan-next
Date: Fri, 28 Jun 2013 22:09:14 -0700 (PDT) [thread overview]
Message-ID: <20130628.220914.1391002839959044176.davem@davemloft.net> (raw)
In-Reply-To: <20130628220735.53e6df97@nehalam.linuxnetplumber.net>
From: Stephen Hemminger <stephen@networkplumber.org>
Date: Fri, 28 Jun 2013 22:07:35 -0700
> On Tue, 25 Jun 2013 18:06:41 -0700
> Stephen Hemminger <stephen@networkplumber.org> wrote:
>
>> Here is current updates for vxlan in net-next. It includes Mike's changes
>> to handle multiple destinations and lots of little cosmetic stuff.
>>
>> This is a fresh vxlan-next repository which was forked from net-next.
>>
>> ---
>> The following changes since commit 8599b52e14a1611dcb563289421bee76751f1d53:
>>
>> bonding: add an option to fail when any of arp_ip_target is inaccessible (2013-06-25 16:58:38 -0700)
>>
>> are available in the git repository at:
>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/shemminger/vxlan-next.git master
>>
>> for you to fetch changes up to ba609e9bf15bd7df35e2c06a2e5aaf9ab9289b10:
>>
>> vxlan: fix function name spelling (2013-06-25 17:06:01 -0700)
>>
>
>
> No response?
> I know pull-requests don't show up patchwork dashboard. Need patches instead?
They do show up for some people, I wonder what magic the patchwork robot
is looking for in the pull request, hmmm...
Anyways, I'm aware of this request now and will process it soon.
But, generally speaking, in the future you should post the patches as
a series and make your "[PATCH 0/N] " posting contain the pull request.
prev parent reply other threads:[~2013-06-29 5:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20130625180641.4fa33ceb@nehalam.linuxnetplumber.net>
2013-06-29 5:07 ` pull-request vxlan-next Stephen Hemminger
2013-06-29 5:09 ` David Miller [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=20130628.220914.1391002839959044176.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.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).