From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Simon Kågström" <simon.kagstrom@netinsight.net>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] mk: Quote $(KERNELCC) to allow ccache builds
Date: Tue, 13 Oct 2015 14:45:11 +0200 [thread overview]
Message-ID: <8756629.OFYVJTNzJr@xps13> (raw)
In-Reply-To: <561CFB9C.5080708@netinsight.net>
2015-10-13 14:39, Simon Kågström:
> On 2015-10-13 14:26, Olivier MATZ wrote:
> > There is the patchwork tool:
> > http://dpdk.org/dev/patchwork/project/dpdk/list/
>
> Thanks! I knew about it, but forgot to look there. It would be nice to
> have tags to signify e.g., for-v2.2, candidate-v2.2 etc. like you can
> have on github to easier see where patches are going, but perhaps
> patchwork doesn't work that way.
No it's not needed currently because every patches in this mailing-list
target an integration in the main branch for the next release.
Exceptions must be notified.
> Is the process to ping old patches like this on the mailing list?
Yes it is the responsibility of the developer and the maintainer to get
reviews. Please check in the MAINTAINERS file who to contact.
> Two of the patches (this one included) I have outstanding are build fixes
> for use in our build environment, so it would be nice to them upstreamed.
Waiting for integration of your patches, maybe you have some free time to
help other developers by making reviews ;)
Thanks
next prev parent reply other threads:[~2015-10-13 12:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-24 7:43 Simon Kagstrom
2015-10-13 12:10 ` Simon Kagstrom
2015-10-13 12:26 ` Olivier MATZ
2015-10-13 12:39 ` Simon Kågström
2015-10-13 12:45 ` Thomas Monjalon [this message]
2015-10-13 12:54 ` Simon Kågström
2015-10-25 17:31 ` 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=8756629.OFYVJTNzJr@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=simon.kagstrom@netinsight.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).