From: Sven Eckelmann <sven@narfation.org>
To: b.a.t.m.a.n@lists.open-mesh.org
Cc: netdev@vger.kernel.org, lindner_marek@yahoo.de,
David Miller <davem@davemloft.net>,
stable@kernel.org
Subject: Re: [B.A.T.M.A.N.] pull request: batman-adv 2011-10-29
Date: Sun, 30 Oct 2011 10:05:04 +0100 [thread overview]
Message-ID: <1676645.jsUbFMd6Ud@sven-laptop.home.narfation.org> (raw)
In-Reply-To: <20111030.030745.1245988853394270780.davem@davemloft.net>
[-- Attachment #1: Type: text/plain, Size: 721 bytes --]
On Sunday 30 October 2011 03:07:45 David Miller wrote:
[...]
> Make a common header:
>
> struct tt_entry_common {
> u8 addr[ETH_ALEN];
> struct hlist_node hash_entry;
> };
>
> Then use that at the beginning of both structures:
>
> struct tt_local_entry {
> struct tt_entry_common common;
> unsigned long last_seen;
> ...
> };
>
> struct tt_global_entry {
> struct tt_entry_comomn common;
> struct orig_node *orig_node;
> ...
> };
>
> And &p->common is what gets passed into tt_response_fill_table().
Thanks for the pull. This is exactly the long term solution we want to submit
later to net-next. But we also wanted to keep the patch as small as possible
for stable@kernel.org
Thanks,
Sven
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2011-10-30 9:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-29 8:06 [B.A.T.M.A.N.] pull request: batman-adv 2011-10-29 Marek Lindner
2011-10-29 8:06 ` [B.A.T.M.A.N.] [PATCH 1/3] batman-adv: remove references for global tt entries Marek Lindner
2011-10-29 8:06 ` [B.A.T.M.A.N.] [PATCH 2/3] batman-adv: add sanity check when removing global tts Marek Lindner
2011-10-29 8:06 ` [B.A.T.M.A.N.] [PATCH 3/3] batman-adv: unify hash_entry field position in tt_local/global_entry Marek Lindner
2011-10-30 7:07 ` [B.A.T.M.A.N.] pull request: batman-adv 2011-10-29 David Miller
2011-10-30 9:05 ` Sven Eckelmann [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=1676645.jsUbFMd6Ud@sven-laptop.home.narfation.org \
--to=sven@narfation.org \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=davem@davemloft.net \
--cc=lindner_marek@yahoo.de \
--cc=netdev@vger.kernel.org \
--cc=stable@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).