Re: [RFC] QR encoding for Oops messages

2014-04-13 Thread Levente Kurusa
Hi, 2014-04-08 19:29 GMT+02:00 Levente Kurusa : > Hi, > > On 04/08/2014 07:20 PM, Jason Cooper wrote: >> On Tue, Apr 08, 2014 at 05:42:00PM +0200, Levente Kurusa wrote: >>> On 04/07/2014 05:20 PM, Jason Cooper wrote: On Sat, Apr 05, 2014 at 11:11:02AM +0200, Levente Kurusa wrote: > Oh

Re: [RFC] QR encoding for Oops messages

2014-04-13 Thread Levente Kurusa
Hi, 2014-04-08 19:29 GMT+02:00 Levente Kurusa le...@linux.com: Hi, On 04/08/2014 07:20 PM, Jason Cooper wrote: On Tue, Apr 08, 2014 at 05:42:00PM +0200, Levente Kurusa wrote: On 04/07/2014 05:20 PM, Jason Cooper wrote: On Sat, Apr 05, 2014 at 11:11:02AM +0200, Levente Kurusa wrote: Oh and

Re: [RFC] QR encoding for Oops messages

2014-04-08 Thread Levente Kurusa
Hi, On 04/08/2014 07:20 PM, Jason Cooper wrote: > On Tue, Apr 08, 2014 at 05:42:00PM +0200, Levente Kurusa wrote: >> On 04/07/2014 05:20 PM, Jason Cooper wrote: >>> On Sat, Apr 05, 2014 at 11:11:02AM +0200, Levente Kurusa wrote: Oh and another suggestion, I think placing it in the

Re: [RFC] QR encoding for Oops messages

2014-04-08 Thread Jason Cooper
On Tue, Apr 08, 2014 at 05:42:00PM +0200, Levente Kurusa wrote: > On 04/07/2014 05:20 PM, Jason Cooper wrote: > > On Sat, Apr 05, 2014 at 11:11:02AM +0200, Levente Kurusa wrote: > >> Oh and another suggestion, I think placing it in the bottom-right > >> corner would be better since then we

Re: [RFC] QR encoding for Oops messages

2014-04-08 Thread Levente Kurusa
Hi, On 04/07/2014 05:20 PM, Jason Cooper wrote: > On Sat, Apr 05, 2014 at 11:11:02AM +0200, Levente Kurusa wrote: >> Or, we could use core_param and simply have 'oops_qr' or >> 'qr_oops'. In my humble opinion the latter sounds better. > > Ack. My original suggestion was focused on 0=disable, >0

Re: [RFC] QR encoding for Oops messages

2014-04-08 Thread Levente Kurusa
Hi, On 04/07/2014 05:20 PM, Jason Cooper wrote: On Sat, Apr 05, 2014 at 11:11:02AM +0200, Levente Kurusa wrote: Or, we could use core_param and simply have 'oops_qr' or 'qr_oops'. In my humble opinion the latter sounds better. Ack. My original suggestion was focused on 0=disable, 0 is

Re: [RFC] QR encoding for Oops messages

2014-04-08 Thread Jason Cooper
On Tue, Apr 08, 2014 at 05:42:00PM +0200, Levente Kurusa wrote: On 04/07/2014 05:20 PM, Jason Cooper wrote: On Sat, Apr 05, 2014 at 11:11:02AM +0200, Levente Kurusa wrote: Oh and another suggestion, I think placing it in the bottom-right corner would be better since then we wouldn't

Re: [RFC] QR encoding for Oops messages

2014-04-08 Thread Levente Kurusa
Hi, On 04/08/2014 07:20 PM, Jason Cooper wrote: On Tue, Apr 08, 2014 at 05:42:00PM +0200, Levente Kurusa wrote: On 04/07/2014 05:20 PM, Jason Cooper wrote: On Sat, Apr 05, 2014 at 11:11:02AM +0200, Levente Kurusa wrote: Oh and another suggestion, I think placing it in the bottom-right corner

Re: [RFC] QR encoding for Oops messages

