From: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Chris Ball <chris@printf.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-mmc@vger.kernel.org
Subject: Re: [GIT PULL] MMC updates for 3.16-rc1
Date: Thu, 12 Jun 2014 07:25:36 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.1406120724100.5160@axis700.grange> (raw)
In-Reply-To: <CA+55aFyEbFLFWLKP5kHw85qTRNoviFk8LhivxXJgAMROdvJtsg@mail.gmail.com>
Hi Linus,
On Wed, 11 Jun 2014, Linus Torvalds wrote:
> On Tue, Jun 10, 2014 at 2:50 PM, Linus Torvalds
> <torvalds@linux-foundation.org> wrote:
> >
> > Also, that new drivers/mmc/host/usdhi6rol0.c driver is one f*cking
> > noisy compile, and knisr certainly has never been tested in a 64-bit
> > environment. Please either fix it, or make it depend on BROKEN.
>
> Guys? Seriously, if that driver isn't fixed, I'm going to mark it
> broken myself. It pretty much generates as many lines of warnings as
> the rest of my "allmodconfig" build combined.
>
> It's extremely annoying, and the crazy warnings are likely to hide
> potential real problems elsewhere, so right now that driver has
> negative value. I do a lot of allmodconfig builds during the merge
> window, and I am not going to look at that warning much longer.
>
> Fix it promptly, or it gets disabled.
I sent a patch a few hours ago:
https://patchwork.kernel.org/patch/4338531/ Since it's only changing print
format strings, it should be a trivial one to review, so, just waiting for
Chris to pick it up and push it to you. Sorry about the trouble.
Thanks
Guennadi
next prev parent reply other threads:[~2014-06-12 5:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-10 19:51 Chris Ball
2014-06-10 21:50 ` Linus Torvalds
2014-06-10 23:47 ` Mike Turquette
2014-06-12 4:27 ` Linus Torvalds
2014-06-12 5:25 ` Guennadi Liakhovetski [this message]
2014-06-12 6:41 ` Ulf Hansson
2014-06-12 7:17 ` Lee Jones
2014-06-12 12:19 ` 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=Pine.LNX.4.64.1406120724100.5160@axis700.grange \
--to=g.liakhovetski@gmx.de \
--cc=chris@printf.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®