From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LkM5c-0001TR-8o for qemu-devel@nongnu.org; Thu, 19 Mar 2009 13:31:32 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LkM5X-0001Np-9t for qemu-devel@nongnu.org; Thu, 19 Mar 2009 13:31:31 -0400 Received: from [199.232.76.173] (port=55281 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LkM5X-0001Nc-2d for qemu-devel@nongnu.org; Thu, 19 Mar 2009 13:31:27 -0400 Received: from mx20.gnu.org ([199.232.41.8]:63748) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1LkM5W-0002oK-Uh for qemu-devel@nongnu.org; Thu, 19 Mar 2009 13:31:27 -0400 Received: from mail.codesourcery.com ([65.74.133.4]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LkM5V-00054G-2L for qemu-devel@nongnu.org; Thu, 19 Mar 2009 13:31:25 -0400 From: Vladimir Prus Subject: Re: [Qemu-devel] SH: Improve the interrupt controller Date: Thu, 19 Mar 2009 20:31:21 +0300 References: <200812112252.17620.vladimir@codesourcery.com> <200903132132.15945.vladimir@codesourcery.com> <200903191717.n2JHHcw8018869@smtp09.dti.ne.jp> In-Reply-To: <200903191717.n2JHHcw8018869@smtp09.dti.ne.jp> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <200903192031.22032.vladimir@codesourcery.com> Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: takasi-y@ops.dti.ne.jp Cc: qemu-devel@nongnu.org On Thursday 19 March 2009 20:17:38 takasi-y@ops.dti.ne.jp wrote: Yoshii, > Sorry for making you be confused, > # I worried when I had been assigned to qemu related job, though.... > > All development works I have done on qemu are for my hobby. > This mail address, which is used to sign-off for qemu, is for my personal use. OK. > > Indeed, mailing patches and revisions back and forth is cumbersome. If the > > above set of patches works for you for r2d, then maybe the best approach > > is to get them checked in -- and then I'll have a baseline to revise my > > patch series against? > Perhaps, that will make things easier. ... > Being asked if I post it, I think I will rather choose not committing it. ... > But, anyway, I don't mind it be checked in, unless it has regressions. ... It is my understanding that my original patch, plus three revision you have sent together cause no regression for r2d. At the same time, my original patch is necessary for sh4a, for reason I have described when I have posted it. Based on that, I will combine my and your patches, and will post it early next week. - Volodya