From: Andre Muezerie <andremue@linux.microsoft.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: Stephen Hemminger <stephen@networkplumber.org>,
Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>,
Tyler Retzlaff <roretzla@linux.microsoft.com>,
dev@dpdk.org
Subject: Re: [PATCH] eal: add getline() function for Windows
Date: Wed, 21 May 2025 13:23:10 -0700 [thread overview]
Message-ID: <20250521202310.GA16276@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net> (raw)
In-Reply-To: <2358541.72vocr9iq0@thomas>
On Wed, May 21, 2025 at 09:00:48AM +0200, Thomas Monjalon wrote:
> 21/05/2025 02:35, Andre Muezerie:
> > On Tue, May 20, 2025 at 10:14:33AM -0700, Stephen Hemminger wrote:
> > > On Mon, 5 May 2025 13:40:07 -0700
> > > Andre Muezerie <andremue@linux.microsoft.com> wrote:
> > >
> > > > Existing DPDK code uses getline(), which is a POSIX function and is
> > > > not available in the Windows APIs.
> > > >
> > > > Instead of rewriting it or coming up with some other replacement, this
> > > > patch makes use of the implementation provided by NetBSD to make it
> > > > possible to compile code dependent on getline on Windows.
> > > >
> > > > Signed-off-by: Andre Muezerie <andremue@linux.microsoft.com>
> > >
> > > Not sure, are BSD-2 and BSD-3 compatible?
> > > Getting license exception approved requires going through the governing board
> > > which can take up to 6 months.
> >
> > Hi Stephen, I would appreciate some guidance here.
> >
> > My understanding is that in general, BSD-2 licensed code can be used in BSD-3
> > licensed projects, as long as the BSD-2 license is retained in the original
> > (BSD-2) files.
> >
> > I do see that BSD-2 was listed in the exception table (for getopt function). It's
> > not clear to me why it needed to be listed as an exception, but if that was
> > needed, it indicates that the same should be done for getline(). Is that not
> > the case?
>
> No matter the compatibility agreed or not in courts,
> if the licence is different we note it as an exception,
> so it is crystal clear for users of DPDK.
> We don't want to have any surprise and we avoid exceptions,
> that's why the Governing Board has to accept it.
>
Thanks for clarifying, Thomas.
I sent an email to the Governing Board requesting the exception.
prev parent reply other threads:[~2025-05-21 20:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-05 20:40 Andre Muezerie
2025-05-20 17:14 ` Stephen Hemminger
2025-05-21 0:35 ` Andre Muezerie
2025-05-21 7:00 ` Thomas Monjalon
2025-05-21 20:23 ` Andre Muezerie [this message]
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=20250521202310.GA16276@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net \
--to=andremue@linux.microsoft.com \
--cc=dev@dpdk.org \
--cc=dmitry.kozliuk@gmail.com \
--cc=roretzla@linux.microsoft.com \
--cc=stephen@networkplumber.org \
--cc=thomas@monjalon.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;
as well as URLs for NNTP newsgroup(s).