All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Teodora Baluta <teobaluta@gmail.com>
Cc: linux-kernel@vger.kernel.org, peter.p.waskiewicz.jr@intel.com
Subject: Re: [RFC] QR encoding for Oops messages
Date: Tue, 18 Mar 2014 21:49:09 +0000	[thread overview]
Message-ID: <20140318214909.GA12807@srcf.ucam.org> (raw)
In-Reply-To: <1395093587-2583-1-git-send-email-teobaluta@gmail.com>

On Mon, Mar 17, 2014 at 02:59:47PM -0700, Teodora Baluta wrote:

> As far as decoding is concerned, there are a lot of apps on mobile devices
> that decode QR codes (just text mostly). In order to make this work, an
> app which also decodes the QR code is needed. I will be working the next
> couple of weeks on an Android app which scans the Oops encoding QR and
> sends it to a server which keeps track of these Oopses that are sent to
> it making a sort of stream of the latest Oopses. Any thoughts on what the best
> workflow would be are more than welcomed.

When I was thinking about doing this a while ago, my plan was to simply 
encode the oops as a URL - that way existing QR reader software would 
work and there's no need to write a specialised application. I also 
registered the domain kbu.gs to provide the service. Obviously I never 
got around to actually writing the code, so this is great!

-- 
Matthew Garrett | mjg59@srcf.ucam.org

  reply	other threads:[~2014-03-18 21:49 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-17 21:59 [RFC] QR encoding for Oops messages Teodora Baluta
2014-03-18 21:49 ` Matthew Garrett [this message]
2014-03-19 20:09   ` Teodora Băluţă
2014-03-19 18:03 ` Borislav Petkov
2014-03-19 20:18   ` Teodora Băluţă
2014-03-19 20:18 ` Dave Jones
2014-03-19 20:28   ` Levente Kurusa
2014-03-19 20:50     ` Teodora Băluţă
2014-03-19 20:51       ` Teodora Băluţă
2014-03-19 21:17       ` Levente Kurusa
2014-03-19 20:38   ` Teodora Băluţă
2014-03-21 13:28     ` Jason Cooper
2014-03-22 17:09       ` Levente Kurusa
2014-03-22 18:20         ` Teodora Băluţă
2014-03-22 18:29           ` Levente Kurusa
2014-03-23 11:51             ` Levente Kurusa
2014-03-23 19:38           ` Jason Cooper
2014-03-30 10:17             ` Levente Kurusa
2014-04-01 14:20               ` Jason Cooper
2014-04-01 21:07                 ` Teodora Băluţă
2014-04-03 20:21                   ` Levente Kurusa
2014-04-04 15:12                     ` Jason Cooper
2014-04-04 15:42                       ` Levente Kurusa
2014-04-03 20:57                 ` David Lang
2014-04-04 15:15                   ` Jason Cooper
2014-04-04 16:17                     ` Levente Kurusa
2014-04-04 21:42                       ` Teodora Băluţă
2014-04-05  9:11                         ` Levente Kurusa
2014-04-07 15:20                           ` Jason Cooper
2014-04-08 15:42                             ` Levente Kurusa
2014-04-08 17:20                               ` Jason Cooper
2014-04-08 17:29                                 ` Levente Kurusa
2014-04-13 20:43                                   ` Levente Kurusa

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=20140318214909.GA12807@srcf.ucam.org \
    --to=mjg59@srcf.ucam.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peter.p.waskiewicz.jr@intel.com \
    --cc=teobaluta@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.