[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20130628.220914.1391002839959044176.davem@davemloft.net>
Date: Fri, 28 Jun 2013 22:09:14 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: stephen@...workplumber.org
Cc: netdev@...r.kernel.org
Subject: Re: pull-request vxlan-next
From: Stephen Hemminger <stephen@...workplumber.org>
Date: Fri, 28 Jun 2013 22:07:35 -0700
> On Tue, 25 Jun 2013 18:06:41 -0700
> Stephen Hemminger <stephen@...workplumber.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.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists