mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chad Williamson <chad@dahc.us>
To: gregkh@linuxfoundation.org
Cc: puff65537@bansheeslibrary.com, viro@zeniv.linux.org.uk,
	tulinizer@gmail.com, devel@driverdev.osuosl.org,
	linux-kernel@vger.kernel.org, Chad Williamson <chad@dahc.us>
Subject: [PATCH v2 6/6] Staging: silicom: remove typedef for dev_desc_t
Date: Tue, 25 Jun 2013 18:59:24 -0500	[thread overview]
Message-ID: <1372204764-16203-3-git-send-email-chad@dahc.us> (raw)
In-Reply-To: <1372204764-16203-1-git-send-email-chad@dahc.us>

Remove the dev_desc_t typedef for the dev_desc struct in bpctl_mod.c,
resolving a checkpatch.pl warning. In fact, we can use an anonymous
struct, since it's only used in the single dev_desc array of device
descriptions, whose definition follows immediately.

Signed-off-by: Chad Williamson <chad@dahc.us>
---
v2: rebased onto latest master in linux-next
---
 drivers/staging/silicom/bpctl_mod.c | 6 ++----
 1 file changed, 2 insertions(+), 4 deletions(-)

diff --git a/drivers/staging/silicom/bpctl_mod.c b/drivers/staging/silicom/bpctl_mod.c
index 91c864c..32bc530 100644
--- a/drivers/staging/silicom/bpctl_mod.c
+++ b/drivers/staging/silicom/bpctl_mod.c
@@ -5981,11 +5981,9 @@ struct bpmod_info {
 
 };
 
-typedef struct _dev_desc {
+struct {
 	char *name;
-} dev_desc_t;
-
-dev_desc_t dev_desc[] = {
+} dev_desc[] = {
 	{"Silicom Bypass PXG2BPFI-SD series adapter"},
 	{"Silicom Bypass PXG2BPFIL-SD series adapter"},
 	{"Silicom Bypass PXG2BPFILX-SD series adapter"},
-- 
1.8.1.4


      parent reply	other threads:[~2013-06-25 23:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-25 23:59 [PATCH v2 3/6] Staging: silicom: remove the bpctl_dev_t typdef Chad Williamson
2013-06-25 23:59 ` [PATCH v2 5/6] Staging: silicom: remove the typedef for bpmod_info_t Chad Williamson
2013-06-25 23:59 ` Chad Williamson [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=1372204764-16203-3-git-send-email-chad@dahc.us \
    --to=chad@dahc.us \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=puff65537@bansheeslibrary.com \
    --cc=tulinizer@gmail.com \
    --cc=viro@zeniv.linux.org.uk \
    /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®