From: Felipe Balbi <balbi@ti.com>
To: Mark Brown <broonie@kernel.org>
Cc: Olof Johansson <olof@lixom.net>, Felipe Balbi <balbi@ti.com>,
Laxman Dewangan <ldewangan@nvidia.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux OMAP Mailing List <linux-omap@vger.kernel.org>
Subject: Re: commit c368e5fc2a190923b786f2de3e79430ea3566a25 regresses MMC
Date: Thu, 21 Nov 2013 19:56:48 -0600 [thread overview]
Message-ID: <20131122015648.GA855@saruman.home> (raw)
In-Reply-To: <20131121205050.GF14725@sirena.org.uk>
[-- Attachment #1: Type: text/plain, Size: 696 bytes --]
Hi,
On Thu, Nov 21, 2013 at 08:50:50PM +0000, Mark Brown wrote:
> /me notes that he'd probably have been less grumpy if the message had
> a subject line that had content in it, even had it gone to the right
oh cut the crap already. It contained the commit sha1 and a pretty
self-explanatory "regresses MMC". You can't expect me to put everything
in the subject and you're only "grumpy" because you're too lazy to move
your neck 5 degrees to the right to read the rest of the line.
what a long thread for such a small issue Mark, just stop it already.
The issue is fixed in -next and that's what matters, everybody's happy.
I know I am with my working MMC on BBB.
--
balbi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2013-11-22 1:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-20 17:58 commit c368e5fc2a190923b786f2de3e79430ea3566a25 regresses MMC Felipe Balbi
2013-11-20 20:34 ` Mark Brown
2013-11-20 20:51 ` Felipe Balbi
2013-11-21 2:48 ` Felipe Balbi
2013-11-21 10:49 ` Mark Brown
2013-11-21 12:58 ` Felipe Balbi
2013-11-21 16:43 ` Stephen Warren
2013-11-21 18:36 ` Mark Brown
2013-11-21 18:44 ` Stephen Warren
2013-11-21 19:28 ` Mark Brown
2013-11-21 20:27 ` Olof Johansson
2013-11-21 20:50 ` Mark Brown
2013-11-22 1:56 ` Felipe Balbi [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=20131122015648.GA855@saruman.home \
--to=balbi@ti.com \
--cc=broonie@kernel.org \
--cc=ldewangan@nvidia.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=olof@lixom.net \
/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).