From: Sven Eckelmann <sven@narfation.org>
To: b.a.t.m.a.n@lists.open-mesh.org
Cc: Geliang Tang <geliangtang@163.com>,
Antonio Quartulli <a@unstable.cc>,
Marek Lindner <mareklindner@neomailbox.ch>
Subject: Re: [B.A.T.M.A.N.] [PATCH 1/3] batman-adv: use to_delayed_work
Date: Thu, 10 Mar 2016 20:41:53 +0100 [thread overview]
Message-ID: <5227202.7FVSH1Kd65@bentobox> (raw)
In-Reply-To: <2c0e66fe07809e4069df34cbeba51583ad943c7a.1451317025.git.geliangtang@163.com>
[-- Attachment #1: Type: text/plain, Size: 724 bytes --]
On Monday 28 December 2015 23:43:37 Geliang Tang wrote:
> Use to_delayed_work() instead of open-coding it.
>
> Signed-off-by: Geliang Tang <geliangtang@163.com>
> ---
> net/batman-adv/bridge_loop_avoidance.c | 2 +-
> net/batman-adv/distributed-arp-table.c | 2 +-
> net/batman-adv/network-coding.c | 2 +-
> net/batman-adv/originator.c | 2 +-
> net/batman-adv/send.c | 4 ++--
> net/batman-adv/translation-table.c | 2 +-
> 6 files changed, 7 insertions(+), 7 deletions(-)
Reviewed-by: Sven Eckelmann <sven@narfation.org>
@Marek, the compatibility code can be found at
https://git.open-mesh.org/batman-adv.git/patch/9122b42725c06a48dc222933722eb8b251335481
Kind regards,
Sven
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-03-10 19:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-28 15:43 [B.A.T.M.A.N.] [PATCH 1/3] batman-adv: use to_delayed_work Geliang Tang
2015-12-28 15:43 ` Geliang Tang
2015-12-28 15:43 ` [PATCH 2/3] staging: rtl8192u: " Geliang Tang
2015-12-28 15:43 ` [PATCH 3/3] staging: rtl8192e: " Geliang Tang
2016-03-10 19:41 ` Sven Eckelmann [this message]
2016-03-28 15:01 ` [B.A.T.M.A.N.] [PATCH 1/3] batman-adv: " Sven Eckelmann
2016-03-28 15:05 ` Marek Lindner
2016-03-28 15:05 ` Marek Lindner
2016-03-28 15:05 ` 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=5227202.7FVSH1Kd65@bentobox \
--to=sven@narfation.org \
--cc=a@unstable.cc \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=geliangtang@163.com \
--cc=mareklindner@neomailbox.ch \
/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.