From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH] mk: Quote $(KERNELCC) to allow ccache builds Date: Tue, 13 Oct 2015 14:45:11 +0200 Message-ID: <8756629.OFYVJTNzJr@xps13> References: <20150924094328.5a2ea3c8@miho> <561CF892.9040507@6wind.com> <561CFB9C.5080708@netinsight.net> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Cc: dev@dpdk.org To: Simon =?ISO-8859-1?Q?K=E5gstr=F6m?= Return-path: Received: from mail-wi0-f175.google.com (mail-wi0-f175.google.com [209.85.212.175]) by dpdk.org (Postfix) with ESMTP id D6B368E89 for ; Tue, 13 Oct 2015 14:46:15 +0200 (CEST) Received: by wicge5 with SMTP id ge5so189749007wic.0 for ; Tue, 13 Oct 2015 05:46:15 -0700 (PDT) In-Reply-To: <561CFB9C.5080708@netinsight.net> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 2015-10-13 14:39, Simon K=E5gstr=F6m: > On 2015-10-13 14:26, Olivier MATZ wrote: > > There is the patchwork tool: > > http://dpdk.org/dev/patchwork/project/dpdk/list/ >=20 > Thanks! I knew about it, but forgot to look there. It would be nice t= o > 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 f= ixes > for use in our build environment, so it would be nice to them upstrea= med. Waiting for integration of your patches, maybe you have some free time = to help other developers by making reviews ;) Thanks