From: "Dmitry Kravkov" <dmitry@broadcom.com>
To: "David Miller" <davem@davemloft.net>
Cc: "bruce.w.allan@intel.com" <bruce.w.allan@intel.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"difrost.kernel@gmail.com" <difrost.kernel@gmail.com>
Subject: Re: [PATCH] sctp compilation failed due to lack of sctp_local_addr_free
Date: Thu, 26 May 2011 22:07:01 +0300 [thread overview]
Message-ID: <1306436821.28745.4.camel@lb-tlvb-dmitry> (raw)
In-Reply-To: <20110526.144416.252997714470172705.davem@davemloft.net>
On Thu, 2011-05-26 at 11:44 -0700, David Miller wrote:
> From: "Allan, Bruce W" <bruce.w.allan@intel.com>
> Date: Thu, 26 May 2011 11:40:34 -0700
>
> >>-----Original Message-----
> >>From: netdev-owner@vger.kernel.org [mailto:netdev-owner@vger.kernel.org] On
> >>Behalf Of David Miller
> >>Sent: Thursday, May 26, 2011 10:39 AM
> >>To: dmitry@broadcom.com
> >>Cc: netdev@vger.kernel.org; difrost.kernel@gmail.com
> >>Subject: Re: [PATCH] sctp compilation failed due to lack of sctp_local_addr_free
> >>
> >>
> >>This has been fixed for days.
> >
> > Fixed in net-2.6, yes, but not yet in net-next-2.6
>
> net-next-2.6 is not active and is just a dummy tree for Stephen
> Rothwell to pull into -next
>
> You should never be referencing or using net-next-2.6 during the
> merge window when new features changes are not being accepted.
> Only net-2.6 is active during this time.
>
Hmm, so how similar will be net-2.6 and net-next-2.6 when re-opened?
You apply a lot of fixes during this time...
And yes, i've hit the compilation error in net-next since i'm using it
as basis for future features submit
next prev parent reply other threads:[~2011-05-26 19:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-26 16:28 [PATCH] sctp compilation failed due to lack of sctp_local_addr_free Dmitry Kravkov
2011-05-26 16:41 ` Dmitry Kravkov
2011-05-26 17:39 ` David Miller
2011-05-26 18:40 ` Allan, Bruce W
2011-05-26 18:44 ` David Miller
2011-05-26 19:07 ` Dmitry Kravkov [this message]
2011-05-26 19:58 ` David Miller
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=1306436821.28745.4.camel@lb-tlvb-dmitry \
--to=dmitry@broadcom.com \
--cc=bruce.w.allan@intel.com \
--cc=davem@davemloft.net \
--cc=difrost.kernel@gmail.com \
--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