From: Chris Ball <cjb@laptop.org>
To: monstr@monstr.eu
Cc: James Walmsley <james@fullfat-fs.co.uk>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-mmc@vger.kernel.org
Subject: Re: SDHCI - Add QUIRK2_BROKEN_WRITE_PROTEXT - Support Xilinx Zynq (Linux 3.9.0)
Date: Tue, 20 Aug 2013 19:13:11 +0100 [thread overview]
Message-ID: <86li3wdydk.fsf@void.printf.net> (raw)
In-Reply-To: <521366EA.7080705@monstr.eu> (Michal Simek's message of "Tue, 20 Aug 2013 14:54:02 +0200")
Hi,
On Tue, Aug 20 2013, Michal Simek wrote:
> Hi James,
>
> isn't it better to implement host->ops->get_ro() function for it?
> It seems me better choice than introducing new quirk option.
Yes, I agree. Thanks,
- Chris.
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
WARNING: multiple messages have this Message-ID (diff)
From: Chris Ball <cjb@laptop.org>
To: monstr@monstr.eu
Cc: James Walmsley <james@fullfat-fs.co.uk>,
"linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-mmc@vger.kernel.org
Subject: Re: SDHCI - Add QUIRK2_BROKEN_WRITE_PROTEXT - Support Xilinx Zynq (Linux 3.9.0)
Date: Tue, 20 Aug 2013 19:13:11 +0100 [thread overview]
Message-ID: <86li3wdydk.fsf@void.printf.net> (raw)
In-Reply-To: <521366EA.7080705@monstr.eu> (Michal Simek's message of "Tue, 20 Aug 2013 14:54:02 +0200")
Hi,
On Tue, Aug 20 2013, Michal Simek wrote:
> Hi James,
>
> isn't it better to implement host->ops->get_ro() function for it?
> It seems me better choice than introducing new quirk option.
Yes, I agree. Thanks,
- Chris.
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
next prev parent reply other threads:[~2013-08-20 18:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-16 12:14 SDHCI - Add QUIRK2_BROKEN_WRITE_PROTEXT - Support Xilinx Zynq (Linux 3.9.0) James Walmsley
2013-08-20 12:54 ` Michal Simek
2013-08-20 18:13 ` Chris Ball [this message]
2013-08-20 18:13 ` Chris Ball
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=86li3wdydk.fsf@void.printf.net \
--to=cjb@laptop.org \
--cc=james@fullfat-fs.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=monstr@monstr.eu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.