From: Simon Kagstrom <simon.kagstrom@netinsight.net>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: dev@dpdk.org
Subject: Re: deadline notice
Date: Thu, 11 Jun 2015 10:45:53 +0200 [thread overview]
Message-ID: <20150611104553.1207678f@miho> (raw)
In-Reply-To: <2892912.hbmKnaj783@xps13>
On Thu, 11 Jun 2015 10:33:21 +0200
Thomas Monjalon <thomas.monjalon@6wind.com> wrote:
> 2015-06-11 09:27, Simon Kagstrom:
> > On Wed, 10 Jun 2015 20:39:59 +0200
> > Thomas Monjalon <thomas.monjalon@6wind.com> wrote:
> >
> > I didn't find this in the list:
> >
> > rte_reorder: Allow sequence numbers > 0 as starting point
>
> It was considered more or less as a fix.
>
> > and I think it would be good to have as well.
>
> Yes of course.
OK, thanks!
It would be good to have some sort of feedback on accepted patches
though - in addition to the above one, I also sent a build-fix
kni: Use utsrelease.h to determine Ubuntu kernel version
which I also think would be good to have (basically, building in a
chroot is broken otherwise). I haven't had time to test the patch on
older Ubuntus though.
So, while this is an old discussion by now, I think DPDK is large
enough to warrant some more infrastructure for patch submissions - at
least in the form of build-tests for patches, and preferrably some sort
of status marker for accepted patches. Basically what Github/Travis-ci
etc already provides.
// Simon
next prev parent reply other threads:[~2015-06-11 8:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-10 18:39 deadline notice Thomas Monjalon
2015-06-10 21:13 ` Abdul, Jaffar
2015-06-11 14:00 ` Thomas Monjalon
2015-06-11 1:30 ` Tetsuya Mukawa
2015-06-11 8:34 ` Thomas Monjalon
2015-06-11 9:20 ` Tetsuya Mukawa
2015-06-11 7:27 ` Simon Kagstrom
2015-06-11 8:33 ` Thomas Monjalon
2015-06-11 8:45 ` Simon Kagstrom [this message]
2015-06-11 9:30 ` Iremonger, Bernard
2015-06-11 9:58 ` Thomas Monjalon
2015-06-11 10:04 ` Iremonger, Bernard
2015-06-11 11:39 ` Thomas Monjalon
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=20150611104553.1207678f@miho \
--to=simon.kagstrom@netinsight.net \
--cc=dev@dpdk.org \
--cc=thomas.monjalon@6wind.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.