From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from aserp1040.oracle.com ([141.146.126.69]:25420 "EHLO aserp1040.oracle.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751147AbcCFTSE (ORCPT ); Sun, 6 Mar 2016 14:18:04 -0500 Subject: Re: [PATCH-v4.1.y 0/8] target: stable backports To: "Nicholas A. Bellinger" , target-devel , stable , Greg Kroah-Hartman References: <1457227469-32210-1-git-send-email-nab@linux-iscsi.org> From: Sasha Levin Message-ID: <56DC8263.5080006@oracle.com> Date: Sun, 6 Mar 2016 14:17:55 -0500 MIME-Version: 1.0 In-Reply-To: <1457227469-32210-1-git-send-email-nab@linux-iscsi.org> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Sender: stable-owner@vger.kernel.org List-ID: On 03/05/2016 08:24 PM, Nicholas A. Bellinger wrote: > From: Nicholas Bellinger > > Hi Sasha, > > The following series contains v4.1.y stable backports for a number > of target patches from upstream code, that don't appear in your > stable tree. > > Also included is a small complile fix specific to v4.1.y code. > > Please apply at your earliest convience. Thanks Nicholas, I've added both series to their corresponding trees. > Btw, I didn't seen any 'failed to apply' messages from you for > any of these patches, which is how I tell from Greg-KH when > something needs to be manually backported. > > Is there a reason for not sending out 'failed to apply' emails..? Good point. Since I was only maintaining 3.18 so far, I'd wait for maintainers to respond to Greg's mails about failure to apply on either 4.1 or 3.14, and just take their backport from there - which did the trick, and also reduced the amount of mails maintainers get regarding -stable trees. I don't have a problem with starting to send "F-T-A" mails as well, but I wonder if we can somehow coordinate these mails between myself and Greg so we won't send one for each and every kernel version, but rather one specifying which stable versions failed to apply? Greg, What are your thoughts about this? Thanks, Sasha