Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932569AbcLLUur (ORCPT ); Mon, 12 Dec 2016 15:50:47 -0500 Received: from smtprelay0161.hostedemail.com ([216.40.44.161]:39291 "EHLO smtprelay.hostedemail.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1752995AbcLLUum (ORCPT ); Mon, 12 Dec 2016 15:50:42 -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:1437:1515:1516:1518:1534:1539:1593:1594:1711:1714:1730:1747:1777:1792:2198:2199:2393:2559:2562:2731:2828:3138:3139:3140:3141:3142:3350:3622:3865:3866:3867:3868:3870:3871:3873:3874:4321:5007:7903:8531:10004:10400:10848:11232:11658:11914:12663:12740:12760:13069:13311:13357:13439:14659:21080:21324:30012:30054:30070: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: owl90_7a3ac30215d12 X-Filterd-Recvd-Size: 1704 Message-ID: <1481575838.1764.39.camel@perches.com> Subject: Re: [PATCH 1/1] Fixed to codestyle From: Joe Perches To: Eric Sandeen , Ozgur Karatas , "david@fromorbit.com" Cc: "linux-xfs@vger.kernel.org" , linux-kernel Date: Mon, 12 Dec 2016 12:50:38 -0800 In-Reply-To: References: <987271481540010@web27o.yandex.ru> <66c68b88-e338-1d9a-b9dd-b8d858ebf349@sandeen.net> <1481566450.1764.23.camel@perches.com> <50420874-ffde-283f-f2e7-cb2ebbec1b84@sandeen.net> <737751481574841@web26j.yandex.ru> Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.22.1-0ubuntu2 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 Content-Length: 597 Lines: 16 On Mon, 2016-12-12 at 14:41 -0600, Eric Sandeen wrote: > On 12/12/16 2:34 PM, Ozgur Karatas wrote: [] > > Can you tell me the true code style? should use to (* uuid)? > > I'm learn to new and I'm newbies :) > > Well, rule #1 for newbies is "code style patches aren't > very useful, and usually are not welcomed by the project." I'd amend that to "newbies should only use checkpatch on files in drivers/staging/" and are generally welcome to do exactly that in order to learn how to submit patches appropriately before finding something actually useful to change in other areas of the kernel.