2014-04-07 Thread Jason Cooper
On Sat, Apr 05, 2014 at 11:11:02AM +0200, Levente Kurusa wrote: > Or, we could use core_param and simply have 'oops_qr' or > 'qr_oops'. In my humble opinion the latter sounds better. Ack. My original suggestion was focused on 0=disable, >0 is scale. I literally pulled the name from my

Re: [RFC] QR encoding for Oops messages

2014-04-07 Thread Jason Cooper
On Sat, Apr 05, 2014 at 11:11:02AM +0200, Levente Kurusa wrote: Or, we could use core_param and simply have 'oops_qr' or 'qr_oops'. In my humble opinion the latter sounds better. Ack. My original suggestion was focused on 0=disable, 0 is scale. I literally pulled the name from my

Re: [RFC] QR encoding for Oops messages

2014-04-05 Thread Levente Kurusa
Hi, On 04/04/2014 11:42 PM, Teodora Băluţă wrote: > On Fri, Apr 4, 2014 at 7:17 PM, Levente Kurusa wrote: >> Hi, >> >> On 04/04/2014 05:15 PM, Jason Cooper wrote: >>> On Thu, Apr 03, 2014 at 01:57:04PM -0700, David Lang wrote: On Tue, 1 Apr 2014, Jason Cooper wrote: >> Now I guess

Re: [RFC] QR encoding for Oops messages

2014-04-05 Thread Levente Kurusa
Hi, On 04/04/2014 11:42 PM, Teodora Băluţă wrote: On Fri, Apr 4, 2014 at 7:17 PM, Levente Kurusa le...@linux.com wrote: Hi, On 04/04/2014 05:15 PM, Jason Cooper wrote: On Thu, Apr 03, 2014 at 01:57:04PM -0700, David Lang wrote: On Tue, 1 Apr 2014, Jason Cooper wrote: Now I guess we need

Re: [RFC] QR encoding for Oops messages

2014-04-04 Thread Teodora Băluţă
On Fri, Apr 4, 2014 at 7:17 PM, Levente Kurusa wrote: > Hi, > > On 04/04/2014 05:15 PM, Jason Cooper wrote: >> On Thu, Apr 03, 2014 at 01:57:04PM -0700, David Lang wrote: >>> On Tue, 1 Apr 2014, Jason Cooper wrote: >>> > Now I guess we need to think how to make it work without a >

Re: [RFC] QR encoding for Oops messages

2014-04-04 Thread Levente Kurusa
Hi, On 04/04/2014 05:15 PM, Jason Cooper wrote: > On Thu, Apr 03, 2014 at 01:57:04PM -0700, David Lang wrote: >> On Tue, 1 Apr 2014, Jason Cooper wrote: >> Now I guess we need to think how to make it work without a framebuffer. I already suggested using the ASCII characters, but

Re: [RFC] QR encoding for Oops messages

2014-04-04 Thread Levente Kurusa
Hi, On 04/04/2014 05:12 PM, Jason Cooper wrote: > On Thu, Apr 03, 2014 at 10:21:39PM +0200, Levente Kurusa wrote: > ... >> Oh and I had an idea of adding a new kernel parameter, something >> like 'qr_oops.*'. (Looking for a better name! :-) ) >> Basically, I thought of the following options so

Re: [RFC] QR encoding for Oops messages

2014-04-04 Thread Jason Cooper
On Thu, Apr 03, 2014 at 01:57:04PM -0700, David Lang wrote: > On Tue, 1 Apr 2014, Jason Cooper wrote: > > >>Now I guess we need to think how to make it work without a > >>framebuffer. I already suggested using the ASCII characters, > >>but seeing the resolution of this QR code for example

Re: [RFC] QR encoding for Oops messages

2014-04-04 Thread Jason Cooper
On Thu, Apr 03, 2014 at 10:21:39PM +0200, Levente Kurusa wrote: ... > Oh and I had an idea of adding a new kernel parameter, something > like 'qr_oops.*'. (Looking for a better name! :-) ) > Basically, I thought of the following options so far: > > * qr_oops.disable=1 - disable it > *

Re: [RFC] QR encoding for Oops messages

2014-04-04 Thread Jason Cooper
On Thu, Apr 03, 2014 at 10:21:39PM +0200, Levente Kurusa wrote: ... Oh and I had an idea of adding a new kernel parameter, something like 'qr_oops.*'. (Looking for a better name! :-) ) Basically, I thought of the following options so far: * qr_oops.disable=1 - disable it *

