From: Cyril Roelandt <tipecaml@gmail.com>
To: balbi@ti.com
Cc: dahlmann.thomas@arcor.de, gregkh@linuxfoundation.org,
linux-geode@lists.infradead.org, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/6] drivers/usb/gadget/amd5536udc.c: code cleanup.
Date: Sat, 25 Feb 2012 02:14:56 +0100 [thread overview]
Message-ID: <1330132502-17057-1-git-send-email-tipecaml@gmail.com> (raw)
Hello,
This series of patches cleans up drivers/usb/gadget/amd5536udc.c, fixing the 33
warnings returned by scripts/checkpatch.pl.
Patch 1/6 removes unneeded braces around one-line statements in if statements
and loops.
Patch 2/6 removes unneeded whitespaces before '\n' in various strings.
Patch 3/6 fixes the indentation of a block.
Patch 4/6 uses the DEFINE_PCI_DEVICE_TABLE macro rather than "const struct
pci_device_id".
Patch 5/6 fixes the type of the ep_string variable.
Patch 6/6 removes a CVS marker that is no longer relevant.
These patches should be trivial and unlikely to break anything.
Regards,
Cyril Roelandt.
next reply other threads:[~2012-02-25 1:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-25 1:14 Cyril Roelandt [this message]
2012-02-25 1:14 ` [PATCH 1/6] amd5536udc: Fix brace coding style issues Cyril Roelandt
2012-02-27 14:35 ` Felipe Balbi
2012-02-25 1:14 ` [PATCH 2/6] amd5536udc: Fix " Cyril Roelandt
2012-02-27 14:35 ` Felipe Balbi
2012-02-25 1:14 ` [PATCH 3/6] amd5536udc: Fix indentation Cyril Roelandt
2012-02-27 14:36 ` Felipe Balbi
2012-02-25 1:15 ` [PATCH 4/6] amd5536udc: use the DEFINE_PCI_DEVICE_TABLE macro Cyril Roelandt
2012-02-27 14:37 ` Felipe Balbi
2012-02-25 1:15 ` [PATCH 5/6] amd5536udc: fix type of ep_string Cyril Roelandt
2012-02-25 15:25 ` Sergei Shtylyov
2012-02-26 14:57 ` Cyril Roelandt
2012-02-26 15:00 ` [PATCH 5/6] amd5536udc: Fix the " Cyril Roelandt
2012-02-27 10:51 ` Sergei Shtylyov
2012-02-27 14:37 ` Felipe Balbi
2012-02-25 1:15 ` [PATCH 6/6] amd5536udc: Remove old CVS markers Cyril Roelandt
2012-02-27 14:37 ` Felipe Balbi
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=1330132502-17057-1-git-send-email-tipecaml@gmail.com \
--to=tipecaml@gmail.com \
--cc=balbi@ti.com \
--cc=dahlmann.thomas@arcor.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-geode@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@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;
as well as URLs for NNTP newsgroup(s).