netdev - Re: [net-next PATCH 00/29] Add support for the Intel FM10000 Ethernet Switch Host Interface

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: <20140919.220332.1854299635044838363.davem@davemloft.net>
Date:	Fri, 19 Sep 2014 22:03:32 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	alexander.duyck@...il.com
Cc:	alexander.h.duyck@...el.com, nhorman@...hat.com,
	netdev@...r.kernel.org, john.fastabend@...il.com,
	matthew.vick@...el.com, jeffrey.t.kirsher@...el.com,
	sassmann@...hat.com
Subject: Re: [net-next PATCH 00/29] Add support for the Intel FM10000
 Ethernet Switch Host Interface

From: Alexander Duyck <alexander.duyck@...il.com>
Date: Fri, 19 Sep 2014 16:52:32 -0700

> I was wondering what changes you wanted for these patches?  The only
> feedback that I have gotten so far was on the last 2 patches, and a one
> liner about dev_consume_skb_any vs dev_kfree_skb_any.  Is there
> something I missed, or do I need  to resubmit the entire set with some
> other sort of fix?

Any time there is any change requested or intended adjustment, I mark
the entire series as changes requested, and you are expected to make
the adjustments and resubmit the entire series.

I do this silently to work my queue as efficiently as possible, and yet
I still sometimes fall very far behind and get backlogged.

Please do not ask me to repeat what's already been stated in the patch
followup postings as I'll fall even further behind.

Thanks.

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