Re: [RFC] QR encoding for Oops messages

2014-04-04 Thread Jason Cooper
On Thu, Apr 03, 2014 at 01:57:04PM -0700, David Lang wrote: On Tue, 1 Apr 2014, Jason Cooper wrote: Now I guess we need to think how to make it work without a framebuffer. I already suggested using the ASCII characters, but seeing the resolution of this QR code for example (147x147), made

Re: [RFC] QR encoding for Oops messages

2014-04-04 Thread Levente Kurusa
Hi, On 04/04/2014 05:12 PM, Jason Cooper wrote: On Thu, Apr 03, 2014 at 10:21:39PM +0200, Levente Kurusa wrote: ... Oh and I had an idea of adding a new kernel parameter, something like 'qr_oops.*'. (Looking for a better name! :-) ) Basically, I thought of the following options so far: *

Re: [RFC] QR encoding for Oops messages

2014-04-04 Thread Levente Kurusa
Hi, On 04/04/2014 05:15 PM, Jason Cooper wrote: On Thu, Apr 03, 2014 at 01:57:04PM -0700, David Lang wrote: On Tue, 1 Apr 2014, Jason Cooper wrote: Now I guess we need to think how to make it work without a framebuffer. I already suggested using the ASCII characters, but seeing the

Re: [RFC] QR encoding for Oops messages

2014-04-04 Thread Teodora Băluţă
On Fri, Apr 4, 2014 at 7:17 PM, Levente Kurusa le...@linux.com wrote: Hi, On 04/04/2014 05:15 PM, Jason Cooper wrote: On Thu, Apr 03, 2014 at 01:57:04PM -0700, David Lang wrote: On Tue, 1 Apr 2014, Jason Cooper wrote: Now I guess we need to think how to make it work without a framebuffer.

Re: [RFC] QR encoding for Oops messages

2014-04-03 Thread David Lang
On Tue, 1 Apr 2014, Jason Cooper wrote: Now I guess we need to think how to make it work without a framebuffer. I already suggested using the ASCII characters, but seeing the resolution of this QR code for example (147x147), made me realize that we can't shuffle that into a 80x25 textmode

Re: [RFC] QR encoding for Oops messages

2014-04-03 Thread Levente Kurusa
Hi, 2014-04-01 23:07 GMT+02:00 Teodora Băluţă : > On Tue, Apr 1, 2014 at 5:20 PM, Jason Cooper wrote: >> On Sun, Mar 30, 2014 at 12:17:17PM +0200, Levente Kurusa wrote: >>> Hi all, >>> >>> (sorry for the late reply, looks like this mail has ran away from my >>> clients) > > same here. > >>> >>>

Re: [RFC] QR encoding for Oops messages

2014-04-03 Thread Levente Kurusa
Hi, 2014-04-01 23:07 GMT+02:00 Teodora Băluţă teobal...@gmail.com: On Tue, Apr 1, 2014 at 5:20 PM, Jason Cooper ja...@lakedaemon.net wrote: On Sun, Mar 30, 2014 at 12:17:17PM +0200, Levente Kurusa wrote: Hi all, (sorry for the late reply, looks like this mail has ran away from my clients)

Re: [RFC] QR encoding for Oops messages

2014-04-03 Thread David Lang
On Tue, 1 Apr 2014, Jason Cooper wrote: Now I guess we need to think how to make it work without a framebuffer. I already suggested using the ASCII characters, but seeing the resolution of this QR code for example (147x147), made me realize that we can't shuffle that into a 80x25 textmode

Re: [RFC] QR encoding for Oops messages

2014-04-01 Thread Teodora Băluţă
On Tue, Apr 1, 2014 at 5:20 PM, Jason Cooper wrote: > On Sun, Mar 30, 2014 at 12:17:17PM +0200, Levente Kurusa wrote: >> Hi all, >> >> (sorry for the late reply, looks like this mail has ran away from my clients) same here. >> >> 2014-03-23 20:38 GMT+01:00 Jason Cooper : >> > All, >> > >> > On

