mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Daniel Lezcano <daniel.lezcano@linaro.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	linux-kernel@vger.kernel.org, Guenter Roeck <linux@roeck-us.net>,
	Sudeep Holla <sudeep.holla@arm.com>
Subject: "[-next] ARM: Fix build if CLKDEV_LOOKUP is not configured"
Date: Tue, 23 Jun 2015 16:37:24 +0100	[thread overview]
Message-ID: <20150623153724.GA7557@n2100.arm.linux.org.uk> (raw)

If you'd like me to apply a patch, it's no good discussing it in a
place where I have no knowledge of, and then suggesting that I
should apply it.

Paul Gortmaker brought your patch to my attention, and said that it
had been breaking MIPS for a week, and asked whether I had any
knowledge of it.  I did not.

Given that the patch was created on 14th June, and it's now some 9
days later, I have to ask what's going on here?  Has someone else
queued it up?  Is someone intending to apply it during the merge
window once the stuff which causes the breakage in my tree has
landed?  Are you still expecting me to somehow pick up a patch that
I had no knowledge of, for a breakage that I had no knowledge of?

Basically, what are you expecting to happen with this patch?

-- 
FTTC broadband for 0.8mile line: currently at 10.5Mbps down 400kbps up
according to speedtest.net.

             reply	other threads:[~2015-06-23 15:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-23 15:37 Russell King - ARM Linux [this message]
2015-06-23 15:49 ` Thomas Gleixner
2015-06-23 16:40   ` Guenter Roeck
2015-06-23 15:56 ` Sudeep Holla

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=20150623153724.GA7557@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=daniel.lezcano@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=sudeep.holla@arm.com \
    --cc=tglx@linutronix.de \
    /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®