From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 122487 invoked by alias); 7 May 2018 16:50:20 -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 122467 invoked by uid 89); 7 May 2018 16:50:20 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.9 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS autolearn=ham version=3.3.2 spammy= X-HELO: mx1.redhat.com Received: from mx3-rdu2.redhat.com (HELO mx1.redhat.com) (66.187.233.73) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 07 May 2018 16:50:19 +0000 Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.rdu2.redhat.com [10.11.54.4]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id C9A6C406C775; Mon, 7 May 2018 16:50:17 +0000 (UTC) Received: from [127.0.0.1] (ovpn04.gateway.prod.ext.ams2.redhat.com [10.39.146.4]) by smtp.corp.redhat.com (Postfix) with ESMTP id 56C682024CA1; Mon, 7 May 2018 16:50:17 +0000 (UTC) Subject: Re: [PATCH] gdb: xtensa: handle privileged registers To: Max Filippov , gdb-patches@sourceware.org References: <20180426024154.5913-1-jcmvbkbc@gmail.com> From: Pedro Alves Message-ID: Date: Mon, 07 May 2018 16:50:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-SW-Source: 2018-05/txt/msg00172.txt.bz2 Hi Max, On 05/07/2018 05:23 PM, Max Filippov wrote: > Ping? > The fix was verified by the reporting party > ( https://github.com/zephyrproject-rtos/zephyr/issues/4309#issuecomment-387017968 > ) > If there are no objections I'd like to commit it. It would help if the the patch included some rationale/explanation. Like: - what is wrong or broken currently, - what does the patch fix, - and how. Could you please resend the patch with that info included in the proposed git commit log? Thanks, Pedro Alves