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: <fa686aa40912171900k386c748awb8d6ccb37d95285f@mail.gmail.com>
Date:	Thu, 17 Dec 2009 20:00:14 -0700
From:	Grant Likely <grant.likely@...retlab.ca>
To:	jassi brar <jassisinghbrar@...il.com>
Cc:	spi-devel-general@...ts.sourceforge.net,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	David Brownell <dbrownell@...rs.sourceforge.net>
Subject: Re: [spi-devel-general] [git pull] 2nd batch of SPI changes

On Thu, Dec 17, 2009 at 5:45 PM, jassi brar <jassisinghbrar@...il.com> wrote:
> On Fri, Dec 18, 2009 at 1:40 AM, Grant Likely <grant.likely@...retlab.ca> wrote:
>> Jassi Brar (1):
>>      spi: Add s3c64xx SPI Controller driver
> IIRC, I didn't get any final ack of acceptance from you or any other maintainer.
> I thought perhaps the patch is lost and was preparing to resend after
> including some minor changes suggested by my ARCH maintainer(Ben Dooks).
> Though I can just as well send those changes as patches right away.
> I apologize, if i messed up.

Don't worry about it, just send an incremental patch.  I'm new to the
SPI maintainer job, and I didn't know any of the background or see any
major reason not to merge the driver, especially since it is a new
driver, and not a change to an existing one.

g.
--
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