Re: [RFC] QR encoding for Oops messages

2014-04-01 Thread Jason Cooper
On Sun, Mar 30, 2014 at 12:17:17PM +0200, Levente Kurusa wrote: > Hi all, > > (sorry for the late reply, looks like this mail has ran away from my clients) > > 2014-03-23 20:38 GMT+01:00 Jason Cooper : > > All, > > > > On Sat, Mar 22, 2014 at 08:20:01PM +0200, Teodora Băluţă wrote: > >> On Sat,

Re: [RFC] QR encoding for Oops messages

2014-04-01 Thread Jason Cooper
On Sun, Mar 30, 2014 at 12:17:17PM +0200, Levente Kurusa wrote: Hi all, (sorry for the late reply, looks like this mail has ran away from my clients) 2014-03-23 20:38 GMT+01:00 Jason Cooper ja...@lakedaemon.net: All, On Sat, Mar 22, 2014 at 08:20:01PM +0200, Teodora Băluţă wrote: On

Re: [RFC] QR encoding for Oops messages

2014-04-01 Thread Teodora Băluţă
On Tue, Apr 1, 2014 at 5:20 PM, Jason Cooper ja...@lakedaemon.net wrote: On Sun, Mar 30, 2014 at 12:17:17PM +0200, Levente Kurusa wrote: Hi all, (sorry for the late reply, looks like this mail has ran away from my clients) same here. 2014-03-23 20:38 GMT+01:00 Jason Cooper

Re: [RFC] QR encoding for Oops messages

2014-03-30 Thread Levente Kurusa
Hi all, (sorry for the late reply, looks like this mail has ran away from my clients) 2014-03-23 20:38 GMT+01:00 Jason Cooper : > All, > > On Sat, Mar 22, 2014 at 08:20:01PM +0200, Teodora Băluţă wrote: >> On Sat, Mar 22, 2014 at 7:09 PM, Levente Kurusa wrote: >> > On 03/21/2014 02:28 PM, Jason

Re: [RFC] QR encoding for Oops messages

2014-03-30 Thread Levente Kurusa
Hi all, (sorry for the late reply, looks like this mail has ran away from my clients) 2014-03-23 20:38 GMT+01:00 Jason Cooper ja...@lakedaemon.net: All, On Sat, Mar 22, 2014 at 08:20:01PM +0200, Teodora Băluţă wrote: On Sat, Mar 22, 2014 at 7:09 PM, Levente Kurusa le...@linux.com wrote: On

Re: [RFC] QR encoding for Oops messages

2014-03-23 Thread Jason Cooper
All, On Sat, Mar 22, 2014 at 08:20:01PM +0200, Teodora Băluţă wrote: > On Sat, Mar 22, 2014 at 7:09 PM, Levente Kurusa wrote: > > On 03/21/2014 02:28 PM, Jason Cooper wrote: ... > >> I would definitely like to see the QR output incorporated into a > >> kernel.org url. That would remove the need

Re: [RFC] QR encoding for Oops messages

2014-03-23 Thread Levente Kurusa
Hi, On 03/22/2014 07:29 PM, Levente Kurusa wrote: > Hi, > > On 03/22/2014 07:20 PM, Teodora Băluţă wrote: >> On Sat, Mar 22, 2014 at 7:09 PM, Levente Kurusa wrote: >>> Hi, >>> >>> On 03/21/2014 02:28 PM, Jason Cooper wrote: On Wed, Mar 19, 2014 at 10:38:30PM +0200, Teodora Băluţă wrote:

Re: [RFC] QR encoding for Oops messages

2014-03-23 Thread Levente Kurusa
Hi, On 03/22/2014 07:29 PM, Levente Kurusa wrote: Hi, On 03/22/2014 07:20 PM, Teodora Băluţă wrote: On Sat, Mar 22, 2014 at 7:09 PM, Levente Kurusa le...@linux.com wrote: Hi, On 03/21/2014 02:28 PM, Jason Cooper wrote: On Wed, Mar 19, 2014 at 10:38:30PM +0200, Teodora Băluţă wrote: On

Re: [RFC] QR encoding for Oops messages

