/openbmc/linux/drivers/media/usb/em28xx/ |
H A D | em28xx-v4l.h | fdf1bc9f Fri Nov 28 05:34:15 CST 2014 Mauro Carvalho Chehab <mchehab@osg.samsung.com> [media] em28xx: checkpatch cleanup: whitespaces/new lines cleanups
This patch is basically produced while testing a tool that Joe Perches sent upstream sometime ago: https://lkml.org/lkml/2014/7/11/794
I used it with those arguments: $ reformat_with_checkpatch.sh drivers/media/usb/em28xx/em28xx*.[ch]
It actually produced 24 patches, with is too much, and showed interesting things: gcc produced different codes on most of the patches, even with just linespace changes. The total code data remained the same on all cases I checked though.
Anyway, provided that we fold the resulting patches, this tool seems useful.
Signed-off-by: Mauro Carvalho Chehab <mchehab@osg.samsung.com> fdf1bc9f Fri Nov 28 05:34:15 CST 2014 Mauro Carvalho Chehab <mchehab@osg.samsung.com> [media] em28xx: checkpatch cleanup: whitespaces/new lines cleanups This patch is basically produced while testing a tool that Joe Perches sent upstream sometime ago: https://lkml.org/lkml/2014/7/11/794 I used it with those arguments: $ reformat_with_checkpatch.sh drivers/media/usb/em28xx/em28xx*.[ch] It actually produced 24 patches, with is too much, and showed interesting things: gcc produced different codes on most of the patches, even with just linespace changes. The total code data remained the same on all cases I checked though. Anyway, provided that we fold the resulting patches, this tool seems useful. Signed-off-by: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
|
H A D | em28xx-vbi.c | fdf1bc9f Fri Nov 28 05:34:15 CST 2014 Mauro Carvalho Chehab <mchehab@osg.samsung.com> [media] em28xx: checkpatch cleanup: whitespaces/new lines cleanups
This patch is basically produced while testing a tool that Joe Perches sent upstream sometime ago: https://lkml.org/lkml/2014/7/11/794
I used it with those arguments: $ reformat_with_checkpatch.sh drivers/media/usb/em28xx/em28xx*.[ch]
It actually produced 24 patches, with is too much, and showed interesting things: gcc produced different codes on most of the patches, even with just linespace changes. The total code data remained the same on all cases I checked though.
Anyway, provided that we fold the resulting patches, this tool seems useful.
Signed-off-by: Mauro Carvalho Chehab <mchehab@osg.samsung.com> fdf1bc9f Fri Nov 28 05:34:15 CST 2014 Mauro Carvalho Chehab <mchehab@osg.samsung.com> [media] em28xx: checkpatch cleanup: whitespaces/new lines cleanups This patch is basically produced while testing a tool that Joe Perches sent upstream sometime ago: https://lkml.org/lkml/2014/7/11/794 I used it with those arguments: $ reformat_with_checkpatch.sh drivers/media/usb/em28xx/em28xx*.[ch] It actually produced 24 patches, with is too much, and showed interesting things: gcc produced different codes on most of the patches, even with just linespace changes. The total code data remained the same on all cases I checked though. Anyway, provided that we fold the resulting patches, this tool seems useful. Signed-off-by: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
|
H A D | em28xx-reg.h | fdf1bc9f Fri Nov 28 05:34:15 CST 2014 Mauro Carvalho Chehab <mchehab@osg.samsung.com> [media] em28xx: checkpatch cleanup: whitespaces/new lines cleanups
This patch is basically produced while testing a tool that Joe Perches sent upstream sometime ago: https://lkml.org/lkml/2014/7/11/794
I used it with those arguments: $ reformat_with_checkpatch.sh drivers/media/usb/em28xx/em28xx*.[ch]
It actually produced 24 patches, with is too much, and showed interesting things: gcc produced different codes on most of the patches, even with just linespace changes. The total code data remained the same on all cases I checked though.
Anyway, provided that we fold the resulting patches, this tool seems useful.
Signed-off-by: Mauro Carvalho Chehab <mchehab@osg.samsung.com> fdf1bc9f Fri Nov 28 05:34:15 CST 2014 Mauro Carvalho Chehab <mchehab@osg.samsung.com> [media] em28xx: checkpatch cleanup: whitespaces/new lines cleanups This patch is basically produced while testing a tool that Joe Perches sent upstream sometime ago: https://lkml.org/lkml/2014/7/11/794 I used it with those arguments: $ reformat_with_checkpatch.sh drivers/media/usb/em28xx/em28xx*.[ch] It actually produced 24 patches, with is too much, and showed interesting things: gcc produced different codes on most of the patches, even with just linespace changes. The total code data remained the same on all cases I checked though. Anyway, provided that we fold the resulting patches, this tool seems useful. Signed-off-by: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
|
H A D | em28xx-camera.c | fdf1bc9f Fri Nov 28 05:34:15 CST 2014 Mauro Carvalho Chehab <mchehab@osg.samsung.com> [media] em28xx: checkpatch cleanup: whitespaces/new lines cleanups
This patch is basically produced while testing a tool that Joe Perches sent upstream sometime ago: https://lkml.org/lkml/2014/7/11/794
I used it with those arguments: $ reformat_with_checkpatch.sh drivers/media/usb/em28xx/em28xx*.[ch]
It actually produced 24 patches, with is too much, and showed interesting things: gcc produced different codes on most of the patches, even with just linespace changes. The total code data remained the same on all cases I checked though.
Anyway, provided that we fold the resulting patches, this tool seems useful.
Signed-off-by: Mauro Carvalho Chehab <mchehab@osg.samsung.com> fdf1bc9f Fri Nov 28 05:34:15 CST 2014 Mauro Carvalho Chehab <mchehab@osg.samsung.com> [media] em28xx: checkpatch cleanup: whitespaces/new lines cleanups This patch is basically produced while testing a tool that Joe Perches sent upstream sometime ago: https://lkml.org/lkml/2014/7/11/794 I used it with those arguments: $ reformat_with_checkpatch.sh drivers/media/usb/em28xx/em28xx*.[ch] It actually produced 24 patches, with is too much, and showed interesting things: gcc produced different codes on most of the patches, even with just linespace changes. The total code data remained the same on all cases I checked though. Anyway, provided that we fold the resulting patches, this tool seems useful. Signed-off-by: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
|
H A D | em28xx-i2c.c | fdf1bc9f Fri Nov 28 05:34:15 CST 2014 Mauro Carvalho Chehab <mchehab@osg.samsung.com> [media] em28xx: checkpatch cleanup: whitespaces/new lines cleanups
This patch is basically produced while testing a tool that Joe Perches sent upstream sometime ago: https://lkml.org/lkml/2014/7/11/794
I used it with those arguments: $ reformat_with_checkpatch.sh drivers/media/usb/em28xx/em28xx*.[ch]
It actually produced 24 patches, with is too much, and showed interesting things: gcc produced different codes on most of the patches, even with just linespace changes. The total code data remained the same on all cases I checked though.
Anyway, provided that we fold the resulting patches, this tool seems useful.
Signed-off-by: Mauro Carvalho Chehab <mchehab@osg.samsung.com> fdf1bc9f Fri Nov 28 05:34:15 CST 2014 Mauro Carvalho Chehab <mchehab@osg.samsung.com> [media] em28xx: checkpatch cleanup: whitespaces/new lines cleanups This patch is basically produced while testing a tool that Joe Perches sent upstream sometime ago: https://lkml.org/lkml/2014/7/11/794 I used it with those arguments: $ reformat_with_checkpatch.sh drivers/media/usb/em28xx/em28xx*.[ch] It actually produced 24 patches, with is too much, and showed interesting things: gcc produced different codes on most of the patches, even with just linespace changes. The total code data remained the same on all cases I checked though. Anyway, provided that we fold the resulting patches, this tool seems useful. Signed-off-by: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
|
H A D | em28xx-audio.c | fdf1bc9f Fri Nov 28 05:34:15 CST 2014 Mauro Carvalho Chehab <mchehab@osg.samsung.com> [media] em28xx: checkpatch cleanup: whitespaces/new lines cleanups
This patch is basically produced while testing a tool that Joe Perches sent upstream sometime ago: https://lkml.org/lkml/2014/7/11/794
I used it with those arguments: $ reformat_with_checkpatch.sh drivers/media/usb/em28xx/em28xx*.[ch]
It actually produced 24 patches, with is too much, and showed interesting things: gcc produced different codes on most of the patches, even with just linespace changes. The total code data remained the same on all cases I checked though.
Anyway, provided that we fold the resulting patches, this tool seems useful.
Signed-off-by: Mauro Carvalho Chehab <mchehab@osg.samsung.com> fdf1bc9f Fri Nov 28 05:34:15 CST 2014 Mauro Carvalho Chehab <mchehab@osg.samsung.com> [media] em28xx: checkpatch cleanup: whitespaces/new lines cleanups This patch is basically produced while testing a tool that Joe Perches sent upstream sometime ago: https://lkml.org/lkml/2014/7/11/794 I used it with those arguments: $ reformat_with_checkpatch.sh drivers/media/usb/em28xx/em28xx*.[ch] It actually produced 24 patches, with is too much, and showed interesting things: gcc produced different codes on most of the patches, even with just linespace changes. The total code data remained the same on all cases I checked though. Anyway, provided that we fold the resulting patches, this tool seems useful. Signed-off-by: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
|
H A D | em28xx-input.c | fdf1bc9f Fri Nov 28 05:34:15 CST 2014 Mauro Carvalho Chehab <mchehab@osg.samsung.com> [media] em28xx: checkpatch cleanup: whitespaces/new lines cleanups
This patch is basically produced while testing a tool that Joe Perches sent upstream sometime ago: https://lkml.org/lkml/2014/7/11/794
I used it with those arguments: $ reformat_with_checkpatch.sh drivers/media/usb/em28xx/em28xx*.[ch]
It actually produced 24 patches, with is too much, and showed interesting things: gcc produced different codes on most of the patches, even with just linespace changes. The total code data remained the same on all cases I checked though.
Anyway, provided that we fold the resulting patches, this tool seems useful.
Signed-off-by: Mauro Carvalho Chehab <mchehab@osg.samsung.com> fdf1bc9f Fri Nov 28 05:34:15 CST 2014 Mauro Carvalho Chehab <mchehab@osg.samsung.com> [media] em28xx: checkpatch cleanup: whitespaces/new lines cleanups This patch is basically produced while testing a tool that Joe Perches sent upstream sometime ago: https://lkml.org/lkml/2014/7/11/794 I used it with those arguments: $ reformat_with_checkpatch.sh drivers/media/usb/em28xx/em28xx*.[ch] It actually produced 24 patches, with is too much, and showed interesting things: gcc produced different codes on most of the patches, even with just linespace changes. The total code data remained the same on all cases I checked though. Anyway, provided that we fold the resulting patches, this tool seems useful. Signed-off-by: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
|
H A D | em28xx-core.c | fdf1bc9f Fri Nov 28 05:34:15 CST 2014 Mauro Carvalho Chehab <mchehab@osg.samsung.com> [media] em28xx: checkpatch cleanup: whitespaces/new lines cleanups
This patch is basically produced while testing a tool that Joe Perches sent upstream sometime ago: https://lkml.org/lkml/2014/7/11/794
I used it with those arguments: $ reformat_with_checkpatch.sh drivers/media/usb/em28xx/em28xx*.[ch]
It actually produced 24 patches, with is too much, and showed interesting things: gcc produced different codes on most of the patches, even with just linespace changes. The total code data remained the same on all cases I checked though.
Anyway, provided that we fold the resulting patches, this tool seems useful.
Signed-off-by: Mauro Carvalho Chehab <mchehab@osg.samsung.com> fdf1bc9f Fri Nov 28 05:34:15 CST 2014 Mauro Carvalho Chehab <mchehab@osg.samsung.com> [media] em28xx: checkpatch cleanup: whitespaces/new lines cleanups This patch is basically produced while testing a tool that Joe Perches sent upstream sometime ago: https://lkml.org/lkml/2014/7/11/794 I used it with those arguments: $ reformat_with_checkpatch.sh drivers/media/usb/em28xx/em28xx*.[ch] It actually produced 24 patches, with is too much, and showed interesting things: gcc produced different codes on most of the patches, even with just linespace changes. The total code data remained the same on all cases I checked though. Anyway, provided that we fold the resulting patches, this tool seems useful. Signed-off-by: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
|
H A D | em28xx-dvb.c | fdf1bc9f Fri Nov 28 05:34:15 CST 2014 Mauro Carvalho Chehab <mchehab@osg.samsung.com> [media] em28xx: checkpatch cleanup: whitespaces/new lines cleanups
This patch is basically produced while testing a tool that Joe Perches sent upstream sometime ago: https://lkml.org/lkml/2014/7/11/794
I used it with those arguments: $ reformat_with_checkpatch.sh drivers/media/usb/em28xx/em28xx*.[ch]
It actually produced 24 patches, with is too much, and showed interesting things: gcc produced different codes on most of the patches, even with just linespace changes. The total code data remained the same on all cases I checked though.
Anyway, provided that we fold the resulting patches, this tool seems useful.
Signed-off-by: Mauro Carvalho Chehab <mchehab@osg.samsung.com> fdf1bc9f Fri Nov 28 05:34:15 CST 2014 Mauro Carvalho Chehab <mchehab@osg.samsung.com> [media] em28xx: checkpatch cleanup: whitespaces/new lines cleanups This patch is basically produced while testing a tool that Joe Perches sent upstream sometime ago: https://lkml.org/lkml/2014/7/11/794 I used it with those arguments: $ reformat_with_checkpatch.sh drivers/media/usb/em28xx/em28xx*.[ch] It actually produced 24 patches, with is too much, and showed interesting things: gcc produced different codes on most of the patches, even with just linespace changes. The total code data remained the same on all cases I checked though. Anyway, provided that we fold the resulting patches, this tool seems useful. Signed-off-by: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
|
H A D | em28xx.h | fdf1bc9f Fri Nov 28 05:34:15 CST 2014 Mauro Carvalho Chehab <mchehab@osg.samsung.com> [media] em28xx: checkpatch cleanup: whitespaces/new lines cleanups
This patch is basically produced while testing a tool that Joe Perches sent upstream sometime ago: https://lkml.org/lkml/2014/7/11/794
I used it with those arguments: $ reformat_with_checkpatch.sh drivers/media/usb/em28xx/em28xx*.[ch]
It actually produced 24 patches, with is too much, and showed interesting things: gcc produced different codes on most of the patches, even with just linespace changes. The total code data remained the same on all cases I checked though.
Anyway, provided that we fold the resulting patches, this tool seems useful.
Signed-off-by: Mauro Carvalho Chehab <mchehab@osg.samsung.com> fdf1bc9f Fri Nov 28 05:34:15 CST 2014 Mauro Carvalho Chehab <mchehab@osg.samsung.com> [media] em28xx: checkpatch cleanup: whitespaces/new lines cleanups This patch is basically produced while testing a tool that Joe Perches sent upstream sometime ago: https://lkml.org/lkml/2014/7/11/794 I used it with those arguments: $ reformat_with_checkpatch.sh drivers/media/usb/em28xx/em28xx*.[ch] It actually produced 24 patches, with is too much, and showed interesting things: gcc produced different codes on most of the patches, even with just linespace changes. The total code data remained the same on all cases I checked though. Anyway, provided that we fold the resulting patches, this tool seems useful. Signed-off-by: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
|
H A D | em28xx-cards.c | fdf1bc9f Fri Nov 28 05:34:15 CST 2014 Mauro Carvalho Chehab <mchehab@osg.samsung.com> [media] em28xx: checkpatch cleanup: whitespaces/new lines cleanups
This patch is basically produced while testing a tool that Joe Perches sent upstream sometime ago: https://lkml.org/lkml/2014/7/11/794
I used it with those arguments: $ reformat_with_checkpatch.sh drivers/media/usb/em28xx/em28xx*.[ch]
It actually produced 24 patches, with is too much, and showed interesting things: gcc produced different codes on most of the patches, even with just linespace changes. The total code data remained the same on all cases I checked though.
Anyway, provided that we fold the resulting patches, this tool seems useful.
Signed-off-by: Mauro Carvalho Chehab <mchehab@osg.samsung.com> fdf1bc9f Fri Nov 28 05:34:15 CST 2014 Mauro Carvalho Chehab <mchehab@osg.samsung.com> [media] em28xx: checkpatch cleanup: whitespaces/new lines cleanups This patch is basically produced while testing a tool that Joe Perches sent upstream sometime ago: https://lkml.org/lkml/2014/7/11/794 I used it with those arguments: $ reformat_with_checkpatch.sh drivers/media/usb/em28xx/em28xx*.[ch] It actually produced 24 patches, with is too much, and showed interesting things: gcc produced different codes on most of the patches, even with just linespace changes. The total code data remained the same on all cases I checked though. Anyway, provided that we fold the resulting patches, this tool seems useful. Signed-off-by: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
|
H A D | em28xx-video.c | fdf1bc9f Fri Nov 28 05:34:15 CST 2014 Mauro Carvalho Chehab <mchehab@osg.samsung.com> [media] em28xx: checkpatch cleanup: whitespaces/new lines cleanups
This patch is basically produced while testing a tool that Joe Perches sent upstream sometime ago: https://lkml.org/lkml/2014/7/11/794
I used it with those arguments: $ reformat_with_checkpatch.sh drivers/media/usb/em28xx/em28xx*.[ch]
It actually produced 24 patches, with is too much, and showed interesting things: gcc produced different codes on most of the patches, even with just linespace changes. The total code data remained the same on all cases I checked though.
Anyway, provided that we fold the resulting patches, this tool seems useful.
Signed-off-by: Mauro Carvalho Chehab <mchehab@osg.samsung.com> fdf1bc9f Fri Nov 28 05:34:15 CST 2014 Mauro Carvalho Chehab <mchehab@osg.samsung.com> [media] em28xx: checkpatch cleanup: whitespaces/new lines cleanups This patch is basically produced while testing a tool that Joe Perches sent upstream sometime ago: https://lkml.org/lkml/2014/7/11/794 I used it with those arguments: $ reformat_with_checkpatch.sh drivers/media/usb/em28xx/em28xx*.[ch] It actually produced 24 patches, with is too much, and showed interesting things: gcc produced different codes on most of the patches, even with just linespace changes. The total code data remained the same on all cases I checked though. Anyway, provided that we fold the resulting patches, this tool seems useful. Signed-off-by: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
|