public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sergey Yanovich <ynvich@gmail.com>
To: Fabio Comolli <fabio.comolli@gmail.com>
Cc: Brad Campbell <brad@wasp.net.au>, Alex Dubov <oakad@yahoo.com>,
	linux-kernel@vger.kernel.org,
	Pierre Ossman <drzeus-mmc@drzeus.cx>
Subject: Re: [mmc] alternative TI FM MMC/SD driver for 2.6.21-rc7
Date: Fri, 20 Apr 2007 13:10:48 +0300	[thread overview]
Message-ID: <462891A8.6080502@gmail.com> (raw)
In-Reply-To: <b637ec0b0704200131g6297d5d5q842edbf160940170@mail.gmail.com>

Hi,

>> > Have you looked at the last version (0.8)? It fixed all outstanding 
>> issues (as far as I know).
>> >
>>
>> Seconded. I've been running Alex's latest driver since its release. I 
>> routinely suspend/resume
>> 60-100 times between boots to S3 and disk, I've suspended with cards 
>> in the socket and I've tested
>> it using SD and MMC .. I've not been able to fault it now. In fact, 
>> checking my mail archives, my
>> last reported bug was on the 17th of Feb and it has been rock solid 
>> since. I just don't think about
>> it anymore, it simply works...
>>

Well, I am tracking Alex's svn. It is for off-the-tree builds. I 
reorganized Alex's code in Oct 2006 and added
a patch to my debian/patches. Until debian shipped linux-2.6.20, there 
were no [tifm_*] in their tree, so no conflicts. The 2.6.20 came with 
tifm_sd-v0.6 which is not so stable. I dug lkml and bugzilla.kernel.org 
for fresh patches, but found 
http://bugzilla.kernel.org/show_bug.cgi?id=8052. Which made me think, 
svn is still unstable. I merged in-kernel updates to my old (v2.6.18-*) 
version. It compiles and runs OK, so I posted it. No offense to anyone.

Best regards,
Sergey

  reply	other threads:[~2007-04-20 10:11 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4627D402.8020107@gmail.com>
2007-04-20  2:17 ` [mmc] alternative TI FM MMC/SD driver for 2.6.21-rc7 Alex Dubov
2007-04-20  8:20   ` Brad Campbell
2007-04-20  8:31     ` Fabio Comolli
2007-04-20 10:10       ` Sergey Yanovich [this message]
2007-04-22  1:34 ` Alex Dubov
2007-04-22 12:15   ` Sergey Yanovich
2007-04-23  7:04     ` Matthew Garrett
2007-04-23  7:29       ` Sergey Yanovich
2007-04-23 13:16         ` Alex Dubov
2007-04-23 14:12           ` Sergey Yanovich
2007-04-24  2:55             ` Alex Dubov
2007-04-24  8:05               ` Sergey Yanovich
2007-04-26  6:36 ` Pierre Ossman
2007-04-27  2:41   ` Alex Dubov
2007-04-27  7:50     ` Sergey Yanovich
2007-04-27 11:23       ` Alex Dubov
2007-04-27 12:14         ` Sergey Yanovich
2007-04-27 16:55           ` Alex Dubov
2007-04-27 18:36             ` Sergey Yanovich
2007-04-28  8:10               ` Alex Dubov
2007-04-28  8:41                 ` Sergey Yanovich
2007-04-28  9:08                   ` Sergey Yanovich
2007-04-28 11:34               ` Pierre Ossman
2007-04-28 11:44                 ` Alex Dubov
2007-04-28 17:07                   ` Sergey Yanovich
2007-04-19 20:53 Sergey Yanovich
2007-04-19 22:56 ` Arnd Bergmann
2007-04-20  9:22   ` Sergey Yanovich

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=462891A8.6080502@gmail.com \
    --to=ynvich@gmail.com \
    --cc=brad@wasp.net.au \
    --cc=drzeus-mmc@drzeus.cx \
    --cc=fabio.comolli@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oakad@yahoo.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