From: Thomas Behan <thomas.behan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: broonie-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Thomas Behan
<thomas.behan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: [PATCH 0/4] spi: omap-100k: Style Fixes
Date: Wed, 27 Nov 2013 23:27:20 -0500 [thread overview]
Message-ID: <1385612844-22482-1-git-send-email-thomas.behan@gmail.com> (raw)
First time contributer here submitting some style fixes.
I watched Greg Kroah-Hartman's youtube video about getting started with
submitting patches and thought I would give it a try. I fixed up some errors
and warnings that checkpatch.pl was giving. All patches are based off of
linux-next.
Any feedback is much appreciated.
Thomas Behan (4):
spi: omap-100k: Fixed spacing on while loops
spi: omap-100k: Fixed spacing on -= operators
spi: omap-100k: Fixed spacing on commas
spi: omap-100k: Fixed style of sizeof operators
drivers/spi/spi-omap-100k.c | 30 +++++++++++++++---------------
1 file changed, 15 insertions(+), 15 deletions(-)
--
1.8.1.2
--
To unsubscribe from this list: send the line "unsubscribe linux-spi" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2013-11-28 4:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-28 4:27 Thomas Behan [this message]
[not found] ` <1385612844-22482-1-git-send-email-thomas.behan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-11-28 4:27 ` [PATCH 1/4] spi: omap-100k: Fixed spacing on while loops Thomas Behan
2013-11-28 4:27 ` [PATCH 2/4] spi: omap-100k: Fixed spacing on -= operators Thomas Behan
2013-11-28 4:27 ` [PATCH 3/4] spi: omap-100k: Fixed spacing on commas Thomas Behan
2013-11-28 4:27 ` [PATCH 4/4] spi: omap-100k: Fixed style of sizeof operators Thomas Behan
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=1385612844-22482-1-git-send-email-thomas.behan@gmail.com \
--to=thomas.behan-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=broonie-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.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;
as well as URLs for NNTP newsgroup(s).