2014-03-23 Thread Jason Cooper
All, On Sat, Mar 22, 2014 at 08:20:01PM +0200, Teodora Băluţă wrote: On Sat, Mar 22, 2014 at 7:09 PM, Levente Kurusa le...@linux.com wrote: On 03/21/2014 02:28 PM, Jason Cooper wrote: ... I would definitely like to see the QR output incorporated into a kernel.org url. That would remove

Re: [RFC] QR encoding for Oops messages

2014-03-22 Thread Levente Kurusa
Hi, On 03/22/2014 07:20 PM, Teodora Băluţă wrote: > On Sat, Mar 22, 2014 at 7:09 PM, Levente Kurusa wrote: >> Hi, >> >> On 03/21/2014 02:28 PM, Jason Cooper wrote: >>> On Wed, Mar 19, 2014 at 10:38:30PM +0200, Teodora Băluţă wrote: On Wed, Mar 19, 2014 at 10:18 PM, Dave Jones wrote: >

Re: [RFC] QR encoding for Oops messages

2014-03-22 Thread Teodora Băluţă
On Sat, Mar 22, 2014 at 7:09 PM, Levente Kurusa wrote: > Hi, > > On 03/21/2014 02:28 PM, Jason Cooper wrote: >> On Wed, Mar 19, 2014 at 10:38:30PM +0200, Teodora Băluţă wrote: >>> On Wed, Mar 19, 2014 at 10:18 PM, Dave Jones wrote: On Mon, Mar 17, 2014 at 02:59:47PM -0700, Teodora Baluta

Re: [RFC] QR encoding for Oops messages

2014-03-22 Thread Levente Kurusa
Hi, On 03/21/2014 02:28 PM, Jason Cooper wrote: > On Wed, Mar 19, 2014 at 10:38:30PM +0200, Teodora Băluţă wrote: >> On Wed, Mar 19, 2014 at 10:18 PM, Dave Jones wrote: >>> On Mon, Mar 17, 2014 at 02:59:47PM -0700, Teodora Baluta wrote: >>> > This feature encodes Oops messages into a QR barcode

Re: [RFC] QR encoding for Oops messages

2014-03-22 Thread Levente Kurusa
Hi, On 03/21/2014 02:28 PM, Jason Cooper wrote: On Wed, Mar 19, 2014 at 10:38:30PM +0200, Teodora Băluţă wrote: On Wed, Mar 19, 2014 at 10:18 PM, Dave Jones da...@redhat.com wrote: On Mon, Mar 17, 2014 at 02:59:47PM -0700, Teodora Baluta wrote: This feature encodes Oops messages into a QR

Re: [RFC] QR encoding for Oops messages

2014-03-22 Thread Teodora Băluţă
On Sat, Mar 22, 2014 at 7:09 PM, Levente Kurusa le...@linux.com wrote: Hi, On 03/21/2014 02:28 PM, Jason Cooper wrote: On Wed, Mar 19, 2014 at 10:38:30PM +0200, Teodora Băluţă wrote: On Wed, Mar 19, 2014 at 10:18 PM, Dave Jones da...@redhat.com wrote: On Mon, Mar 17, 2014 at 02:59:47PM

Re: [RFC] QR encoding for Oops messages

2014-03-22 Thread Levente Kurusa
Hi, On 03/22/2014 07:20 PM, Teodora Băluţă wrote: On Sat, Mar 22, 2014 at 7:09 PM, Levente Kurusa le...@linux.com wrote: Hi, On 03/21/2014 02:28 PM, Jason Cooper wrote: On Wed, Mar 19, 2014 at 10:38:30PM +0200, Teodora Băluţă wrote: On Wed, Mar 19, 2014 at 10:18 PM, Dave Jones

Re: [RFC] QR encoding for Oops messages

2014-03-21 Thread Jason Cooper
On Wed, Mar 19, 2014 at 10:38:30PM +0200, Teodora Băluţă wrote: > On Wed, Mar 19, 2014 at 10:18 PM, Dave Jones wrote: > > On Mon, Mar 17, 2014 at 02:59:47PM -0700, Teodora Baluta wrote: > > > This feature encodes Oops messages into a QR barcode that is scannable by > > > any device with a

