From: Stephen Hemminger <stephen@networkplumber.org>
To: Tyler Retzlaff <roretzla@linux.microsoft.com>
Cc: Raul Ferrando <rferrandop@protonmail.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: Get started contributing to the DPDK
Date: Thu, 29 Dec 2022 17:55:31 -0800 [thread overview]
Message-ID: <20221229175531.7bfe0674@hermes.local> (raw)
In-Reply-To: <20221229174413.GA20765@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net>
On Thu, 29 Dec 2022 09:44:13 -0800
Tyler Retzlaff <roretzla@linux.microsoft.com> wrote:
> hi Raul,
>
> On Wed, Dec 28, 2022 at 10:40:45PM +0000, Raul Ferrando wrote:
> > Dear DPDK team,
> >
> > My name is Raul and I recently discovered the DPDK project and I am very interested in contributing and becoming more involved. Can you please provide some guidance on how to get started with my first contribution? I am particularly interested in tackling bugs that are suitable for beginners.
> >
>
> dpdk documents contribution guidelines here
> https://core.dpdk.org/contribute/
>
> and in more detail here
> https://doc.dpdk.org/guides/contributing/patches.html
>
> welcome! we look forward to your contributions.
The bugzilla exists here https://bugs.dpdk.org/ bu not that useful.
Most of the bugs are specific to hardware types.
One bug that could be worked on, is the existing applications and examples
often incorrectly handle shutdown from a signal. It is not safe to call the
close and cleanup functions directly in a signal handler; the proper way to
do it is to only set a flag in the signal handler, then do cleanup in
the main thread when the main loop exits.
next prev parent reply other threads:[~2022-12-30 1:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-28 22:40 Raul Ferrando
2022-12-29 17:44 ` Tyler Retzlaff
2022-12-30 1:55 ` Stephen Hemminger [this message]
2022-12-30 18:03 ` Raul Ferrando
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=20221229175531.7bfe0674@hermes.local \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=rferrandop@protonmail.com \
--cc=roretzla@linux.microsoft.com \
/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).