From mboxrd@z Thu Jan  1 00:00:00 1970
From: Oliver Hartkopp <socketcan@hartkopp.net>
Subject: Awaiting upsteam? - Re: [PATCH net-next v3] em_canid: Ematch rule
 to match CAN frames according to their identifiers
Date: Tue, 03 Jul 2012 07:15:49 +0200
Message-ID: <4FF28005.4050108@hartkopp.net>
References: <1341241568-13438-1-git-send-email-lisovy@gmail.com> <4FF1DF65.5080306@hartkopp.net> <4FF1E26F.5000106@hartkopp.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Return-path: <netdev-owner@vger.kernel.org>
In-Reply-To: <4FF1E26F.5000106@hartkopp.net>
Sender: netdev-owner@vger.kernel.org
To: David Miller <davem@davemloft.net>
Cc: Marc Kleine-Budde <mkl@pengutronix.de>, netdev@vger.kernel.org, linux-can@vger.kernel.org, lartc@vger.kernel.org
List-Id: linux-can.vger.kernel.org

Hello Dave,

i've seen that you tagged this patch as "Awaiting upstream" in Patchwork.

Does this mean, that *you* are waiting for another re-spin of the patch OR do
you expect this patch go through a sub-tree like Marcs can-next tree?

Who is committing these "awaiting upstream" patches?

Thanks for clarification,
Oliver