From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759990AbbCDTHh (ORCPT ); Wed, 4 Mar 2015 14:07:37 -0500 Received: from pmta2.delivery10.ore.mailhop.org ([54.69.62.154]:35835 "EHLO pmta2.delivery10.ore.mailhop.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758020AbbCDTHg (ORCPT ); Wed, 4 Mar 2015 14:07:36 -0500 X-Greylist: delayed 72492 seconds by postgrey-1.27 at vger.kernel.org; Wed, 04 Mar 2015 14:07:36 EST X-Mail-Handler: DuoCircle Outbound SMTP X-Originating-IP: 104.193.169.186 X-Report-Abuse-To: abuse@duocircle.com (see https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information for abuse reporting information) X-MHO-User: U2FsdGVkX1/ltp1ZBHYG/12xDRACMvKb Date: Wed, 4 Mar 2015 11:02:09 -0800 From: Tony Lindgren To: Andrew Morton Cc: Valentin Rothberg , linux-kernel@vger.kernel.org Subject: Re: Removal of IRQF_DISABLED Message-ID: <20150304190206.GB13520@atomide.com> References: <20150304094555.f621ca1a.akpm@linux-foundation.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150304094555.f621ca1a.akpm@linux-foundation.org> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Andrew Morton [150304 09:46]: > On Wed, 4 Mar 2015 10:53:07 +0100 Valentin Rothberg wrote: > > > Hi, > > > > Andrew asked me to prepare one big patch that removes the > > IRQF_DISABLED flag entirely. I already sent a few small patches that > > remove the usage of this flag, two of them [1, 2] have been applied > > by Tony to omap-for-v4.1/l3. Hence, I cannot remove the definition > > now and leave the files of [1, 2] untouched. > > > > I don't want to break anything or cause troubles while merging. So > > shall I wait until v4.1 to send the big patch or is there are nice way > > to get it merged now (e.g., getting [1, 2] into omap-for-v4.0)? > > > > You're over-sweating this - merging patches is what we do ;) > > Just send the patch, against current Linus mainline and I'll work it > out. Yeah and I'll drop my omap-for-v4.1/l3 branch no problem. I don't yet have anything applied on top of those two patches. Regards, Tony