From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: 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=-2.5 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,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 8241BC43381 for ; Thu, 14 Mar 2019 17:29:07 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 4A08E2087C for ; Thu, 14 Mar 2019 17:29:07 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1552584547; bh=Tlnq7HZ/lXZS3pNWpu/TPTTGiQGUdg6J92YgJo0PuJ8=; h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From; b=R8SGVLiB4bF9kWi/oWi3shkNPhBtHfDQjy1DsMdfD4bOGOh8HQ3aZ64gi4PC9fD3w RilOOE1+IpNC/b5xh8nwCsNXgZA0+acUscvNWFo+rzu5B3agpkyC4EQdxh6zWYol3D e5IlfiXPGnbrA/vXpCsppSg8DDKoJWebC8Thz1oY= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726485AbfCNR3G (ORCPT ); Thu, 14 Mar 2019 13:29:06 -0400 Received: from mail.kernel.org ([198.145.29.99]:56120 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726424AbfCNR3G (ORCPT ); Thu, 14 Mar 2019 13:29:06 -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 0878C2087C; Thu, 14 Mar 2019 17:29:06 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1552584546; bh=Tlnq7HZ/lXZS3pNWpu/TPTTGiQGUdg6J92YgJo0PuJ8=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=eKZOd7UPOw0Caom9q0fMNCke9/4q6nEr4G1LSbZBAdZyZIY/CT22t6wZfxdKAzMn4 wp/9e8ToAUu30apv9fLQFjdGQQhIzf2Ha927D/WGjiItt7Q2tZS43C7wo5IHM6GnBB P8fq178M9kAoskzVj4zCbfKTu/Z5TVF62y7zb/WA= Date: Thu, 14 Mar 2019 10:29:05 -0700 From: Greg KH To: Jinpu Wang Cc: "v3.14+, only the raid10 part" Subject: Re: [RFC stable-4.14 00/11] PSI feature for 4.14 Message-ID: <20190314172905.GC28850@kroah.com> References: <20190312102002.31737-1-jinpuwang@gmail.com> <20190312114343.GA28214@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.11.4 (2019-03-13) Sender: stable-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: stable@vger.kernel.org On Wed, Mar 13, 2019 at 11:15:43AM +0100, Jinpu Wang wrote: > snip > > 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 > (Resend to reply to all, sorry) > > Thanks Greg, > > We want the feature for our product. Yeah, I know we have > stable-rules, didn't expect > the patches to be included, just in case other guys also need PSI. > > I'm not aware of android-common did the backport already, could you > point me the link? > > I checked in > https://android.googlesource.com/kernel/common/+/refs/heads/android-4.14* > > I didn't find the psi support. Ah, I was wrong, sorry, it has been submitted to AOSP, but not merged yet. Here's the 4.14 patches queued up and ready to go: https://android-review.googlesource.com/q/topic:%22psi+4.14+backport%22+(status:open%20OR%20status:merged) The 4.9 and 4.19 branches also have them queued up: https://android-review.googlesource.com/q/topic:%22psi+4.9+backport%22+(status:open%20OR%20status:merged) https://android-review.googlesource.com/q/topic:%22psi+4.19+backport%22+(status:open%20OR%20status:merged) I talked to the developer this week and he said he was waiting for a few of the remaining patches to be merged upstream first before merging to AOSP to ensure that nothing diverged. Hopefully that should happen in a few weeks or so, after the merge window is open and maintainers reopen their development branches. thanks, greg k-h