From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: Patrick Farrell <paf@cray.com>
Cc: "john.hammond@intel.com" <john.hammond@intel.com>,
"jsimmons@infradead.org" <jsimmons@infradead.org>,
"lai.siyao@intel.com" <lai.siyao@intel.com>,
"oleg.drokin@intel.com" <oleg.drokin@intel.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"stable-commits@vger.kernel.org" <stable-commits@vger.kernel.org>
Subject: Re: Patch "staging: lustre: mdc: Make IT_OPEN take lookup bits lock" has been added to the 4.10-stable tree
Date: Thu, 11 May 2017 14:22:03 +0200 [thread overview]
Message-ID: <20170511122203.GA12521@kroah.com> (raw)
In-Reply-To: <CY4PR11MB17513A806206DED46E1BCBE3CBED0@CY4PR11MB1751.namprd11.prod.outlook.com>
On Thu, May 11, 2017 at 12:10:19PM +0000, Patrick Farrell wrote:
> Greg et al.,
>
>
> Can someone copied here say why this was pushed to stable? When I wrote the
> patch, my impression was the code was wrong but it didn't cause any problems.
> I thought this was basically cleanup. If someone found a problem associated
> with this patch, I'd be curious to hear.
I thought it was needed, based on the patch and the fixes: field. But
you are right, it's not really necessary, so I'll go drop it from the
queue. Thanks for noticing this and letting me know.
greg k-h
prev parent reply other threads:[~2017-05-11 12:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-11 8:25 Patch "staging: lustre: mdc: Make IT_OPEN take lookup bits lock" has been added to the 4.10-stable tree gregkh
[not found] ` <CY4PR11MB17513A806206DED46E1BCBE3CBED0@CY4PR11MB1751.namprd11.prod.outlook.com>
2017-05-11 12:22 ` gregkh [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=20170511122203.GA12521@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=john.hammond@intel.com \
--cc=jsimmons@infradead.org \
--cc=lai.siyao@intel.com \
--cc=oleg.drokin@intel.com \
--cc=paf@cray.com \
--cc=stable-commits@vger.kernel.org \
--cc=stable@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.