From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Miller Subject: Re: What is "Awaiting Upstream" ? Date: Sat, 13 Sep 2014 15:33:19 -0400 (EDT) Message-ID: <20140913.153319.2070458565920303316.davem@davemloft.net> References: Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: netdev@vger.kernel.org To: vadim4j@gmail.com Return-path: Received: from shards.monkeyblade.net ([149.20.54.216]:37473 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752078AbaIMTdV (ORCPT ); Sat, 13 Sep 2014 15:33:21 -0400 In-Reply-To: Sender: netdev-owner@vger.kernel.org List-ID: From: Vadim Kochan Date: Sat, 13 Sep 2014 21:27:57 +0300 > Sorry for the noise, I tried to google but did not find the answer: > > Could someone explain what does it mean "Awaiting Upstream" status > for the sent patch in the patchwork system ? It means that the patch isn't going directly into my tree, and should be picked up by the maintainer of the subsystem that handles such cases. This is what happens for nearly all wireless, netfilter, and IPSEC changes. Because all of those subsystems have their own top-level maintainers from which I pull from.