From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757515AbcFAHwE (ORCPT ); Wed, 1 Jun 2016 03:52:04 -0400 Received: from bombadil.infradead.org ([198.137.202.9]:43277 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750835AbcFAHwB (ORCPT ); Wed, 1 Jun 2016 03:52:01 -0400 Date: Wed, 1 Jun 2016 00:51:42 -0700 From: Christoph Hellwig To: Krzysztof Kozlowski Cc: Christoph Hellwig , Russell King , Catalin Marinas , Will Deacon , Joerg Roedel , Andrew Morton , Marek Szyprowski , Michal Hocko , Mel Gorman , Arnd Bergmann , Andy Lutomirski , linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, xen-devel@lists.xenproject.org, dri-devel@lists.freedesktop.org, linux-samsung-soc@vger.kernel.org, iommu@lists.linux-foundation.org, sstabellini@kernel.org, Bartlomiej Zolnierkiewicz Subject: Re: [RFC v2] dma-mapping: Use unsigned long for dma_attrs Message-ID: <20160601075142.GA1700@infradead.org> References: <1464609246-6948-1-git-send-email-k.kozlowski@samsung.com> <1464609246-6948-2-git-send-email-k.kozlowski@samsung.com> <20160531170420.GB25366@infradead.org> <574E746A.2030806@samsung.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <574E746A.2030806@samsung.com> User-Agent: Mutt/1.5.24 (2015-08-30) X-SRS-Rewrite: SMTP reverse-path rewritten from by bombadil.infradead.org. See http://www.infradead.org/rpr.html Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jun 01, 2016 at 07:36:42AM +0200, Krzysztof Kozlowski wrote: > > No really for this patch, but I would much prefer to document them next > > to the code in the long run. Also I really think these BIT() macros > > are a distraction compared to the (1 << N) notation. > > Not much difference to me but maybe plain number: > ... 0x01u > ... 0x02u > ? I prefer the little bit shifts, but even the explicit values are much better than the obsfucating macros :) Anyway, your patch and in the end all three methods will get the work done. > > I'd just kill this helper, much easier to simply open code it in the > > caller. > > Keeping it for now helps reducing the number of changes in the patch. > The patch will be quite big as it has to replace all the uses atomically. > > I can get rid of the helper in consecutive patch. Sounds fine.