From: Maksymilian Piechota <maksymilianpiechota@gmail.com>
To: Joe Perches <joe@perches.com>
Cc: Maksymilian Piechota <maksymilianpiechota@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org, devel@driverdev.osuosl.org
Subject: Re: [PATCH 001] staging: wlan-ng: Add tabstop preceding the statement
Date: Tue, 31 Jan 2017 07:20:27 -0500 [thread overview]
Message-ID: <20170131122026.GA12809@maks-debian.localdomain> (raw)
In-Reply-To: <1485864424.20550.28.camel@perches.com>
On Tue, Jan 31, 2017 at 04:07:04AM -0800, Joe Perches wrote:
> On Tue, 2017-01-31 at 06:33 -0500, Maksymilian Piechota wrote:
> > On Tue, Jan 31, 2017 at 03:18:45AM -0800, Joe Perches wrote:
> > > checkpatch is just a guide, it's brainless.
> > >
> > > The reason these lines are > 80 columns is
> > > overly long/verbose identifiers.
> > >
> > > If you really want to clean up the code here,
> > > the P90211ENUM_ prefixes are a bit misleading
> > > as they all are #define and not enums at all.
> > >
> > But would you like me to remove this prefixes for all of the enums from
> > p80211types.h? Are you sure it won't cause any symbol conflicts?
>
> No, I don't want that, I'd prefer you think about it.
>
> Also, a useful effort would be to (from the README)
>
> TODO:
> []
> - move to use the in-kernel wireless stack
>
> where most all of the P80211 code would be removed.
>
> Anyway, sure, use checkpatch as a tool to help when
> learning the process of how to submit patches properly.
> Then move on to more thoroughly understand a block of
> code in the kernel that can be improved with cleaner
> style and logic and bug fixes you could submit.
>
> That's be much more appreciated than random 80 column
> fixups and strict checkpatch compliance done without
> a thorough understanding of the code.
>
> In any case, welcome, hope you stick around.
It's clear that there are a lot more usefull patches than 80 column fix,
but as you said, I learn how to submit patches and there is is
constraint to submit only one checkpatch warning fix.
Many thanks for advice how to proceed. I will take a look at it when I
finish Greg's tutorial.
Thank you, I hope to have a significant contribution to Linux Community.
prev parent reply other threads:[~2017-01-31 12:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-30 16:31 Maksymilian Piechota
2017-01-30 16:44 ` Greg Kroah-Hartman
2017-01-31 4:00 ` Joe Perches
2017-01-31 11:04 ` Maksymilian Piechota
2017-01-31 11:18 ` Joe Perches
2017-01-31 11:33 ` Maksymilian Piechota
2017-01-31 12:07 ` Joe Perches
2017-01-31 12:20 ` Maksymilian Piechota [this message]
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=20170131122026.GA12809@maks-debian.localdomain \
--to=maksymilianpiechota@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®