From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michal Hocko Subject: Re: [PATCH 0/11] introduce down_write_killable for rw_semaphore Date: Fri, 1 Apr 2016 11:21:46 +0200 Message-ID: <20160401092146.GC8916@dhcp22.suse.cz> References: <1456750705-7141-1-git-send-email-mhocko@kernel.org> <20160330133217.GV3408@twins.programming.kicks-ass.net> <20160331085926.GB27831@dhcp22.suse.cz> <20160331092005.GA18640@gmail.com> <20160331100331.73eb381a45a1e03473f700a9@linux-foundation.org> <20160401063348.GA6815@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20160401063348.GA6815@gmail.com> Sender: linux-alpha-owner@vger.kernel.org To: Ingo Molnar Cc: Andrew Morton , Peter Zijlstra , LKML , Ingo Molnar , Thomas Gleixner , "H. Peter Anvin" , "David S. Miller" , Tony Luck , Chris Zankel , Max Filippov , x86@kernel.org, linux-alpha@vger.kernel.org, linux-ia64@vger.kernel.org, linux-s390@vger.kernel.org, linux-sh@vger.kernel.org, sparclinux@vger.kernel.org, linux-xtensa@linux-xtensa.org, linux-arch@vger.kernel.org List-Id: linux-arch.vger.kernel.org On Fri 01-04-16 08:33:48, Ingo Molnar wrote: [...] > I can help on the Git level: I can do tip:locking/rwsem tree with only these > changes, with stable sha1's, on which the remaining work can be based. The > locking tree typically goes in early during the merge window, so there's no > real dependencies. OK, I will wait for this series to apear in tip:locking/rwsem and then post the follow up patches to Andrew. If you can base this branch on 4.5 that would be ideal for mmotm git tree workflow but I can work that around should there be a complication. Thanks! -- Michal Hocko SUSE Labs From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm0-f65.google.com ([74.125.82.65]:33213 "EHLO mail-wm0-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752460AbcDAJVu (ORCPT ); Fri, 1 Apr 2016 05:21:50 -0400 Date: Fri, 1 Apr 2016 11:21:46 +0200 From: Michal Hocko Subject: Re: [PATCH 0/11] introduce down_write_killable for rw_semaphore Message-ID: <20160401092146.GC8916@dhcp22.suse.cz> References: <1456750705-7141-1-git-send-email-mhocko@kernel.org> <20160330133217.GV3408@twins.programming.kicks-ass.net> <20160331085926.GB27831@dhcp22.suse.cz> <20160331092005.GA18640@gmail.com> <20160331100331.73eb381a45a1e03473f700a9@linux-foundation.org> <20160401063348.GA6815@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160401063348.GA6815@gmail.com> Sender: linux-arch-owner@vger.kernel.org List-ID: To: Ingo Molnar Cc: Andrew Morton , Peter Zijlstra , LKML , Ingo Molnar , Thomas Gleixner , "H. Peter Anvin" , "David S. Miller" , Tony Luck , Chris Zankel , Max Filippov , x86@kernel.org, linux-alpha@vger.kernel.org, linux-ia64@vger.kernel.org, linux-s390@vger.kernel.org, linux-sh@vger.kernel.org, sparclinux@vger.kernel.org, linux-xtensa@linux-xtensa.org, linux-arch@vger.kernel.org Message-ID: <20160401092146.QU66afH2DbT10i9zdVkTnFxf9JgBGdoUFRXxiaKOiTg@z> On Fri 01-04-16 08:33:48, Ingo Molnar wrote: [...] > I can help on the Git level: I can do tip:locking/rwsem tree with only these > changes, with stable sha1's, on which the remaining work can be based. The > locking tree typically goes in early during the merge window, so there's no > real dependencies. OK, I will wait for this series to apear in tip:locking/rwsem and then post the follow up patches to Andrew. If you can base this branch on 4.5 that would be ideal for mmotm git tree workflow but I can work that around should there be a complication. Thanks! -- Michal Hocko SUSE Labs