From: David Miller <davem@davemloft.net>
To: leedom@chelsio.com
Cc: hariprasad@chelsio.com, netdev@vger.kernel.org, nirranjan@chelsio.com
Subject: Re: [PATCH net-next 1/3] cxgb4: Add support for loopback between VI of same port
Date: Fri, 22 May 2015 14:01:00 -0400 (EDT) [thread overview]
Message-ID: <20150522.140100.204940697669252730.davem@davemloft.net> (raw)
In-Reply-To: <4985EFDD773FCB459EF7915D2A3621ADBDA809@nice.asicdesigners.com>
From: Casey Leedom <leedom@chelsio.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".
next prev parent reply other threads:[~2015-05-22 18:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-17 10:45 [PATCH net-next 0/3] cxgb4/cxgb4vf: Adds VI loopback, FL starvation support and cleanup Hariprasad Shenai
2015-05-17 10:45 ` [PATCH net-next 1/3] cxgb4: Add support for loopback between VI of same port Hariprasad Shenai
2015-05-18 3:46 ` David Miller
2015-05-21 16:36 ` Casey Leedom
2015-05-21 19:30 ` David Miller
2015-05-22 16:49 ` Casey Leedom
2015-05-22 18:01 ` David Miller [this message]
2015-05-22 23:46 ` Casey Leedom
2015-05-17 10:45 ` [PATCH net-next 2/3] cxgb4: Add debugfs facility to inject FL starvation Hariprasad Shenai
2015-05-17 10:45 ` [PATCH net-next 3/3] cxgb4/cxgb4vf: function and argument name cleanup Hariprasad Shenai
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150522.140100.204940697669252730.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=hariprasad@chelsio.com \
--cc=leedom@chelsio.com \
--cc=netdev@vger.kernel.org \
--cc=nirranjan@chelsio.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).