From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <SRS0=lxM9=RP=vger.kernel.org=stable-owner@kernel.org>
X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on
	aws-us-west-2-korg-lkml-1.web.codeaurora.org
X-Spam-Level: 
X-Spam-Status: No, score=-7.5 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED,
	DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,
	MENTIONS_GIT_HOSTING,SPF_PASS,URIBL_BLOCKED,USER_AGENT_MUTT autolearn=ham
	autolearn_force=no version=3.4.0
Received: from mail.kernel.org (mail.kernel.org [198.145.29.99])
	by smtp.lore.kernel.org (Postfix) with ESMTP id F0FD8C43381
	for <stable@archiver.kernel.org>; Tue, 12 Mar 2019 11:43:44 +0000 (UTC)
Received: from vger.kernel.org (vger.kernel.org [209.132.180.67])
	by mail.kernel.org (Postfix) with ESMTP id BD1AC206DF
	for <stable@archiver.kernel.org>; Tue, 12 Mar 2019 11:43:44 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org;
	s=default; t=1552391024;
	bh=pOt2/fK6bWG1RiHKoaSKEogeiScyBfv2ivrQ0gwNmn0=;
	h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From;
	b=AvZJGUpTPYoYVpaZoFSUM9p3iGQREmgtVcCRWnG71FR6cWhMUzDMIdsmYDIBSwm1z
	 WX+PQE2h9xxCcCR+MdJXB8SmAGRj+/a4epF+i+A1zWhaArrKG7WG/Cc2hAeTMLT5VK
	 BEoWu0MGBWUScbi6MrByPuMhDLbB+liHiaC4291M=
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1726008AbfCLLno (ORCPT <rfc822;stable@archiver.kernel.org>);
        Tue, 12 Mar 2019 07:43:44 -0400
Received: from mail.kernel.org ([198.145.29.99]:37090 "EHLO mail.kernel.org"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1725887AbfCLLnn (ORCPT <rfc822;stable@vger.kernel.org>);
        Tue, 12 Mar 2019 07:43:43 -0400
Received: from localhost (unknown [12.27.65.221])
        (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
        (No client certificate requested)
        by mail.kernel.org (Postfix) with ESMTPSA id 63472206DF;
        Tue, 12 Mar 2019 11:43:43 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org;
        s=default; t=1552391023;
        bh=pOt2/fK6bWG1RiHKoaSKEogeiScyBfv2ivrQ0gwNmn0=;
        h=Date:From:To:Cc:Subject:References:In-Reply-To:From;
        b=IjVjVJZwn3FSujdyDm1s4FJ9yxgwcXpL3KQBEKLK576RJG141B6bZlvrPVJO9iLH5
         2mSYHzMWJpSqaHjNa5hC//Ol9tFwx5kogIAyhCdYN7v7i98WBHCGElYNM9mtSyFb8x
         l4CJq6DZeNVKpSprBwnnfbx9F2lZ4QX17bXSwBds=
Date:   Tue, 12 Mar 2019 04:43:43 -0700
From:   Greg KH <gregkh@linuxfoundation.org>
To:     Jack Wang <jinpuwang@gmail.com>
Cc:     stable@vger.kernel.org
Subject: Re: [RFC stable-4.14 00/11] PSI feature for 4.14
Message-ID: <20190312114343.GA28214@kroah.com>
References: <20190312102002.31737-1-jinpuwang@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20190312102002.31737-1-jinpuwang@gmail.com>
User-Agent: Mutt/1.11.3 (2019-02-01)
Sender: stable-owner@vger.kernel.org
Precedence: bulk
List-ID: <stable.vger.kernel.org>
X-Mailing-List: stable@vger.kernel.org

On Tue, Mar 12, 2019 at 11:19:51AM +0100, Jack Wang wrote:
> Hi Folks,
> 
> This is a backport for PSI feature from:
> http://git.cmpxchg.org/cgit.cgi/linux-psi.git/log/?h=psi-4.17
> 
> The patches are included since 4.20.
> 
> We're run LTP tests and stress test with these patches on 4.14.93,
> no problem found.
> 
> I send them out for review, also maybe there are other guys are intereseted.
> 
> I kept the conflict note in commit message, so it's easier to review.

This is nice, but why?  We can't take new features into the stable
kernel trees.  For Android devices (which do want PSI), all of the
patches are already backported into the android-common 4.14 branch,
right?  Or does this differ from that backport somehow?

thanks,

greg k-h