From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 66855 invoked by alias); 21 Jun 2019 06:34:51 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 66847 invoked by uid 89); 21 Jun 2019 06:34:51 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-12.2 required=5.0 tests=AWL,BAYES_00,SPF_PASS autolearn=ham version=3.3.1 spammy=H*Ad:U*palves, multi-line, HX-Languages-Length:1048, August X-HELO: mx1.suse.de Received: from mx2.suse.de (HELO mx1.suse.de) (195.135.220.15) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 21 Jun 2019 06:34:50 +0000 Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id C7F0BAD69; Fri, 21 Jun 2019 06:34:47 +0000 (UTC) Subject: [PING][PATCH] Fix amd64->i386 linux syscall restart problem From: Tom de Vries To: Kevin Buettner , gdb-patches@sourceware.org Cc: Pedro Alves References: <20190316221341.021f7c62@f29-4.lan> <975e7120-1b61-2807-5aab-b961e07a80d0@redhat.com> <20190409192916.79fcb539@f29-4.lan> <20190410171606.0e736077@f29-4.lan> <40eb20c2-f6d0-eb16-d6fe-c717138b6559@suse.de> Message-ID: Date: Fri, 21 Jun 2019 06:34:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: <40eb20c2-f6d0-eb16-d6fe-c717138b6559@suse.de> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2019-06/txt/msg00407.txt.bz2 On 21-05-19 14:59, Tom de Vries wrote: > On 11-04-19 02:16, Kevin Buettner wrote: >> On Wed, 10 Apr 2019 12:42:30 +0100 >> Pedro Alves wrote: >> >>>> Below is a diff showing the new comments. It also includes the >>>> changes which wrap the multi-line expressions in parens. >>> >>> Thanks, that new version of the comment looks great. >> >> It's in now. Thanks for the review. > > Hi, > > the tests fixed by this commit fail on the 8.3 branch (filed as PR24592). > > The commit applies cleanly on the 8.3 branch, and make the tests pass. > > OK to backport? Hi, [ Ping. ] I'm probably missing some context here. It seems sofar there are no commits to the 8.3 branch. AFAIU, a respin release 8.3.1 is targeted for 3 months after 8.3, so around 11th of August. What kind of fixes are acceptable for the respin? Do they have to be regression fixes? Or are functionality fixes like this one also allowed? Who's responsibility is it to backport fixes? Thanks, - Tom