netdev - patch "workflow" - what deferred state means?

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-next>] [day] [month] [year] [list]

Date:	Mon, 7 Nov 2011 21:07:45 +0200
From:	Maz The Northener <mazziesaccount@...il.com>
To:	netdev <netdev@...r.kernel.org>
Subject: patch "workflow" - what deferred state means?

Hi!

I sent a few versions of a patch to the netdev some days ago. I
recently stumbled upon patchwork website, and noticed that the latest
versions of my patches had "deferred" state. I tried searching for
what that means, but only thing I managed to find was Uboot project's
explanation. They used deferred state to mean that patch in question
depends on something not currently in source tree. I doubt that's the
case here though. Maybe it is because my patch was created against rc4
kernel.

I was just wondering if I could do some conclusion based on the state.
I naturally am keen to know if patch is rejected, or if it stil may
end up in kernel, or if there is something I could still do in order
to improve the situation? Maybe creating the patch against new 3.1
kernel would help you?

So is the different states of patches explained somewhere?

--Matti Vaittinen
--
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