From: "Linus Lüssing" <linus.luessing@c0d3.blue>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] [PATCH] batman-adv: compat: Substitute compat code for netlink constification
Date: Tue, 18 Oct 2016 23:24:42 +0200 [thread overview]
Message-ID: <20161018212442.GG6366@otheros> (raw)
In-Reply-To: <20161018212125.32010-1-linus.luessing@c0d3.blue>
On Tue, Oct 18, 2016 at 11:21:25PM +0200, Linus Lüssing wrote:
> Substitutes the compat-patches approach for the netlink const changes to
> the prefered way of using compat-includes.
>
> Signed-off-by: Linus Lüssing <linus.luessing@c0d3.blue>
> ---
Actually, it isn't a substitution yet, the compat-patches thing is
still there.
Let me know what you think about this approach and if you like it
what I should do about the replacements.sh.
next prev parent reply other threads:[~2016-10-18 21:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-18 21:21 [B.A.T.M.A.N.] [PATCH] batman-adv: compat: Substitute compat code for netlink constification Linus Lüssing
2016-10-18 21:24 ` Linus Lüssing [this message]
2016-10-18 21:28 ` Sven Eckelmann
2016-10-18 23:22 ` Linus Lüssing
2016-10-19 6:31 ` Sven Eckelmann
2016-10-20 18:33 ` Linus Lüssing
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=20161018212442.GG6366@otheros \
--to=linus.luessing@c0d3.blue \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox