From: linux@prisktech.co.nz (Tony Prisk)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv2 0/3] Add support for velocity network driver on platform devices
Date: Tue, 30 Apr 2013 07:19:02 +1200 [thread overview]
Message-ID: <517EC7A6.9030204@prisktech.co.nz> (raw)
In-Reply-To: <20130429.151528.2251094691456287740.davem@davemloft.net>
On 30/04/13 07:15, David Miller wrote:
> You prepared these patches against a net-next tree which is at least
> a week old, I know this because that's when the NETIF_F_* flags for
> VLAN offloading changed their names which causes your third patch
> to fail to apply.
>
> Do not do this, net-next changes every day and rapidly, don't take
> the chance that the driver you're touching is unpopular and thus
> hasn't had changes to it recently. Tree-wide interface changes
> happen all the time.
Apologies - I didn't realise. These patches are based against 3.8-rc8.
I will rebase against net-next and resend.
Regards
Tony P
WARNING: multiple messages have this Message-ID (diff)
From: Tony Prisk <linux@prisktech.co.nz>
To: David Miller <davem@davemloft.net>
Cc: romieu@fr.zoreil.com, netdev@vger.kernel.org,
vt8500-wm8505-linux-kernel@googlegroups.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCHv2 0/3] Add support for velocity network driver on platform devices
Date: Tue, 30 Apr 2013 07:19:02 +1200 [thread overview]
Message-ID: <517EC7A6.9030204@prisktech.co.nz> (raw)
In-Reply-To: <20130429.151528.2251094691456287740.davem@davemloft.net>
On 30/04/13 07:15, David Miller wrote:
> You prepared these patches against a net-next tree which is at least
> a week old, I know this because that's when the NETIF_F_* flags for
> VLAN offloading changed their names which causes your third patch
> to fail to apply.
>
> Do not do this, net-next changes every day and rapidly, don't take
> the chance that the driver you're touching is unpopular and thus
> hasn't had changes to it recently. Tree-wide interface changes
> happen all the time.
Apologies - I didn't realise. These patches are based against 3.8-rc8.
I will rebase against net-next and resend.
Regards
Tony P
next prev parent reply other threads:[~2013-04-29 19:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-29 7:50 [PATCHv2 0/3] Add support for velocity network driver on platform devices Tony Prisk
2013-04-29 7:50 ` Tony Prisk
2013-04-29 7:50 ` [PATCHv2 1/3] net: velocity: Rename vptr->dev to vptr->netdev Tony Prisk
2013-04-29 7:50 ` Tony Prisk
2013-04-29 7:50 ` [PATCHv2 2/3] net: velocity: Convert to generic dma functions Tony Prisk
2013-04-29 7:50 ` Tony Prisk
2013-04-29 7:50 ` [PATCHv2 3/3] net: velocity: Add platform device support to VIA velocity driver Tony Prisk
2013-04-29 7:50 ` Tony Prisk
2013-04-29 19:15 ` [PATCHv2 0/3] Add support for velocity network driver on platform devices David Miller
2013-04-29 19:15 ` David Miller
2013-04-29 19:19 ` Tony Prisk [this message]
2013-04-29 19:19 ` Tony Prisk
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=517EC7A6.9030204@prisktech.co.nz \
--to=linux@prisktech.co.nz \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.