netdev - Re: [PATCH v7] Network driver for the Armada 370 and Armada XP ARM Marvell SoCs

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 15 Nov 2012 08:33:19 +0100
From:	Thomas Petazzoni <thomas.petazzoni@...e-electrons.com>
To:	David Miller <davem@...emloft.net>
Cc:	romieu@...zoreil.com, kernel@...tstofly.org,
	netdev@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
	jason@...edaemon.net, andrew@...n.ch,
	gregory.clement@...e-electrons.com, alior@...vell.com,
	dima@...vell.com
Subject: Re: [PATCH v7] Network driver for the Armada 370 and Armada XP ARM
 Marvell SoCs

David,

On Wed, 14 Nov 2012 21:59:22 -0500 (EST), David Miller wrote:
> From: Thomas Petazzoni <thomas.petazzoni@...e-electrons.com>
> Date: Wed, 14 Nov 2012 15:56:44 +0100
> 
> > The previous versions of this patch set have been sent on September
> > 4th (v1), October 11th (v2), October 23rd (v3), October 26th (v4),
> > November 12th (v5), November 13th (v6) and now comes the v7 of the
> > driver. The number of comments over the last versions have been really
> > small, and I would really appreciate if this driver could land into
> > the 3.8 kernel release.
> 
> I can't apply this patch to net-next, because for one thing there
> are missing dependencies.  For example, the file:
> 
> arch/arm/boot/dts/armada-xp-openblocks-ax3-4.dts
> 
> doesn't exist there, therefore patch #6 won't apply.

Yes, this is expected: those patches were provided to allow people to
test the driver on the OpenBlocks platform, which is much more widely
available than the Armada XP evaluation board from Marvell.

Would you mind if we take, with your Ack, the network driver through
the arm-soc tree, so that we can carry the related patches modifying
the Device Tree and so on? If not, then I'll send you a pull request
with just the drivers/net changes, and we'll integrate the ARM-related
changes through the arm-soc tree, in which we will have the necessary
dependencies. I'm fine with any of those solutions.

Thanks,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
--
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