From: Marek Lindner <mareklindner@neomailbox.ch>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] [PATCH-next 2/3] net: add possibility to pass information about upper device via notifier
Date: Sun, 13 Dec 2015 14:04:48 +0800 [thread overview]
Message-ID: <2652144.R6jIfFcVYF@voltaire> (raw)
In-Reply-To: <1449606915-6457-2-git-send-email-sven@narfation.org>
[-- Attachment #1: Type: text/plain, Size: 612 bytes --]
On Tuesday, December 08, 2015 21:35:14 Sven Eckelmann wrote:
> From: Jiri Pirko <jiri@mellanox.com>
>
> Sometimes the drivers and other code would find it handy to know some
> internal information about upper device being changed. So allow upper-code
> to pass information down to notifier listeners during linking.
>
> Signed-off-by: Jiri Pirko <jiri@mellanox.com>
> Signed-off-by: David S. Miller <davem@davemloft.net>
> ---
> compat-include/linux/netdevice.h | 2 +-
> net/batman-adv/hard-interface.c | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
Applied in revision 4291a5b.
Thanks,
Marek
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-12-13 6:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-08 20:35 [B.A.T.M.A.N.] [PATCH-next 1/3] net: propagate upper priv via netdev_master_upper_dev_link Sven Eckelmann
2015-12-08 20:35 ` [B.A.T.M.A.N.] [PATCH-next 2/3] net: add possibility to pass information about upper device via notifier Sven Eckelmann
2015-12-13 6:04 ` Marek Lindner [this message]
2015-12-08 20:35 ` [B.A.T.M.A.N.] [PATCH-next 3/3] batman-adv: Act on NETDEV_*_TYPE_CHANGE events Sven Eckelmann
2015-12-13 6:30 ` Marek Lindner
2015-12-13 6:01 ` [B.A.T.M.A.N.] [PATCH-next 1/3] net: propagate upper priv via netdev_master_upper_dev_link Marek Lindner
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=2652144.R6jIfFcVYF@voltaire \
--to=mareklindner@neomailbox.ch \
--cc=b.a.t.m.a.n@lists.open-mesh.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.