From: "Ravinandan Arakali" <ravinandan.arakali@neterion.com>
To: "'David S. Miller'" <davem@davemloft.net>
Cc: <hch@infradead.org>, <raghavendra.koushik@neterion.com>,
<jgarzik@pobox.com>, <netdev@oss.sgi.com>,
<leonid.grossman@neterion.com>, <rapuru.sriram@neterion.com>
Subject: RE: default directive in Kconfig(subject modified)
Date: Tue, 9 Aug 2005 14:26:05 -0700 [thread overview]
Message-ID: <001001c59d28$f41c1160$4810100a@pc.s2io.com> (raw)
In-Reply-To: <20050808.193816.70216612.davem@davemloft.net>
Yes, I got the run-time feature message. It will require quite
a bit of code reshuffle and testing to make sure we don't
break existing code in any way.
Thanks,
Ravi
-----Original Message-----
From: David S. Miller [mailto:davem@davemloft.net]
Sent: Monday, August 08, 2005 7:38 PM
To: ravinandan.arakali@neterion.com
Cc: hch@infradead.org; raghavendra.koushik@neterion.com;
jgarzik@pobox.com; netdev@oss.sgi.com; leonid.grossman@neterion.com;
rapuru.sriram@neterion.com
Subject: Re: default directive in Kconfig(subject modified)
From: "Ravinandan Arakali" <ravinandan.arakali@neterion.com>
Date: Mon, 8 Aug 2005 17:40:45 -0700
> Can somebody throw light on the below subject ?
> We have S2io configured as a module and 2buff mode is
> one of the suboptions under S2io. But a directive such
> as "default y" does not seem to enable 2buff mode.
Independant of this issue, can you please acknowledge what
many people are trying to show you in that you MUST make
this a run-time selectable feature.
Yes, that means the driver will have to have two totally
seperate code paths. But that should not be inefficient
because you can just hook up different transmit and
interrupt handler methods depending upon the mode selected.
prev parent reply other threads:[~2005-08-09 21:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-09 0:40 default directive in Kconfig(subject modified) Ravinandan Arakali
2005-08-09 2:38 ` David S. Miller
2005-08-09 21:26 ` Ravinandan Arakali [this message]
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='001001c59d28$f41c1160$4810100a@pc.s2io.com' \
--to=ravinandan.arakali@neterion.com \
--cc=davem@davemloft.net \
--cc=hch@infradead.org \
--cc=jgarzik@pobox.com \
--cc=leonid.grossman@neterion.com \
--cc=netdev@oss.sgi.com \
--cc=raghavendra.koushik@neterion.com \
--cc=rapuru.sriram@neterion.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).