From: Rusty Russell <rusty@rustcorp.com.au>
To: Takashi Iwai <takashi.iwai@gmail.com>
Cc: Takashi Iwai <tiwai@suse.de>, linux-kernel@vger.kernel.org
Subject: Re: Problems with string (charp) module parameters
Date: Sat, 24 Oct 2009 01:18:35 +1030 [thread overview]
Message-ID: <200910240118.36256.rusty@rustcorp.com.au> (raw)
In-Reply-To: <200910230050.41790.rusty@rustcorp.com.au>
On Fri, 23 Oct 2009 12:50:41 am Rusty Russell wrote:
> I'll post my current patch series: it needs testing, but I'd appreciate
> your thoughts.
OK, ignore that. I have two new series. Tested.
The first is for 2.6.32. It's simple, and avoids the worst problems.
The real fix is the longer series, for 2.6.33.
Thanks,
Rusty.
next prev parent reply other threads:[~2009-10-23 14:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-13 10:37 Problems with string (charp) module parameters Takashi Iwai
2009-10-21 13:11 ` Rusty Russell
2009-10-22 2:13 ` Takashi Iwai
2009-10-22 14:20 ` Rusty Russell
2009-10-22 15:54 ` Paul E. McKenney
2009-10-23 14:48 ` Rusty Russell [this message]
2009-10-21 15:28 ` [PATCH 1/2] param: don't make the kernel_param's const Rusty Russell
2009-10-21 15:45 ` [PATCH 2/2] param: initialize flags when processing array Rusty Russell
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=200910240118.36256.rusty@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=takashi.iwai@gmail.com \
--cc=tiwai@suse.de \
/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