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] [day] [month] [year] [list]
Message-ID: <09383930-0cc9-490e-be4e-e45cc9a31041@BN1BFFO11FD016.protection.gbl>
Date:	Mon, 25 Aug 2014 07:42:07 -0700
From:	Sören Brinkmann <soren.brinkmann@...inx.com>
To:	Olof Johansson <olof@...om.net>
CC:	Michal Simek <michal.simek@...inx.com>,
	<linux-arm-kernel@...ts.infradead.org>,
	<linux-kernel@...r.kernel.org>, Arnd Bergmann <arnd@...db.de>,
	Kevin Hilman <khilman@...aro.org>
Subject: Re: [PATCH 00/11] ARM: multi_v7_defconfig: Enable Zynq/Xilinx drivers

On Fri, 2014-08-22 at 09:17PM -0700, Olof Johansson wrote:
> On Fri, Aug 22, 2014 at 08:54:25AM -0700, Soren Brinkmann wrote:
> > Hi,
> > 
> > I went through the defconfig and searched for Zynq drivers. The result is
> > this series of patches. The first few are all for Zynq and pretty much
> > straight forward. The second half is mostly soft-IP, I think. That
> > soft-IP works with Zynq devices, but I'm not sure whether those should
> > go into the multi_v7 defconfig.
> 
> Thanks, SĂren! 
> 
> There's no need to split up into individual patches like this, but it was
> convenient in case I wanted to only apply a few of them. I took them all
> as one patch, and used your series description as commit message since
> none of the individual patches had any. :)

Yeah, that was my thinking. It's easier to squash things than splitting.
Thanks for taking it.

> 
> As far as "unusual" drivers in the multiconfig; yeah, we need to deal
> with that at some point due to kernel size. We're likely to switch ti
> using modules first, but it'll make things slightly more complicated
> since people will need to start dealing with initrds and at least I
> don't have a good setup for that in my test farm yet. :-)

I agree. Monolithic kernels make those things a lot easier.

	Thanks,
	Sören
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