Re: [RFC] QR encoding for Oops messages

2014-03-21 Thread Jason Cooper
On Wed, Mar 19, 2014 at 10:38:30PM +0200, Teodora Băluţă wrote: On Wed, Mar 19, 2014 at 10:18 PM, Dave Jones da...@redhat.com wrote: On Mon, Mar 17, 2014 at 02:59:47PM -0700, Teodora Baluta wrote: This feature encodes Oops messages into a QR barcode that is scannable by any device with

Re: [RFC] QR encoding for Oops messages

2014-03-19 Thread Levente Kurusa
Hi, 2014-03-19 21:50 GMT+01:00 Teodora Băluţă : > On Wed, Mar 19, 2014 at 10:28 PM, Levente Kurusa wrote: >> Hi, >> >> 2014-03-19 21:18 GMT+01:00 Dave Jones : >>> On Mon, Mar 17, 2014 at 02:59:47PM -0700, Teodora Baluta wrote: >>> > This feature encodes Oops messages into a QR barcode that is

Re: [RFC] QR encoding for Oops messages

2014-03-19 Thread Teodora Băluţă
On Wed, Mar 19, 2014 at 10:50 PM, Teodora Băluţă wrote: > On Wed, Mar 19, 2014 at 10:28 PM, Levente Kurusa wrote: >> Hi, >> >> 2014-03-19 21:18 GMT+01:00 Dave Jones : >>> On Mon, Mar 17, 2014 at 02:59:47PM -0700, Teodora Baluta wrote: >>> > This feature encodes Oops messages into a QR barcode

Re: [RFC] QR encoding for Oops messages

2014-03-19 Thread Teodora Băluţă
On Wed, Mar 19, 2014 at 10:28 PM, Levente Kurusa wrote: > Hi, > > 2014-03-19 21:18 GMT+01:00 Dave Jones : >> On Mon, Mar 17, 2014 at 02:59:47PM -0700, Teodora Baluta wrote: >> > This feature encodes Oops messages into a QR barcode that is scannable by >> > any device with a camera. >> >> ...

Re: [RFC] QR encoding for Oops messages

2014-03-19 Thread Teodora Băluţă
On Wed, Mar 19, 2014 at 10:18 PM, Dave Jones wrote: > On Mon, Mar 17, 2014 at 02:59:47PM -0700, Teodora Baluta wrote: > > This feature encodes Oops messages into a QR barcode that is scannable by > > any device with a camera. > > ... > > > include/linux/print_oops.h | 11 + > >

Re: [RFC] QR encoding for Oops messages

2014-03-19 Thread Levente Kurusa
Hi, 2014-03-19 21:18 GMT+01:00 Dave Jones : > On Mon, Mar 17, 2014 at 02:59:47PM -0700, Teodora Baluta wrote: > > This feature encodes Oops messages into a QR barcode that is scannable by > > any device with a camera. > > ... > > > include/linux/print_oops.h | 11 + > >

Re: [RFC] QR encoding for Oops messages

2014-03-19 Thread Dave Jones
On Mon, Mar 17, 2014 at 02:59:47PM -0700, Teodora Baluta wrote: > This feature encodes Oops messages into a QR barcode that is scannable by > any device with a camera. ... > include/linux/print_oops.h | 11 + > include/linux/qrencode.h | 546 + > kernel/Makefile

Re: [RFC] QR encoding for Oops messages

2014-03-19 Thread Teodora Băluţă
On Wed, Mar 19, 2014 at 8:03 PM, Borislav Petkov wrote: > On Mon, Mar 17, 2014 at 02:59:47PM -0700, Teodora Baluta wrote: >> This feature encodes Oops messages into a QR barcode that is scannable by >> any device with a camera. >> >> If the config option for this feature is enabled, then when an

Re: [RFC] QR encoding for Oops messages

2014-03-19 Thread Teodora Băluţă
On Tue, Mar 18, 2014 at 11:49 PM, Matthew Garrett wrote: > 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

Re: [RFC] QR encoding for Oops messages

2014-03-19 Thread Borislav Petkov
On Mon, Mar 17, 2014 at 02:59:47PM -0700, Teodora Baluta wrote: > This feature encodes Oops messages into a QR barcode that is scannable by > any device with a camera. > > If the config option for this feature is enabled, then when an Oops is > in progress, the printk() calls' strings are

