| 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
| ||
|
Date: Fri, 07 Dec 2012 14:04:34 +0000 From: Grant Likely <grant.likely@...retlab.ca> To: Mark Brown <broonie@...nsource.wolfsonmicro.com> Cc: spi-devel-general@...ts.sourceforge.net, linux-kernel@...r.kernel.org Subject: Re: [PATCH] spi: Remove SPI_BUFSIZ restriction on spi_write_then_read() On Fri, 7 Dec 2012 12:41:41 +0900, Mark Brown <broonie@...nsource.wolfsonmicro.com> wrote: > On Thu, Dec 06, 2012 at 02:04:27PM +0000, Grant Likely wrote: > > > Alright, applied. I've also merged in your spi-next tree. Let me know if > > that causes problems because it needs to be rebased. > > No problem - do you just want to take over the SPI tree again or should > I carry on applying things? Yes, please keep doing what you're doing! It's a huge help. Whenever I sit down to do patch maintenance, I'll pull in your tree first. As long as your tree doesn't get rebased then that should work well. I also promise to not rebase my tree without talking to you first so you can pull in mine before applying more patches on top. It's a huge help to be reading through the mailing list and be able to ignore any messages that I've seen you've already replied to or applied. g. -- Grant Likely, B.Sc, P.Eng. Secret Lab Technologies, Ltd. -- 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