[lkml]   [2018]   [Jan]   [22]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [RFC PATCH v2 0/1] of: easier debugging for node life cycle issues
Hi Frank,

> Please go back and read the thread for version 1. Simply resubmitting a
> forward port is ignoring that whole conversation.
> There is a lot of good info in that thread. I certainly learned stuff in it.

Yes, I did that and learned stuff, too. My summary of the discussion was:

- you mentioned some drawbacks you saw (like the mixture of trace output
and printk output)
- most of them look like addressed to me? (e.g. Steven showed a way to redirect
printk to trace)
- you posted your version (which was, however, marked as "not user friendly"
even by yourself)
- The discussion stalled over having two approaches

So, I thought reposting would be a good way of finding out if your
concerns were addressed in the discussion or not. If I overlooked
something, I am sorry for that. Still, my intention is to continue the
discussion, not to ignore it. Because as it stands, we don't have such a
debugging mechanism in place currently, and with people working with DT
overlays, I'd think it would be nice to have.

Kind regards,


[unhandled content-type:application/pgp-signature]
 \ /
  Last update: 2018-01-22 12:50    [W:0.149 / U:1.696 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site