From: David Miller <davem@davemloft.net>
To: sw@simonwunderlich.de
Cc: netdev@vger.kernel.org, b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [PATCH 0/3] pull request for net-next: batman-adv 2017-10-23
Date: Tue, 24 Oct 2017 01:15:32 +0100 (WEST) [thread overview]
Message-ID: <20171024.011532.1257110831650284794.davem@davemloft.net> (raw)
In-Reply-To: <20171023153704.32120-1-sw@simonwunderlich.de>
From: Simon Wunderlich <sw@simonwunderlich.de>
Date: Mon, 23 Oct 2017 17:37:01 +0200
> here is another small documentation/cleanup pull request of batman-adv to go
> into net-next.
>
> Please pull or let me know of any problem!
Pulled, thanks Simon.
prev parent reply other threads:[~2017-10-24 0:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-23 15:37 [PATCH 0/3] pull request for net-next: batman-adv 2017-10-23 Simon Wunderlich
2017-10-23 15:37 ` [PATCH 1/3] batman-adv: Add missing kerneldoc for extack Simon Wunderlich
2017-10-23 15:37 ` [PATCH 2/3] batman-adv: Avoid spurious warnings from bat_v neigh_cmp implementation Simon Wunderlich
2017-10-23 15:37 ` [PATCH 3/3] batman-adv: use inline kernel-doc for uapi constants Simon Wunderlich
2017-10-24 0:15 ` David Miller [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=20171024.011532.1257110831650284794.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=netdev@vger.kernel.org \
--cc=sw@simonwunderlich.de \
/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