From: "David S. Miller" <davem@davemloft.net>
To: jengelh@linux01.gwdg.de
Cc: lcapitulino@mandriva.com.br, akpm@osdl.org,
robert.olsson@its.uu.se, netdev@oss.sgi.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] pktgen: Adds missing __init.
Date: Fri, 06 Jan 2006 13:17:34 -0800 (PST) [thread overview]
Message-ID: <20060106.131734.78923714.davem@davemloft.net> (raw)
In-Reply-To: <Pine.LNX.4.61.0601062003000.28630@yvahk01.tjqt.qr>
From: Jan Engelhardt <jengelh@linux01.gwdg.de>
Date: Fri, 6 Jan 2006 20:04:13 +0100 (MET)
> >diff --git a/net/core/pktgen.c b/net/core/pktgen.c
> >index 06cad2d..5eeae0d 100644
> >--- a/net/core/pktgen.c
> >+++ b/net/core/pktgen.c
> >@@ -2883,7 +2883,7 @@ static int pktgen_add_device(struct pktg
> > return add_dev_to_thread(t, pkt_dev);
> > }
> >
> >-static struct pktgen_thread *pktgen_find_thread(const char* name)
> >+static struct pktgen_thread __init *pktgen_find_thread(const char* name)
>
> I do not know what CodingStyle says about it (it is correct GCC code),
> what do the others think of the more often placement of __init as in
> __init static struct pktgen_thread *pktgen_find_thread(const char *name)
> or
> static __init struct pktgen_thread *pktgen_find_thread(const char *name)
> [depending on what people like]
It should be right before the function name, "struct foo *" is a full
return type specification, so any other attributes should appear either
before or after that.
I'll fix this up when I apply Luis's patch.
prev parent reply other threads:[~2006-01-06 21:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-06 15:11 Luiz Fernando Capitulino
2006-01-06 19:04 ` Jan Engelhardt
2006-01-06 21:17 ` David S. 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=20060106.131734.78923714.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akpm@osdl.org \
--cc=jengelh@linux01.gwdg.de \
--cc=lcapitulino@mandriva.com.br \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=robert.olsson@its.uu.se \
/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®