Fixes the following warning:
drivers/staging/wlags49_h2/sta_h2.c:4471:10: warning: symbol 'fw_image' was not
declared. Should it be static?
Signed-off-by: Luis Ortega
---
drivers/staging/wlags49_h2/sta_h2.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drive
Fixed badly placed and unnecessary braces.
PS: Performed as task 10 of the Eudyptula Challenge.
Signed-off-by: Luis Ortega
---
Changes for v2:
- Removed accidental
---
drivers/staging/bcm/Qos.c | 174 +-
1 file changed, 48 insertions(+), 126
On Tue, Apr 8, 2014 at 11:11 PM, Greg KH wrote:
>
> Why the before the '{' character?
It must have slipped in accidentally. Feel free to remove.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at
Fixed badly placed and unnecessary braces.
PS: Performed as task 10 of the Eudyptula Challenge.
Signed-off-by: Luis Ortega
---
drivers/staging/bcm/Qos.c | 174 +-
1 file changed, 48 insertions(+), 126 deletions(-)
diff --git a/drivers/staging/bcm
> On Fri, Feb 14, 2014 at 09:09:52AM +0200, Jani Nikula wrote:
>
> It seems that it will be better to track this in bugzilla rather than
> the mailing lists. Please file a bug on DRM/Intel component at
> https://bugs.freedesktop.org/enter_bug.cgi?product=DRI. Attach these
> files.
Done. We can co
troller (rev 03)
> Please provide dmesg with drm.debug=0xe with 3.14-rc2.
Care to explain a bit more before I recompile 3.14-rc2? Do I need to
enable some particular debug option? How do I proceed for drm.debug=0xe?
Luis
> On Thu, Feb 13, 2014 at 05:04:23PM +0200, Jani Nikula wrote:
> On T
Hi, testing 3.14-rc2 I noticed I could not adjust the brightness of the
screen any longer. This problem is already present in 3.14-rc1. 3.13 works fine.
My hardware is a netbook with intel atom and a 945GM graphics card.
I bisected the problem down to the next commit:
bc0bb9fd1c7810407ab810d204b
January 2014 19:46:11 Luis Ortega wrote:
>> Fixed lines exceeding 80 characters long wherever possible,
>> as per the coding style.
>>
>> Signed-off-by: Luis Ortega
>
> checkpatch did not complain on the initial submission, so I guess it's more an
> issue of tas
Fixed a few spelling errors.
Signed-off-by: Luis Ortega
---
drivers/input/touchscreen/zforce_ts.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/drivers/input/touchscreen/zforce_ts.c
b/drivers/input/touchscreen/zforce_ts.c
index 2175f34..c145c1d 100644
--- a
12 to 257 bytes.
Signed-off-by: Luis Ortega
---
drivers/input/touchscreen/zforce_ts.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/input/touchscreen/zforce_ts.c
b/drivers/input/touchscreen/zforce_ts.c
index e082d5c..afb2492 100644
--- a/drivers/input/touchs
value from the buffer, these
checks are unnecessary and we should simply compare against zero.
Signed-off-by: Luis Ortega
---
drivers/input/touchscreen/zforce_ts.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/input/touchscreen/zforce_ts.c
b/drivers/input/touchscreen
Fixed lines exceeding 80 characters long wherever possible,
as per the coding style.
Signed-off-by: Luis Ortega
---
drivers/input/touchscreen/zforce_ts.c | 19 ---
1 file changed, 12 insertions(+), 7 deletions(-)
diff --git a/drivers/input/touchscreen/zforce_ts.c
b/drivers
As a kernel newbie and owner of a Barnes & Noble e-reader I was
curious to review this driver to learn more about the touchscreen.
The first two patches are fairly innocuous whereas the last two
slightly modify the code to fix two small issues I discovered.
I don't have the setup to test them but
Fixed coding style issue where lines are indented with spaces
instead of tabs.
Signed-off-by: Luis Ortega Perez de Villar
---
drivers/staging/dwc2/core.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/dwc2/core.c b/drivers/staging/dwc2/core.c
index
14 matches
Mail list logo
