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]
Date:	Mon, 02 Nov 2015 22:34:57 +0100
From:	Arnd Bergmann <arnd@...db.de>
To:	Tony Cho <tony.cho@...el.com>
Cc:	glen lee <glen.lee@...el.com>, linux-wireless@...r.kernel.org,
	Rachel Kim <rachel.kim@...el.com>, devel@...verdev.osuosl.org,
	Chris Park <chris.park@...el.com>, gregkh@...uxfoundation.org,
	Stanislav Kholmanskikh <kholmanskikh.s.s@...il.com>,
	Johnny Kim <johnny.kim@...el.com>,
	linux-kernel@...r.kernel.org, Leo Kim <leo.kim@...el.com>
Subject: Re: [PATCH 00/19] staging/wilc1000 cleanups

On Friday 23 October 2015 16:51:13 Tony Cho wrote:
> Hi Arnd,
> First of all, I would like to say "thank you" for your efforts and 
> contributions.
> We are updating the driver because new revision came up and making new 
> patches
> to make it stable and elegant as Linux driver. In these days, we are 
> sending big changes
> while testing such patches and also doing updates at once.
> 
> As you did, we are scheduled to provide the patches making device tree 
> and delete all of platform
> dependencies as you removed WILC_SDIO_IRQ_GPIO as well as other things. 
> So, I would like to
> discuss with you for your series of patch.
> 
> In this time, I think it's important to make the driver to be compiled 
> even if the link problem
> happens as you reported. So, how about deleting all of SPI related files 
> from source tree and
> even from Kconfig for the time being because new bus driver will come or 
> revert
> the Kconfig and then can we expect the best patch in the near feature?
> 
> I respect your efforts and patches, so your opinion is very important to me.

Hi Tony,

I've seen you have merged the patches that you mentioned into Greg's
tree. I have now rebased my patches on top, including the separate SPI
driver. Once we merge those, it should work fine, and having multiple
front-end drivers gives a nice template for adding future hardware
specific variations like another bus, or a newer model on the same
bus. I'll post my patches after some more testing.

	Arnd
--
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