netdev - Awaiting upsteam? - Re: [PATCH net-next v3] em_canid: Ematch rule to match CAN frames according to their identifiers

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4FF28005.4050108@hartkopp.net>
Date:	Tue, 03 Jul 2012 07:15:49 +0200
From:	Oliver Hartkopp <socketcan@...tkopp.net>
To:	David Miller <davem@...emloft.net>
CC:	Marc Kleine-Budde <mkl@...gutronix.de>, netdev@...r.kernel.org,
	linux-can@...r.kernel.org, lartc@...r.kernel.org
Subject: Awaiting upsteam? - Re: [PATCH net-next v3] em_canid: Ematch rule
 to match CAN frames according to their identifiers

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
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html