On Thu, Nov 15, 2012 at 4:01 AM, Stephen Rothwell wrote:
> Hi Grant,
>
> Today's linux-next merge of the spi tree got a conflict in
> drivers/spi/spi-xcomm.c between commit b31659004337 ("spi: Add
> AD-FMCOMMS1-EBZ I2C-SPI bridge driver") from Linus' tree and commit
> 0e312dcca718 ("spi/xcomm:
The following adds a helper for matching the linux,stdout-path property
in the chosen node and makes use of it in the i.MX serial driver.
changes since v3:
- move code from separate files to drivers/of/base.c and include/linux/of.h
changes since v2:
- move helper to OF core and make it
devicetrees may have a linux,stdout-path property in the chosen
node describing the console device. This adds a helper function
to match a device against this property so a driver can call
add_preferred_console for a matching device.
Signed-off-by: Sascha Hauer
---
drivers/of/base.c | 28
devicetrees may have the linux,stdout-path property to specify the
console. This patch adds support to the i.MX serial driver for this.
Signed-off-by: Sascha Hauer
---
drivers/tty/serial/imx.c |3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/tty/serial/imx.c
Traditionally console support is optional for serial drivers. This
makes it non optional for the i.MX driver since it's not worth
asking questions for a feature virtually every user of this driver
wants to have.
Signed-off-by: Sascha Hauer
---
drivers/tty/serial/Kconfig | 16 +---
(2012/11/15 11:54), Glauber Costa wrote:
> Suggested by akpm. I originally decided to put it closer to the use of
> the work struct, but let's move it to top.
>
> Signed-off-by: Glauber Costa
> CC: Michal Hocko
> CC: Kamezawa Hiroyuki
> CC: Johannes Weiner
> CC: Andrew Morton
Reviewed-by:
On Wed, Nov 14, 2012 at 03:33:16PM -0800, David Rientjes wrote:
> On Wed, 7 Nov 2012, Kirill A. Shutemov wrote:
>
> > diff --git a/mm/huge_memory.c b/mm/huge_memory.c
> > index f36bc7d..41f05f1 100644
> > --- a/mm/huge_memory.c
> > +++ b/mm/huge_memory.c
> > @@ -726,6 +726,16 @@ int
(2012/11/15 11:54), Glauber Costa wrote:
> Following the pattern found in the allocators, where we do our best to
> the fast paths function-call free, all the externally visible functions
> for kmemcg were marked __always_inline.
>
> It is fair to say, however, that this should be up to the
> > - if (timeout < 0) {
> > - dev_err(>adev->dev,
> > - "wait_for_completion_timeout "
> > - "returned %d waiting for event\n", timeout);
> > - status = timeout;
> > - }
> > -
> No, it is wrong. You need to
(2012/11/15 11:54), Glauber Costa wrote:
> The original reason for the existence of this test, was that
> memcg_kmem_cache_create could be called from either softirq context
> (where memcg_stop/resume_account is not needed), or process context,
> (where memcg_stop/resume_account is needed). Just
On Wed, Nov 14, 2012 at 03:28:15PM -0800, David Rientjes wrote:
> On Wed, 7 Nov 2012, Kirill A. Shutemov wrote:
>
> > diff --git a/mm/huge_memory.c b/mm/huge_memory.c
> > index 90e651c..f36bc7d 100644
> > --- a/mm/huge_memory.c
> > +++ b/mm/huge_memory.c
> > @@ -1611,6 +1611,7 @@ int
this is a driver for ST-Ericsson u8500 board(Snowball), with a ARM core inside.
so you should compile like this:
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- u8500_defconfig
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- uImage
On 15 November 2012 17:13, Zhang Rui wrote:
> On Thu,
2012/11/15 15:59, Wen Congyang wrote:
> We had introduced acpi_hotmem_initialized to avoid strange add_memory fail
> message. But the memory device may not be used by the kernel, and the
> device should be bound when the driver is being loaded. Remove
> acpi_hotmem_initialized to allow that the
2012/11/15 15:59, Wen Congyang wrote:
> We eject the memory device even if it is in use. It is very dangerous,
> and it will cause the kernel to be panicked.
>
> CC: David Rientjes
> CC: Jiang Liu
> CC: Len Brown
> CC: Benjamin Herrenschmidt
> CC: Paul Mackerras
> CC: Christoph Lameter
>
On Tuesday 13 November 2012, Russell King - ARM Linux wrote:
> You're missing something; that is one of the greatest powers of open
> source. The many eyes (and minds) effect. Someone out there probably
> has a solution to whatever problem, the trick is to find that person. :)
>
> I think we
2012/11/15 15:59, Wen Congyang wrote:
> If acpi_memory_enable_device() fails, acpi_memory_enable_device() will
> return a non-zero value, which means we fail to bind the memory device to
> this driver. So we should free memory device before
> acpi_memory_device_add() returns.
>
> CC: David
Hi, Liu Jiang
At 11/14/2012 10:52 PM, Jiang Liu Wrote:
> On 11/07/2012 04:43 AM, Andrew Morton wrote:
>> On Tue, 6 Nov 2012 09:31:57 +0800
>> Jiang Liu wrote:
>>
>>> Changeset 7f1290f2f2 tries to fix a issue when calculating
>>> zone->present_pages, but it causes a regression to 32bit systems
2012/11/15 15:59, Wen Congyang wrote:
> We allocate memory to store acpi_memory_info, so we should free it before
> freeing mem_device.
>
> CC: David Rientjes
> CC: Jiang Liu
> CC: Len Brown
> CC: Benjamin Herrenschmidt
> CC: Paul Mackerras
> CC: Christoph Lameter
> Cc: Minchan Kim
> CC:
On Wednesday 14 November 2012, H. Peter Anvin wrote:
> On 11/14/2012 04:18 AM, Arnd Bergmann wrote:
> > Since we are in the review phase for two new architectures that we
> > should be merging into the mainline kernel, I think we need to
> > come up with a solution for making them use a proper
On Wed, 14 Nov 2012, Dmitry Torokhov wrote:
> On Wed, Nov 14, 2012 at 04:59:21PM +0100, Benjamin Tissoires wrote:
> > Some devices provides the actual timestamp (hid_dg_scan_time in win8 ones)
> > computed by the hardware itself. This value is global to the frame and is
> > not specific to the
2012/11/15 15:59, Wen Congyang wrote:
> The memory device can be removed by 2 ways:
> 1. send eject request by SCI
> 2. echo 1 >/sys/bus/pci/devices/PNP0C80:XX/eject
>
> We handle the 1st case in the module acpi_memhotplug, and handle
> the 2nd case in ACPI eject notification. This 2 events may
On Thu, 2012-11-15 at 16:32 +0800, Hongbo Zhang wrote:
> On 15 November 2012 16:13, Zhang Rui wrote:
> > On Fri, 2012-11-09 at 19:29 +0800, hongbo.zhang wrote:
> >> From: "hongbo.zhang"
> >>
> >> This driver is based on the thermal management framework in thermal_sys.c.
> >> A
> >> thermal zone
On Thu, Nov 15, 2012 at 8:49 AM, Sascha Hauer wrote:
> On Wed, Nov 14, 2012 at 08:49:54PM +, Grant Likely wrote:
>> On Fri, Nov 2, 2012 at 9:48 AM, Sascha Hauer wrote:
>> > devicetrees may have a linux,stdout-path property in the chosen
>> > node describing the console device. This adds a
Hi Alan,
thanks again for your answer.
Reading the manual of the board I found this specification:
LVDS: 24-bit dual channel via CH7511 thru eDP
The Chrontel CH7511 is a DisplayPort (DP/eDP) to LVDS converter.
So, what I understand is that the LVDS interface that comes out
from the connector on
Hi all,
The code looks correct and inviting to me as it has led to good cleanups.
I dont think passing 0 as the argument to the function
sched_clock_idle_wakeup_event()
should lead to problems,as it does not do anything useful with the
passed arguments.
My only curiosity is what was the purpose
> "Andreas" == Andreas Larsson writes:
Hi,
>> Adding a type define (TYPE_OCORES / TYPE_GRLIB) and a 2nd
>> of_device_id entry with .data = TYPE_GRLIB, and then using that in
>> the probe routine would be nicer. Have a look at i2c-at91.c for an
>> example of a driver doing something like
On Thu 15-11-12 17:45:18, KAMEZAWA Hiroyuki wrote:
> (2012/11/14 18:15), David Rientjes wrote:
[...]
> >@@ -708,15 +671,17 @@ out:
> >
> > /*
> > * The pagefault handler calls here because it is out of memory, so kill a
> >- * memory-hogging task. If a populated zone has ZONE_OOM_LOCKED set, a
After commit "TTY: move tty buffers to tty_port", the tty buffers are
not freed in some drivers. This is because tty_port_destructor is not
called whenever a tty_port is freed. This was an assumption I counted
with but was unfortunately untrue. So fix the drivers to fulfil this
assumption.
Here
On Thursday, November 15, 2012 3:52 PM Thierry Reding wrote
> On Thu, Nov 15, 2012 at 10:30:11AM +0900, Jingoo Han wrote:
> > On Friday, November 09, 2012 11:05 PM Thierry Reding wrote
> > >
> > > This function finds the struct backlight_device for a given device tree
> > > node. A dummy function
After commit "TTY: move tty buffers to tty_port", the tty buffers are
not freed in some drivers. This is because tty_port_destructor is not
called whenever a tty_port is freed. This was an assumption I counted
with but was unfortunately untrue. So fix the drivers to fulfil this
assumption.
This
After commit "TTY: move tty buffers to tty_port", the tty buffers are
not freed in some drivers. This is because tty_port_destructor is not
called whenever a tty_port is freed. This was an assumption I counted
with but was unfortunately untrue.
Those using refcounting are safe now, but for those
After commit "TTY: move tty buffers to tty_port", the tty buffers are
not freed in some drivers. This is because tty_port_destructor is not
called whenever a tty_port is freed. This was an assumption I counted
with but was unfortunately untrue. So fix the drivers to fulfil this
assumption.
Here
After commit "TTY: move tty buffers to tty_port", the tty buffers are
not freed in some drivers. This is because tty_port_destructor is not
called whenever a tty_port is freed. This was an assumption I counted
with but was unfortunately untrue. So fix the drivers to fulfil this
assumption.
To be
On Thu, Nov 15, 2012 at 12:11:47AM -0800, David Rientjes wrote:
[...]
> Might not be too difficult if you implement your own cgroup to aggregate
> these tasks for which you want to know memory pressure events; it would
> have to be triggered for the task trying to allocate memory at any given
>
From: Lai Jiangshan
N_HIGH_MEMORY stands for the nodes that has normal or high memory.
N_MEMORY stands for the nodes that has any memory.
The code here need to handle with the nodes which have memory, we should
use N_MEMORY instead.
Signed-off-by: Lai Jiangshan
Acked-by: Christoph Lameter
Do not access unsafe port->tty pointer when we have a safe tty
already. Use the safe one.
Signed-off-by: Jiri Slaby
---
drivers/tty/isicom.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/tty/isicom.c b/drivers/tty/isicom.c
index d7492e1..5f3ecbc 100644
---
After commit "TTY: move tty buffers to tty_port", the tty buffers are
not freed in some drivers. This is because tty_port_destructor is not
called whenever a tty_port is freed. This was an assumption I counted
with but was unfortunately untrue. So fix the drivers to fulfil this
assumption.
Here
I introduced severe memory leaks by (still -next) commit "TTY: move
tty buffers to tty_port", especially in the pty driver. I did not
realize that tty_port is not destroyed as I had imagined. Most of the
drivers simply do not use the tty_port-reference-counted model.
In this series, some are
From: Lai Jiangshan
N_HIGH_MEMORY stands for the nodes that has normal or high memory.
N_MEMORY stands for the nodes that has any memory.
The code here need to handle with the nodes which have memory, we should
use N_MEMORY instead.
Signed-off-by: Lai Jiangshan
Acked-by: Hillf Danton
From: Lai Jiangshan
N_HIGH_MEMORY stands for the nodes that has normal or high memory.
N_MEMORY stands for the nodes that has any memory.
The code here need to handle with the nodes which have memory, we should
use N_MEMORY instead.
Signed-off-by: Lai Jiangshan
Acked-by: Hillf Danton
From: Lai Jiangshan
N_HIGH_MEMORY stands for the nodes that has normal or high memory.
N_MEMORY stands for the nodes that has any memory.
The code here need to handle with the nodes which have memory, we should
use N_MEMORY instead.
Signed-off-by: Lai Jiangshan
Signed-off-by: Wen Congyang
From: Lai Jiangshan
N_HIGH_MEMORY stands for the nodes that has normal or high memory.
N_MEMORY stands for the nodes that has any memory.
The code here need to handle with the nodes which have memory, we should
use N_MEMORY instead.
Signed-off-by: Lai Jiangshan
Acked-by: Christoph Lameter
On Thu, 15 Nov 2012 09:43:07 +0200 (EET), Pekka Enberg wrote:
> On Thu, 15 Nov 2012, Namhyung Kim wrote:
>> This is an RFC patchset to separate GTK GUI codes to a shared object,
>> called libperf-gtk.so and use it with libdl. It's in an early-stage
>> so probably has some rough edges, but I'd
From: Lai Jiangshan
N_HIGH_MEMORY stands for the nodes that has normal or high memory.
N_MEMORY stands for the nodes that has any memory.
The code here need to handle with the nodes which have memory, we should
use N_MEMORY instead.
Signed-off-by: Lai Jiangshan
Acked-by: Hillf Danton
From: Lai Jiangshan
N_HIGH_MEMORY stands for the nodes that has normal or high memory.
N_MEMORY stands for the nodes that has any memory.
The code here need to handle with the nodes which have memory, we should
use N_MEMORY instead.
Since we introduced N_MEMORY, we update the initialization of
From: Lai Jiangshan
update nodemasks management for N_MEMORY
Signed-off-by: Lai Jiangshan
Signed-off-by: Wen Congyang
---
Documentation/memory-hotplug.txt | 5 ++-
include/linux/memory.h | 1 +
mm/memory_hotplug.c | 87 +---
3
This patch is part3 of the following patchset:
https://lkml.org/lkml/2012/10/29/319
Part1 is here:
https://lkml.org/lkml/2012/10/31/30
Part2 is here:
https://lkml.org/lkml/2012/10/31/73
Part4 is here:
https://lkml.org/lkml/2012/10/31/129
Part5 is here:
From: Lai Jiangshan
N_HIGH_MEMORY stands for the nodes that has normal or high memory.
N_MEMORY stands for the nodes that has any memory.
The code here need to handle with the nodes which have memory, we should
use N_MEMORY instead.
Signed-off-by: Lai Jiangshan
Signed-off-by: Wen Congyang
From: Lai Jiangshan
N_HIGH_MEMORY stands for the nodes that has normal or high memory.
N_MEMORY stands for the nodes that has any memory.
The code here need to handle with the nodes which have memory, we should
use N_MEMORY instead.
Signed-off-by: Lai Jiangshan
Signed-off-by: Wen Congyang
From: Lai Jiangshan
N_HIGH_MEMORY stands for the nodes that has normal or high memory.
N_MEMORY stands for the nodes that has any memory.
The code here need to handle with the nodes which have memory, we should
use N_MEMORY instead.
Signed-off-by: Lai Jiangshan
Signed-off-by: Wen Congyang
From: Lai Jiangshan
N_HIGH_MEMORY stands for the nodes that has normal or high memory.
N_MEMORY stands for the nodes that has any memory.
The code here need to handle with the nodes which have memory, we should
use N_MEMORY instead.
Signed-off-by: Lai Jiangshan
Acked-by: Hillf Danton
From: Lai Jiangshan
N_HIGH_MEMORY stands for the nodes that has normal or high memory.
N_MEMORY stands for the nodes that has any memory.
The code here need to handle with the nodes which have memory, we should
use N_MEMORY instead.
Signed-off-by: Lai Jiangshan
Acked-by: Hillf Danton
From: Lai Jiangshan
We have N_NORMAL_MEMORY for standing for the nodes that have normal memory with
zone_type <= ZONE_NORMAL.
And we have N_HIGH_MEMORY for standing for the nodes that have normal or high
memory.
But we don't have any word to stand for the nodes that have *any* memory.
And we
On Wed, Nov 14, 2012 at 03:22:03PM -0800, David Rientjes wrote:
> On Wed, 7 Nov 2012, Kirill A. Shutemov wrote:
>
> > diff --git a/Documentation/vm/transhuge.txt b/Documentation/vm/transhuge.txt
> > index f734bb2..677a599 100644
> > --- a/Documentation/vm/transhuge.txt
> > +++
On Thu, Nov 15, 2012 at 01:51:46PM +0530, Prashant Gaikwad wrote:
> On Saturday 10 November 2012 02:40 AM, Stephen Warren wrote:
> >On 11/09/2012 11:44 AM, Thierry Reding wrote:
> >>On Fri, Nov 09, 2012 at 10:34:41AM -0700, Stephen Warren wrote:
> >...
> >>>I really hope soon that Tegra will
[...]
> From: Chuansheng Liu
> Date: Tue, Nov 6, 2012 at 6:18 PM
> Subject: [PATCH 1/7] I2c-nomadik: Fix the usage of wait_for_completion_timeout
> To: linus.wall...@linaro.org, w.s...@pengutronix.de
> Cc: linux-arm-ker...@lists.infradead.org,
> linux-kernel@vger.kernel.org,
tty from struct sdio_uart_port is unused. Proper refcounted tty in
tty_port->tty is used instead. So remove the member from that
structure.
Signed-off-by: Jiri Slaby
---
drivers/mmc/card/sdio_uart.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/mmc/card/sdio_uart.c
After commit "TTY: move tty buffers to tty_port", the tty buffers are
not freed in some drivers. This is because tty_port_destructor is not
called whenever a tty_port is freed. This was an assumption I counted
with but was unfortunately untrue. So fix the drivers to fulfil this
assumption.
PTY is
On Wed, Nov 14, 2012 at 08:49:54PM +, Grant Likely wrote:
> On Fri, Nov 2, 2012 at 9:48 AM, Sascha Hauer wrote:
> > devicetrees may have a linux,stdout-path property in the chosen
> > node describing the console device. This adds a helper function
> > to match a device against this property
(2012/11/14 18:15), David Rientjes wrote:
out_of_memory() is a globally defined function to call the oom killer.
x86, sh, and powerpc all use a function of the same name within file
scope in their respective fault.c unnecessarily. Inline the functions
into the pagefault handlers to clean the
(2012/11/14 18:15), David Rientjes wrote:
out_of_memory() will already cause current to schedule if it has not been
killed, so doing it again in pagefault_out_of_memory() is redundant.
Remove it.
Cc: KAMEZAWA Hiroyuki
Cc: KOSAKI Motohiro
Cc: Michal Hocko
Signed-off-by: David Rientjes
(2012/11/14 18:15), David Rientjes wrote:
To lock the entire system from parallel oom killing, it's possible to
pass in a zonelist with all zones rather than using
for_each_populated_zone() for the iteration. This obsoletes
try_set_system_oom() and clear_system_oom() so that they can be
On Wed, Nov 14, 2012 at 03:12:54PM -0800, David Rientjes wrote:
> On Wed, 7 Nov 2012, Kirill A. Shutemov wrote:
>
> > diff --git a/mm/huge_memory.c b/mm/huge_memory.c
> > index d767a7c..05490b3 100644
> > --- a/mm/huge_memory.c
> > +++ b/mm/huge_memory.c
> > @@ -1259,6 +1259,8 @@ int
Hi Pekka,
On Thu, 15 Nov 2012 09:47:23 +0200 (EET), Pekka Enberg wrote:
> On Tue, 13 Nov 2012, Namhyung Kim wrote:
>> From: Namhyung Kim
>>
>> Implement progress update function for GTK2 front end.
>>
>> Note that since it will be called before gtk main loop so that
>> we should call gtk event
(2012/11/14 18:15), David Rientjes wrote:
With hotpluggable and memoryless nodes, it's possible that node 0 will
not be online, so use the first online node's zonelist rather than
hardcoding node 0 to pass a zonelist with all zones to the oom killer.
Cc: Greg Kroah-Hartman
Signed-off-by: David
On 2012-11-13 23:45, Peter Korsgaard wrote:
"Andreas" == Andreas Larsson writes:
Hi,
Andreas> The registers in the GRLIB port of the controller are 32-bit
Andreas> and in big endian byte order. The PRELOW and PREHIGH registers
Andreas> are merged into one register. The subsequent
15.11.2012 01:01, J. Bruce Fields пишет:
On Mon, Nov 12, 2012 at 12:37:54PM +0400, Stanislav Kinsbursky wrote:
07.11.2012 22:33, J. Bruce Fields пишет:
On Tue, Nov 06, 2012 at 08:36:05AM -0500, J. Bruce Fields wrote:
On Tue, Nov 06, 2012 at 08:10:18AM -0500, Christoph Hellwig wrote:
On Tue,
UARTs no longer require call-back information, since the reset
call-back was removed in 43b5f0d69291374f602ad8e1817f329573a59010.
The only AUXDATA dependencies remaining for UARTs are DMA settings.
Signed-off-by: Lee Jones
---
arch/arm/mach-ux500/cpu-db8500.c |3 +--
1 file changed, 1
On 15 November 2012 16:13, Zhang Rui wrote:
> On Fri, 2012-11-09 at 19:29 +0800, hongbo.zhang wrote:
>> From: "hongbo.zhang"
>>
>> This driver is based on the thermal management framework in thermal_sys.c. A
>> thermal zone device is created with the trip points to which cooling devices
>> can
Hi,
Since the 32KHz clock was removed from the twl-regulator (0e8e5c34
regulator: twl: Remove references to 32kHz clock from DT bindings),
we've been having problems with our wl12xx chip that is connected
through the omap_hsmmc.
Our card simply doesn't get added to the system and we get lots of
with the last detached port state file remaining , usbip reports error on
attaching. So clean up the state files on detaching.
Signed-off-by: Harvey Yang
---
drivers/staging/usbip/userspace/src/usbip_detach.c |9 +
1 files changed, 9 insertions(+), 0 deletions(-)
diff --git
On Wed, Nov 14, 2012 at 03:08:45PM -0800, David Rientjes wrote:
> On Wed, 7 Nov 2012, Kirill A. Shutemov wrote:
>
> > diff --git a/include/linux/mm.h b/include/linux/mm.h
> > index fa06804..fe329da 100644
> > --- a/include/linux/mm.h
> > +++ b/include/linux/mm.h
> > @@ -516,6 +516,14 @@ static
On 11/15/2012 05:58 AM, Axel Lin :
> of_match_device() may return NULL.
>
> Signed-off-by: Axel Lin
Seems sensible,
Acked-by: Nicolas Ferre
> ---
> This resend CC Jean-Christophe.
>
> drivers/pinctrl/pinctrl-at91.c | 17 +
> 1 file changed, 13 insertions(+), 4
On Saturday 10 November 2012 02:40 AM, Stephen Warren wrote:
On 11/09/2012 11:44 AM, Thierry Reding wrote:
On Fri, Nov 09, 2012 at 10:34:41AM -0700, Stephen Warren wrote:
...
I really hope soon that Tegra will support DT bindings for clocks
so we can get rid of the AUXDATA, but unfortunately
On Wed, 14 Nov 2012, Jens Axboe wrote:
> Date: Wed, 14 Nov 2012 08:21:41 -0700
> From: Jens Axboe
> To: Lukáš Czerner
> Cc: linux-kernel@vger.kernel.org, linux-fsde...@vger.kernel.org,
> jmo...@redhat.com, a...@linux-foundation.org
> Subject: Re: [PATCH v3] loop: Limit the number of
On Wed, Nov 14, 2012 at 08:03:49AM +0100, Stefani Seibold wrote:
> Am Freitag, den 09.11.2012, 10:32 +0800 schrieb Yuanhan Liu:
> > On Thu, Nov 08, 2012 at 01:37:15PM +0100, Stefani Seibold wrote:
> > > Am Donnerstag, den 08.11.2012, 20:24 +0800 schrieb Yuanhan Liu:
>
> > Yes, it is. I will try
On Thu, 15 Nov 2012, Kirill A. Shutemov wrote:
> > > @@ -778,6 +790,11 @@ int copy_huge_pmd(struct mm_struct *dst_mm, struct
> > > mm_struct *src_mm,
> > > pte_free(dst_mm, pgtable);
> > > goto out_unlock;
> > > }
> > > + if (is_huge_zero_pmd(pmd)) {
> > > +
On Fri, 2012-11-09 at 19:29 +0800, hongbo.zhang wrote:
> From: "hongbo.zhang"
>
> This driver is based on the thermal management framework in thermal_sys.c. A
> thermal zone device is created with the trip points to which cooling devices
> can be bound, the current cooling device is cpufreq,
On Wed, 14 Nov 2012, Anton Vorontsov wrote:
> Thanks again for your inspirational comments!
>
Heh, not sure I've been too inspirational (probably more annoying than
anything else). I really do want generic memory pressure notifications in
the kernel and already have some ideas on how I can
On 11/15/2012 03:17 AM, Stephen Rothwell wrote:
Hi John,
Today's linux-next merge of the wireless-next tree got a conflict in
drivers/net/wireless/brcm80211/brcmfmac/wl_cfg80211.c between commit
d61f978b8f26 ("brcmfmac: fix typo in CONFIG_BRCMISCAN") from the tree
and commit f07998959d57
On Wed, Nov 14, 2012 at 08:49:54PM +, Grant Likely wrote:
> > +int of_device_is_stdout_path(struct device_node *dn)
> > +{
> > + const char *name;
> > +
> > + name = of_get_property(of_chosen, "linux,stdout-path", NULL);
> > + if (name == NULL)
> > + return 0;
>
On Thu, Nov 15, 2012 at 07:22:20AM +, Nithin Sujir wrote:
> > On Wed, 14 Nov 2012, Nithin Nayak Sujir wrote:
> >
> > > This was fixed by
> > >
> > > commit de0a41484c47d783dd4d442914815076aa2caac2
> > > Author: Paul Gortmaker
> > > Date: Mon Oct 1 11:43:49 2012 -0400
> > >
> > > tg3:
On Wed, Nov 14, 2012 at 02:33:44PM -0800, David Rientjes wrote:
> On Wed, 7 Nov 2012, Kirill A. Shutemov wrote:
>
> > diff --git a/mm/huge_memory.c b/mm/huge_memory.c
> > index ff834ea..0d903bf 100644
> > --- a/mm/huge_memory.c
> > +++ b/mm/huge_memory.c
> > @@ -701,6 +701,18 @@ static inline
On Wed, Nov 14, 2012 at 02:33:44PM -0800, David Rientjes wrote:
On Wed, 7 Nov 2012, Kirill A. Shutemov wrote:
diff --git a/mm/huge_memory.c b/mm/huge_memory.c
index ff834ea..0d903bf 100644
--- a/mm/huge_memory.c
+++ b/mm/huge_memory.c
@@ -701,6 +701,18 @@ static inline struct page
On Thu, Nov 15, 2012 at 07:22:20AM +, Nithin Sujir wrote:
On Wed, 14 Nov 2012, Nithin Nayak Sujir wrote:
This was fixed by
commit de0a41484c47d783dd4d442914815076aa2caac2
Author: Paul Gortmaker paul.gortma...@windriver.com
Date: Mon Oct 1 11:43:49 2012 -0400
On Wed, Nov 14, 2012 at 08:49:54PM +, Grant Likely wrote:
+int of_device_is_stdout_path(struct device_node *dn)
+{
+ const char *name;
+
+ name = of_get_property(of_chosen, linux,stdout-path, NULL);
+ if (name == NULL)
+ return 0;
+
+ if
On 11/15/2012 03:17 AM, Stephen Rothwell wrote:
Hi John,
Today's linux-next merge of the wireless-next tree got a conflict in
drivers/net/wireless/brcm80211/brcmfmac/wl_cfg80211.c between commit
d61f978b8f26 (brcmfmac: fix typo in CONFIG_BRCMISCAN) from the tree
and commit f07998959d57
On Wed, 14 Nov 2012, Anton Vorontsov wrote:
Thanks again for your inspirational comments!
Heh, not sure I've been too inspirational (probably more annoying than
anything else). I really do want generic memory pressure notifications in
the kernel and already have some ideas on how I can tie
On Fri, 2012-11-09 at 19:29 +0800, hongbo.zhang wrote:
From: hongbo.zhang hongbo.zh...@linaro.com
This driver is based on the thermal management framework in thermal_sys.c. A
thermal zone device is created with the trip points to which cooling devices
can be bound, the current cooling device
On Thu, 15 Nov 2012, Kirill A. Shutemov wrote:
@@ -778,6 +790,11 @@ int copy_huge_pmd(struct mm_struct *dst_mm, struct
mm_struct *src_mm,
pte_free(dst_mm, pgtable);
goto out_unlock;
}
+ if (is_huge_zero_pmd(pmd)) {
+ set_huge_zero_page(pgtable,
On Wed, Nov 14, 2012 at 08:03:49AM +0100, Stefani Seibold wrote:
Am Freitag, den 09.11.2012, 10:32 +0800 schrieb Yuanhan Liu:
On Thu, Nov 08, 2012 at 01:37:15PM +0100, Stefani Seibold wrote:
Am Donnerstag, den 08.11.2012, 20:24 +0800 schrieb Yuanhan Liu:
Yes, it is. I will try log API
On Wed, 14 Nov 2012, Jens Axboe wrote:
Date: Wed, 14 Nov 2012 08:21:41 -0700
From: Jens Axboe ax...@kernel.dk
To: Lukáš Czerner lczer...@redhat.com
Cc: linux-kernel@vger.kernel.org, linux-fsde...@vger.kernel.org,
jmo...@redhat.com, a...@linux-foundation.org
Subject: Re: [PATCH v3] loop:
On Saturday 10 November 2012 02:40 AM, Stephen Warren wrote:
On 11/09/2012 11:44 AM, Thierry Reding wrote:
On Fri, Nov 09, 2012 at 10:34:41AM -0700, Stephen Warren wrote:
...
I really hope soon that Tegra will support DT bindings for clocks
so we can get rid of the AUXDATA, but unfortunately
On 11/15/2012 05:58 AM, Axel Lin :
of_match_device() may return NULL.
Signed-off-by: Axel Lin axel@ingics.com
Seems sensible,
Acked-by: Nicolas Ferre nicolas.fe...@atmel.com
---
This resend CC Jean-Christophe.
drivers/pinctrl/pinctrl-at91.c | 17 +
1 file
On Wed, Nov 14, 2012 at 03:08:45PM -0800, David Rientjes wrote:
On Wed, 7 Nov 2012, Kirill A. Shutemov wrote:
diff --git a/include/linux/mm.h b/include/linux/mm.h
index fa06804..fe329da 100644
--- a/include/linux/mm.h
+++ b/include/linux/mm.h
@@ -516,6 +516,14 @@ static inline pte_t
with the last detached port state file remaining , usbip reports error on
attaching. So clean up the state files on detaching.
Signed-off-by: Harvey Yang harvey.huawei.y...@gmail.com
---
drivers/staging/usbip/userspace/src/usbip_detach.c |9 +
1 files changed, 9 insertions(+), 0
Hi,
Since the 32KHz clock was removed from the twl-regulator (0e8e5c34
regulator: twl: Remove references to 32kHz clock from DT bindings),
we've been having problems with our wl12xx chip that is connected
through the omap_hsmmc.
Our card simply doesn't get added to the system and we get lots of
On 15 November 2012 16:13, Zhang Rui rui.zh...@intel.com wrote:
On Fri, 2012-11-09 at 19:29 +0800, hongbo.zhang wrote:
From: hongbo.zhang hongbo.zh...@linaro.com
This driver is based on the thermal management framework in thermal_sys.c. A
thermal zone device is created with the trip points to
UARTs no longer require call-back information, since the reset
call-back was removed in 43b5f0d69291374f602ad8e1817f329573a59010.
The only AUXDATA dependencies remaining for UARTs are DMA settings.
Signed-off-by: Lee Jones lee.jo...@linaro.org
---
arch/arm/mach-ux500/cpu-db8500.c |3 +--
1
15.11.2012 01:01, J. Bruce Fields пишет:
On Mon, Nov 12, 2012 at 12:37:54PM +0400, Stanislav Kinsbursky wrote:
07.11.2012 22:33, J. Bruce Fields пишет:
On Tue, Nov 06, 2012 at 08:36:05AM -0500, J. Bruce Fields wrote:
On Tue, Nov 06, 2012 at 08:10:18AM -0500, Christoph Hellwig wrote:
On Tue,
601 - 700 of 1366 matches
Mail list logo
