From mboxrd@z Thu Jan 1 00:00:00 1970 From: Oliver Hartkopp Subject: Re: [PATCH 2/2] net/sched: CAN Filter/Classifier Date: Mon, 04 Jun 2012 10:02:34 +0200 Message-ID: <4FCC6B9A.4090207@volkswagen.de> References: <1337937157-7680-1-git-send-email-lisovy@gmail.com> <1337937157-7680-2-git-send-email-lisovy@gmail.com> <4FCC605F.5090103@volkswagen.de> <4FCC675A.2070309@pengutronix.de> <4FCC6875.80700@pengutronix.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from mr1.volkswagen.de ([194.114.62.75]:49660 "EHLO mr1.volkswagen.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752887Ab2FDIDA (ORCPT ); Mon, 4 Jun 2012 04:03:00 -0400 In-Reply-To: <4FCC6875.80700@pengutronix.de> Sender: linux-can-owner@vger.kernel.org List-ID: To: Marc Kleine-Budde Cc: Rostislav Lisovy , linux-can@vger.kernel.org, pisa@cmp.felk.cvut.cz, sojkam1@fel.cvut.cz On 04.06.2012 09:49, Marc Kleine-Budde wrote: > On 06/04/2012 09:44 AM, Marc Kleine-Budde wrote: >> On 06/04/2012 09:14 AM, Oliver Hartkopp wrote: >>> Hello Rostislav, >>> >>> the merge window is closed and net-next is now open. >>> >>> Please re-spin you patches based on the can-next tree >>> >>> https://gitorious.org/linux-can/linux-can-next >> I'm not sure, that I'm the correct gateway for net/sched patch. > > ...If David takes the patch, it shouldn't be based on linux-can-next > Ok, then creating a patch based on net-next and posting them on netdev would be the better approach - thanks for the clarification. Do you think linux-can and lartc ML for CC is still a good idea? Regards, Oliver