netdev - Re: [PATCH net-next 1/3] cxgb4: Add support for loopback between VI of same port

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: <20150522.140100.204940697669252730.davem@davemloft.net>
Date:	Fri, 22 May 2015 14:01:00 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	leedom@...lsio.com
Cc:	hariprasad@...lsio.com, netdev@...r.kernel.org,
	nirranjan@...lsio.com
Subject: Re: [PATCH net-next 1/3] cxgb4: Add support for loopback between
 VI of same port

From: Casey Leedom <leedom@...lsio.com>
Date: Fri, 22 May 2015 16:49:03 +0000

>   Oh I definitely understand that and agree.  Unfortunately I've
> inherited a driver architecture that makes that ... "difficult"
> for many operations ...  And I have an internal bug filed
> against me to fix those particular issues.
> 
>   However, that doesn't answer at least one of my questions
> which was how do I pass information into the driver _before_
> it does the device probe?

I did answer the question, I said that if you fix the real actual
core problem then you won't have this need to begin with.

I thought I made that perfectly clear.

I really am not going to entertain arguments of the form "it's
too hard to implement this correctly so I'm going to try
and slam a module parameter into the driver to fix things".
--
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