From: re.emese@gmail.com
To: linux-kernel@vger.kernel.org
Cc: Emese Revfy <re.emese@gmail.com>,
netdev@vger.kernel.org, davem@davemloft.net,
shemminger@vyatta.com
Subject: [PATCH 1/1] Constify struct neigh_ops for 2.6.32-git-053fe57ac v2
Date: Mon, 14 Dec 2009 01:00:15 +0100 [thread overview]
Message-ID: <b6a0951139abdcfa2ab65e4da0423e2d0e0ae13d.1260663002.git.re.emese@gmail.com> (raw)
In-Reply-To: <cover.1260663002.git.re.emese@gmail.com>
From: Emese Revfy <re.emese@gmail.com>
Signed-off-by: Emese Revfy <re.emese@gmail.com>
---
include/net/neighbour.h | 12 ++++++------
1 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/include/net/neighbour.h b/include/net/neighbour.h
index 0302f31..ac37ed6 100644
--- a/include/net/neighbour.h
+++ b/include/net/neighbour.h
@@ -121,12 +121,12 @@ struct neighbour {
struct neigh_ops {
int family;
- void (*solicit)(struct neighbour *, struct sk_buff*);
- void (*error_report)(struct neighbour *, struct sk_buff*);
- int (*output)(struct sk_buff*);
- int (*connected_output)(struct sk_buff*);
- int (*hh_output)(struct sk_buff*);
- int (*queue_xmit)(struct sk_buff*);
+ void (* const solicit)(struct neighbour *, struct sk_buff*);
+ void (* const error_report)(struct neighbour *, struct sk_buff*);
+ int (* const output)(struct sk_buff*);
+ int (* const connected_output)(struct sk_buff*);
+ int (* const hh_output)(struct sk_buff*);
+ int (* const queue_xmit)(struct sk_buff*);
};
struct pneigh_entry {
--
1.6.5.3
next prev parent reply other threads:[~2009-12-13 23:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-14 0:00 [PATCH 0/1] " re.emese
2009-12-14 0:00 ` re.emese [this message]
2009-12-14 0:00 ` [PATCH 1/2] Constify struct nlmsvc_binding " re.emese
2009-12-14 0:00 ` [PATCH 2/2] " re.emese
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=b6a0951139abdcfa2ab65e4da0423e2d0e0ae13d.1260663002.git.re.emese@gmail.com \
--to=re.emese@gmail.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.com \
/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®