linux-kernel - Re: [RFC][PATCH] MMC: Use write timeout value as read from CSR

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20080920130652.05f3da6d@mjolnir.drzeus.cx>
Date:	Sat, 20 Sep 2008 13:06:52 +0200
From:	Pierre Ossman <drzeus-mmc@...eus.cx>
To:	"Matt Fleming" <mattjfleming@...glemail.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [RFC][PATCH] MMC: Use write timeout value as read from CSR

On Mon, 15 Sep 2008 10:24:22 +0100
"Matt Fleming" <mattjfleming@...glemail.com> wrote:

> 
> OK, I can see your point here. However, this is a completely different
> change to my original patch. Would it not make more sense to queue my
> original patch and then for me to write some patches to move all the
> timeout info into the request structure?
> 

It's better to get it right directly. I'd consider this a bug fix
patch, so it can be applied at any time during the development cycle.

> 
> So, what I propose is this. Could you please queue my bug fix (I can
> send the two patches again) and then I will begin working on the
> generic patches to fix the issues that you've raised in this thread?
> How does that sound?

It shouldn't take that long to write the more proper solution, so get
to it and it should be possible to get in even for .27.

-- 
     -- Pierre Ossman

  Linux kernel, MMC maintainer        http://www.kernel.org
  rdesktop, core developer          http://www.rdesktop.org

  WARNING: This correspondence is being monitored by the
  Swedish government. Make sure your server uses encryption
  for SMTP traffic and consider using PGP for end-to-end
  encryption.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/