On Friday, June 14, 2013 12:32:27 AM Jiang Liu wrote:
Initialize acpi_dock_notifier_list from function acpi_dock_init()
instead of dock_add() to avoid initializing it multiple times.
Well, makes sense.
Thanks,
Rafael
Signed-off-by: Jiang Liu jiang@huawei.com
Cc: Shaohua Li
On Friday, June 14, 2013 12:32:28 AM Jiang Liu wrote:
All dock device related data structures are created during driver
initialization, so kill the redundant spin lock in dock device object.
As a cleanup, it definitely makes sense, but does it fix anything?
Rafael
Signed-off-by: Jiang Liu
On Thu, Jun 13, 2013 at 6:38 PM, Doug Anderson diand...@chromium.org wrote:
A level-triggered interrupt should be acked after the interrupt line
becomes inactive and before it is unmasked, or else another interrupt
will be immediately triggered. Acking before or after calling the
handler is
On Friday, June 14, 2013 12:32:29 AM Jiang Liu wrote:
Mark all initialization functions with __init to reduce memory
consumption at runtime.
Again, this is a *cleanup*, not a fix. Please don't mix cleanups with fixes,
especially with ones you want to go into 3.10, because the cleanups aren't
On Wed, Jun 12, 2013 at 04:54:37PM +0300, Oded Gabbay wrote:
The P2020 has a non-standard implementation of the SDHCI_HOST_CONTROL
register. This patch adds a QUIRK in the SDHCI header to signal that
a host controller has a non-standard SDHCI_HOST_CONTROL register. The
patch adds a check to
On Thu, Jun 13, 2013 at 12:33:13AM +0200, Lars-Peter Clausen wrote:
On 06/12/2013 09:59 PM, Thierry Reding wrote:
On Wed, Jun 12, 2013 at 05:05:18PM +0530, Sachin Kamat wrote:
Hi Thierry,
On 12 June 2013 16:59, Thierry Reding thierry.red...@gmail.com wrote:
Some drivers don't set the
On Thu, Jun 13, 2013 at 5:37 PM, Alexey Brodkin
alexey.brod...@synopsys.com wrote:
Driver for non-standard on-chip ethernet device ARC EMAC 10/100,
instantiated in some legacy ARC (Synopsys) FPGA Boards such as
ARCAngel4/ML50x.
Much better. But still few comments below.
+++
On Thu, Jun 13, 2013 at 7:25 PM, Doug Anderson diand...@chromium.org wrote:
+PIN CONTROLLER - SAMSUNG
+M: Linus Walleij linus.wall...@linaro.org
+M: Kukjin Kim kgene@samsung.com
So actually this would be:
M: Thomas Abraham thomas.abra...@linaro.org
M: Tomasz Figa
On Thu, Jun 13, 2013 at 10:55:17AM +0530, Sachin Kamat wrote:
On 13 June 2013 03:01, Marc Kleine-Budde m...@pengutronix.de wrote:
Commit 75096579c3ac (lib: devres: Introduce devm_ioremap_resource())
introduced devm_ioremap_resource() and encourage to check its return value
with
IS_ERR().
On Friday, June 14, 2013 12:32:31 AM Jiang Liu wrote:
Introduce several helper functions, which will be used to simplify code.
Signed-off-by: Jiang Liu jiang@huawei.com
Again, this is not 3.10 material.
And you could easily say three instead of several in the changelog. :-)
Thanks,
2013/6/13 Alexander E. Patrakov patra...@gmail.com:
2013/6/13 Jiang Liu jiang@huawei.com:
Alexander E. Patrakov patra...@gmail.com reports two bugs related to
dock station support on Sony VAIO VPCZ23A4R. Actually there are at least
four bugs related to Sony VAIO VPCZ23A4R dock support.
1)
From: Onur Atilla oati...@gmail.com
The rate table of the proximity sensor has included
one incorrect value that is not supported by the HW.
This value is now corrected from 25Hz to 20Hz. The
corresponding rate in the time table is corrected to
50ms accordingly.
Signed-off-by: Onur Atilla
prox_read_result() has been split in two functions:
- ps_get_result(): reads the proximity value from the register
- prox_read_result(): applies the logic above the proximity value
Signed-off-by: Andi Shyti a...@etezian.org
---
drivers/misc/bh1770glc.c | 53
the prox0_raw file in the sysfs interface reads the proximity
value directly from the register instead of reporting the last
read value; in this way userspace applications can have a real
time value
Signed-off-by: Andi Shyti a...@etezian.org
---
drivers/misc/bh1770glc.c |5 +
1 file
From: Onur Atilla oati...@gmail.com
lux0_raw file gives the raw Ambient Light Sensor (ALS) value,
before adjusting it with the calibration coefficients, whereas
lux0_inputreturns the calibrated ALS value.
Signed-off-by: Onur Atilla oati...@gmail.com
Signed-off-by: Andi Shyti a...@etezian.org
---
From: Onur Atilla oati...@gmail.com
The Ambient Light Sensor (ALS) glass attenuation parameter should
be configurable and two new parameters are introduced:
als_scf_BH1770 and als_scf_SFH7770.
Signed-off-by: Onur Atilla oati...@gmail.com
Signed-off-by: Andi Shyti a...@etezian.org
---
From: Onur Atilla oati...@gmail.com
Introduced lux0_glass_factor and lux0_comp_factor on sysfs
lux0_glass_factor and lux0_sensor_comp_factor are provided as
read-only files on the sysfs structure of the bh1770glc optical sensor.
Signed-off-by: Onur Atilla oati...@gmail.com
Signed-off-by: Andi
On Thursday, June 13, 2013 08:26:10 PM Rafael J. Wysocki wrote:
On Friday, June 14, 2013 12:32:26 AM Jiang Liu wrote:
ACPI dock driver can't be built as a module any more, so clean up
module related code.
Signed-off-by: Jiang Liu jiang@huawei.com
Cc: Shaohua Li shaohua...@intel.com
On Friday, June 14, 2013 12:32:32 AM Jiang Liu wrote:
Use new helper functions to simpilify ACPI dock, acpiphp code.
Signed-off-by: Jiang Liu jiang@huawei.com
Not 3.10 material.
For now, please *only* send the patches from this series that are *necessary*
to fix the regression. All of
On Thu, Jun 13, 2013 at 7:37 AM, Russell King - ARM Linux
li...@arm.linux.org.uk wrote:
On Wed, Jun 12, 2013 at 07:13:23PM -0700, Colin Cross wrote:
From code inspection, I believe this will also improve block device
performance where the bounce limit was set to BLK_BOUNCE_HIGH, which
was
On Thu, Jun 13, 2013 at 2:55 PM, Christian Ruppert
christian.rupp...@abilis.com wrote:
Traditionally, GPIO ranges are based on consecutive ranges of both GPIO
and pin numbers. This patch allows for GPIO ranges with arbitrary lists
of pin numbers.
Signed-off-by: Christian Ruppert
Hi,
This patchset contains a collection of new features and fixes for
the bh1770glc driver for the BH1770 and SFH7770 proximity
and ambient light sensor device.
In few words this is what it brings:
- /dev/input/event interface
- removal obsolete and wrong parameters
- new relevant parameters for
From: Onur Atilla oati...@gmail.com
Removed unused variables and definitions, adjusted some code
alignement and removed trailing spaces.
Signed-off-by: Onur Atilla oati...@gmail.com
Signed-off-by: Andi Shyti a...@etezian.org
---
drivers/misc/bh1770glc.c | 55
From: Onur Atilla oati...@gmail.com
Changed the neutral glass attenuation value from 16384
to 8192. This is for adaptation to the new scaling factor.
Signed-off-by: Onur Atilla oati...@gmail.com
Signed-off-by: Andi Shyti a...@etezian.org
---
include/linux/i2c/bh1770glc.h |4 ++--
1 file
lux_raw_result_show() will run directly the lux_get_result()
instead of using another support function
Signed-off-by: Andi Shyti a...@etezian.org
---
drivers/misc/bh1770glc.c |9 ++---
1 file changed, 2 insertions(+), 7 deletions(-)
diff --git a/drivers/misc/bh1770glc.c
From: Onur Atilla oati...@gmail.com
The als_int_enable switch decides whether the sensor interrupt
signal is triggered by both proximity and the ambient light
sensors or only by the proximity sensor.
The low and high threshold values are set to their minimum and
maximum in order to disable ALS
From: Onur Atilla oati...@gmail.com
Sensor compensation factor input from the platform
is being checked now before use.
Signed-off-by: Onur Atilla oati...@gmail.com
Signed-off-by: Andi Shyti a...@etezian.org
---
drivers/misc/bh1770glc.c | 13 +++--
1 file changed, 11 insertions(+), 2
On Thu, 13 Jun 2013, Willy Tarreau wrote:
Sven-Haegar, Christoph,
concerning the issue below, I could reproduce both Sven-Haegar's error
(running
make headers_check with the patch applied) and Christoph's build error with
gcc
4.7 on i686 without the patch.
I noticed that neither
From: Onur Atilla oati...@gmail.com
Some obsolete version-dependent coefficient and constant settings
were removed out of the sensor detection functions. These values
cause unwanted offset between different sensor types.
Signed-off-by: Onur Atilla oati...@gmail.com
Signed-off-by: Andi Shyti
The driver generates an event in /dev/input/ under the name
'bh1770'. It's a switch event where is reported '0' or '1'
whenever the sensor detects something crossing the threshold.
Signed-off-by: Onur Atilla oati...@gmail.com
Signed-off-by: Phil Carmody p...@asdf.org
Signed-off-by: Andi Shyti
kstrtoul() calls have been done by using base 0
up to now. This allowed hexadecimal and octal
entry on the sysfs interface.
Hexadecimal or octal entry is not required, nor
wanted for the proximity sensor.
The base is now changed to 10 in order to accept
only decimal numbers on the proximity
From: Onur Atilla oati...@gmail.com
Added dynamic threshold capability to the driver and removed
constant threshold value setting, thresh_above1_value, from
the sysfs interface.
Only one threshold value is visible and configurable through
the sysfs interface now; it is prox0_threshold_value.
On Thu, Jun 13, 2013 at 12:14:54PM -0600, Bjorn Helgaas wrote:
On Wed, May 29, 2013 at 4:29 PM, Bjorn Helgaas bhelg...@google.com wrote:
This fixes a copy and paste error introduced by 9f060e2231
(block: Convert integrity to bvec_alloc_bs()).
Found by Coverity (CID 1020654).
Signed-off-by: Andi Shyti a...@etezian.org
---
drivers/misc/bh1770glc.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/misc/bh1770glc.c b/drivers/misc/bh1770glc.c
index 031a9fa..bd90eaf 100644
--- a/drivers/misc/bh1770glc.c
+++ b/drivers/misc/bh1770glc.c
@@ -273,7
On Thu, 2013-06-13 at 21:25 +0300, Andy Shevchenko wrote:
On Thu, Jun 13, 2013 at 5:37 PM, Alexey Brodkin
alexey.brod...@synopsys.com wrote:
Driver for non-standard on-chip ethernet device ARC EMAC 10/100,
instantiated in some legacy ARC (Synopsys) FPGA Boards such as
ARCAngel4/ML50x.
From: Onur Atilla oati...@gmail.com
Instead of using a constant value, the LED current
of the proximity sensor is now made individually
configurable for each product.
bh1770glc reads the platform-defined data and sets
the most suitable current value accordingly.
Signed-off-by: Onur Atilla
proximity sensor doesn't need to be adjusted; removed all the
overcode used for the proximity coefficients
Signed-off-by: Andi Shyti a...@etezian.org
---
drivers/misc/bh1770glc.c | 39 ++-
1 file changed, 2 insertions(+), 37 deletions(-)
diff --git
Tang Chen tangc...@cn.fujitsu.com wrote:
From: Yinghai Lu ying...@kernel.org
Prepare to put page table on local nodes.
Move calling of init_mem_mapping() to early_initmem_init().
Rework alloc_low_pages to allocate page table in following order:
BRK, local node, low range
Still only
From: Onur Atilla oati...@gmail.com
Changed all exposed scalers to 8192 (Q13) in order to
achieve consistency in the sysfs interface.
Signed-off-by: Onur Atilla oati...@gmail.com
Signed-off-by: Andi Shyti a...@etezian.org
---
drivers/misc/bh1770glc.c |4 ++--
1 file changed, 2
On Thu, Jun 13, 2013 at 2:55 PM, Christian Ruppert
christian.rupp...@abilis.com wrote:
This patch adds the infrastructure required to register non-linear gpio
ranges through gpiolib and the standard GPIO device tree bindings.
Signed-off-by: Christian Ruppert christian.rupp...@abilis.com
On 06/13, Thomas Gleixner wrote:
On Thu, 13 Jun 2013, Daniel Lezcano wrote:
I prefer Thomas to have a look at it and ack it. I changed Cc to To for
Thomas.
The patch does not apply on tip timers/core. The code has been
reworked a month ago. Please work against tip timers/core. That's
Hi Linus,
Please pull from the git repository at
git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git
acpi-3.10-rc6
to receive one ACPI fix for v3.10-rc6 which is
commit 8c9b7a7b2fc2750af418ddc28e707c42e78aa0bf
ACPI / video: Do not bind to device objects with a scan handler
On Thu, Jun 13, 2013 at 9:32 AM, Jiang Liu jiang@huawei.com wrote:
Alexander E. Patrakov patra...@gmail.com reports two bugs related to
dock station support on Sony VAIO VPCZ23A4R. Actually there are at least
four bugs related to Sony VAIO VPCZ23A4R dock support.
1) can't correctly detect
On Thu, Jun 13, 2013 at 08:31:08PM +0200, Sven-Haegar Koch wrote:
On Thu, 13 Jun 2013, Willy Tarreau wrote:
Sven-Haegar, Christoph,
concerning the issue below, I could reproduce both Sven-Haegar's error
(running
make headers_check with the patch applied) and Christoph's build error
On Wed, Jun 12, 2013 at 04:53:25PM +0300, Oded Gabbay wrote:
@@ -262,7 +288,23 @@ static const struct sdhci_pltfm_data sdhci_esdhc_pdata =
{
static int sdhci_esdhc_probe(struct platform_device *pdev)
{
- return sdhci_pltfm_register(pdev, sdhci_esdhc_pdata);
+ struct sdhci_host
On Thu, Jun 13, 2013 at 03:23:37PM +0530, Mayuresh Kulkarni wrote:
[...]
diff --git a/drivers/gpu/host1x/drm/dc.c b/drivers/gpu/host1x/drm/dc.c
[...]
@@ -1128,9 +1129,7 @@ static int tegra_dc_probe(struct platform_device *pdev)
return PTR_ERR(dc-clk);
}
- err =
Hi Linus,
Another set of fixes, the biggest bit of this is yet another tweak to
the UEFI anti-bricking code; apparently we finally got some feedback
from Samsung as to what makes at least their systems fail. This set
should actually fix the boot regressions that some other systems
(e.g. SGI)
On Thursday, June 13, 2013 11:42:16 AM Yinghai Lu wrote:
On Thu, Jun 13, 2013 at 9:32 AM, Jiang Liu jiang@huawei.com wrote:
Alexander E. Patrakov patra...@gmail.com reports two bugs related to
dock station support on Sony VAIO VPCZ23A4R. Actually there are at least
four bugs related to
Hello, Andrew, Kent.
(cc'ing NFS folks for id[r|a] discussion)
On Wed, Jun 12, 2013 at 08:03:11PM -0700, Andrew Morton wrote:
They all sound like pretty crappy reasons ;) If the idr/ida interface
is nasty then it can be wrapped to provide the same interface as the
percpu tag allocator.
I
On one sytem that mtrr range is more then 44bits, in dmesg we have
[0.00] MTRR default type: write-back
[0.00] MTRR fixed ranges enabled:
[0.00] 0-9 write-back
[0.00] A-B uncachable
[0.00] C-D write-through
[0.00]
On Thu, 13 Jun 2013 11:53:18 -0700 Tejun Heo t...@kernel.org wrote:
Hello, Andrew, Kent.
(cc'ing NFS folks for id[r|a] discussion)
On Wed, Jun 12, 2013 at 08:03:11PM -0700, Andrew Morton wrote:
They all sound like pretty crappy reasons ;) If the idr/ida interface
is nasty then it can
Hello, Andrew, Kent.
On Wed, Jun 12, 2013 at 04:38:54PM -0700, Andrew Morton wrote:
...
+unsigned percpu_tag_alloc(struct percpu_tag_pool *pool, gfp_t gfp)
+{
+ DEFINE_WAIT(wait);
+ struct percpu_tag_cpu_freelist *tags;
+ unsigned long flags;
+ unsigned tag, this_cpu;
+
+
On Thu, 13 Jun 2013 11:53:18 -0700
Tejun Heo t...@kernel.org wrote:
Hello, Andrew, Kent.
(cc'ing NFS folks for id[r|a] discussion)
On Wed, Jun 12, 2013 at 08:03:11PM -0700, Andrew Morton wrote:
They all sound like pretty crappy reasons ;) If the idr/ida interface
is nasty then it can
On 06/13/2013 12:49 PM, Thierry Reding wrote:
On Thu, Jun 13, 2013 at 03:23:37PM +0530, Mayuresh Kulkarni wrote:
[...]
diff --git a/drivers/gpu/host1x/drm/dc.c
b/drivers/gpu/host1x/drm/dc.c
[...]
@@ -1128,9 +1129,7 @@ static int tegra_dc_probe(struct
platform_device *pdev) return
On 06/13/2013 07:55 PM, Greg KH wrote:
I'm announcing the release of the 3.9.6 kernel.
Greg,
did you forget to push? 3.0 and 3.4 appeared on the mirrors, unlike 3.9...
thanks,
--
js
suse labs
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to
On Thu, 13 Jun 2013 12:06:10 -0700 Tejun Heo t...@kernel.org wrote:
Hello, Andrew, Kent.
On Wed, Jun 12, 2013 at 04:38:54PM -0700, Andrew Morton wrote:
...
+unsigned percpu_tag_alloc(struct percpu_tag_pool *pool, gfp_t gfp)
+{
+ DEFINE_WAIT(wait);
+ struct percpu_tag_cpu_freelist
On Thu, Jun 13, 2013 at 12:02 PM, Rafael J. Wysocki r...@sisk.pl wrote:
On Thursday, June 13, 2013 11:42:16 AM Yinghai Lu wrote:
On Thu, Jun 13, 2013 at 9:32 AM, Jiang Liu jiang@huawei.com wrote:
Alexander E. Patrakov patra...@gmail.com reports two bugs related to
dock station support on
On Thu, Jun 13, 2013 at 11:53:18AM -0700, Tejun Heo wrote:
The thing is that id[r|a] guarantee that the lowest available slot is
allocated and this is important because it's used to name things which
are visible to userland - things like block device minor number,
device indicies and so on.
Hello, Andrew.
On Thu, Jun 13, 2013 at 12:04:39PM -0700, Andrew Morton wrote:
The thing is that id[r|a] guarantee that the lowest available slot is
allocated
That isn't the case for ida_get_new_above() - the caller gets to
control the starting index.
Hmmm? get_new_above() is the same,
On Thu, Jun 13, 2013 at 08:34:38PM +0800, Bob Liu wrote:
Hi Seth,
On 06/04/2013 04:33 AM, Seth Jennings wrote:
This is the latest version of the zswap patchset for compressed swap
caching.
This is submitted for merging into linux-next and inclusion in v3.11.
Have you noticed that
On Thu, Jun 13, 2013 at 9:33 PM, Joe Perches j...@perches.com wrote:
On Thu, 2013-06-13 at 21:25 +0300, Andy Shevchenko wrote:
On Thu, Jun 13, 2013 at 5:37 PM, Alexey Brodkin
alexey.brod...@synopsys.com wrote:
Driver for non-standard on-chip ethernet device ARC EMAC 10/100,
instantiated in
On Thu, Jun 13, 2013 at 09:10:55PM +0200, Jiri Slaby wrote:
On 06/13/2013 07:55 PM, Greg KH wrote:
I'm announcing the release of the 3.9.6 kernel.
Greg,
did you forget to push? 3.0 and 3.4 appeared on the mirrors, unlike 3.9...
Ick, you are right, I forgot to push the git tree, which
On 06/13/2013 03:12 AM, Alexandre Courbot wrote:
Add basic support for booting secondary processors on Tegra devices
using the Trusted Foundations secure monitor.
Signed-off-by: Alexandre Courbot acour...@nvidia.com
---
Documentation/devicetree/bindings/arm/tegra.txt| 11 +
On 06/13/2013 08:24 PM, Thierry Reding wrote:
On Thu, Jun 13, 2013 at 10:55:17AM +0530, Sachin Kamat wrote:
On 13 June 2013 03:01, Marc Kleine-Budde m...@pengutronix.de wrote:
Commit 75096579c3ac (lib: devres: Introduce devm_ioremap_resource())
introduced devm_ioremap_resource() and encourage
Bob Liu reported a memory leak in zswap. This was due to the
under_reclaim field in the zbud header not being initialized
to 0, which resulted in zbud_free() not freeing the page
under the false assumption that the page was undergoing
zbud reclaim.
This patch properly initializes the
On 06/13/2013 03:12 AM, Alexandre Courbot wrote:
Not all Tegra devices need to set the CPU reset handler in the same way.
s/need/can/ ?
In particular, devices using a TrustZone secure monitor cannot set the
reset handler directly and need to do it through a firmware operation.
This patch
Hello,
On Thu, Jun 13, 2013 at 12:13:24PM -0700, Andrew Morton wrote:
As I understand it, if a task is stuck in this loop at freeze time, the
whole freeze attempt will fail. But it's been a long time since I
thought about or worked on this stuff.
It depends on who's calling the allocator but
On 06/13/2013 03:12 AM, Alexandre Courbot wrote:
Use a firmware operation to set the CPU reset handler and only resort to
doing it ourselves if there is none defined.
This supports the booting of secondary CPUs on devices using a TrustZone
secure monitor.
diff --git
On Thu, 13 Jun 2013 12:15:07 -0700 Tejun Heo t...@kernel.org wrote:
Hello, Andrew.
On Thu, Jun 13, 2013 at 12:04:39PM -0700, Andrew Morton wrote:
The thing is that id[r|a] guarantee that the lowest available slot is
allocated
That isn't the case for ida_get_new_above() - the caller
On 06/12/2013 12:33 PM, Tony Lindgren wrote:
* Linus Walleij linus.wall...@linaro.org [130611 12:59]:
On Tue, Jun 11, 2013 at 6:33 PM, Stephen Warren swar...@wwwdotorg.org
wrote:
On 06/11/2013 02:16 AM, Linus Walleij wrote:
From: Linus Walleij linus.wall...@linaro.org
In addition to the
Geert Uytterhoeven dixit:
Should these be truncated to 32-bit explicitly, or is this a bug in mksh?
mksh in “mksh mode” operates specifically on 32-bit integer data
types with defined wraparound and other guarantees beyond what
POSIX does. There is an “lksh” binary in the mksh binary package
in
Hello,
On Thu, Jun 13, 2013 at 12:23:39PM -0700, Andrew Morton wrote:
The lowest number guarantee makes them different. Maybe tag
allocation can be layered on top as a caching layer, I don't know, but
at any rate we need at least two different operation modes.
Why? Tag allocation
On 06/11/2013 01:53 PM, Linus Walleij wrote:
On Tue, Jun 11, 2013 at 6:33 PM, Stephen Warren swar...@wwwdotorg.org wrote:
On 06/11/2013 02:16 AM, Linus Walleij wrote:
From: Linus Walleij linus.wall...@linaro.org
In addition to the recently introduced pinctrl core
control, the PM runtime pin
On 06/11/2013 01:59 PM, Linus Walleij wrote:
From: Linus Walleij linus.wall...@linaro.org
This document snippet tries to be helpful and define the pin
PM states and helpers, and how they should be used to create
some kind of common ontology around this.
Oops. I haven't been keeping up well.
Andy Shevchenko andy.shevche...@gmail.com :
[...]
I just realize you are using circular buffer here. What about to use
them with linux' native framework? Documentation/circular-buffers.txt
It's almost unused in drivers/net. I won't mind if it stays this way.
--
Ueimor
--
To unsubscribe from
On Tue, Jun 11, 2013 at 07:09:00AM -0400, Jeff Layton wrote:
When we convert over to using the i_lock to protect the i_flock list,
that will introduce a potential lock inversion problem in locks_show.
When we want to walk the i_flock list, we'll need to take the i_lock.
Rather than do that,
On Friday, June 14, 2013 12:32:25 AM Jiang Liu wrote:
Current ACPI glue logic expects that physical devices are destroyed
before destroying companion ACPI devices, otherwise it will break the
ACPI unbind logic and cause following warning messages:
[ 185.026073] usb usb5: Oops, 'acpi_handle'
On Thu, Jun 13, 2013 at 05:12:55PM +0800, Li Zefan wrote:
Sorry for updating the patchset so late.
I've made some changes for the memory barrier thing, and I agree with
Michal that there can be improvement but can be a separate patch.
If this version is ok for everyone, I'll send the whole
From: Joe Perches j...@perches.com
Date: Thu, 13 Jun 2013 11:33:21 -0700
On Thu, 2013-06-13 at 21:25 +0300, Andy Shevchenko wrote:
On Thu, Jun 13, 2013 at 5:37 PM, Alexey Brodkin
+ if (unlikely((info OWN_MASK) == FOR_EMAC)) {
+ /* BD is still owned by
Commit 699390354da6c258b65bf8fa79cfd5feaede50b6
('pty: Ignore slave pty close() if never successfully opened')
introduced a bug with ptys whereby a write() in parallel with an
open() on an existing pty could mistakenly indicate an I/O error.
Only indicate an I/O error if the condition on open()
Am 06.06.2013 12:51, schrieb Alexander Holler:
hctosys= specifies the driver (RTC) name which sets the system clock at
boot, if and only if userspace hasn't set the time before the driver will
be loaded.
If hctosys will not be specified, the first available hardware clock
with a valid time will
On Thu, 13 Jun 2013 20:24:48 +0200 Thierry Reding thierry.red...@gmail.com
wrote:
On Thu, Jun 13, 2013 at 10:55:17AM +0530, Sachin Kamat wrote:
On 13 June 2013 03:01, Marc Kleine-Budde m...@pengutronix.de wrote:
Commit 75096579c3ac (lib: devres: Introduce devm_ioremap_resource())
On Thu, Jun 13, 2013 at 11:39:50AM -0700, Stephen Boyd wrote:
On 06/13, Thomas Gleixner wrote:
On Thu, 13 Jun 2013, Daniel Lezcano wrote:
I prefer Thomas to have a look at it and ack it. I changed Cc to To for
Thomas.
The patch does not apply on tip timers/core. The code has been
Joshua reported: Commit cd7b304dfaf1 (x86, range: fix missing merge
during add range) broke mtrr cleanup on his setup in 3.9.5.
corresponding commit in upstream is fbe06b7bae7c.
*BAD*gran_size: 64K chunk_size: 16M num_reg: 6 lose cover RAM: -0G
https://bugzilla.kernel.org/show_bug.cgi?id=59491
Joshua reported: Commit cd7b304dfaf1 (x86, range: fix missing merge
during add range) broke mtrr cleanup on his setup in 3.9.5.
corresponding commit in upstream is fbe06b7bae7c.
*BAD*gran_size: 64K chunk_size: 16M num_reg: 6 lose cover RAM: -0G
https://bugzilla.kernel.org/show_bug.cgi?id=59491
Joshua reported: Commit cd7b304dfaf1 (x86, range: fix missing merge
during add range) broke mtrr cleanup on his setup in 3.9.5.
corresponding commit in upstream is fbe06b7bae7c.
The reason is add_range_with_merge could generate blank spot.
We could avoid that by searching new expanded start/end,
Preserve the backing device's logical size, use 512 byte
sectors when there is no backing device.
The logical block size has no impact on performance, but
it alters the meaning of on-disk structures like partition
tables. Preserve the backing device's sector size to keep
bcache transparent, and
On Thu, 13 Jun 2013 15:45:46 -0400
J. Bruce Fields bfie...@fieldses.org wrote:
On Tue, Jun 11, 2013 at 07:09:00AM -0400, Jeff Layton wrote:
When we convert over to using the i_lock to protect the i_flock list,
that will introduce a potential lock inversion problem in locks_show.
When we
If device is disconnected check occurs to be true in ezusb_access_ltv(),
it just return -ENODEV. But that means request_context is leaked since
there are no any references to it anymore.
The patch adds a call to ezusb_request_context_put() before return.
Found by Linux Driver Verification project
On 06/13/2013 10:25 PM, Andy Shevchenko wrote:
On Thu, Jun 13, 2013 at 5:37 PM, Alexey Brodkin
alexey.brod...@synopsys.com wrote:
Driver for non-standard on-chip ethernet device ARC EMAC 10/100,
instantiated in some legacy ARC (Synopsys) FPGA Boards such as
ARCAngel4/ML50x.
Much better. But
From: Linus Walleij linus.wall...@linaro.org
The stubs for the !PINCTRL case were placed in the wrong
part of the file, causing breakage in linux-next when compiling
SH without pinctrl. Fix it up by moving the stubs to the right
place.
Signed-off-by: Linus Walleij linus.wall...@linaro.org
---
On Thu, Jun 13, 2013 at 9:39 PM, Stephen Warren swar...@wwwdotorg.org wrote:
On 06/11/2013 01:59 PM, Linus Walleij wrote:
From: Linus Walleij linus.wall...@linaro.org
This document snippet tries to be helpful and define the pin
PM states and helpers, and how they should be used to create
On Thu, 13 Jun 2013, Michal Hocko wrote:
Right now it appears that that number of users is 0 and we're talking
about a problem that was reported in 3.2 that was released a year and a
half ago. The rules of inclusion in stable also prohibit such a change
from being backported,
On 06/13/2013 11:53 AM, Yinghai Lu wrote:
- if (base size_or_mask || size size_or_mask) {
+ if (base (boot_cpu_data.x86_phys_bits - PAGE_SHIFT) ||
+ base (base + size) ||
+ (base + size - 1) (boot_cpu_data.x86_phys_bits - PAGE_SHIFT)) {
On Thu, Jun 13, 2013 at 11:25 PM, Alexey Brodkin
alexey.brod...@synopsys.com wrote:
On 06/13/2013 10:25 PM, Andy Shevchenko wrote:
On Thu, Jun 13, 2013 at 5:37 PM, Alexey Brodkin
alexey.brod...@synopsys.com wrote:
Driver for non-standard on-chip ethernet device ARC EMAC 10/100,
instantiated
On Wed, 2013-06-12 at 17:06 +0200, Arnd Bergmann wrote:
On Tuesday 11 June 2013, James Bottomley wrote:
Really, no, it's not a good idea at all. It invites tons of patches
littering the code with BUG_ONs where we might possibly get a NULL
dereference. All it does is add extra instructions
Let's try to get this wrapped up?
On Thu, 6 Jun 2013 14:43:51 +0200 Peter Zijlstra pet...@infradead.org wrote:
Patch bc3e53f682 (mm: distinguish between mlocked and pinned pages)
broke RLIMIT_MEMLOCK.
I rather like what bc3e53f682 did, actually. RLIMIT_MEMLOCK limits the
amount of memory
On Thu, Jun 13, 2013 at 10:25:02PM +0200, Gabriel de Perthuis wrote:
Preserve the backing device's logical size, use 512 byte
sectors when there is no backing device.
The logical block size has no impact on performance, but
it alters the meaning of on-disk structures like partition
tables.
From: Tobias Polzer tobias.pol...@fau.de
In uf_process_ma_packet_req() (staging/csr/unifi_pdu_processing.c), the
test for
(staInfo-timSet != CSR_WIFI_TIM_RESET) || (staInfo-timSet !=
CSR_WIFI_TIM_RESETTING)
obviously makes no sense and causes GCC to emit a warning if
-Wlogical-op is enabled.
As
On Thu, Jun 13, 2013 at 12:21:52PM -0700, Tejun Heo wrote:
Hello,
On Thu, Jun 13, 2013 at 12:13:24PM -0700, Andrew Morton wrote:
As I understand it, if a task is stuck in this loop at freeze time, the
whole freeze attempt will fail. But it's been a long time since I
thought about or
401 - 500 of 1440 matches
Mail list logo
