From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932115AbdAJWMz (ORCPT ); Tue, 10 Jan 2017 17:12:55 -0500 Received: from smtprelay0030.hostedemail.com ([216.40.44.30]:60947 "EHLO smtprelay.hostedemail.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S932067AbdAJWMx (ORCPT ); Tue, 10 Jan 2017 17:12:53 -0500 X-Session-Marker: 6A6F6540706572636865732E636F6D X-Spam-Summary: 2,0,0,,d41d8cd98f00b204,joe@perches.com,:::::::::::::::,RULES_HIT:41:355:379:541:599:973:988:989:1260:1277:1311:1313:1314:1345:1359:1373:1381:1437:1515:1516:1518:1534:1539:1593:1594:1711:1730:1747:1777:1792:2393:2559:2562:2828:3138:3139:3140:3141:3142:3352:3622:3865:3866:3867:3868:3872:3873:3874:4321:5007:7875:8527:8957:9010:10004:10400:10848:11232:11658:11914:12043:12048:12214:12679:12740:12760:12895:13069:13311:13357:13439:14181:14659:14721:21080:30030:30054:30060:30083:30091,0,RBL:none,CacheIP:none,Bayesian:0.5,0.5,0.5,Netcheck:none,DomainCache:0,MSF:not bulk,SPF:fn,MSBL:0,DNSBL:none,Custom_rules:0:0:0,LFtime:1,LUA_SUMMARY:none X-HE-Tag: magic40_35f96f4ed014c X-Filterd-Recvd-Size: 1547 Message-ID: <1484086369.12006.9.camel@perches.com> Subject: Re: [PATCH] staging: android/ion: Fix coding style issues From: Joe Perches To: Bogdan Purcareata , labbott@redhat.com, sumit.semwal@linaro.org, gregkh@linuxfoundation.org, arve@android.com, riandrews@android.com, devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org Date: Tue, 10 Jan 2017 14:12:49 -0800 In-Reply-To: References: Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.22.3-0ubuntu0.1 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 2017-01-10 at 23:40 +0200, Bogdan Purcareata wrote: > Fix following checkpatch warnings: > - Lines over 80 characters > - void function with return statement > - Unaligned comment mark > - Header function prototypes missing variable names Please read Documentation/SubmittingPatches (umm, make that Documentation/process/submitting-patches.rst) Make sure to send the patch to yourself only until you know you can apply it correctly and then send it to the mailing list. btw: This should probably be a series of 4 patches, each single patch doing one of the things listed above. And do please use checkpatch on your proposed patches.