From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754191AbdCWIY7 (ORCPT ); Thu, 23 Mar 2017 04:24:59 -0400 Received: from mail.free-electrons.com ([62.4.15.54]:59263 "EHLO mail.free-electrons.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751449AbdCWIY6 (ORCPT ); Thu, 23 Mar 2017 04:24:58 -0400 Date: Thu, 23 Mar 2017 09:16:24 +0100 From: Boris Brezillon To: Masahiro Yamada Cc: linux-mtd@lists.infradead.org, Laurent Monat , thorsten.christiansson@idquantique.com, Enrico Jorns , Jason Roberts , Artem Bityutskiy , Dinh Nguyen , Marek Vasut , Brian Norris , Graham Moore , David Woodhouse , Masami Hiramatsu , Chuanxiao Dong , Jassi Brar , Linux Kernel Mailing List , Richard Weinberger , Cyrille Pitchen Subject: Re: [PATCH v2 12/53] mtd: nand: denali: support HW_ECC_FIXUP capability Message-ID: <20170323091624.6894b07c@bbrezillon> In-Reply-To: References: <1490191680-14481-1-git-send-email-yamada.masahiro@socionext.com> <1490191680-14481-13-git-send-email-yamada.masahiro@socionext.com> <20170322220937.202c5180@bbrezillon> X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.30; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 23 Mar 2017 16:06:19 +0900 Masahiro Yamada wrote: > Hi Boris, > > 2017-03-23 6:09 GMT+09:00 Boris Brezillon : > > On Wed, 22 Mar 2017 23:07:19 +0900 > > Masahiro Yamada wrote: > > > >> @@ -339,6 +352,7 @@ struct denali_nand_info { > >> int bbtskipbytes; > >> int max_banks; > >> unsigned int caps; > >> +#define DENALI_CAP_HW_ECC_FIXUP BIT(0) > > > > Can you move this definition outside of the struct denali_nand_info > > definition? > > > My idea was to put relevant macros close to the "caps" member. > Actually, "struct mmc_host" does similar. > > > If you do not like it, yes, I can move it. > Anyway, this is a matter of taste, > and I do not have a strong opinion about this. > > Indeed, I prefer when macro and struct definitions are clearly separated.