From: Pasakorn Tiwatthanont <pasakorn.tiwatthanont@nectec.or.th>
To: Marc.Obbad@smsc.com
Cc: bridge-bounces@lists.osdl.org, bridge@linux-foundation.org,
netdev@vger.kernel.org
Subject: Re: Re: rstp for 2.4 kernel: port state keeps changing
Date: Tue, 22 May 2007 08:05:35 +0700 [thread overview]
Message-ID: <465241DF.4090009@nectec.or.th> (raw)
In-Reply-To: <OF2B235CAE.4C560998-ON8525729F.005E1121-8525729F.005E4D58@smsc.com>
[-- Attachment #1.1: Type: text/plain, Size: 4161 bytes --]
Dear,
Could I use this patch with main stream, Linux x86 for PC ?
Best regards,
Pasakorn
Marc.Obbad@smsc.com wrote:
> For me, I ma building for Embedded platform.
> Go to Directory where the Makefile is and do this:
>
>
> make -C $LINUX_DIR SUBDIRS=WD modules
> LINUX_DIR should point to LINUX directory
>
> LINUX_DIR=ome/swdev/PPC/linux/ as example
>
> -Marc.
>
>
>
>
> Pasakorn Tiwatthanont
> <ptiwatthanont@gmail.com>
> Sent by: To
> bridge-bounces@lists.osdl.org Marc Obbad/SMSC@SMSC
> cc
> bridge-bounces@lists.osdl.org, bridge@linux-foundation.org,
> 03/15/2007 01:56 AM netdev@vger.kernel.org
> Subject
> Re: [Bridge] rstp for 2.4 kernel: port state keeps changing
> Please respond to
> ptiwatthanont@gmail.com
>
>
>
>
>
>
>
>
> Dear, I tried to patch rstp-2.4.zip but I can not compile it.
> If don't take your time too much, please explain me how to use
> this patch files.
>
> Thank you very much
> iPAS
>
> Marc.Obbad@smsc.com wrote:
> I have downloaded RSTP from this site:
>
>
> http://developer.osdl.org/shemminger/prototypes/rstp-2.4.zip
>
>
> -Marc
>
>
>
>
>
>
> Stephen Hemminger
>
> <shemminger@linux-foundation.org>
>
> Sent by:
> To
> bridge-bounces@lists.osdl.org Marc Obbad/SMSC@SMSC
>
> cc
> netdev@vger.kernel.org, bridge@linux-foundation.org
>
> 03/09/2007 01:55 PM
> Subject
> Re: [Bridge] rstp for 2.4 kernel: port state keeps
> changing
>
>
>
>
>
>
>
>
>
>
> On Fri, 9 Mar 2007 12:24:40 -0500
> Marc.Obbad@smsc.com wrote:
>
>
> Hi,
>
> I am using RSTP for 2.4 kernel.
>
>
> RSTP is not in the mainline kernel tree. Please post the patch or a where the
> source can be downloaded.
>
> --
> Stephen Hemminger <shemminger@linux-foundation.org>
> _______________________________________________
> Bridge mailing list
> Bridge@lists.osdl.org
> https://lists.osdl.org/mailman/listinfo/bridge
>
>
> _______________________________________________
> Bridge mailing list
> Bridge@lists.osdl.org
> https://lists.osdl.org/mailman/listinfo/bridge
>
> _______________________________________________
> Bridge mailing list
> Bridge@lists.osdl.org
> https://lists.osdl.org/mailman/listinfo/bridge
>
>
>
>
[-- Attachment #1.2: Type: text/html, Size: 6258 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
Bridge mailing list
Bridge@lists.linux-foundation.org
https://lists.linux-foundation.org/mailman/listinfo/bridge
prev parent reply other threads:[~2007-05-22 1:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-09 17:24 rstp for 2.4 kernel: port state keeps changing Marc.Obbad
2007-03-09 18:55 ` Stephen Hemminger
2007-03-09 20:20 ` [Bridge] " Marc.Obbad
2007-03-09 20:31 ` Stephen Hemminger
2007-03-15 5:56 ` Pasakorn Tiwatthanont
2007-03-15 17:10 ` [Bridge] " Marc.Obbad
2007-05-22 1:05 ` Pasakorn Tiwatthanont [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=465241DF.4090009@nectec.or.th \
--to=pasakorn.tiwatthanont@nectec.or.th \
--cc=Marc.Obbad@smsc.com \
--cc=bridge-bounces@lists.osdl.org \
--cc=bridge@linux-foundation.org \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).