From: Leandro Lucarella <luca@llucax.com.ar>
To: Jon Maloy <jon.maloy@ericsson.com>
Cc: Neil Horman <nhorman@tuxdriver.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"tipc-discussion@lists.sourceforge.net"
<tipc-discussion@lists.sourceforge.net>,
David Miller <davem@davemloft.net>
Subject: Re: Linux 2.6.35/TIPC 2.0 ABI breaking changes
Date: Wed, 20 Oct 2010 16:23:50 -0300 [thread overview]
Message-ID: <20101020192350.GR8781@llucax.com.ar> (raw)
In-Reply-To: <20101020182851.GP8781@llucax.com.ar>
Leandro Lucarella, el 20 de octubre a las 15:28 me escribiste:
> Jon Maloy, el 20 de octubre a las 14:10 me escribiste:
> > <...>
> > > >
> > > > Remember, permitting both is a superset of the current one
> > > (NBO only)
> > > > so it is fully backwards compatible. We break absolutly nothing by
> > > > permitting this.
> > > >
> > > Thats effectively reverting both our patches though, isn't it
> > > (not that I'm disagreeing with it, just looking for
> > > clarification). If we revert my patch and reintroduce the
> > > htohl mechanism which tracks endianess, we might as well
> > > revert the TIPC_SUB_SERVICE flag as well, yeah?
> >
> > Absolutely. I think it was a mistake to change that value.
> > But I don't think we need to reintroduce the htohl(). That
> > was just one way of doing it. If I understood your suggestion
> > from yesterday correctly you converted the whole message within
> > one if()clause, without any htohl(). I have have no problem with
> > that approach.
>
> There is a difference between both solutions, the htohl() version
> tracked the need for swap as a struct subscription member (which was
> used when sending back events). Neils patch doesn't do that tracking.
> I don't really know the implications of this, but maybe it would be
> a wise idea to stay in the safe side and revert both patches for now.
BTW, I tried 2.6.37 reverting both offending patches and everything
seems to work well.
--
Leandro Lucarella (AKA luca) http://llucax.com.ar/
----------------------------------------------------------------------
GPG Key: 5F5A8D05 (F8CD F9A7 BF00 5431 4145 104C 949E BFB6 5F5A 8D05)
----------------------------------------------------------------------
Vivimos en una época muy contemporánea, Don Inodoro...
-- Mendieta
next prev parent reply other threads:[~2010-10-20 19:24 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100927163823.GD2834@integratech.com.ar>
[not found] ` <29C1DC0826876849BDD9F1C67ABA2943090B67EC@ala-mail09.corp.ad.wrs.com>
[not found] ` <20100929153805.GG2834@integratech.com.ar>
[not found] ` <29C1DC0826876849BDD9F1C67ABA29430914AC18@ala-mail09.corp.ad.wrs.com>
[not found] ` <20101001150034.GS8781@llucax.com.ar>
[not found] ` <0434463FDA60A94FA978ACA44617682DEE843EDD79@EUSAACMS0702.eamcs.ericsson.se>
[not found] ` <20101001162346.GV8781@llucax.com.ar>
[not found] ` <4CA69F18.7000005@amln.net>
[not found] ` <0434463FDA60A94FA978ACA44617682DEE8446A03B@EUSAACMS0702.eamcs.ericsson.se>
2010-10-18 15:04 ` Linux 2.6.35/TIPC 2.0 ABI breaking changes [was: TIPC 2.0 and TIPC_SUB_SERVICE] Leandro Lucarella
2010-10-18 18:46 ` Leandro Lucarella
2010-10-18 20:42 ` Paul Gortmaker
2010-10-18 22:17 ` Linux 2.6.35/TIPC 2.0 ABI breaking changes David Miller
2010-10-18 23:11 ` Paul Gortmaker
2010-10-18 23:38 ` Leandro Lucarella
2010-10-18 23:45 ` Neil Horman
2010-10-19 2:16 ` Leandro Lucarella
2010-10-19 8:16 ` David Miller
2010-10-19 11:04 ` Neil Horman
2010-10-19 11:06 ` David Miller
2010-10-19 13:19 ` Leandro Lucarella
2010-10-19 13:28 ` Neil Horman
2010-10-19 20:18 ` Neil Horman
2010-10-19 20:43 ` Leandro Lucarella
2010-10-19 22:03 ` Leandro Lucarella
2010-10-20 17:20 ` Leandro Lucarella
2010-10-20 17:57 ` Jon Maloy
2010-10-20 18:04 ` Neil Horman
2010-10-20 18:10 ` Jon Maloy
2010-10-20 18:28 ` Leandro Lucarella
2010-10-20 19:23 ` Leandro Lucarella [this message]
2010-10-20 22:59 ` Leandro Lucarella
2010-10-20 18:24 ` Leandro Lucarella
2010-10-20 18:37 ` Jon Maloy
2010-10-20 18:44 ` Leandro Lucarella
2010-10-20 17:57 ` Neil Horman
2010-10-18 23:58 ` Alan Cox
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=20101020192350.GR8781@llucax.com.ar \
--to=luca@llucax.com.ar \
--cc=davem@davemloft.net \
--cc=jon.maloy@ericsson.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=tipc-discussion@lists.sourceforge.net \
/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