Re: [PATCH 2.6.23 1/2] Make the iw_cxgb3 module parameters writable.

ugh, missed these before my last merge...

anyway:

why do we want to parameters writable?  a good changelog tells me
what, why and how, and this changelog just covered the "what".  Also,
I assume you've checked that it's OK for these variables to change at
any time?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: [PATCH 2.6.23 1/2] Make the iw_cxgb3 module parameters writable.
    • From: Steve Wise <[email protected]>

• References:
  • [PATCH 2.6.23 1/2] Make the iw_cxgb3 module parameters writable.
    • From: Steve Wise <[email protected]>

• Prev by Date: [GIT PULL] please pull infiniband.git
• Next by Date: Re: Reading a bad sector does not report failure as 'read error' but hangs PC with 'Machine Check Exception'
• Previous by thread: Re: [PATCH 2.6.23 2/2] iw_cxgb3: Always call low level send function via cxgb3_ofld_send().
• Next by thread: Re: [PATCH 2.6.23 1/2] Make the iw_cxgb3 module parameters writable.
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]