linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Felipe Balbi <balbi@ti.com>
Cc: Luciano Coelho <coelho@ti.com>,
	svenkatr@ti.com, linux-omap@vger.kernel.org,
	linux-mmc@vger.kernel.org, cjb@laptop.org, lrg@ti.com,
	linux-kernel@vger.kernel.org,
	Peter Ujfalusi <peter.ujfalusi@ti.com>,
	Tony Lindgren <tony@atomide.com>
Subject: Re: 32kHz clock removal causes problems omap_hsmmc
Date: Wed, 19 Dec 2012 09:45:52 +0000	[thread overview]
Message-ID: <20121219094552.GN4985@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20121218095450.GB27751@arwen.pp.htv.fi>

[-- Attachment #1: Type: text/plain, Size: 838 bytes --]

On Tue, Dec 18, 2012 at 11:54:50AM +0200, Felipe Balbi wrote:

> damn, this is still part of our v3.7-rc kernel. Original commit was done
> with no testing whatsoever and caused a big regression to (at least)
> TI's WiFi driver which depend on SDIO to function.

> Too bad things break and even when reported nobody gives a rat's ***
> about them :-s

I guess it's going to be even more of an issue going forward given the
recent events but FWIW it was always very unusual to see any review of
any TWL patches, the PMIC appeared to have been rather abandoned so the
only way of getting any testing was to put stuff in -next and hope.

Mind you, if there is an issue it doesn't seem that serious given that
it took at least one kernel release before anyone noticed and even when
they did you're the first person who bothered to respond...

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2012-12-19  9:46 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-15  8:31 32kHz clock removal causes problems omap_hsmmc Luciano Coelho
2012-12-18  9:54 ` Felipe Balbi
2012-12-19  9:45   ` Mark Brown [this message]
2012-12-19 10:00     ` Peter Ujfalusi
2012-12-19 10:09       ` Mark Brown
2012-12-19 10:18         ` Peter Ujfalusi
2012-12-19 10:32           ` Mark Brown
2012-12-19 10:45             ` Luciano Coelho
2012-12-19 10:56               ` Peter Ujfalusi
2012-12-19 11:00                 ` Peter Ujfalusi
2012-12-19 11:02                 ` Mark Brown
2012-12-19 11:07                 ` Luciano Coelho
2012-12-19 13:01                 ` Felipe Balbi
2012-12-19 13:51                   ` Benoit Cousson
2012-12-19 13:54                     ` Felipe Balbi
2012-12-19 13:58                     ` Mark Brown
2012-12-19 13:58                     ` Luciano Coelho
2012-12-19 14:04                       ` Benoit Cousson
2012-12-19 18:06                         ` R Sricharan
2012-12-19 14:31                   ` Peter Ujfalusi
2012-12-19 16:28           ` Tony Lindgren
2012-12-19 10:01     ` Luciano Coelho
2012-12-19 10:28       ` Mark Brown
2012-12-19 10:42         ` Luciano Coelho

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=20121219094552.GN4985@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=balbi@ti.com \
    --cc=cjb@laptop.org \
    --cc=coelho@ti.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=lrg@ti.com \
    --cc=peter.ujfalusi@ti.com \
    --cc=svenkatr@ti.com \
    --cc=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).