On Thu, Feb 24, 2022 at 10:53:01AM -0300, Guilherme G. Piccoli wrote: > On 24/02/2022 10:24, Daniel Vetter wrote: > > Some things changed, and add two useful links. > > > > v2: Also include a link to the QR encoding work. Plus review from > > Javier. > > > > Reviewed-by: Javier Martinez Canillas <javierm@xxxxxxxxxx> > > Cc: Javier Martinez Canillas <javierm@xxxxxxxxxx> > > Cc: Pekka Paalanen <ppaalanen@xxxxxxxxx> > > Cc: gpiccoli@xxxxxxxxxx > > Signed-off-by: Daniel Vetter <daniel.vetter@xxxxxxxxx> > > --- > > Hi Daniel, thanks for the improvement - much appreciated! > > Below a comment inline; other than that, feel free to add my: > Reviewed-by: Guilherme G. Piccoli <gpiccoli@xxxxxxxxxx> > > Cheers, > > > Guilherme > > > [...] > > > > -* There's also proposal for a simplied DRM console instead of the full-blown > > - fbcon and DRM fbdev emulation. Any kind of panic handling tricks should > > - obviously work for both console, in case we ever get kmslog merged. > > +* Encoding the actual oops and preceeding dmesg in a QR might help with the > > Email client complains about "preceeding" word - misspelled maybe? Indeed, I've fixed this while applying. -Daniel > > > + dread "important stuff scrolled away" problem. See `[RFC][PATCH] Oops messages > > + transfer using QR codes > > + <https://lore.kernel.org/lkml/1446217392-11981-1-git-send-email-alexandru.murtaza@xxxxxxxxx/>`_ > > + for some example code that could be reused. > > > > Contact: Daniel Vetter > > -- Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch
