to be a clean solution.
Signed-off-by: Jan Luebbe
---
fs/proc/array.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/proc/array.c b/fs/proc/array.c
index 2edbb657f859..b76b1e29fc36 100644
--- a/fs/proc/array.c
+++ b/fs/proc/array.c
@@ -462,7 +462,7 @@ static int do_task_
This is a corresponding change as "PCI: mvebu: Check DRAM window size" applied
to the Orion PCIe driver. I don't have the relevant hardware myself, but the
patch may still be useful for someone who has. This is completely untested.
Signed-off-by: Jan Luebbe <j...@pengutronix.de&g
This is a corresponding change as "PCI: mvebu: Check DRAM window size" applied
to the Orion PCIe driver. I don't have the relevant hardware myself, but the
patch may still be useful for someone who has. This is completely untested.
Signed-off-by: Jan Luebbe
---
arch/arm/mach-dove/pcie
The sum of the DRAM windows may exceed 4GB (at least on Armada XP).
Return an error in that case.
Signed-off-by: Jan Luebbe <j...@pengutronix.de>
---
drivers/pci/host/pci-mvebu.c | 27 ++-
1 file changed, 22 insertions(+), 5 deletions(-)
diff --git a/drivers/pci/ho
The sum of the DRAM windows may exceed 4GB (at least on Armada XP).
Return an error in that case.
Signed-off-by: Jan Luebbe
---
drivers/pci/host/pci-mvebu.c | 27 ++-
1 file changed, 22 insertions(+), 5 deletions(-)
diff --git a/drivers/pci/host/pci-mvebu.c b/drivers
).
This patch changes the type in 'struct mbus_dram_window' from u32 to
u64, which allows us to keep using the same register calculation code in
most MBUS-using drivers (which calculate ->size - 1 again).
Signed-off-by: Jan Luebbe <j...@pengutronix.de>
---
drivers/bus/mvebu-mbus.c | 2 +-
incl
).
This patch changes the type in 'struct mbus_dram_window' from u32 to
u64, which allows us to keep using the same register calculation code in
most MBUS-using drivers (which calculate ->size - 1 again).
Signed-off-by: Jan Luebbe
---
drivers/bus/mvebu-mbus.c | 2 +-
include/linux/mbus.h
on each other, they could also go in separatly.
Jan Luebbe (2):
bus: mbus: fix window size calculation for 4GB windows
PCI: mvebu: Check DRAM window size
drivers/bus/mvebu-mbus.c | 2 +-
drivers/pci/host/pci-mvebu.c | 27 ++-
include/linux/mbus.h | 4 ++--
3
on each other, they could also go in separatly.
Jan Luebbe (2):
bus: mbus: fix window size calculation for 4GB windows
PCI: mvebu: Check DRAM window size
drivers/bus/mvebu-mbus.c | 2 +-
drivers/pci/host/pci-mvebu.c | 27 ++-
include/linux/mbus.h | 4 ++--
3
Signed-off-by: Jan Luebbe <j...@pengutronix.de>
---
drivers/misc/eeprom/Kconfig | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/misc/eeprom/Kconfig b/drivers/misc/eeprom/Kconfig
index de58762097c4..d1c8cd5b33e2 100644
--- a/drivers/misc/eeprom/Kconfig
+++ b/d
Signed-off-by: Jan Luebbe
---
drivers/misc/eeprom/Kconfig | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/misc/eeprom/Kconfig b/drivers/misc/eeprom/Kconfig
index de58762097c4..d1c8cd5b33e2 100644
--- a/drivers/misc/eeprom/Kconfig
+++ b/drivers/misc/eeprom/Kconfig
-off-by: Jan Luebbe
---
This patch depends on my two recent pps-gpio patches, which are currently
in Andrew Morton's mmotm. So it should probably also go via Andrew if it
is acceptable.
Changes since v1:
- Do not allocate a pdata struct, store info in pps_gpio_device_data
-off-by: Jan Luebbe j...@pengutronix.de
---
This patch depends on my two recent pps-gpio patches, which are currently
in Andrew Morton's mmotm. So it should probably also go via Andrew if it
is acceptable.
Changes since v1:
- Do not allocate a pdata struct, store info
Signed-off-by: Jan Luebbe
---
This patch depends on my two recent pps-gpio patches, which are currently
in Andrew Morton's mmotm. So it should probably also go via Andrew if it
is acceptable.
Documentation/devicetree/bindings/pps/pps-gpio.txt | 20 +++
drivers/pps/clients/pps-gpio.c
Signed-off-by: Jan Luebbe j...@pengutronix.de
---
This patch depends on my two recent pps-gpio patches, which are currently
in Andrew Morton's mmotm. So it should probably also go via Andrew if it
is acceptable.
Documentation/devicetree/bindings/pps/pps-gpio.txt | 20 +++
drivers/pps
From: Lucas Stach
Register layout is the same, so just add the variant to the
appropriate places.
Signed-off-by: Lucas Stach
Signed-off-by: Jan Luebbe
---
drivers/rtc/rtc-rs5c372.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/drivers/rtc/rtc-rs5c372.c b/drivers/rtc/rtc-rs5c372.c
From: Lucas Stach l.st...@pengutronix.de
Register layout is the same, so just add the variant to the
appropriate places.
Signed-off-by: Lucas Stach l.st...@pengutronix.de
Signed-off-by: Jan Luebbe j...@pengutronix.de
---
drivers/rtc/rtc-rs5c372.c | 5 +
1 file changed, 5 insertions(+)
diff
This removes some boilerplate code (no functional changes).
Signed-off-by: Jan Luebbe
Acked-by: Rodolfo Giometti
---
drivers/pps/clients/pps-gpio.c | 18 +-
1 file changed, 1 insertion(+), 17 deletions(-)
diff --git a/drivers/pps/clients/pps-gpio.c b/drivers/pps/clients/pps
Signed-off-by: Jan Luebbe
Acked-by: Rodolfo Giometti
---
Andrew,
I send these patches to you as requested by PPS maintainer Rodolfo Giometti:
http://www.linuxpps.org/pipermail/discussions/2013-April/004424.html
The acks were only posed to the list above.
Thanks,
Jan
drivers/pps/clients/pps
Signed-off-by: Jan Luebbe j...@pengutronix.de
Acked-by: Rodolfo Giometti giome...@enneenne.com
---
Andrew,
I send these patches to you as requested by PPS maintainer Rodolfo Giometti:
http://www.linuxpps.org/pipermail/discussions/2013-April/004424.html
The acks were only posed to the list above
This removes some boilerplate code (no functional changes).
Signed-off-by: Jan Luebbe j...@pengutronix.de
Acked-by: Rodolfo Giometti giome...@enneenne.com
---
drivers/pps/clients/pps-gpio.c | 18 +-
1 file changed, 1 insertion(+), 17 deletions(-)
diff --git a/drivers/pps
Signed-off-by: Jan Luebbe
---
drivers/pps/clients/pps-gpio.c | 31 ---
1 file changed, 8 insertions(+), 23 deletions(-)
diff --git a/drivers/pps/clients/pps-gpio.c b/drivers/pps/clients/pps-gpio.c
index 2bf0c1b..221858d 100644
--- a/drivers/pps/clients/pps-gpio.c
This removes some boilerplate code (no functional changes).
Signed-off-by: Jan Luebbe
---
drivers/pps/clients/pps-gpio.c | 18 +-
1 file changed, 1 insertion(+), 17 deletions(-)
diff --git a/drivers/pps/clients/pps-gpio.c b/drivers/pps/clients/pps-gpio.c
index 221858d
Signed-off-by: Jan Luebbe j...@pengutronix.de
---
drivers/pps/clients/pps-gpio.c | 31 ---
1 file changed, 8 insertions(+), 23 deletions(-)
diff --git a/drivers/pps/clients/pps-gpio.c b/drivers/pps/clients/pps-gpio.c
index 2bf0c1b..221858d 100644
--- a/drivers/pps
This removes some boilerplate code (no functional changes).
Signed-off-by: Jan Luebbe j...@pengutronix.de
---
drivers/pps/clients/pps-gpio.c | 18 +-
1 file changed, 1 insertion(+), 17 deletions(-)
diff --git a/drivers/pps/clients/pps-gpio.c b/drivers/pps/clients/pps-gpio.c
Previously the alarm event was not propagated into the RTC subsystem.
By adding a call to rtc_update_irq, this fixes a timeout problem with
the hwclock utility.
Signed-off-by: Jan Luebbe
---
drivers/rtc/rtc-isl1208.c |3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/rtc/rtc
Previously the alarm event was not propagated into the RTC subsystem.
By adding a call to rtc_update_irq, this fixes a timeout problem with
the hwclock utility.
Signed-off-by: Jan Luebbe j...@pengutronix.de
---
drivers/rtc/rtc-isl1208.c |3 +++
1 file changed, 3 insertions(+)
diff --git
Signed-off-by: Jan Luebbe
---
drivers/rtc/rtc-imxdi.c |2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/rtc/rtc-imxdi.c b/drivers/rtc/rtc-imxdi.c
index b2fe920..85f19ad 100644
--- a/drivers/rtc/rtc-imxdi.c
+++ b/drivers/rtc/rtc-imxdi.c
@@ -392,6 +392,8 @@ static int
Signed-off-by: Jan Luebbe j...@pengutronix.de
---
drivers/rtc/rtc-imxdi.c |2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/rtc/rtc-imxdi.c b/drivers/rtc/rtc-imxdi.c
index b2fe920..85f19ad 100644
--- a/drivers/rtc/rtc-imxdi.c
+++ b/drivers/rtc/rtc-imxdi.c
@@ -392,6 +392,8 @@ static
Signed-off-by: Jan Luebbe
---
Changes since v1:
- As recommended by Joerg Roedel, check for overlap with vmalloc and
module address ranges.
lib/dma-debug.c |8
1 file changed, 8 insertions(+)
diff --git a/lib/dma-debug.c b/lib/dma-debug.c
index 66ce414..b35992b 100644
Signed-off-by: Jan Luebbe j...@pengutronix.de
---
Changes since v1:
- As recommended by Joerg Roedel, check for overlap with vmalloc and
module address ranges.
lib/dma-debug.c |8
1 file changed, 8 insertions(+)
diff --git a/lib/dma-debug.c b/lib/dma-debug.c
index 66ce414
Signed-off-by: Jan Luebbe
---
I'm not sure why we don't check for high memory, is there any problem
with this approach?
lib/dma-debug.c |3 +++
1 file changed, 3 insertions(+)
diff --git a/lib/dma-debug.c b/lib/dma-debug.c
index 66ce414..7d60ff0 100644
--- a/lib/dma-debug.c
+++ b/lib/dma
Signed-off-by: Jan Luebbe j...@pengutronix.de
---
I'm not sure why we don't check for high memory, is there any problem
with this approach?
lib/dma-debug.c |3 +++
1 file changed, 3 insertions(+)
diff --git a/lib/dma-debug.c b/lib/dma-debug.c
index 66ce414..7d60ff0 100644
--- a/lib/dma
On Sun, 2007-09-30 at 09:20 +0200, Ingo Molnar wrote:
> * Jan Luebbe <[EMAIL PROTECTED]> wrote:
> > From: Jan Lübbe <[EMAIL PROTECTED]>
> >
> > The new behaviour of CFS exposes a race which occurs if a switch is
> > requested when vt_mode.mode is VT_PROCES
On Sun, 2007-09-30 at 09:20 +0200, Ingo Molnar wrote:
* Jan Luebbe [EMAIL PROTECTED] wrote:
From: Jan Lübbe [EMAIL PROTECTED]
The new behaviour of CFS exposes a race which occurs if a switch is
requested when vt_mode.mode is VT_PROCESS.
The process with vc-vt_pid is signaled before
From: Jan Lübbe <[EMAIL PROTECTED]>
The new behaviour of CFS exposes a race which occurs if a switch is
requested when vt_mode.mode is VT_PROCESS.
The process with vc->vt_pid is signaled before vc->vt_newvt is set. This
causes the switch to fail when triggered by the monitoing process
because
From: Jan Lübbe [EMAIL PROTECTED]
The new behaviour of CFS exposes a race which occurs if a switch is
requested when vt_mode.mode is VT_PROCESS.
The process with vc-vt_pid is signaled before vc-vt_newvt is set. This
causes the switch to fail when triggered by the monitoing process
because the
37 matches
Mail list logo
