From: David Miller <davem@davemloft.net>
To: himangi774@gmail.com
Cc: andrew.ruder@elecsyscorp.com, joe@perches.com,
Baohua.Song@csr.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, julia.lawall@lip6.fr
Subject: Re: [PATCH] dm9000: Remove typedef board_info_t
Date: Thu, 07 Aug 2014 16:05:32 -0700 (PDT) [thread overview]
Message-ID: <20140807.160532.655009033527959008.davem@davemloft.net> (raw)
In-Reply-To: <20140807191814.GA20351@himangi-Dell>
From: Himangi Saraogi <himangi774@gmail.com>
Date: Fri, 8 Aug 2014 00:48:14 +0530
> The Linux kernel coding style guidelines suggest not using typedefs
> for structure types. This patch gets rid of the typedef for board_info_t.
> Also, the name of the structs is changed to drop the _t, to make the
> name look less typedef-like.
>
> The following Coccinelle semantic patch detects the cases:
...
> Signed-off-by: Himangi Saraogi <himangi774@gmail.com>
> Acked-by: Julia Lawall <julia.lawall@lip6.fr>
Applied.
prev parent reply other threads:[~2014-08-07 23:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-07 19:18 [PATCH] dm9000: Remove typedef board_info_t Himangi Saraogi
2014-08-07 23:05 ` David Miller [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=20140807.160532.655009033527959008.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Baohua.Song@csr.com \
--cc=andrew.ruder@elecsyscorp.com \
--cc=himangi774@gmail.com \
--cc=joe@perches.com \
--cc=julia.lawall@lip6.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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).