From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <libc-alpha-return-89296-listarch-libc-alpha=sources.redhat.com@sourceware.org>
Received: (qmail 23167 invoked by alias); 18 Jan 2018 13:36:04 -0000
Mailing-List: contact libc-alpha-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <libc-alpha.sourceware.org>
List-Subscribe: <mailto:libc-alpha-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/libc-alpha/>
List-Post: <mailto:libc-alpha@sourceware.org>
List-Help: <mailto:libc-alpha-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: libc-alpha-owner@sourceware.org
Received: (qmail 23142 invoked by uid 89); 18 Jan 2018 13:36:03 -0000
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-2.0 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS,URIBL_RED autolearn=ham version=3.3.2 spammy=concerned, validation, HCC:D*net
X-HELO: relay1.mentorg.com
Date: Thu, 18 Jan 2018 13:36:00 -0000
From: Joseph Myers <joseph@codesourcery.com>
To: Rafal Luzynski <digitalfreak@lingonborough.com>
CC: <libc-alpha@sourceware.org>, Rical Jasan <ricaljasan@pacific.net>
Subject: Re: [PING][PATCH v12 5/6] Documentation to the above changes (bug
 10871).
In-Reply-To: <1471926159.251959.1516277048618@poczta.nazwa.pl>
Message-ID: <alpine.DEB.2.20.1801181331520.2753@digraph.polyomino.org.uk>
References: <1802414843.37687.1515744747279@poczta.nazwa.pl> <1927758682.38060.1515745107778@poczta.nazwa.pl> <49ea50a9-3cca-bbfe-8c75-41ea603d1a58@pacific.net> <232736801.586762.1516016805848@poczta.nazwa.pl>
 <1471926159.251959.1516277048618@poczta.nazwa.pl>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
X-ClientProxiedBy: svr-ies-mbx-01.mgc.mentorg.com (139.181.222.1) To
 svr-ies-mbx-01.mgc.mentorg.com (139.181.222.1)
X-SW-Source: 2018-01/txt/msg00600.txt.bz2

On Thu, 18 Jan 2018, Rafal Luzynski wrote:

> PING - I'm getting worried about my patches.  Carlos, anybody?

I'm concerned more generally that we still have multiple complicated 
architecture-independent patches, especially this one and C11 threads, 
pending review for 2.27, as the architecture validation for 2.27 can't 
really start until those patches have either been accepted or postponed to 
2.28.  (Architecture maintainers of course can and should do preliminary 
testing and fixing issues found, but we should resolve the major 
architecture-independent patches before any near-final validation for the 
release.)

-- 
Joseph S. Myers
joseph@codesourcery.com