linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Morgan Read <mstuff@read.org.nz>, linux-wireless@vger.kernel.org
Cc: sgruszka@redhat.com
Subject: Re: iwlegacy and bridging iwl3945...? (sort of)
Date: Wed, 07 Oct 2015 09:34:28 +0200	[thread overview]
Message-ID: <1444203268.28872.0.camel@sipsolutions.net> (raw)
In-Reply-To: <5614C6CA.7060701@read.org.nz> (sfid-20151007_091629_834143_05F2E30E)


> However, before I go down that route are any of the options for bonding, 
> which again seem as if they would work, actually a reality?
> 

I don't really know anything about bonding, sorry.

johannes

      reply	other threads:[~2015-10-07  7:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-04 19:38 iwlegacy and bridging iwl3945...? (sort of) Morgan Read
2015-10-05  6:54 ` Johannes Berg
2015-10-07  7:16   ` Morgan Read
2015-10-07  7:34     ` Johannes Berg [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=1444203268.28872.0.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mstuff@read.org.nz \
    --cc=sgruszka@redhat.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;
as well as URLs for NNTP newsgroup(s).