Re: [RFC] QR encoding for Oops messages

2014-03-19 Thread Borislav Petkov
On Mon, Mar 17, 2014 at 02:59:47PM -0700, Teodora Baluta wrote: This feature encodes Oops messages into a QR barcode that is scannable by any device with a camera. If the config option for this feature is enabled, then when an Oops is in progress, the printk() calls' strings are buffered.

Re: [RFC] QR encoding for Oops messages

2014-03-19 Thread Teodora Băluţă
On Tue, Mar 18, 2014 at 11:49 PM, Matthew Garrett mj...@srcf.ucam.org wrote: 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

Re: [RFC] QR encoding for Oops messages

2014-03-19 Thread Dave Jones
On Mon, Mar 17, 2014 at 02:59:47PM -0700, Teodora Baluta wrote: This feature encodes Oops messages into a QR barcode that is scannable by any device with a camera. ... include/linux/print_oops.h | 11 + include/linux/qrencode.h | 546 + kernel/Makefile|

Re: [RFC] QR encoding for Oops messages

2014-03-19 Thread Levente Kurusa
Hi, 2014-03-19 21:18 GMT+01:00 Dave Jones da...@redhat.com: On Mon, Mar 17, 2014 at 02:59:47PM -0700, Teodora Baluta wrote: This feature encodes Oops messages into a QR barcode that is scannable by any device with a camera. ... include/linux/print_oops.h | 11 +

Re: [RFC] QR encoding for Oops messages

2014-03-19 Thread Teodora Băluţă
On Wed, Mar 19, 2014 at 8:03 PM, Borislav Petkov b...@alien8.de wrote: On Mon, Mar 17, 2014 at 02:59:47PM -0700, Teodora Baluta wrote: This feature encodes Oops messages into a QR barcode that is scannable by any device with a camera. If the config option for this feature is enabled, then

Re: [RFC] QR encoding for Oops messages

2014-03-19 Thread Teodora Băluţă
On Wed, Mar 19, 2014 at 10:18 PM, Dave Jones da...@redhat.com wrote: On Mon, Mar 17, 2014 at 02:59:47PM -0700, Teodora Baluta wrote: This feature encodes Oops messages into a QR barcode that is scannable by any device with a camera. ... include/linux/print_oops.h | 11 +

Re: [RFC] QR encoding for Oops messages

2014-03-19 Thread Teodora Băluţă
On Wed, Mar 19, 2014 at 10:28 PM, Levente Kurusa le...@linux.com wrote: Hi, 2014-03-19 21:18 GMT+01:00 Dave Jones da...@redhat.com: On Mon, Mar 17, 2014 at 02:59:47PM -0700, Teodora Baluta wrote: This feature encodes Oops messages into a QR barcode that is scannable by any device with a

Re: [RFC] QR encoding for Oops messages

2014-03-19 Thread Teodora Băluţă
On Wed, Mar 19, 2014 at 10:50 PM, Teodora Băluţă teobal...@gmail.com wrote: On Wed, Mar 19, 2014 at 10:28 PM, Levente Kurusa le...@linux.com wrote: Hi, 2014-03-19 21:18 GMT+01:00 Dave Jones da...@redhat.com: On Mon, Mar 17, 2014 at 02:59:47PM -0700, Teodora Baluta wrote: This feature

Re: [RFC] QR encoding for Oops messages

2014-03-19 Thread Levente Kurusa
Hi, 2014-03-19 21:50 GMT+01:00 Teodora Băluţă teobal...@gmail.com: On Wed, Mar 19, 2014 at 10:28 PM, Levente Kurusa le...@linux.com wrote: Hi, 2014-03-19 21:18 GMT+01:00 Dave Jones da...@redhat.com: On Mon, Mar 17, 2014 at 02:59:47PM -0700, Teodora Baluta wrote: This feature encodes Oops

Re: [RFC] QR encoding for Oops messages

2014-03-18 Thread Matthew Garrett
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 >

Re: [RFC] QR encoding for Oops messages

2014-03-18 Thread Matthew Garrett
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