From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.linuxfoundation.org ([140.211.169.12]:45413 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752040AbcIGG2t (ORCPT ); Wed, 7 Sep 2016 02:28:49 -0400 Date: Wed, 7 Sep 2016 08:28:52 +0200 From: Greg Kroah-Hartman To: Vineet Gupta Cc: arcml , "stable@vger.kernel.org" Subject: Re: WTF: patch "[PATCH] ARC: Support syscall ABI v4" was seriously submitted to be applied to the 4.7-stable tree? Message-ID: <20160907062852.GA1287@kroah.com> References: <1473080592214136@kroah.com> <584a8fcd-6876-de0d-3c5e-8b4dad12c49d@synopsys.com> <20160906193810.GB22028@kroah.com> <7ab12d76-875a-c06f-08e3-ef628edda1b9@synopsys.com> <1e3ae422-d8ff-326e-29bd-b58002b5163b@synopsys.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1e3ae422-d8ff-326e-29bd-b58002b5163b@synopsys.com> Sender: stable-owner@vger.kernel.org List-ID: On Tue, Sep 06, 2016 at 01:28:45PM -0700, Vineet Gupta wrote: > On 09/06/2016 01:22 PM, Vineet Gupta wrote: > > > Not "we need to support gcc6 for > > > old kernels", as really, if someone wants to update userspace, they > > > don't update their kernel? > > FWIW, I'm not arguing for the backport inclusion - I'm just trying to explain the > context more. > > Thing is your regular user/customer don't really care/know about these details. So > there are tools bugs and more often than not the easy answer for tools providers > is "this is a known issue in gcc x.y which has been fixed in gcc x2.y2 so consider > upgrading". So it is for such class of users that having such backports makes life > a little easy. That's fine, but who would be upgrading their userspace gcc and then wanting to rebuild their kernel for an old kernel release? What prevents them from also updating their kernel? I understand the context, I'm just trying to say that this really is a "new feature" you are wanting here from what I can tell. I'd recommend just having people upgrade their kernel :) thanks, greg k-h From mboxrd@z Thu Jan 1 00:00:00 1970 From: gregkh@linuxfoundation.org (Greg Kroah-Hartman) Date: Wed, 7 Sep 2016 08:28:52 +0200 Subject: WTF: patch "[PATCH] ARC: Support syscall ABI v4" was seriously submitted to be applied to the 4.7-stable tree? In-Reply-To: <1e3ae422-d8ff-326e-29bd-b58002b5163b@synopsys.com> References: <1473080592214136@kroah.com> <584a8fcd-6876-de0d-3c5e-8b4dad12c49d@synopsys.com> <20160906193810.GB22028@kroah.com> <7ab12d76-875a-c06f-08e3-ef628edda1b9@synopsys.com> <1e3ae422-d8ff-326e-29bd-b58002b5163b@synopsys.com> List-ID: Message-ID: <20160907062852.GA1287@kroah.com> To: linux-snps-arc@lists.infradead.org On Tue, Sep 06, 2016@01:28:45PM -0700, Vineet Gupta wrote: > On 09/06/2016 01:22 PM, Vineet Gupta wrote: > > > Not "we need to support gcc6 for > > > old kernels", as really, if someone wants to update userspace, they > > > don't update their kernel? > > FWIW, I'm not arguing for the backport inclusion - I'm just trying to explain the > context more. > > Thing is your regular user/customer don't really care/know about these details. So > there are tools bugs and more often than not the easy answer for tools providers > is "this is a known issue in gcc x.y which has been fixed in gcc x2.y2 so consider > upgrading". So it is for such class of users that having such backports makes life > a little easy. That's fine, but who would be upgrading their userspace gcc and then wanting to rebuild their kernel for an old kernel release? What prevents them from also updating their kernel? I understand the context, I'm just trying to say that this really is a "new feature" you are wanting here from what I can tell. I'd recommend just having people upgrade their kernel :) thanks, greg k-h