From: Vineet Gupta <Vineet.Gupta1@synopsys.com> To: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>, arcml <linux-snps-arc@lists.infradead.org> Cc: "stable@vger.kernel.org" <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? Date: Tue, 6 Sep 2016 13:21:21 -0700 [thread overview] Message-ID: <7ab12d76-875a-c06f-08e3-ef628edda1b9@synopsys.com> (raw) In-Reply-To: <20160906193810.GB22028@kroah.com> On 09/06/2016 12:39 PM, gregkh@linuxfoundation.org wrote: > On Tue, Sep 06, 2016 at 09:50:46AM -0700, Vineet Gupta wrote: >> On 09/05/2016 06:03 AM, gregkh@linuxfoundation.org wrote: >>> The patch below was submitted to be applied to the 4.7-stable tree. >>> >>> I fail to see how this patch meets the stable kernel rules as found at >>> Documentation/stable_kernel_rules.txt. >>> >>> I could be totally wrong, and if so, please respond to >>> <stable@vger.kernel.org> and let me know why this patch should be >>> applied. Otherwise, it is now dropped from my patch queues, never to be >>> seen again. >> Hi Greg, >> >> We are about to switch to new version of GNU tools (gcc 6.x based) which >> unfortunately has a non compatible ABI change - as described in the patch. >> >> Some of our customers are going to stick with older kernels and thus this helps >> them upgrade to newer tools with their existing baseline kernels. > That's nice, but it's a new feature. Stick with old userspace for older > kernels, and use new kernels for new userspace if you so desire. I understand your point. This is what we did at the time of upstreaming the kernel - and was something I was hoping to avoid this time because this is a flag day change. People get locked into kernel version or tools - when the kernel code itself didn't really change a bit. But if this really is against the norms of stable backports, then I suppose we can't do much ? Thx, -Vineet > > We do allow some new gcc fixes to be backported, but that's always where > we have found bugs, or build warnings. Not "we need to support gcc6 for > old kernels", as really, if someone wants to update userspace, they > don't update their kernel? > > thanks, > > greg k-h >
WARNING: multiple messages have this Message-ID (diff)
From: Vineet.Gupta1@synopsys.com (Vineet Gupta) To: linux-snps-arc@lists.infradead.org Subject: WTF: patch "[PATCH] ARC: Support syscall ABI v4" was seriously submitted to be applied to the 4.7-stable tree? Date: Tue, 6 Sep 2016 13:21:21 -0700 [thread overview] Message-ID: <7ab12d76-875a-c06f-08e3-ef628edda1b9@synopsys.com> (raw) In-Reply-To: <20160906193810.GB22028@kroah.com> On 09/06/2016 12:39 PM, gregkh@linuxfoundation.org wrote: > On Tue, Sep 06, 2016@09:50:46AM -0700, Vineet Gupta wrote: >> On 09/05/2016 06:03 AM, gregkh@linuxfoundation.org wrote: >>> The patch below was submitted to be applied to the 4.7-stable tree. >>> >>> I fail to see how this patch meets the stable kernel rules as found at >>> Documentation/stable_kernel_rules.txt. >>> >>> I could be totally wrong, and if so, please respond to >>> <stable at vger.kernel.org> and let me know why this patch should be >>> applied. Otherwise, it is now dropped from my patch queues, never to be >>> seen again. >> Hi Greg, >> >> We are about to switch to new version of GNU tools (gcc 6.x based) which >> unfortunately has a non compatible ABI change - as described in the patch. >> >> Some of our customers are going to stick with older kernels and thus this helps >> them upgrade to newer tools with their existing baseline kernels. > That's nice, but it's a new feature. Stick with old userspace for older > kernels, and use new kernels for new userspace if you so desire. I understand your point. This is what we did at the time of upstreaming the kernel - and was something I was hoping to avoid this time because this is a flag day change. People get locked into kernel version or tools - when the kernel code itself didn't really change a bit. But if this really is against the norms of stable backports, then I suppose we can't do much ? Thx, -Vineet > > We do allow some new gcc fixes to be backported, but that's always where > we have found bugs, or build warnings. Not "we need to support gcc6 for > old kernels", as really, if someone wants to update userspace, they > don't update their kernel? > > thanks, > > greg k-h >
next prev parent reply other threads:[~2016-09-06 20:21 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-09-05 13:03 WTF: patch "[PATCH] ARC: Support syscall ABI v4" was seriously submitted to be applied to the 4.7-stable tree? gregkh 2016-09-06 16:50 ` Vineet Gupta 2016-09-06 19:38 ` gregkh 2016-09-06 20:21 ` Vineet Gupta [this message] 2016-09-06 20:21 ` Vineet Gupta 2016-09-06 20:28 ` Vineet Gupta 2016-09-06 20:28 ` Vineet Gupta 2016-09-07 6:28 ` Greg Kroah-Hartman 2016-09-07 6:28 ` Greg Kroah-Hartman 2016-09-07 16:38 ` Vineet Gupta 2016-09-07 16:38 ` Vineet Gupta 2016-09-09 11:39 ` Greg Kroah-Hartman 2016-09-09 11:39 ` Greg Kroah-Hartman 2016-09-09 17:08 ` Vineet Gupta 2016-09-09 17:08 ` Vineet Gupta
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=7ab12d76-875a-c06f-08e3-ef628edda1b9@synopsys.com \ --to=vineet.gupta1@synopsys.com \ --cc=gregkh@linuxfoundation.org \ --cc=linux-snps-arc@lists.infradead.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: linkBe 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.