From: Takashi Iwai <tiwai@suse.de>
To: dedekind1@gmail.com
Cc: Rusty Russell <rusty@rustcorp.com.au>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org, Sitsofe Wheeler <sitsofe@yahoo.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Christof Schmitt <christof.schmitt@de.ibm.com>
Subject: Re: [PULL] param sysfs oops (simple, leaky) fix, bool arrays fix
Date: Thu, 06 May 2010 08:24:10 +0200 [thread overview]
Message-ID: <s5h39y5v985.wl%tiwai@suse.de> (raw)
In-Reply-To: <1273050258.3702.133.camel@localhost>
At Wed, 05 May 2010 12:04:18 +0300,
Artem Bityutskiy wrote:
>
> On Wed, 2010-05-05 at 11:49 +0300, Artem Bityutskiy wrote:
> > > Fixing in the way of the later upstream is a bit too intrusive as a
> > > stable patch. So, I'm also not sure whether we should take it,
> > > too...
> >
> > To be frank I do not really understand what you mean.
>
> If you meant 'let's not change it 2.6.34' - fair enough, it was already
> in 2.6.32, so there is probably no reason to hurry. But I suggest to
> still consider this as a big issue and fix as soon as we can.
Ah, sorry I was confused. I somehow thought Rusty's patch has been
already merged after 2.6.32, but it didn't happen in reality.
Then I'm for merging the changes even for 2.6.34 although it's late.
In the API side, there aren't many changes. And it might reduce the
whole binary size in the end by the use of module_parm_ops pointer,
too.
thanks,
Takashi
next prev parent reply other threads:[~2010-05-06 6:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-28 22:32 Rusty Russell
2010-04-27 10:31 ` Artem Bityutskiy
2010-04-27 10:53 ` Artem Bityutskiy
2010-05-04 2:23 ` Rusty Russell
2010-05-04 18:07 ` Artem Bityutskiy
2010-05-05 5:33 ` Rusty Russell
2010-05-05 7:25 ` Artem Bityutskiy
2010-05-05 7:44 ` Takashi Iwai
2010-05-05 8:49 ` Artem Bityutskiy
2010-05-05 9:04 ` Artem Bityutskiy
2010-05-06 6:24 ` Takashi Iwai [this message]
2010-05-06 2:28 ` Rusty Russell
2010-06-22 16:50 ` Phil Carmody
2010-06-22 23:23 ` 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=s5h39y5v985.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=christof.schmitt@de.ibm.com \
--cc=dedekind1@gmail.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=sitsofe@yahoo.com \
--cc=torvalds@linux-foundation.org \
/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
all inboxes | Powered by JetHome®