From: Ben Hutchings <[email protected]> Date: Thu, 12 Sep 2013 02:59:53 +0100
> On Wed, 2013-09-11 at 15:26 -0400, David Miller wrote: >> From: Luis Henriques <[email protected]> >> Date: Wed, 11 Sep 2013 11:57:17 +0100 >> >> > I was looking at the backport for commit >> > >> > 85dfb745ee40232876663ae206cba35f24ab2a40 af_key: initialize satype in >> > key_notify_policy_flush() >> > >> > and I believe there's something wrong with it. It patches function >> > key_notify_sa_flush() instead of key_notify_policy_flush(). Is this >> > correct or a mistake? ... > My script shows these: > > $ git check-in-stable 85dfb745ee40232876663ae206cba35f24ab2a40 > 3.0: e00f3fd af_key: initialize satype in key_notify_policy_flush() > 3.2: 54811a1 af_key: initialize satype in key_notify_policy_flush() > 3.4: 1a5abb4 af_key: initialize satype in key_notify_policy_flush() > > This fix was requested in: > > http://thread.gmane.org/gmane.linux.kernel.stable/62076 > > and it looks like Greg and I didn't recognise it as being in your > domain, so we applied directly. Greg, please toss the bogus version I sent you, just as Ben did. Thanks! -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
