linux-kernel - Re: [PATCH v5 0/3] Fix lubbock and mainstone interrupts

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: <5225589.tkUhR6vGoM@wuerfel>
Date:	Mon, 27 Apr 2015 11:16:17 +0200
From:	Arnd Bergmann <arnd@...db.de>
To:	Robert Jarzmik <robert.jarzmik@...e.fr>
Cc:	linux-arm-kernel@...ts.infradead.org,
	Daniel Mack <daniel@...que.org>,
	Haojian Zhuang <haojian.zhuang@...il.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH v5 0/3] Fix lubbock and mainstone interrupts

On Sunday 26 April 2015 11:31:13 Robert Jarzmik wrote:
> Arnd Bergmann <arnd@...db.de> writes:
> 
> > On Saturday 25 April 2015 23:13:20 Robert Jarzmik wrote:
> >> This serie was submitted to the lak list, then migrated to mfd drivers, to end
> >> up again here. There was no change since last submission. Let's hope this is the
> >> last spin and that these platform will be fixed at last.
> >> 
> >
> > Should these be marked 'Cc: stable@...r.kernel.org'?
> I can do this. I thought that 3 patches of 100+ lines, and the fact that these
> boards were broken since october 2011 would prevent this serie from reaching the
> stable branch.
> 
> Well, I'll resubmit with this information, and after comments stage it to my
> fixes branch. Let's see what stable tree people will do.
> 
> > Can you also add a 'Fixes' tag with the commit that introduced the problem?
> Sure.

You are right about the size limit, I didn't see how big the patches
actually are. In this case, leave the 'Fixes' tag, but don't add
the Cc to stable.

	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/