From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759789AbbIDSAT (ORCPT ); Fri, 4 Sep 2015 14:00:19 -0400 Received: from mail.linuxfoundation.org ([140.211.169.12]:53062 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752295AbbIDSAS (ORCPT ); Fri, 4 Sep 2015 14:00:18 -0400 Date: Fri, 4 Sep 2015 11:00:17 -0700 From: "gregkh@linuxfoundation.org" To: Jose Rivera Cc: Nayeemahmed Badebade , Stuart Yoder , "agraf@suse.de" , "hgujulan@visteon.com" , "linux-kernel@vger.kernel.org" Subject: Re: [PATCH] Staging: fsl-mc/bus: mc-bus.c: Fixed coding style issues Message-ID: <20150904180017.GA6649@kroah.com> References: <20150903164834.GD31709@kroah.com> <1441386033-2900-1-git-send-email-itachi.opsrc@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Sep 04, 2015 at 05:48:55PM +0000, Jose Rivera wrote: > > -----Original Message----- > > From: Nayeemahmed Badebade [mailto:itachi.opsrc@gmail.com] > > Sent: Friday, September 04, 2015 12:01 PM > > To: gregkh@linuxfoundation.org > > Cc: Rivera Jose-B46482; Yoder Stuart-B08248; agraf@suse.de; > > hgujulan@visteon.com; linux-kernel@vger.kernel.org > > Subject: [PATCH] Staging: fsl-mc/bus: mc-bus.c: Fixed coding style issues > > > > Fixed coding style issues where kernel types u16,u64,u32 should be > > preferred over uint16_t,uint64_t,uint32_t > > > Nayeemahmed, > > Thanks for your interests in helping us clean up this coding style issue. > However, doing this for all the files related to the MC bus driver (not just > for one) is something that I intend to do in a future patch as > part of the "Cleanup" item of our TODO list. > Doing this clean up across the board for all files is preferable than > doing it just for this file in this patch. Sorry, but we never postpone a change submitted by someone just because someone says "sometime in the future we will be making much the same change". That's a sure way to kill productivity and stop developers from helping you out. If you really wanted to make this type of change, you would have done so already, so obviously it's not a high priority. I'll take Nayeemahmed's patch. greg k-h