On Wed 11-07-12 11:48:54, Hugh Dickins wrote:
> On Tue, 10 Jul 2012, Michal Hocko wrote:
> > On Mon 09-07-12 13:37:39, Hugh Dickins wrote:
> > > On Mon, 9 Jul 2012, Michal Hocko wrote:
> > > >
> > > > Maybe I am missing something but who does the uncharge from:
> > > > shmem_unuse
> > > >
On Thu, 2012-07-12 at 15:43 +0200, Thomas Gleixner wrote:
> On Thu, 12 Jul 2012, Mike Galbraith wrote:
> > On Thu, 2012-07-12 at 15:31 +0200, Thomas Gleixner wrote:
> > > A quick check for memcpy finds that __btrfs_close_devices() does a
> > > memcpy of btrfs_device structs w/o initializing the
On Tue, Jul 10, 2012 at 10:18:30PM +0800, w...@linux.intel.com wrote:
> Hi Al,
>
> The linux-next kernel reliably hung after this line:
>
> [4.846260] debug: unmapping init [mem
> 0x88000182a000-0x8800019f]
FYI, in another config (attached), it hangs after:
[6.803484]
On 07/12/2012 03:23 PM, Udo van den Heuvel wrote:
> How to list what modules/programs are using that irq?
cat /proc/interrupts
--
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
On Thu, 12 Jul 2012, Mike Galbraith wrote:
> On Thu, 2012-07-12 at 15:31 +0200, Thomas Gleixner wrote:
> > A quick check for memcpy finds that __btrfs_close_devices() does a
> > memcpy of btrfs_device structs w/o initializing the lock in the new
> > copy, but I have no idea whether that's the
Hi, Linus,
Jens is still on vacation, and this is a pretty important patch to get
merged. Would you mind taking a look?
This commit:
commit 080399aaaf3531f5b8761ec0ac30ff98891e8686
Author: Jeff Moyer
Date: Fri May 11 16:34:10 2012 +0200
block: don't mark buffers beyond end of disk as
Insert exynos5 TMU sensor changes into the thermal driver. Some exynos4
changes are made generic for exynos series.
[a...@linux-foundation.org: fix comment layout]
Signed-off-by: SangWook Ju
Signed-off-by: Amit Daniel Kachhap
Cc: Donggeun Kim
Acked-by: Guenter Roeck
Cc: Durgadoss
Cc: Len
Add necessary default platform data support needed for TMU driver. This
dt/non-dt values are tested for origen exynos4210 and smdk exynos5250
platforms.
Signed-off-by: Amit Daniel Kachhap
Cc: Donggeun Kim
Acked-by: Guenter Roeck
Cc: SangWook Ju
Cc: Durgadoss
Cc: Len Brown
Cc: Jean Delvare
This code added creates a link between temperature sensors, linux thermal
framework and cooling devices for samsung exynos platform. This layer
monitors the temperature from the sensor and informs the generic thermal
layer to take the necessary cooling action.
[a...@linux-foundation.org: fix
This movement is needed because the hwmon entries and corresponding sysfs
interface is a duplicate of utilities already provided by
driver/thermal/thermal_sys.c. The goal is to place it in thermal folder
and add necessary functions to use the in-kernel thermal interfaces.
Signed-off-by: Amit
This patchset introduces a new generic cooling device based on cpufreq
that can be used on non-ACPI platforms. As a proof of concept, we have
drivers for the following platforms using this mechanism now:
* Samsung Exynos (Exynos4 and Exynos5) in the current patchset.
* TI OMAP
Hi Len,
This series is a repost of the thermal support for exynos platform.
These set of patches were already accepted for 3.5 merge.
(https://lkml.org/lkml/2012/6/2/7) but somehow could not go through so,
I am resending them again with rebasing against 3.5-rc6. Please apply them
for 3.6 merge.
On 07/11/2012 09:52 PM, Yasuaki Ishimatsu wrote:
> Does the following patch include your comment? If O.K., I will separate
> the patch from the series and send it for bug fix.
Looks sane to me. It does now mean that the calling conventions for
some of the other firmware_map*() functions are
On Thu, Jul 12, 2012 at 02:29:38PM +0200, Michal Hocko wrote:
>On Thu 12-07-12 19:51:25, Wanpeng Li wrote:
>> On Thu, Jul 12, 2012 at 01:08:38PM +0200, Michal Hocko wrote:
>> >On Thu 12-07-12 18:39:21, Wanpeng Li wrote:
>> >> From: Wanpeng Li
>> >>
>> >> Function mem_cgroup_do_charge will call
On Thu, 2012-07-12 at 15:31 +0200, Thomas Gleixner wrote:
> On Thu, 12 Jul 2012, Mike Galbraith wrote:
> > On Thu, 2012-07-12 at 13:43 +0200, Thomas Gleixner wrote:
> > > rawlock points to ...968 and the node_list to ...970.
> > >
> > > struct rt_mutex {
> > > raw_spinlock_t
On Wed, 11 Jul 2012, Konrad Rzeszutek Wilk wrote:
> >> > contacts, with Grant and Olof joining in as time permits.
> >>
> >> Acked-by: Grant Likely
> >
> > I would be interested in attending it as well. I believe Stefano has a
> > strong
> > interest as well (since he and Ian Campbell are
On Thu, 12 Jul 2012, Mike Galbraith wrote:
> On Thu, 2012-07-12 at 13:43 +0200, Thomas Gleixner wrote:
> > rawlock points to ...968 and the node_list to ...970.
> >
> > struct rt_mutex {
> > raw_spinlock_t wait_lock;
> > struct plist_head wait_list;
> >
> > The
This patch-set makes UFS file-system stop using the VFS '->write_supers()'
call-back and the '->s_dirt' superblock field because I plan to remove them
once all users are gone.
Like some other similar patch-sets (affs, hfs, hfsplus, reiserfs), we switch to
a delayed job for writing out the
From: Artem Bityutskiy
This patch makes UFS stop using the VFS '->write_super()' method along with
the 's_dirt' superblock flag, because they are on their way out.
The way we implement this is that we schedule a delay job instead relying on
's_dirt' and '->write_super()'.
The whole "superblock
From: Artem Bityutskiy
UFS calls 'ufs_write_super()' from 'ufs_put_super()' in order to write the
superblocks to the media. However, it is not needed because VFS calls
'->sync_fs()' before calling '->put_super()' - so by the time we are in
'ufs_write_super()', the superblocks are already
From: Artem Bityutskiy
This patch does not do any functional changes. It only moves 3 functions
in fs/ufs/super.c a little bit up in order to prepare for further changes
where I'll need this new arrangement to avoid forward declarations.
Signed-off-by: Artem Bityutskiy
---
fs/ufs/super.c |
On 2012-07-11 17:15, Alan Stern wrote:
> On Wed, 11 Jul 2012, Udo van den Heuvel wrote:
>
>> New occurrence:
>
>> Any clues and/or updates?
>
> Didn't you see the message I posted on Monday?
>
> http://marc.info/?l=linux-usb=134186054713868=2
Nothing changed except the kernel.
Main
Hi Rob,
Thank you for your comments.
(2012/07/06 21:54), Rob Landley wrote:
On 07/05/2012 05:51 AM, Mitsuo Hayasaka wrote:
Add an explantion about the sysfs parameter to the limit
maximum read/write request size.
Signed-off-by: Mitsuo Hayasaka
Cc: Rob Landley
Cc: Miklos Szeredi
---
> I fixed it up (I think - see below) and can carry the fix as necessary.
> Please check this and talk to each other ...
I also noticed the bindings today [1]. They came in via a seperate
patch (suboptimal) which has no ack by a devicetree maintainer which I'd
really like to see here, because
There is a big problem since 3.5-rc1 which potentially
mess the installations
rdev don't give longer back the root device like
/dev/sda1 , but in the bios form like 0x80010300
rdev is essential for the installation programs and for
the installation f.ex. of lilo . It's not conveniente
On 07/12/2012 02:14 PM, Rob Herring wrote:
+Required child properties:
+- reg : should contain the individual bit and polarity to control
+the clock gate. A polarity of 0 means that by setting the
+bit to 1 the clock passes through the clock gate while
+setting the bit to 0
-Removed unnecessary OOM messages.
-Removed embedded message prefixes.
-Added __func__ to some pr_err messages.
-Converted printk(KERN_ERR to pr_err
-Refactored split printk strings onto a single line
-Removed the space before the '!'.
Signed-off-by: Toshiaki Yamane
---
-Added pr_fmt.
-Converted printk(KERN_INFO to pr_info
-Removed embedded message prefixes.
Signed-off-by: Toshiaki Yamane
---
drivers/staging/panel/panel.c | 12 +++-
1 files changed, 7 insertions(+), 5 deletions(-)
diff --git a/drivers/staging/panel/panel.c
Deleted #if 0 blocks
Signed-off-by: Toshiaki Yamane
---
drivers/staging/panel/panel.c | 10 --
1 files changed, 0 insertions(+), 10 deletions(-)
diff --git a/drivers/staging/panel/panel.c b/drivers/staging/panel/panel.c
index 7365089..c625567 100644
---
On 7/12/2012 5:09 AM, Stephen Rothwell wrote:
Hi all,
Today's linux-next merge of the net-next tree got a conflict in
drivers/net/ethernet/mellanox/mlx4/main.c between commit 6634961c14d3
("mlx4: Put physical GID and P_Key table sizes in mlx4_phys_caps struct
and paravirtualize them") from the
On 7/12/2012 5:13 AM, Stephen Rothwell wrote:
Hi all,
Today's linux-next merge of the net-next tree got a conflict in
include/linux/mlx4/device.h between commit 396f2feb05d7 ("mlx4_core:
Implement mechanism for reserved Q_Keys") from the infiniband tree and
commit 0ff1fb654bec ("{NET, IB}/mlx4:
REGULATOR_STATUS_UNDEFINED is to be returned by regulator, if any other state
doesn't really apply.
Signed-off-by: Krystian Garbaciak
---
drivers/regulator/core.c |5 -
include/linux/regulator/driver.h |2 ++
2 files changed, 6 insertions(+), 1 deletions(-)
diff --git
On Tue, Jul 10, 2012 at 04:52:03PM +0400, Michael Tokarev wrote:
> I tried to debug this again, maybe to reproduce in a virtual machine,
> and found out that it is only 32bit server code shows this issue:
> after updating the kernel on the server to 64bit (the same version)
> I can't reproduce
On 07/12/2012 05:10 PM, Yasuaki Ishimatsu wrote:
> Even if acpi_processor_handle_eject() offlines cpu, there is a chance
> to online the cpu after that. So the patch closes the window by using
> get/put_online_cpus().
>
> Why does the patch change _cpu_up() logic?
>
> The patch cares the race of
Instead of aborting the probe in case a slot initialization fails, allow
initialization of as many slots as possible. If there are atleast one
instance of slot that is successfully initialized, allow the driver probe
to succeed.
Signed-off-by: Thomas Abraham
---
drivers/mmc/host/dw_mmc.c | 23
Hi,
I just now checked in the kernel archives if the patch in section 3.2 mentioned
in RFC 5961 for RST attacks with predictable sequence numbers.
I see some discussion happened in 2004 timeframe.
I was just wondering if in the latest linux source, the patch is made available.
Appreciate your
Some platforms allow for clock gating and control of bus interface unit clock
and card interface unit clock. Add support for clock lookup of optional biu
and ciu clocks for clock gating and clock speed determination.
Signed-off-by: Abhilash Kesavan
Signed-off-by: Thomas Abraham
---
Add device tree based discovery support.
Signed-off-by: Thomas Abraham
---
.../devicetree/bindings/mmc/synposis-dw-mshc.txt | 108 +++
drivers/mmc/host/dw_mmc-pltfm.c| 24 +++
drivers/mmc/host/dw_mmc.c | 201 +++-
The instantiation of the Synopsis Designware controller on Exynos5250
include extension for SDR and DDR specific tx/rx phase shift timing
and CIU internal divider. In addition to that, the option to skip the
command hold stage is also introduced. Add support for these Exynos5250
specfic
If the write protect pad of the controller is not connected to the write
protect pin of the slot, the driver should be notified of this condition
so that incorrect check for write protection by reading the WRTORT
register can avoided. The get_ro platform callback can be used for in
such cases, but
The 'struct dw_mci' maintains a copy of the pdev->dev instance instead of
maintaining a reference to that 'struct device' instance. Any resource
allocated using the device resource management kernel API with the instance
of 'struct device' in 'struct dw_mci' is then incorrect. Fix this by
This patch series adds device tree support for Synopsis Designware Mobile
Storage Host Controller.
The first patch converts the copy of controller device instance into a
reference. This is need to allow device resource management api to correctly
manage the resources allocated by the driver. The
(2012/07/12 4:50), Steven Rostedt wrote:
> From: Steven Rostedt
>
> Add saving full regs for function tracing on i386.
> The saving of regs was influenced by patches sent out by
> Masami Hiramatsu.
>
> Cc: Masami Hiramatsu
> Signed-off-by: Steven Rostedt
> ---
> arch/x86/include/asm/ftrace.h
On 07/12/2012 04:52 PM, Yasuaki Ishimatsu wrote:
> Even if cpu_down() fails, acpi_processor_remove() continues to remove the cpu.
> But in this case, it should return error number since some process may run on
> the cpu. If the cpu has a running process and the cpu is turned the power off,
> the
On 07/11/2012 07:17 AM, Ingo Molnar wrote:
>
> * John Stultz wrote:
>
>> Over the weekend, Thomas got a chance to review the leap
>> second fix in more detail and had a few additional changes he
>> wanted to make to improve performance as well as style.
John,
FYI -- Using a mix of AMD
On 07/12/2012 03:44 AM, Jan Ceuleers wrote:
> On 07/11/2012 06:47 PM, John Stultz wrote:
>> I'll see if my worry is unfounded, but it might be a bit too clever for rare
>> events.
>
> Full ACK.
>
> There is an unfortunate history of critical-to-moderately-serious bugs in
> the leap second
On 07/12/2012 11:25 AM, Raghavendra K T wrote:
>>
>> The problem occurs even with no overcommit at all. One vcpu is in a
>> legitimately long pause loop. All those exits accomplish nothing, since
>> all vcpus are scheduled. Better to let it spin in guest mode.
>>
>
> I agree. One idea is we
This patch adjusts the LPC32xx MLC NAND driver to the new pl08x DMA interface,
fixing the compile error resulting from changed pl08x structures.
Signed-off-by: Roland Stigge
---
Applies to today's linux-next (integrated lpc32xx-next and dma branches which
collide)
On Thu 12-07-12 19:51:25, Wanpeng Li wrote:
> On Thu, Jul 12, 2012 at 01:08:38PM +0200, Michal Hocko wrote:
> >On Thu 12-07-12 18:39:21, Wanpeng Li wrote:
> >> From: Wanpeng Li
> >>
> >> Function mem_cgroup_do_charge will call mem_cgroup_reclaim,
> >> there are two break points in
This patch adjusts the LPC32xx platform support to the new pl08x DMA interface,
fixing the compile error resulting from changed pl08x structures.
Signed-off-by: Roland Stigge
---
Applies to today's linux-next (integrated lpc32xx-next and dma branches which
collide)
This patch adjusts the LPC32xx SLC NAND driver to the new pl08x DMA interface,
fixing the compile error resulting from changed pl08x structures.
Signed-off-by: Roland Stigge
---
Applies to today's linux-next (integrated lpc32xx-next and dma branches which
collide)
On 07/12/2012 02:15 AM, Sebastian Hesselbarth wrote:
> As Rob's clock binding support patch is now up on clk-next, I'd like to
> draw attention on this patch again.
> --
> This patch adds support for using clock gates (clk-gate) from DT based
> on Rob Herrings DT clk binding support for 3.6.
>
>
(2012/07/12 4:50), Steven Rostedt wrote:
> From: Steven Rostedt
>
> Add a way to have different functions calling different trampolines.
> If a ftrace_ops wants regs saved on the return, then have only the
> functions with ops registered to save regs. Functions registered by
> other ops would
On 12/07/12 12:49, Roger Pau Monne wrote:
> David Vrabel wrote:
>> On 09/07/12 15:45, Konrad Rzeszutek Wilk wrote:
>>> On Fri, Jun 22, 2012 at 05:14:41PM +0100, Stefano Stabellini wrote:
We used to rely on a core_initcall to initialize Xen on ARM, however
core_initcalls are actually
On Wed, Jul 11, 2012 at 7:51 PM, Joe Perches wrote:
> On Wed, 2012-07-11 at 19:25 +0200, Kay Sievers wrote:
>> > If your solution is just for the dev_ messages
>> > (ie: with vprintk_emit descriptors), then it's not
>> > too ugly.
>>
>> Yeah, I thought only about these. But there might be more
On Thursday 12 July 2012 05:28 PM, Wolfram Sang wrote:
* PGP Signed by an unknown key
Can you please point me your git path so that I can verify it?
git://git.pengutronix.de/git/wsa/linux.git i2c-embedded/for-next
or
> Can you please point me your git path so that I can verify it?
git://git.pengutronix.de/git/wsa/linux.git i2c-embedded/for-next
or
http://git.pengutronix.de/?p=wsa/linux.git;a=shortlog;h=refs/heads/i2c-embedded/for-next
--
Pengutronix e.K. | Wolfram Sang
On Thu, 2012-07-12 at 13:43 +0200, Thomas Gleixner wrote:
> On Thu, 12 Jul 2012, Mike Galbraith wrote:
> > On Thu, 2012-07-12 at 10:44 +0200, Mike Galbraith wrote:
> > > On Thu, 2012-07-12 at 07:47 +0200, Mike Galbraith wrote:
> > > > Greetings,
> > > >
> > > > I'm chasing btrfs critters in an
On Thu 12-07-12 12:26:45, Will Deacon wrote:
> On Thu, Jul 12, 2012 at 12:16:59PM +0100, Michal Hocko wrote:
> > On Wed 11-07-12 18:48:02, Will Deacon wrote:
> > > Just to confirm, the following quick hack at least results in the correct
> > > flushing for me (on ARM):
> > >
> > >
> > > diff
Linus, please pull a couple of KVM fixes from:
git://git.kernel.org/pub/scm/virt/kvm/kvm.git master
One is an adjustment for an irq layer change that affected device
assignment, the other a one-liner ppc fix.
Alex Williamson
On Thu, Jul 12, 2012 at 01:08:38PM +0200, Michal Hocko wrote:
>On Thu 12-07-12 18:39:21, Wanpeng Li wrote:
>> From: Wanpeng Li
>>
>> Function mem_cgroup_do_charge will call mem_cgroup_reclaim,
>> there are two break points in mem_cgroup_reclaim:
>> if (total && (flag &
David Vrabel wrote:
> On 09/07/12 15:45, Konrad Rzeszutek Wilk wrote:
>> On Fri, Jun 22, 2012 at 05:14:41PM +0100, Stefano Stabellini wrote:
>>> We used to rely on a core_initcall to initialize Xen on ARM, however
>>> core_initcalls are actually called after early consoles are initialized.
>>>
On Thu, 12 Jul 2012, Mike Galbraith wrote:
> On Thu, 2012-07-12 at 10:44 +0200, Mike Galbraith wrote:
> > On Thu, 2012-07-12 at 07:47 +0200, Mike Galbraith wrote:
> > > Greetings,
> > >
> > > I'm chasing btrfs critters in an enterprise 3.0-rt kernel, and just
> > > checked to see if they're
Even if acpi_processor_handle_eject() offlines cpu, there is a chance
to online the cpu after that. So the patch closes the window by using
get/put_online_cpus().
Why does the patch change _cpu_up() logic?
The patch cares the race of hot-remove cpu and _cpu_up(). If the patch
does not change it,
acpi_bus_trim() stops removing devices, when acpi_bus_remove() return error
number. But acpi_bus_remove() cannot return error number correctly.
acpi_bus_remove() only return -EINVAL, when dev argument is NULL. Thus even if
device cannot be removed correctly, acpi_bus_trim() ignores and continues
Even if acpi_processor_handle_eject() offlines cpu, there is a chance
to online the cpu after that. So the patch closes the window by using
get/put_online_cpus().
Why does the patch change _cpu_up() logic?
The patch cares the race of hot-remove cpu and _cpu_up(). If the patch
does not change it,
On Thu, Jul 12, 2012 at 12:16:59PM +0100, Michal Hocko wrote:
> On Wed 11-07-12 18:48:02, Will Deacon wrote:
> > Just to confirm, the following quick hack at least results in the correct
> > flushing for me (on ARM):
> >
> >
> > diff --git a/mm/hugetlb.c b/mm/hugetlb.c
> > index e198831..7a7c9d3
On Thu, 2012-07-12 at 11:12 +0300, Avi Kivity wrote:
> On 07/12/2012 05:17 AM, Benjamin Herrenschmidt wrote:
> >> ARM doesn't have an instruction for cpu_relax(), so it can't intercept
> >> it. Given ppc's dislike of overcommit, and the way it implements
> >> cpu_relax() by adjusting hw thread
On Thu, 2012-07-12 at 13:16 +0200, Michal Hocko wrote:
> On Wed 11-07-12 18:48:02, Will Deacon wrote:
> > On Tue, Jul 10, 2012 at 11:42:34AM +0100, Will Deacon wrote:
> > > On Tue, Jul 10, 2012 at 10:45:13AM +0100, Will Deacon wrote:
> > > > On Tue, Jul 10, 2012 at 12:57:14AM +0100, Hugh Dickins
On Thu, 2012-07-12 at 00:05 -0700, Gerard Snitselaar wrote:
> Commit 9778b696 (powerpc: Use CURRENT_THREAD_INFO instead of open
> coded assembly) got a rejected merge file iommu.c.rej committed with
> it.
Oops, that's me having too much coffee & using git citool ... I'll get
rid of it, thanks.
Hi
On Thu, Nov 18, 2010 at 6:17 PM, Tatyana Brokhman
wrote:
>
> Add config_ep_by_speed() to configure the endpoint according to the gadget
> speed. Using this function will spare the FDs from handling the endpoint
> chosen descriptor.
>
> Signed-off-by: Tatyana Brokhman
> ---
>
Even if cpu_down() fails, acpi_processor_remove() continues to remove the cpu.
But in this case, it should return error number since some process may run on
the cpu. If the cpu has a running process and the cpu is turned the power off,
the system may not work well.
Signed-off-by: Yasuaki
On Wed 11-07-12 18:48:02, Will Deacon wrote:
> On Tue, Jul 10, 2012 at 11:42:34AM +0100, Will Deacon wrote:
> > On Tue, Jul 10, 2012 at 10:45:13AM +0100, Will Deacon wrote:
> > > On Tue, Jul 10, 2012 at 12:57:14AM +0100, Hugh Dickins wrote:
> > > > If I start to grep the architectures for
On Thu 12-07-12 18:39:21, Wanpeng Li wrote:
> From: Wanpeng Li
>
> Function mem_cgroup_do_charge will call mem_cgroup_reclaim,
> there are two break points in mem_cgroup_reclaim:
> if (total && (flag & MEM_CGROUP_RECLAIM_SHIRINK))
> break;
> if (mem_cgroup_margin(memcg))
> break;
>
On Thu, 12 Jul 2012, Mike Galbraith wrote:
> crash> struct rt_mutex 0x8801770601c8
> struct rt_mutex {
> wait_lock = {
> raw_lock = {
> slock = 7966
> }
> },
> wait_list = {
> node_list = {
> next = 0x880175eedbe0,
> prev = 0x880175eedbe0
> },
The function dup_task() may fail at the following function calls in
the following order.
0) alloc_task_struct_node()
1) alloc_thread_info_node()
2) arch_dup_task_struct()
Error by 0) is not a matter, it can just return. But error by 1)
requires releasing task_struct allocated by 0) before it
On 07/12/2012 04:28 PM, Nikunj A Dadhania wrote:
On Wed, 11 Jul 2012 16:22:29 +0530, Raghavendra K
T wrote:
On 07/11/2012 02:23 PM, Avi Kivity wrote:
This adds some tiny overhead to vcpu entry. You could remove it by
using the vcpu->requests mechanism to clear the flag, since
On Thu, Jul 12, 2012 at 1:25 AM, Kevin Hilman wrote:
> There is quite a bit of other things to do in remove to properly cleanup
> what is done in probe.
OK I'm dropping this patch for now...
Yours,
Linus Walleij
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the
On Wed, 11 Jul 2012 16:22:29 +0530, Raghavendra K T
wrote:
> On 07/11/2012 02:23 PM, Avi Kivity wrote:
> >
> > This adds some tiny overhead to vcpu entry. You could remove it by
> > using the vcpu->requests mechanism to clear the flag, since
> > vcpu->requests is already checked on every entry.
On Thu, Jul 12, 2012 at 12:09 PM, Marc Zyngier wrote:
> On Thu, 12 Jul 2012 02:18:42 +0200, Linus Walleij
> wrote:
>
> Hi Linus,
>
>> I'm reviewing the only patch I really understand...
>>
>> 2012/7/6 Catalin Marinas :
>>
>>> +/* This isn't really used any more */
>>> +#define CLOCK_TICK_RATE
On Thu, Jul 12, 2012 at 03:50:15PM +0800, Gao feng wrote:
> there are some out of bound accesses in netprio cgroup.
>
> now before accessing the dev->priomap.priomap array,we only check
> if the dev->priomap exist.and because we don't want to see
> additional bound checkings in fast path, so we
Hi,
> -Original Message-
> From: Wei Ni [mailto:w...@nvidia.com]
> Sent: Thursday, July 12, 2012 3:53 PM
> To: Zhang, Rui; Brown, Len; a...@linux-foundation.org; kh...@linux-fr.org;
> j...@perches.com; R, Durgadoss
> Cc: linux-kernel@vger.kernel.org; linux-te...@ger.kernel.org;
>
Case REGULATOR_STATUS_STANDBY -> REGULATOR_MODE_STANDBY.
Signed-off-by: Krystian Garbaciak
---
drivers/regulator/core.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/regulator/core.c b/drivers/regulator/core.c
index 09a737c..af44b94 100644
---
On Thu, Jul 12, 2012 at 1:42 AM, Mike Turquette wrote:
> This has been fixed in Pawell's patch, "clk: Check parent for NULL in
> clk_change_rate".
Yes, that'll probably work.
A small nitpick though:
I have slightly different semantics, Pawel's patch assigns zero if
parent is NULL, then use
On Wed, 11 Jul 2012 14:04:03 +0300, Avi Kivity wrote:
>
> > So this would probably improve guests that uses cpu_relax, for example
> > stop_machine_run. I have no measurements, though.
>
> smp_call_function() too (though that can be converted to directed yield
> too). It seems worthwhile.
>
On Thu, Jul 12, 2012 at 12:39 PM, Linus Walleij
wrote:
> On Wed, Jul 11, 2012 at 9:01 PM, Sedat Dilek wrote:
>
>> BTW, didn't see your tree in linux-next [1].
>>
>> [1]
>> http://git.kernel.org/?p=linux/kernel/git/next/linux-next.git;a=blob;f=Next/Trees#l184
>
> Look at line 185?
>
Yesterday
On Wed, Jul 11, 2012 at 03:48:28PM -0500, Seth Jennings wrote:
> On 07/11/2012 02:42 PM, Konrad Rzeszutek Wilk wrote:
> Which architecture was this under? It sounds x86-ish? Is this on
> Westmere and more modern machines? What about Core2 architecture?
>
> Oh how did it work on
From: Wanpeng Li
Function mem_cgroup_do_charge will call mem_cgroup_reclaim,
there are two break points in mem_cgroup_reclaim:
if (total && (flag & MEM_CGROUP_RECLAIM_SHIRINK))
break;
if (mem_cgroup_margin(memcg))
break;
so mem_cgroup_reclaim can't guarantee reclaim enough
On Wed, Jul 11, 2012 at 9:01 PM, Sedat Dilek wrote:
> BTW, didn't see your tree in linux-next [1].
>
> [1]
> http://git.kernel.org/?p=linux/kernel/git/next/linux-next.git;a=blob;f=Next/Trees#l184
Look at line 185?
Yours,
Linus Walleij
--
To unsubscribe from this list: send the line
On Thu, Jul 5, 2012 at 10:06 AM, Cong Meng wrote:
> This patch implements the hotplug support for virtio-scsi.
> When there is a device attached/detached, the virtio-scsi driver will be
> signaled via event virtual queue and it will add/remove the scsi device
> in question automatically.
>
> v2:
On Thursday 12 July 2012 04:05 PM, Wolfram Sang wrote:
* PGP Signed by an unknown key
On Tue, Jul 10, 2012 at 04:50:44PM +0530, Laxman Dewangan wrote:
To provide the late suspend and early resume for i2c
driver, convert the suspend/resume as
suspend-> suspend_noirq
resume ->
On Tue, Jul 10, 2012 at 04:50:44PM +0530, Laxman Dewangan wrote:
> To provide the late suspend and early resume for i2c
> driver, convert the suspend/resume as
> suspend-> suspend_noirq
> resume -> resume_noirq
>
> Signed-off-by: Laxman Dewangan
Applied to next on top of Rafael's
From: Rafael J. Wysocki
Make the OLPC XO15 SCI driver define its resume callback through
a struct dev_pm_ops object rather than by using a legacy PM hook
in struct acpi_device_ops.
Signed-off-by: Rafael J. Wysocki
---
This patch was missing from my patchset converting ACPI do the PM handling
Hi, all
I'm working on the tegra thermal throttling upstream issue.
The tegra30 board use the nct1008 as the thermal sensor, and the lm90 is
the sensor driver. We want to use the generic thermal sysfs.
My question is where should we register the thermal zone device? We may
have two place to do
On Thu 12-07-12 17:32:11, Wanpeng Li wrote:
> On Wed, Jul 11, 2012 at 03:47:57PM +0200, Michal Hocko wrote:
> >On Wed 11-07-12 21:24:41, Wanpeng Li wrote:
> >> From: Wanpeng Li
> >>
> >> Since hierachical_memory_limit shows "of bytes of memory limit with
> >> regard to hierarchy under which the
On Thu 12-07-12 18:05:19, Minchan Kim wrote:
> Hi Michal,
>
> On Thu, Jul 12, 2012 at 10:19:23AM +0200, Michal Hocko wrote:
> > On Thu 12-07-12 11:50:48, Minchan Kim wrote:
> > > In __zone_watermark_ok, free and min are signed long type
> > > while z->lowmem_reserve[classzone_idx] is unsigned
Otherwise they can't be filtered for a defined task.
perf record -e sched:sched_switch ./foo
This command doesn't report any event without this patch.
I think it isn't a big problem for security, if someone will know
who will be executed next. By default perf is disabled for non-root
users.
I
HAYASAKA Mitsuo writes:
> Hi Yuan and Han-Wen,
>
> Thank you for your comments.
>
> (2012/07/06 22:58), Han-Wen Nienhuys wrote:
>> On Fri, Jul 6, 2012 at 2:53 AM, Liu Yuan wrote:
>>> On 07/05/2012 06:50 PM, Mitsuo Hayasaka wrote:
One of the ways to solve this is to make them tunable.
Namjae Jeon writes:
>> I guess, if Windows truncates the above clusters than file size, it may
>> be prefer to truncate on linux too. We really need it over umount?
>> We never know the file whether corrupted or preallocated.
>>
>> And at least for now, it would be better to put under
or write.
It is not possible to use the CS line as a GPIO on some SoC, so we
need to workaround this by implementing a single SPI transfer to
access the PMIC.
Reviewed-by: Mark Brown
Acked-by: Marc Reilly
Signed-off-by: Philippe Rétornaz
Signed-off-by: Samuel Ortiz
Origin: next-20120712
601 - 700 of 1654 matches
Mail list logo
