public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Jo-Philipp Wich <jow@openwrt.org>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] [RFC] batman-adv boot setup scheme on OpenWRT
Date: Mon, 10 Dec 2012 01:13:43 +0100	[thread overview]
Message-ID: <50C52937.1060308@openwrt.org> (raw)
In-Reply-To: <CAHD-aqJ9vCqHBSa53zDvWvAr1hJnqqjr_Jxj0YEtV4BCFkuu+g@mail.gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi.

> I'd also add 'netifd' as a dependency in the makefile

You could but I do not think it is necessary. kmod-batman-adv works
well without netifd, the onyl thing that would break is the support
scripts.

Also netifd is pretty much guranteed to be present in current release
so you can rely on it, but people who do not have it installed for
wahtever reason might still want to use the batman kernel module, so
I'd opt for not making it a hard dependency.

Cheers,
Jow

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with undefined - http://www.enigmail.net/

iEYEARECAAYFAlDFKTcACgkQdputYINPTPMRrwCcDBW58q62Jm7lJKIywuLX7B15
59MAn3G4pLJUn7ACt5iTxBpOx8qjS7E4
=btbj
-----END PGP SIGNATURE-----

  reply	other threads:[~2012-12-10  0:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-23 12:52 [B.A.T.M.A.N.] [RFC] batman-adv boot setup scheme on OpenWRT Gui Iribarren
2012-11-23 14:00 ` Gui Iribarren
2012-11-26 10:40   ` Marek Lindner
2012-11-26 10:45     ` Sven Eckelmann
2012-12-02 13:19       ` Gui Iribarren
2012-12-09 11:10         ` Moritz Warning
2012-12-09 14:31           ` Marek Lindner
2012-12-09 16:03             ` Moritz Warning
2012-12-09 16:20               ` Antonio Quartulli
2012-12-09 16:35               ` Gui Iribarren
2012-12-10  0:13                 ` Jo-Philipp Wich [this message]
2012-12-09 16:50               ` Moritz Warning
2012-11-25 17:12 ` 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=50C52937.1060308@openwrt.org \
    --to=jow@openwrt.org \
    --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