On 08/08/2013 06:56 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.10.6 release.
There are 102 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be m
On Thu, 2013-08-08 at 23:02 +0800, ethan.zhao wrote:
> 在 2013-8-6，下午3:29，Mike Galbraith 写道：
>
> > +int sched_needs_cpu(int cpu)
> > +{
> > + return cpu_rq(cpu)->avg_idle < sysctl_sched_migration_cost;
> > +}
> > +
> > #else /* CONFIG_NO_HZ_COMMON */
> >
> > static inline bool got_nohz_idle_k
If there is more than one pca963x chips on the system and there are
some LEDs without platform_data names, the driver wont be able to
provide unique naming to them.
This will cause led_class_dev_register to fail, unregistering all the
LEDs of the chip.
This patch adds the i2c address to the name
Add support for PCA9634 chip, which belongs to the same family as the
9633 but with support for 8 outputs instead of 4.
Signed-off-by: Ricardo Ribalda Delgado
---
drivers/leds/Kconfig|7 ++--
drivers/leds/leds-pca9633.c | 74 +++
2 files chan
To update an LED a register has to be read, updated and writen. If
another LED whas been updated at the same time, this could lead into
wrong updates.
This patch addes a common mutex to all the leds of the same chip to
protect the ledout register.
Signed-off-by: Ricardo Ribalda Delgado
---
driv
The driver now supports the chips pca9633 and pca9634, therefore we
rename the files to more genereic and meaningul names
Signed-off-by: Ricardo Ribalda Delgado
---
drivers/leds/Kconfig |2 +-
drivers/leds/Makefile |2 +-
drivers/leds/leds-pca96
Add Support for the PCA9634 chip. Simimart to the 9633, but with 8 outputs
instead of 4.
Fix bug when 2 chips where present on the system, the ledclass will fail and
the chip wont probe.
Protect ledout register with a mutex to support updates of more than leds at
the same time
v2: Contains fee
On Wed, Aug 07, 2013 at 06:15:50PM -0500, Fionnuala Gunter wrote:
> This patch fixes a bug that is triggered when cts(cbc(aes)) is used with
> nx-crypto driver on input larger than 32 bytes.
>
> The chaining value from co-processor was not being saved. This value is
> needed because it is used as
Hello Bryan
I understand your concerns, but I think that it is more practical to
keep the old names.
First of all there will be some defconfig that we will break with the
new names, the same will happen with the platform data. I know that we
don't have to support out of tree systems, but it wont
On Fri, Aug 02, 2013 at 12:09:50PM +, Marcelo Cerri wrote:
> This series of patches fixes two bugs that are triggered when the input data
> is
> too large. The first one is caused by the miscalculation of physical addresses
> and the second one by some limits that the co-processor has to the i
On Fri, 09 Aug 2013 00:41:25 +0200, Tomasz Figa wrote:
> Hi KyongHo,
>
> On Thursday 08 of August 2013 18:38:49 Cho KyongHo wrote:
> > This commit adds device tree support for System MMU.
> > This also include the following changes and enhancements:
> >
> > * use managed device helper functions.
On Fri, Aug 09, 2013 at 04:25:04PM +1000, Benjamin Herrenschmidt wrote:
> On Wed, 2013-08-07 at 18:15 -0500, Fionnuala Gunter wrote:
> > This patch fixes a bug that is triggered when cts(cbc(aes)) is used with
> > nx-crypto driver on input larger than 32 bytes.
> >
> > The chaining value from co-p
Separate out GTK codes to a shared object called libperf-gtk.so. This
time only GTK codes are built with -fPIC and libperf remains as is.
Cc: Andi Kleen
Reviewed-by: Pekka Enberg
Signed-off-by: Namhyung Kim
---
tools/perf/Makefile| 42 ++
tools/
Call setup/exit GTK browser function using libdl.
Cc: Andi Kleen
Reviewed-by: Pekka Enberg
Signed-off-by: Namhyung Kim
---
tools/perf/ui/gtk/gtk.h | 3 +++
tools/perf/ui/setup.c | 50 +++--
tools/perf/ui/ui.h | 12 +---
3 files change
Run GTK hist and annotation browser using libdl.
Cc: Andi Kleen
Reviewed-by: Pekka Enberg
Signed-off-by: Namhyung Kim
---
tools/perf/builtin-annotate.c | 26 +++---
tools/perf/builtin-report.c | 16 ++--
tools/perf/config/Makefile| 2 +-
tools/perf/ui/gtk
Hi,
This is v3 of gtk code separation patchset to reduce library
dependencies of the perf executable.
I only built libperf-gtk.so with -fPIC, and it's not linked to libperf
at build time. All unresolved symbols used for perf should be
resolved at runtime via perf executable (so libperf.a) - I di
On Wed, 2013-08-07 at 18:15 -0500, Fionnuala Gunter wrote:
> This patch fixes a bug that is triggered when cts(cbc(aes)) is used with
> nx-crypto driver on input larger than 32 bytes.
>
> The chaining value from co-processor was not being saved. This value is
> needed because it is used as the IV
2013/7/22 Joe Perches :
> commit 3370dc916c ("pinctrl:sirf:re-arch and add support for
> new SiRFatlas6 SoC") moved the files, update the patterns.
>
> Signed-off-by: Joe Perches
> cc: Barry Song <21cn...@gmail.com>
> cc: Linus Walleij
Acked-by: Barry Song
> ---
> MAINTAINERS | 2 +-
> 1 file
On Thu, Aug 08, 2013 at 09:14:31AM +0300, Dan Aloni wrote:
> On Thu, Aug 8, 2013 at 8:50 AM, Neil Horman wrote:
> >
> > On Wed, Aug 07, 2013 at 12:02:44PM +0300, Dan Aloni wrote:
> [..]
> >
> > > When my 'ifup eth' script was fired multiple times and ran concurrent o>
> > > @@ -682,7 +689,11 @@ r
This patch fixes the use of XATTR_NODE_OFFSET.
o The offset should not use several MSB bits which are used by marking node
blocks.
o IS_DNODE should handle XATTR_NODE_OFFSET to avoid potential abnormality
during the fsync call.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/f2fs.h | 12 +++-
f
From: "Felipe F. Tonello"
This patch adds jack support for ALSA KControl.
This support is necessary since the new kcontrol is used by user-space
daemons, such as PulseAudio(>=2.0), to do jack detection.)
Also, HDA's CONFIG_SND_HDA_INPUT_JACK is disabled because it causes to use
standard
snd_ja
Previously xattr node blocks are stored to the COLD_NODE log, which means that
our roll-forward mechanism doesn't recover the xattr node blocks at all.
Only the direct node blocks in the WARM_NODE log can be recovered.
So, let's resolve the issue simply by conducting checkpoint during fsync when a
This patch introduces a new inline function, cur_cp_version, to reduce redundant
codes.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/checkpoint.c | 6 +++---
fs/f2fs/f2fs.h | 7 ++-
fs/f2fs/file.c | 3 +--
fs/f2fs/recovery.c | 4 ++--
fs/f2fs/xattr.c | 2 +-
5 files changed, 13
Hi Arnaldo,
On Thu, 8 Aug 2013 12:21:16 -0300, Arnaldo Carvalho de Melo wrote:
> Em Thu, Aug 08, 2013 at 03:34:08PM +0900, Namhyung Kim escreveu:
>> Separate out GTK codes to a shared object called libperf-gtk.so. This
>> time only GTK codes are built with -fPIC and libperf remains as is.
>
> [ac
Hi all,
Changes since 20130808:
*crickets*
I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
(patches at http://www.kernel.org/pub/linux/kernel/next/ )
On 08/09/2013 05:33 AM, Guenter Roeck wrote:
> On 08/08/2013 01:40 PM, Stephen Warren wrote:
>> On 08/08/2013 02:36 PM, Sergei Shtylyov wrote:
>>> Hello.
>>>
>>> On 08/08/2013 10:56 AM, Wei Ni wrote:
>>>
Enable thermal sensor nct1008 for t114 dalmore.
>>>
Signed-off-by: Wei Ni
---
>
On Fri, 09 Aug 2013 00:26:51 +0200, Tomasz Figa wrote:
> Hi KyongHo,
>
> On Thursday 08 of August 2013 18:38:35 Cho KyongHo wrote:
> > Signed-off-by: Cho KyongHo
> > ---
> > .../bindings/iommu/samsung,exynos4210-sysmmu.txt | 103 +++
> > arch/arm/boot/dts/exynos4.dtsi
On 08/09/2013 01:37 AM, Stephen Warren wrote:
> On 08/08/2013 12:56 AM, Wei Ni wrote:
>> Add OF document for lm90 in Documentation/devicetree/.
>
>> diff --git a/Documentation/devicetree/bindings/hwmon/lm90.txt
>> b/Documentation/devicetree/bindings/hwmon/lm90.txt
>
>> +Required node properties:
On Friday, August 09, 2013 1:07 PM, Jingoo Han wrote:
>
> 'rd_size' is used only in this file.
> Fix the following sparse warning:
>
> drivers/block/brd.c:432:5: warning: symbol 'rd_size' was not declared. Should
> it be static?
>
> Signed-off-by: Jingoo Han
> ---
> drivers/block/brd.c |2
On 08/09/2013 01:35 AM, Stephen Warren wrote:
> On 08/08/2013 12:56 AM, Wei Ni wrote:
>> Enable thermal sensor nct1008 for t114 dalmore.
>
> It'd be best to remove this patch from the series; send one series to
> the LM90 maintainer with just the driver and DT binding changes, and
> another series
Hi Alan, hi Dominik,
maybe you want me to help out a bit - I'm having trouble getting a
Delock PCMCIA to USB-2 adapter to work under linux, with strange
behavior in some situations. The trouble is that while I can *read* via
fast (usb 2.0) transfers from the port, an ehci-triggered write just
On 08/08/2013 08:58 PM, Artem Bityutskiy wrote:
On Thu, 2013-08-08 at 16:06 -0700, Brian Norris wrote:
On Thu, Aug 08, 2013 at 04:33:35PM +0800, Huang Shijie wrote:
Hi Artem & Brian:
Hi Huang and others,
On Thu, May 16, 2013 at 8:17 PM, Huang Shijie wrote:
1.) Why add the ECC information to
On Thu, 08 Aug 2013 16:00:18 +0200, Tomasz Figa wrote:
> On Thursday 08 of August 2013 18:38:04 Cho KyongHo wrote:
> > Since kmalloc() does not guarantee that the allignment of 1KiB when it
> > allocates 1KiB, it is required to allocate lv2 page table from own
> > slab that guarantees alignment of
Hi all.
Instead of adding the support of regulators in each device, let's think about
whether it is possible to create a global regulator for any device on the I2C
bus.
I see it like this:
We add an extra field in the i2c_board_info structure "power_name" and handle
it in the i2c_device_{probe/r
'rng_dev' is used only in this file.
Fix the following sparse warning:
drivers/char/hw_random/picoxcell-rng.c:36:15: warning: symbol 'rng_dev' was not
declared. Should it be static?
Signed-off-by: Jingoo Han
---
drivers/char/hw_random/picoxcell-rng.c |2 +-
1 file changed, 1 insertion(+),
(2013/08/09 11:43), Gu Zheng wrote:
> Hi Ishimatsu-san,
> On 08/06/2013 06:11 PM, Yasuaki Ishimatsu wrote:
>
>> try_offline_node() checks that all cpus related with removed node have been
>> removed by using cpu_present_bits. If all cpus related with removed node have
>> been removed, try_offline_
On 08/09/2013 12:47 AM, Toshi Kani wrote:
add_memory() and remove_memory() can only handle a memory range aligned
with section. There are problems when an unaligned range is added and
then deleted as follows:
- add_memory() with an unaligned range succeeds, but __add_pages()
called from a
Hi David,
On Wed, 07 Aug 2013 09:44:24 -0400, David Ahern wrote:
> On 8/5/13 3:17 AM, Namhyung Kim wrote:
>>> I don't think this is a problem, its in line with Ingo's suggestion of a
>>> new perf ioctl to ask the kernel to generate PERF_RECORD_MMAP events for
>>> existing threads.
>>
>> Hmm.. coul
Quoting Stephen Boyd (2013-07-25 09:45:42)
> On 07/25, Tomasz Figa wrote:
> > On Wednesday 24 of July 2013 17:43:32 Stephen Boyd wrote:
> > > Some of Qualcomm's clocks can change their parent and rate at the
> > > same time with a single register write. Add support for this
> > > hardware to the co
This patch extends do_mbind() to handle vma with VM_HUGETLB set.
We will be able to migrate hugepage with mbind(2) after
applying the enablement patch which comes later in this series.
ChangeLog v3:
- revert introducing migrate_movable_pages
- added alloc_huge_page_noerr free from ERR_VALUE
Cha
Currently hugepage migration works well only for pmd-based hugepages
(mainly due to lack of testing,) so we had better not enable migration
of other levels of hugepages until we are ready for it.
Some users of hugepage migration (mbind, move_pages, and migrate_pages)
do page table walk and check p
This patch extends check_range() to handle vma with VM_HUGETLB set.
We will be able to migrate hugepage with migrate_pages(2) after
applying the enablement patch which comes later in this series.
Note that for larger hugepages (covered by pud entries, 1GB for
x86_64 for example), we simply skip it
This patch enables hugepage migration from migrate_pages(2),
move_pages(2), and mbind(2).
Signed-off-by: Naoya Horiguchi
Acked-by: Hillf Danton
Acked-by: Andi Kleen
Reviewed-by: Wanpeng Li
---
include/linux/mempolicy.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git v3.11-rc
Currently migrate_huge_page() takes a pointer to a hugepage to be
migrated as an argument, instead of taking a pointer to the list of
hugepages to be migrated. This behavior was introduced in commit
189ebff28 ("hugetlb: simplify migrate_huge_page()"), and was OK
because until now hugepage migration
Until now we can't offline memory blocks which contain hugepages because
a hugepage is considered as an unmovable page. But now with this patch
series, a hugepage has become movable, so by using hugepage migration we
can offline such memory blocks.
What's different from other users of hugepage mig
This patch extends move_pages() to handle vma with VM_HUGETLB set.
We will be able to migrate hugepage with move_pages(2) after
applying the enablement patch which comes later in this series.
We avoid getting refcount on tail pages of hugepage, because unlike thp,
hugepage is not split and we need
Before enabling each user of page migration to support hugepage,
this patch enables the list of pages for migration to link not only
LRU pages, but also hugepages. As a result, putback_movable_pages()
and migrate_pages() can handle both of LRU pages and hugepages.
ChangeLog v5:
- remove putback_a
Now we have extended hugepage migration and it's opened to many users
of page migration, which is a good reason to consider hugepage as movable.
So we can go to the direction to remove this parameter. In order to
allow userspace to prepare for the removal, let's leave this sysctl handler
as noop fo
Here is the 5th version of hugepage migration patchset.
Changes in this version are as follows:
- removed putback_active_hugepages() as a cleanup (1/9)
- added code to check movability of a given hugepage (8/9)
- set GFP MOVABLE flag depending on the movability of hugepage (9/9).
I feel that 8/
Hi,
Recently we met quite a lot of random kernel panic issues after enable
CONFIG_PROC_PAGE_MONITOR in kernel, after debuggint sometime we found
this has something to do with following bug in pagemap:
In struc pagemapread:
struct pagemapread {
int pos, len;
pagemap_entry_t *buffer;
b
Hi Linus
mostly radeon, more fixes for dynamic power management which is is off by
default for this release anyways, but there are a large number of testers,
so I'd like to keep merging the fixes,
otherwise, radeon UVD fixes affecting suspend/resume regressions, i915
regression fixes, one for
Quoting James Hogan (2013-07-29 04:24:57)
> This patchset adds support for automatic selection of the best parent
> for a clock mux, i.e. the one which can provide the closest clock rate
> to that requested. It can be disabled by a new CLK_SET_RATE_NO_REPARENT
> flag (which is set for all uses of c
On 08/09/2013 01:38 AM, Paolo Bonzini wrote:
> Il 06/08/2013 15:16, Xiao Guangrong ha scritto:
>> Hi Gleb, Paolo, Marcelo, Takuya,
>>
>> Any comments or further comments? :)
>
> It's not the easiest patch to review. I've looked at it (beyond the
> small comments I have already posted), but it wil
On Fri, Aug 09, 2013 at 06:29:17AM +0200, Stefan Lippers-Hollmann wrote:
> On Friday 09 August 2013, Greg Kroah-Hartman wrote:
> > 3.10-stable review patch. If anyone has any objections, please let me know.
> >
> > --
> >
> > From: Russell King
> >
> > commit a5463cd3435475386c
On 08/08/2013 06:41 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.4.57 release.
There are 25 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be ma
On Friday 09 August 2013, Greg Kroah-Hartman wrote:
> 3.10-stable review patch. If anyone has any objections, please let me know.
>
> --
>
> From: Russell King
>
> commit a5463cd3435475386cbbe7b06e01292ac169d36f upstream.
>
> If kuser helpers are not provided by the kernel, di
On Fri, Aug 09, 2013 at 06:13:02AM +0200, Stefan Lippers-Hollmann wrote:
> Hi
>
> On Friday 09 August 2013, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 3.10.6 release.
> […]
> > The whole patch series can be found in one patch at:
> > kernel.org/pub/linux
On 08/09/2013 06:34 AM, H. Peter Anvin wrote:
The kbuild test bot is reporting some pretty serious errors for this
patchset. I think these are serious enough that the patchset will need
to be respun.
I am working on that.
--
To unsubscribe from this list: send the line "unsubscribe linux-
On Thu, 08 Aug 2013 15:54:50 +0200, Tomasz Figa wrote:
> On Thursday 08 of August 2013 18:37:43 Cho KyongHo wrote:
> > This prevents allocating lv2 page table for the lv1 page table entry
> ^ What this is this this about? :)
>
As you might indicate, 'this' means this patch :)
> > that already h
Hi
On Friday 09 August 2013, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 3.10.6 release.
[…]
> The whole patch series can be found in one patch at:
> kernel.org/pub/linux/kernel/v3.0/stable-review/patch-3.10.6-rc1.gz
[…]
There appears to be a problem wit
'rd_size' is used only in this file.
Fix the following sparse warning:
drivers/block/brd.c:432:5: warning: symbol 'rd_size' was not declared. Should
it be static?
Signed-off-by: Jingoo Han
---
drivers/block/brd.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/bl
On 8 August 2013 21:37, Viresh Kumar wrote:
> Its useless and the correct routine isn't called at all :) .. I will add that
> additional patch and send it to you and will get this change out of this
> commit.
The two commits look like this now attached too in case you want
to test:
commit 9abdc9
mg_times_out() is used only in this file.
Fix the following sparse warning:
drivers/block/mg_disk.c:639:6: warning: symbol 'mg_times_out' was not declared.
Should it be static?
Signed-off-by: Jingoo Han
---
drivers/block/mg_disk.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
The local variables such as 'bio_list', and 'pages' are pointers;
thus, use NULL instead of 0 to fix the following sparse warnings.
drivers/block/rbd.c:2166:32: warning: Using plain integer as NULL pointer
drivers/block/rbd.c:2168:31: warning: Using plain integer as NULL pointer
Signed-off-by: Ji
On Thu, 08 Aug 2013 15:42:24 +0200, Tomasz Figa wrote:
> Hi KyongHo,
>
> On Thursday 08 of August 2013 18:37:25 Cho KyongHo wrote:
> > This commit remove which is removed.
>
> I would prefer a more meaningful commit message, something among following
> lines:
>
> 8<---
> Commit 25e9d28d92 (ARM
On Thu, 08 Aug 2013 15:44:09 +0200, Tomasz Figa wrote:
> On Thursday 08 of August 2013 18:37:34 Cho KyongHo wrote:
> > This commit adds cache flush for removed small and large page entries
> > in exynos_iommu_unmap(). Missing cache flush of removed page table
> > entries can cause missing page faul
On Thu, Aug 08, 2013 at 08:42:12PM -0700, Guenter Roeck wrote:
> On 08/08/2013 06:41 PM, Greg Kroah-Hartman wrote:
> >This is the start of the stable review cycle for the 3.0.90 release.
> >There are 22 patches in this series, all will be posted as a response
> >to this one. If anyone has any issu
On Thu, 2013-08-08 at 16:06 -0700, Brian Norris wrote:
> On Thu, Aug 08, 2013 at 04:33:35PM +0800, Huang Shijie wrote:
> > Hi Artem & Brian:
> > >Hi Huang and others,
> > >
> > >On Thu, May 16, 2013 at 8:17 PM, Huang Shijie wrote:
> > >>1.) Why add the ECC information to the nand_chip{} ?
> ...
>
On 08/08/2013 06:41 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.0.90 release.
There are 22 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be ma
On Fri, 2013-08-09 at 08:49 +0530, Kumar Gaurav wrote:
> Please ignore the below patch. I'll be resending this with 0 instead of
> IRQF_TRIGGER_NONE
Hey again Kumar.
This is one of those patches that should just have
IRQF_DISABLED completely elided.
> On Friday 09 August 2013 08:47 AM, Kumar Ga
On 9 August 2013 00:20, Stephen Warren wrote:
> I don't think so. I think it's reasonable to have a per-SoC cpufreq
> driver whose primary content is the parameterization data and/or custom
> hooks for a unified core cpufreq driver. The duplicate parts of each
> cpufreq driver can be moved into th
Please ignore the below patch. I'll be resending this with 0 instead of
IRQF_TRIGGER_NONE
On Friday 09 August 2013 08:47 AM, Kumar Gaurav wrote:
Removed IRQF_DISABLED as it's no-op and should be removed
Signed-off-by: Kumar Gaurav
---
arch/avr32/kernel/time.c |2 +-
1 file changed, 1 in
Removed IRQF_DISABLED as it's no-op and should be removed
Signed-off-by: Kumar Gaurav
---
arch/avr32/kernel/time.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/avr32/kernel/time.c b/arch/avr32/kernel/time.c
index 869a1c6..0566c81 100644
--- a/arch/avr32/kernel/time
On Fri, August 09, 2013, Chris Ball wrote:
> On Fri, Aug 09 2013, Olof Johansson wrote:
> > On Thu, Aug 8, 2013 at 5:16 PM, Doug Anderson wrote:
> >
> >> I guess my overall question is: if there are no actual implementations
> >> of multislot, shouldn't we kill it and simplify the code a whole lot
On 8/8/13 1:58 AM, Adrian Hunter wrote:
On 08/08/13 00:59, David Ahern wrote:
Commit b55ae0a9 added code-reading.c which fails to compile on Fedora 16
with compiler version:
$ gcc --version
gcc (GCC) 4.6.3 20120306 (Red Hat 4.6.3-2)
Failure message is:
tests/code-reading.c: In function ‘do_sor
On Fri, Aug 02, 2013 at 02:03:47PM +0200, Piotr Sarna wrote:
> Commit 5688978 ("ext4: improve handling of conflicting mount options")
> introduced incorrect messages shown while choosing wrong mount options.
>
> Firstly, both cases of incorrect mount options, "data=journal,delalloc"
> and "data=jo
> Sorry, I don't understand what is not implemented. Without your patch, the
> PHY driver handles both PMU registers of Exynos4.
I don't have an Exynos4 to actually test this, so please let me know
if I'm missing something here... but in order to hit the right HOST
PHY register in the current upst
On 8/8/13 11:08 AM, Arnaldo Carvalho de Melo wrote:
Em Wed, Aug 07, 2013 at 10:50:50PM -0400, David Ahern escreveu:
Save vmlinux or kallsyms path loaded using embedded default lookup (ie.,
not a user specified path). Upcoming perf sched timehist command requires
kernel symbols for properly compu
On 8/8/13 11:06 AM, Arnaldo Carvalho de Melo wrote:
Em Wed, Aug 07, 2013 at 10:50:49PM -0400, David Ahern escreveu:
Avoids strcmp processing each sample.
How so? This is done just when loading a DSO, when then each symbol is
checked against this list.
hmmm see that now, yes. The timehist
Hi Ishimatsu-san,
On 08/06/2013 06:11 PM, Yasuaki Ishimatsu wrote:
> try_offline_node() checks that all cpus related with removed node have been
> removed by using cpu_present_bits. If all cpus related with removed node have
> been removed, try_offline_node() clears the node information.
>
> But
> -Original Message-
> From: Jon Mason [mailto:jdma...@kudzu.us]
> Sent: Friday, August 09, 2013 8:04 AM
> To: Wang, Rui Y
> Cc: liu...@gmail.com; Sosnowski, Maciej; Koul, Vinod;
> chenkep...@huawei.com; linux-kernel@vger.kernel.org;
> linux-...@vger.kernel.org; Luck, Tony; Guo, Chaohong; D
On Thu, 08 Aug 2013 22:43:43 +0100, Will Deacon wrote:
> On Thu, Aug 08, 2013 at 10:38:10PM +0100, Tomasz Figa wrote:
> > On Thursday 08 of August 2013 08:09:49 Rob Herring wrote:
> > > On Thu, Aug 1, 2013 at 8:05 AM, Cho KyongHo
> > wrote:
> > > > Should this align with ARM System MMU bindings?
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Russell King
commit 19accfd373847ac3d10623c5d20f948846299741 upstream.
Move the machine vector stubs into the page above the vector page,
which we can prevent from being visible to userspace.
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Russell King
commit 5b43e7a383d69381ffe53423e46dd0fafae07da3 upstream.
Poison the memory between each kuser helper. This ensures that any
branch between the kuser helpers will be appropriatel
This is the start of the stable review cycle for the 3.10.6 release.
There are 102 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made by Sun Aug 11 01:46:31 UTC 2013.
Anything receiv
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Aaro Koskinen
commit fe956a1d4081ce1a959f87df397a15e252201f10 upstream.
slots-fan on G5 Xserve is always running at full speed with windfarm_rm31
driver, resulting in a very high acoustic nois
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Russell King
commit 48be69a026b2c17350a5ef18a1959a919f60be7d upstream.
Move the signal handlers into a VDSO page rather than keeping them in
the vectors page. This allows us to place them ran
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Russell King
commit b9b32bf70f2fb710b07c94e13afbc729afe221da upstream.
Use linker magic to create the vectors and vector stubs: we can tell the
linker to place them at an appropriate VMA, but
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Russell King
commit f6f91b0d9fd971c630cef908dde8fe8795aefbf8 upstream.
Provide a kernel configuration option to allow the kernel user helpers
to be removed from the vector page, thereby preven
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Catalin Marinas
commit bdae73cd374e28db544fdd9b77de689a36e3c129 upstream.
As of commit b9d4d42ad9 (ARM: Remove __ARCH_WANT_INTERRUPTS_ON_CTXSW on
pre-ARMv6 CPUs), the mm switching on VIVT proc
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Will Deacon
commit acfdd4b1f7590d02e9bae3b73bdbbc4a31b05d38 upstream.
a.out support on ARM requires that argc, argv and envp are passed in
r0-r2 respectively, which requires hacking load_aout_
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Robert Jennings
commit 3be7db6ab45b21345386d1a466da133b19cde5e4 upstream.
When an associativity level change is found for one thread, the
siblings threads need to be updated as well. This is
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Alex Ivanov
commit 06f0cce43a32bd2357cea1d8733bba48693d556b upstream.
Allow binding of user memory to the AGP GART on systems with HP
Quicksilver AGP bus. This resolves 'bind memory failed' er
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Russell King
commit 8c0cc8a5d90bc7373a7a9e7f7a40eb41f51e03fc upstream.
Olof reports that noMMU builds error out with:
arch/arm/kernel/signal.c: In function 'setup_return':
arch/arm/kernel/sig
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Thomas Bogendoerfer
commit dd5e6d6a3db09b16b7c222943977865eead88cc3 upstream.
We can't use dev->mod_index for selecting the interrupt routing entry,
because it's not an index into interrupt ro
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Vivien Didelot
commit 5c52add19733eb36d8619713312f5604efef3502 upstream.
Without this patch, the values for ideality (register 0x4b) and ideality
selection mask (register 0x4c) are inverted.
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Russell King
commit e0d407564b532d978b03ceccebd224a05d02f111 upstream.
Unfortunately, I never committed the fix to a nasty oops which can
occur as a result of that commit:
[ cut h
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Axel Lin
commit d5a12ea7a9e58d9e5c19d25cb668aadb396423ec upstream.
Platform drivers use "platform:" prefix in module alias.
Also use DRIVER_NAME in MODULE_ALIAS to make module autoloading work
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Will Deacon
commit bf3f0f332f76a85ff3a0b393aaded5a8533769c0 upstream.
Commit ae8a8b9553bd ("ARM: 7691/1: mm: kill unused TLB_CAN_READ_FROM_L1_CACHE
and use ALT_SMP instead") added early functi
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Vinod Koul
commit a8d30608eaed6cc759b8e2e8a842591f797f upstream.
the return value of SNDRV_COMPRESS_VERSION always return default -ENOTTY as the
return value was never updated for this cal
1 - 100 of 820 matches
Mail list logo
