From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Pierre Ossman <drzeus@drzeus.cx>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [MMC] Use command class to determine read-only status.
Date: Sun, 30 Oct 2005 10:16:46 +0000 [thread overview]
Message-ID: <20051030101646.GA26501@flint.arm.linux.org.uk> (raw)
In-Reply-To: <4363FA3E.3000701@drzeus.cx>
On Sun, Oct 30, 2005 at 12:39:58AM +0200, Pierre Ossman wrote:
> Russell King wrote:
> >On Fri, Oct 28, 2005 at 09:36:05AM +0200, Pierre Ossman wrote:
> >>If a card doesn't support the "write block" command class then
> >>any attempts to open the device should reflect this by denying
> >>write access.
> >
> >I'd rather we kept printk messages as one printk if at all possible.
> >How about encapsulating both of these conditions into an inline
> >function:
> >
>
> Ok with me. New patch included.
Applied, thanks.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core
prev parent reply other threads:[~2005-10-30 10:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-28 7:36 [PATCH] [MMC] Use command class to determine read-only status Pierre Ossman
2005-10-28 20:14 ` Russell King
2005-10-29 22:39 ` Pierre Ossman
2005-10-30 10:16 ` Russell King [this message]
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=20051030101646.GA26501@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=drzeus@drzeus.cx \
--cc=linux-kernel@vger.kernel.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