| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Fri, 28 Feb 2014 20:09:34 -0800 From: Greg Kroah-Hartman <gregkh@...uxfoundation.org> To: Masood Mehmood <ody.guru@...il.com> Cc: devel@...verdev.osuosl.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH] Staging:tidspbridge: Fixing coding style On Fri, Feb 28, 2014 at 12:30:04AM -0800, Masood Mehmood wrote: > > On Fri, Feb 28, 2014 at 07:01:56PM -0800, Greg Kroah-Hartman wrote: > > On Fri, Feb 28, 2014 at 06:15:52PM -0800, Masood Mehmood wrote: > > > > > > > > > > > Fixing some basic coding style issues. > > > > Which issues did you fix? Please be more specific. Did you fix them > > for the whole driver, or just a specific file? > > - Unnecessary line break and space. > - and some * adjusted to the data name > - Removed braces for single statement if conditions. Great, can you put that in the patch itself? As it's small, they all can be in the same patch, but normally we only want one patch per "type" of change. For this case, if it was lots of changes, you would break it up into different patches. > I just realized, other files of the same driver also need some style fixes. > I'll send another patch with reset of the files included. Watch out, now you might want to send multiple patches, based on the above "one thing per patch" rule. thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists