From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-pl0-x244.google.com ([2607:f8b0:400e:c01::244]) by bombadil.infradead.org with esmtps (Exim 4.89 #1 (Red Hat Linux)) id 1emjvd-00076d-Cr for linux-mtd@lists.infradead.org; Fri, 16 Feb 2018 17:36:11 +0000 Received: by mail-pl0-x244.google.com with SMTP id 31so2027286ple.9 for ; Fri, 16 Feb 2018 09:35:58 -0800 (PST) Message-ID: <1518802552.4426.5.camel@gmail.com> Subject: Re: [PATCH NAND 0/5] Replace printk statements with pr_*macros From: Shreeya Patel To: Ezequiel Garcia Cc: Boris Brezillon , Richard Weinberger , David Woodhouse , Brian Norris , Marek Vasut , Cyrille Pitchen , outreachy-kernel , linux-mtd@lists.infradead.org Date: Fri, 16 Feb 2018 23:05:52 +0530 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 8bit List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Fri, 2018-02-16 at 14:19 -0300, Ezequiel Garcia wrote: > Hi Shreeya, > > Thanks for the contribution. > > On 16 February 2018 at 13:50, Shreeya Patel > wrote: > > > > This patchset removes all the log levels i.e. KERN_WARN, > > KERN_NOTICE, KERN_ERR, KERN_INFO, KERN_DEBUG used in the printk > > statements and replaces the printk statements with appropriate > > pr_*macros. > > According to the kernel coding style, pr_*macro is the preferred > > way to print the message. > > > So, two things to begin with. > > First of all, despite this contribution being part of outreachy, > I believe you can include mailing lists in your case. > > In other words, don't use the "nol" option in get_maintainer > script and Cc the MTD mailing list: linux-mtd at lists.infradead.org. Ok. I'll take care of this. > > > > > > > Shreeya Patel (5): > >   mtd/nand: Replace printk with pr_warn > >   mtd/nand: Replace printk with pr_notice > >   mtd/nand: Replace printk with pr_err > >   mtd/nand: Replace printk with pr_info > >   mtd/nand: Replace printk with pr_debug > > > This is a non-usual split. We usually split patches per-driver, > instead of grouping all the pr_{} of a given type together. > > Can you re-do the series? Grouping the changes per-driver, > i.e. all the pr_{} changes in cafe_nand.c together, and so on. Yes, I'll do it again. :) Also, I wanted to ask you that there are still printk statements  present in the driver which are just printing the message i.e. they don't include any log levels. So should I leave them as it is? Thanks for your reviews  > > > > >  drivers/mtd/nand/ams-delta.c     |  4 +-- > >  drivers/mtd/nand/cafe_nand.c     |  4 +-- > >  drivers/mtd/nand/cs553x_nand.c   |  8 ++--- > >  drivers/mtd/nand/diskonchip.c    | 76 +++++++++++++++++++++------- > > ------------ > >  drivers/mtd/nand/fsl_elbc_nand.c |  4 +-- > >  drivers/mtd/nand/fsl_ifc_nand.c  |  2 +- > >  drivers/mtd/nand/mxc_nand.c      |  2 +- > >  drivers/mtd/nand/nand_bch.c      | 12 +++---- > >  drivers/mtd/nand/nandsim.c       | 10 +++--- > >  drivers/mtd/nand/r852.c          |  2 +- > >  drivers/mtd/nand/r852.h          |  6 ++-- > >  drivers/mtd/nand/sh_flctl.c      |  2 +- > >  drivers/mtd/nand/sm_common.c     |  5 ++- > >  13 files changed, 70 insertions(+), 67 deletions(-) > > > > -- > > 2.7.4 > > > >