linux-kernel - Re: [PATCH v3 0/6] i2c: at91: add support to FIFOs and alternative command

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:	Tue, 2 Jun 2015 17:52:22 +0200
From:	Ludovic Desroches <ludovic.desroches@...el.com>
To:	Wolfram Sang <wsa@...-dreams.de>
CC:	Cyrille Pitchen <cyrille.pitchen@...el.com>,
	<nicolas.ferre@...el.com>, <linux-i2c@...r.kernel.org>,
	<linux-kernel@...r.kernel.org>,
	<linux-arm-kernel@...ts.infradead.org>,
	<devicetree@...r.kernel.org>, <pawel.moll@....com>,
	<mark.rutland@....com>, <ijc+devicetree@...lion.org.uk>,
	<galak@...eaurora.org>, <robh+dt@...nel.org>
Subject: Re: [PATCH v3 0/6] i2c: at91: add support to FIFOs and alternative
 command

On Wed, Jun 03, 2015 at 12:36:28AM +0900, Wolfram Sang wrote:
> 
> > If you send a new version, could you add stable in Cc to patch 3/6:
> 
> No need to send a new version just because of an additional ack. I can
> apply that. However...
> 
> > Cc: stable@...r.kernel.org #3.10 and later
> > If not, Wolfram could you do it please?
> 
> The problem with 3/6 is that it seems to depend on 1/6 which is a
> cleanup patch. If cleaning up is not essential for the bugfix, the
> latter should be done first. To avoid exactly this problem.
> 
> 

I was thinking the same so I have tried to cherry-pick the patch on a 3.10.79
and it didn't cause any conflicts so I thought it could be sent to stable as
is.

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