From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Sasha Levin <sasha.levin@oracle.com>
Cc: "Nicholas A. Bellinger" <nab@linux-iscsi.org>,
target-devel <target-devel@vger.kernel.org>,
stable <stable@vger.kernel.org>
Subject: Re: [PATCH-v4.1.y 0/8] target: stable backports
Date: Mon, 7 Mar 2016 12:43:01 -0800 [thread overview]
Message-ID: <20160307204301.GA27319@kroah.com> (raw)
In-Reply-To: <56DC8263.5080006@oracle.com>
On Sun, Mar 06, 2016 at 02:17:55PM -0500, Sasha Levin wrote:
> On 03/05/2016 08:24 PM, Nicholas A. Bellinger wrote:
> > From: Nicholas Bellinger <nab@linux-iscsi.org>
> >
> > 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?
I don't know, I don't check any trees other than the ones I care about,
and send those messages out "manually" when I eventually give up on
trying to apply a patch. Sasha, please send them out if you can't get a
patch to apply that is marked to be added to the kernels you are
maintaining, there's no reason for you not to.
thanks,
greg k-h
prev parent reply other threads:[~2016-03-07 20:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-06 1:24 [PATCH-v4.1.y 0/8] target: stable backports Nicholas A. Bellinger
2016-03-06 1:24 ` [PATCH-v4.1.y 1/8] iscsi-target: Fix rx_login_comp hang after login failure Nicholas A. Bellinger
2016-03-06 1:24 ` [PATCH-v4.1.y 2/8] target: Fix race for SCF_COMPARE_AND_WRITE_POST checking Nicholas A. Bellinger
2016-03-06 1:24 ` [PATCH-v4.1.y 3/8] target: fix COMPARE_AND_WRITE non zero SGL offset data corruption Nicholas A. Bellinger
2016-03-06 1:24 ` [PATCH-v4.1.y 4/8] target: Fix LUN_RESET active I/O handling for ACK_KREF Nicholas A. Bellinger
2016-03-06 1:24 ` [PATCH-v4.1.y 5/8] target: Fix TAS handling for multi-session se_node_acls Nicholas A. Bellinger
2016-03-06 1:24 ` [PATCH-v4.1.y 6/8] target: Fix remote-port TMR ABORT + se_cmd fabric stop Nicholas A. Bellinger
2016-03-06 1:24 ` [PATCH-v4.1.y 7/8] target: Fix race with SCF_SEND_DELAYED_TAS handling Nicholas A. Bellinger
2016-03-06 1:24 ` [PATCH-v4.1.y 8/8] target: Fix linux-4.1.y specific compile warning Nicholas A. Bellinger
2016-03-06 19:17 ` [PATCH-v4.1.y 0/8] target: stable backports Sasha Levin
2016-03-07 2:32 ` Nicholas A. Bellinger
2016-03-07 20:43 ` Greg Kroah-Hartman [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160307204301.GA27319@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=nab@linux-iscsi.org \
--cc=sasha.levin@oracle.com \
--cc=stable@vger.kernel.org \
--cc=target-devel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox