[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20140121.232001.48714613002250339.davem@davemloft.net>
Date: Tue, 21 Jan 2014 23:20:01 -0800 (PST)
From: David Miller <davem@...emloft.net>
To: hannes@...essinduktion.org
Cc: netdev@...r.kernel.org
Subject: Re: [PATCH net-next v5 0/0] reciprocal_divide update
From: Hannes Frederic Sowa <hannes@...essinduktion.org>
Date: Wed, 22 Jan 2014 02:29:38 +0100
> This patch is on top of aee636c4809fa5 ("bpf: do not use reciprocal
> divide") from Eric that sits in net tree. It will not create a merge
> conflict, but it depends on this one, so we suggest, if possible, to
> merge net into net-next.
>
> We are proposing this change with only small modifications from the
> v2 version, namely updating the name of trim to reciprocal_scale
> (as commented on by Ben Hutchings and Eric Dumazet, thanks!).
>
> We thought about introducing the reciprocal_divide algorithm in
> parallel to the one already used by the kernel but faced organizational
> issues, leading us to the conclusion that it is best to just replace
> the old one: We could not come up with names for the different
> implementations and also with a way to describe the differences to
> guide developers which one to choose in which situation. This is
> because we cannot specify the correct semantics for the version
> which is currently used by the kernel. Altough it seems to not be
> causing problems in the kernel, we cannot surely say so in the
> case of flex_array for the future. Current usage seems ok, but
> future users could run into problems.
Series applied, thanks.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists