From: Pierre Ossman <drzeus-list@drzeus.cx>
To: Andrew Morton <akpm@osdl.org>
Cc: rmk+lkml@arm.linux.org.uk, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mmc: Multi-sector writes
Date: Thu, 18 Aug 2005 07:48:04 +0200 [thread overview]
Message-ID: <43042114.7010503@drzeus.cx> (raw)
In-Reply-To: <20050817155641.12bb20fc.akpm@osdl.org>
Andrew Morton wrote:
>The fact that this is enabled under the experimental
>CONFIG_MMC_BULKTRANSFER seems unfortunate. I mean, if the code works OK
>then we should just enable it unconditionally, no?
>
>
>
It was made this way to make Russell more open to it. I have since not
recieved any more comments from him so I figured I could pass it by you
instead to get more wide spread testing. The long term goal was removing
the config and having it on all the time.
>I'm thinking that it would be better to not have the config option there
>and then re-add it late in the 2.6.14 cycle if someone reports problems
>which cannot be fixed. Or at least make it default to 'y' so we get more
>testing coverage, then remove the config option later. Or something.
>
>Thoughts?
>
>
Removing it would be preferable by me. All that #ifdef tends to clutter
up the code. After som initial problem with a buggy card everything has
worked flawlesly.
Rgds
Pierre
next prev parent reply other threads:[~2005-08-18 5:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-14 12:41 [PATCH] mmc: Multi-sector writes Pierre Ossman
2005-08-17 22:56 ` Andrew Morton
2005-08-18 5:48 ` Pierre Ossman [this message]
2005-08-18 5:48 ` Andrew Morton
2005-08-18 6:38 ` Russell King
2005-08-18 7:26 ` Pierre Ossman
2005-08-18 8:23 ` Russell King
2005-08-18 8:48 ` Pierre Ossman
2005-08-18 20:19 ` Pavel Machek
2005-08-19 5:00 ` Pierre Ossman
2005-08-19 7:58 ` Pavel Machek
2005-08-19 8:12 ` Pierre Ossman
2005-08-18 9:42 ` Alan Cox
2005-08-18 9:33 ` Pierre Ossman
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=43042114.7010503@drzeus.cx \
--to=drzeus-list@drzeus.cx \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+lkml@arm.linux.org.uk \
/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