From: Yiannis Yiakoumis <yiannisy@stanford.edu>
To: Dave Taht <dave.taht@gmail.com>
Cc: bismark-devel <bismark-devel@lists.bufferbloat.net>
Subject: Re: [Bismark-devel] openflow-1.0 requires ucitrigger
Date: Sun, 8 May 2011 11:13:34 -0700 [thread overview]
Message-ID: <BANLkTikk9xaJpvDHp63Y6Nau2X1M4UY8LA@mail.gmail.com> (raw)
In-Reply-To: <BANLkTimrSfe-J_zrm_5Wizu2OM1+it8Nyw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 664 bytes --]
Hi Dave,
Just get to looking at this. I got a warning when I built it, but haven't
tried the image in the latest backfire. I used it for triggers (i.e. restart
openflow when the network configuration has changed).
Not sure how others deal with it now. Does it break the image or only gives
you a warning?
Thanks,
Y.
On Sun, May 8, 2011 at 11:03 AM, Dave Taht <dave.taht@gmail.com> wrote:
> which is no longer in openwrt's mainline as per:
>
> https://dev.openwrt.org/changeset/26308
>
> Did you need it for a reason? Got a substitute?
>
> --
> Dave Täht
> SKYPE: davetaht
> US Tel: 1-239-829-5608
> http://the-edge.blogspot.com
>
[-- Attachment #2: Type: text/html, Size: 1192 bytes --]
prev parent reply other threads:[~2011-05-08 18:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-08 18:03 Dave Taht
2011-05-08 18:13 ` Yiannis Yiakoumis [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=BANLkTikk9xaJpvDHp63Y6Nau2X1M4UY8LA@mail.gmail.com \
--to=yiannisy@stanford.edu \
--cc=bismark-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
/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