On Tue, 11 Mar 2014, Paul Bolle wrote:
> On Mon, 2014-03-10 at 21:50 +0100, Thomas Gleixner wrote:
> > Dammit no. We want to know WHY!
>
> Here I am one and half year after reporting seeing this error. I'm not
> aware of anyone reporting it before me. Anyhow, I don't think things
> were working fine up to v3.13. And in my report (I'm not going to link
You can think what you want.
According to Julian things were working fine for him and he actually
sat down and found out WHY things stopped working. That's what counts.
I really have a hard time to understand why you are wasting everyones
time with a completely pointless discussion about the printk level of
this particular thing. It's not spewing a backtrace. It's one line of
printk and there is no rule, that recoverable issues are not allowed
to be printed at KERN_ERR level.
Julian noticed a change of behaviour due to that after 3.13. That's
way more important than your personal dislike of a particular error
level.
Thanks,
tglx
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
