netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ursula Braun <braunu@de.ibm.com>
To: davem@davemloft.net, netdev@vger.kernel.org, linux-s390@vger.kernel.org
Subject: [patch 1/1] 8021q: transfer dev_id from real device
Date: Mon, 08 Oct 2007 17:05:05 +0200	[thread overview]
Message-ID: <20071008150820.837583000@linux.vnet.ibm.com> (raw)
In-Reply-To: 20071008150504.855164000@linux.vnet.ibm.com

[-- Attachment #1: 8021q-vlan.diff --]
[-- Type: text/plain, Size: 1000 bytes --]

From: Ursula Braun <braunu@de.ibm.com>

A net_device struct provides field dev_id. It is used for
unique ipv6 generation in case of shared network cards
(as for the OSA network cards of IBM System z). 
If VLAN devices are built on top of such shared network cards,
this dev_id information needs to be transferred to the VLAN device.

Signed-off-by: Ursula Braun <braunu@de.ibm.com>
---
 net/8021q/vlan.c |    3 +++
 1 file changed, 3 insertions(+)

Index: net-2.6.24-uschi/net/8021q/vlan.c
===================================================================
--- net-2.6.24-uschi.orig/net/8021q/vlan.c
+++ net-2.6.24-uschi/net/8021q/vlan.c
@@ -331,6 +331,9 @@ static int vlan_dev_init(struct net_devi
 					  (1<<__LINK_STATE_DORMANT))) |
 		      (1<<__LINK_STATE_PRESENT);
 
+	/* ipv6 shared card related stuff */
+	dev->dev_id = real_dev->dev_id;
+
 	if (is_zero_ether_addr(dev->dev_addr))
 		memcpy(dev->dev_addr, real_dev->dev_addr, dev->addr_len);
 	if (is_zero_ether_addr(dev->broadcast))

-- 

  reply	other threads:[~2007-10-08 15:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-08 15:05 [patch 0/1] [8021q] qeth-related patch for net-2.6.24 Ursula Braun
2007-10-08 15:05 ` Ursula Braun [this message]
2007-10-09  3:29   ` [patch 1/1] 8021q: transfer dev_id from real device David Miller

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=20071008150820.837583000@linux.vnet.ibm.com \
    --to=braunu@de.ibm.com \
    --cc=davem@davemloft.net \
    --cc=linux-s390@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).