From: Joe Perches <joe@perches.com>
To: Eric Sandeen <sandeen@sandeen.net>,
Ozgur Karatas <okaratas@member.fsf.org>,
"david@fromorbit.com" <david@fromorbit.com>
Cc: "linux-xfs@vger.kernel.org" <linux-xfs@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] Fixed to codestyle
Date: Mon, 12 Dec 2016 12:50:38 -0800 [thread overview]
Message-ID: <1481575838.1764.39.camel@perches.com> (raw)
In-Reply-To: <cbf01379-fbcb-b42e-abc1-1b368b9d6633@sandeen.net>
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.
next prev parent reply other threads:[~2016-12-12 20:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-12 10:53 [PATCH 1/1] Fixed to codestyle Ozgur Karatas
2016-12-12 13:49 ` Eric Sandeen
2016-12-12 18:14 ` Joe Perches
2016-12-12 18:35 ` Eric Sandeen
2016-12-12 20:34 ` Ozgur Karatas
2016-12-12 20:41 ` Eric Sandeen
2016-12-12 20:49 ` Ozgur Karatas
2016-12-12 20:50 ` Joe Perches [this message]
2016-12-12 20:54 ` Ozgur Karatas
2016-12-12 21:17 ` Eric Sandeen
2016-12-12 20:31 ` Ozgur Karatas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1481575838.1764.39.camel@perches.com \
--to=joe@perches.com \
--cc=david@fromorbit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=okaratas@member.fsf.org \
--cc=sandeen@sandeen.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox