DPDK patches and discussions
 help / color / mirror / Atom feed
From: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
To: Stefan Kanthak <stefan.kanthak@nexgo.de>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "hannes@stressinduktion.org" <hannes@stressinduktion.org>
Subject: Re: [dpdk-dev] [BUG] Maintainer for	lib/librte_eal/common/rte_reciprocal.c?
Date: Thu, 28 Mar 2019 04:35:09 +0000	[thread overview]
Message-ID: <CY4PR1801MB1863A73B62C8E3F8475A7D0BDE590@CY4PR1801MB1863.namprd18.prod.outlook.com> (raw)
In-Reply-To: <0D8EBD99DC5246E394511624D3B09B10@W340>

Hi Stefan,

Thanks for the heads up, I am planning to use a modified version of
https://github.com/hcs0/Hackers-Delight/blob/master/divluh.c.txt
for simplicity as we don't require the remainder.

Regards,
Pavan.

> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of Stefan Kanthak
> Sent: Tuesday, March 26, 2019 6:41 AM
> To: dev@dpdk.org
> Cc: hannes@stressinduktion.org
> Subject: [dpdk-dev] [BUG] Maintainer for
> lib/librte_eal/common/rte_reciprocal.c?
> 
> Hi @ll,
> 
> <https://git.dpdk.org/dpdk/plain/MAINTAINERS> does NOT list a maintainer
> for lib/librte_eal/common/rte_reciprocal.c
> 
> Whoever it is should take a close look at <https://skanthak.homepage.t-
> online.de/division.html>,
> then fix the most obvious bug plus the many deficiencies of
> divide_128_div_64_to_64().
> 
> regards
> Stefan Kanthak

  parent reply	other threads:[~2019-03-28  4:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-26  1:11 Stefan Kanthak
2019-03-26  1:11 ` Stefan Kanthak
2019-03-28  4:35 ` Pavan Nikhilesh Bhagavatula [this message]
2019-03-28  4:35   ` Pavan Nikhilesh Bhagavatula
2019-04-05 19:17   ` [dpdk-dev] [BUG] Maintainer forlib/librte_eal/common/rte_reciprocal.c? Stefan Kanthak
2019-04-05 19:17     ` Stefan Kanthak

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=CY4PR1801MB1863A73B62C8E3F8475A7D0BDE590@CY4PR1801MB1863.namprd18.prod.outlook.com \
    --to=pbhagavatula@marvell.com \
    --cc=dev@dpdk.org \
    --cc=hannes@stressinduktion.org \
    --cc=stefan.kanthak@nexgo.de \
    /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).