From: Walt Feasel <waltfeasel@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Samuel Thibault <samuel.thibault@ens-lyon.org>,
devel@driverdev.osuosl.org, kirk@reisers.ca,
linux-kernel@vger.kernel.org, w.d.hubbs@gmail.com,
chris@the-brannons.com, speakup@linux-speakup.org
Subject: Re: [PATCH v2 0/6] staging: speakup: speakup_soft.c checkpatch modifications
Date: Wed, 23 Nov 2016 11:24:12 -0500 [thread overview]
Message-ID: <20161123162412.GA5814@localhost> (raw)
In-Reply-To: <20161123155632.GC8719@kroah.com>
On Wed, Nov 23, 2016 at 04:56:32PM +0100, Greg KH wrote:
> On Wed, Nov 23, 2016 at 05:52:25AM -0500, Fleetwood Farm wrote:
> > On Nov 23, 2016 4:08 AM, "Greg KH" <gregkh@linuxfoundation.org> wrote:
> > >
> > > On Mon, Nov 21, 2016 at 10:19:19AM -0500, Walt Feasel wrote:
> > > > Make Linux kernel style modifications for speak_soft.c to include:
> > > >
> > > > Space around operator
> > > > Logical continuation
> > > > Multiple blank lines
> > > > Blank line after {
> > > > comment modifications
> > > > Align parenthesis
> > >
> > > Ok, now that you have a bunch of cleanup patches accepted, why not work
> > > on some "real" code changes? There's no need to fix all of the coding
> > > style issues in drivers/staging/ at once, leave some for other people to
> > > learn on :)
> > >
> > > thanks,
> > >
> > > greg k-h
> >
> > Well, I have around 40 more patches already prepared waiting for my limit to
> > clear (which just did) and about 12 more files left to checkpatch in speakup.
> > I am currently waiting on the newbies administer to clear my sent emails asking
> > advice on if some of my tougher challenges (octals and CamelCase) are done
> > correctly.
>
> "newbies administrator"?
>
Yes have a email saying my email "is being held until the list moderator can
review it for approval"
> > I am also currently waiting on the u-boot mailing list administer to do the
> > same on some of my patches.
> > I also am doing some online 'c' courses to increase (get) my skills set.
> > What type of "real" code changes did you have in mind with my limited skill
> > set?
>
> I'd strongly suggest working on some userspace programs to get a
> less-limited skill set :) Then find some area of the kernel you are
> interested in, and help out there. Speakup really can use the help, and
> the community of users of their devices is very good, so any real work
> you can do there would always be greatly appreciated.
>
That is good advice about limiting skill set. I am trying to do that with
converting some of my simple bash scripts to 'c'. While it may not be very
usefull it is a start and won't mess up anything important for others.
I do think I am learning from these simple checkpatch patches as I try to
research the items I do not know. Plus I think it instills a good style
format. I have written programs in the past for my jobs but never in 'c'
and this driver stuff is over my head.
I do not wish to burden/annoy anyone with these simple fixes, I thought
it may help with getting them out of staging. I won't take offense if it is
preferred I did not do them.
I am not very quick on subtleties so if anyone wishes for me to move on I will.
> best of luck,
>
> greg k-h
Walt
prev parent reply other threads:[~2016-11-23 16:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-21 15:19 [PATCH v2 0/6] staging: speakup: speakup_soft.c checkpatch modifications Walt Feasel
2016-11-21 15:19 ` [PATCH v2 1/6] staging: speakup: speakup_soft.c Space around operator Walt Feasel
2016-11-21 15:19 ` [PATCH v2 2/6] staging: speakup: speakup_soft.c Logical continuation Walt Feasel
2016-11-21 15:19 ` [PATCH v2 3/6] staging: speakup: speakup_soft.c Multiple blank lines Walt Feasel
2016-11-21 15:19 ` [PATCH v2 4/6] staging: speakup: speakup_soft.c Blank line after { Walt Feasel
2016-11-21 15:19 ` [PATCH v2 5/6] staging: speakup: speakup_soft.c comment modifications Walt Feasel
2016-11-21 15:19 ` [PATCH v2 6/6] staging: speakup: speakup_soft.c Align parenthesis Walt Feasel
2016-11-23 9:09 ` [PATCH v2 0/6] staging: speakup: speakup_soft.c checkpatch modifications Greg KH
[not found] ` <CACfmeC=-NKgX4QKF0Btj6OTvOxSjZgcoQ4BrNLq5NEpPSZ+1Ww@mail.gmail.com>
2016-11-23 15:56 ` Greg KH
2016-11-23 16:24 ` Walt Feasel [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=20161123162412.GA5814@localhost \
--to=waltfeasel@gmail.com \
--cc=chris@the-brannons.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=kirk@reisers.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=samuel.thibault@ens-lyon.org \
--cc=speakup@linux-speakup.org \
--cc=w.d.hubbs@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.