linux-kernel - Re: "[-next] ARM: Fix build if CLKDEV

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 23 Jun 2015 17:49:19 +0200 (CEST)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Russell King - ARM Linux <linux@....linux.org.uk>
cc:	Daniel Lezcano <daniel.lezcano@...aro.org>,
	linux-kernel@...r.kernel.org, Guenter Roeck <linux@...ck-us.net>,
	Sudeep Holla <sudeep.holla@....com>
Subject: Re: "[-next] ARM: Fix build if CLKDEV_LOOKUP is not configured"

On Tue, 23 Jun 2015, Russell King - ARM Linux wrote:
> 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?

Pick it up please. I ignored it when Sudeep said, that it should go
through your tree, of course w/o cc'ing you.

Guenter did not cc you probably because he thought it's wreckage
originating from the clocksource tree.

Thanks,

	tglx



--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/