From: Marek Vasut <marek.vasut@gmail.com>
To: linux-arm-kernel@lists.arm.linux.org.uk
Cc: Linus Walleij <linus.ml.walleij@gmail.com>,
Linus Walleij <linus.walleij@stericsson.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, Pierre Ossman <pierre@ossman.eu>
Subject: Re: [PATCH 1/2] MMC Agressive clocking framework v5
Date: Tue, 21 Jul 2009 22:35:46 +0200 [thread overview]
Message-ID: <200907212235.47006.marek.vasut@gmail.com> (raw)
In-Reply-To: <63386a3d0907211328v3c060012r3acc2d5f88e4d9eb@mail.gmail.com>
Dne Út 21. července 2009 22:28:25 Linus Walleij napsal(a):
> Then the ChangeLog I missed yesterday due to sitting up too
> late:
>
> ChangeLog v4->v5:
>
> * Make mmc_set_data_timeout() in core.c work even if ios.clock is
> set to zero by the clock gating code.
>
> * Give the host-centric functions the mmc_host_clk* prefix instead
> so it is clear that it's host functionality that is being
> called.
>
> * Mailing this to Andrew Morton and LKML since the previous MMC
> maintainer stepped down.
Pierre gave up on mmc subsystem maintainance ?
>
> Linus Walleij
>
> -------------------------------------------------------------------
> List admin: http://lists.arm.linux.org.uk/mailman/listinfo/linux-arm-kernel
> FAQ: http://www.arm.linux.org.uk/mailinglists/faq.php
> Etiquette: http://www.arm.linux.org.uk/mailinglists/etiquette.php
next prev parent reply other threads:[~2009-07-21 20:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-20 22:26 [PATCH 1/2] MMC Agressive clocking framework v5 Linus Walleij
2009-07-21 20:28 ` Linus Walleij
2009-07-21 20:35 ` Marek Vasut [this message]
2009-07-21 22:44 ` Linus Walleij
2009-07-22 0:46 ` Madhusudhan
2009-07-22 12:11 ` David Vrabel
2009-07-22 22:33 ` Linus Walleij
2009-07-23 14:15 ` David Vrabel
2009-07-23 18:15 ` Adrian Hunter
2009-07-23 20:25 ` Linus Walleij
2009-07-24 22:03 ` Madhusudhan
2009-07-24 22:59 ` Andrew Morton
2009-07-25 11:35 ` Adrian Hunter
2009-07-23 20:30 ` Linus Walleij
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=200907212235.47006.marek.vasut@gmail.com \
--to=marek.vasut@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linus.ml.walleij@gmail.com \
--cc=linus.walleij@stericsson.com \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=pierre@ossman.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox