From: David Miller <davem@davemloft.net>
To: sven@narfation.org
Cc: ordex@autistici.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, paulus@samba.org,
linux-ppp@vger.kernel.org
Subject: Re: net: add seq_before/seq_after functions
Date: Thu, 19 May 2011 05:08:24 -0400 (EDT) [thread overview]
Message-ID: <20110519.050824.838971689287732822.davem@davemloft.net> (raw)
In-Reply-To: <201105191054.34912.sven@narfation.org>
From: Sven Eckelmann <sven@narfation.org>
Date: Thu, 19 May 2011 10:54:32 +0200
> On Wednesday 18 May 2011 14:38:39 Antonio Quartulli wrote:
>> Introduce two operations to handle comparison between packet sequence
>> numbers taking into account overflow/wraparound. Batman-adv uses
>> these functions already to check for successor packet even in case of
>> overflow.
>
> Thanks for your efforts to bring that to the kernel. But when you prepare a
> patch then you have to add a signoff. And also David S. Miller is the
> maintainer for this header - it would be interesting to ask him first when we
> want to change that file.
Well it makes no sense to add these interfaces until we see an
upstream submission of code which will actually use it.
Also I'm skeptical that such generic sounding interfaces make
sense when it appears to me that these are protocol specific
sequence number tests so probably belong in whatever protocol
is upcoming which will use these interfaces.
Again, this is why we want to see the code that's going to use
these new routines before we can seriously consider adding them
at all.
next prev parent reply other threads:[~2011-05-19 9:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1305722319-8315-1-git-send-email-ordex@autistici.org>
2011-05-19 8:54 ` net: add seq_before/seq_after functions Sven Eckelmann
2011-05-19 9:08 ` David Miller [this message]
2011-05-19 9:21 ` Sven Eckelmann
2011-05-19 18:52 ` 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=20110519.050824.838971689287732822.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-ppp@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=ordex@autistici.org \
--cc=paulus@samba.org \
--cc=sven@narfation.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).