From: Namhyung Kim
The trace_run() function calls several evlist functions but misses
some pair-wise cleanup routines on return path. Fix it.
Signed-off-by: Namhyung Kim
---
tools/perf/builtin-trace.c | 16 +++-
1 file changed, 11 insertions(+), 5 deletions(-)
diff --git
From: Namhyung Kim
It's a pair of perf_evlist__open().
Signed-off-by: Namhyung Kim
---
tools/perf/util/evlist.c | 19 ---
tools/perf/util/evlist.h | 1 +
2 files changed, 13 insertions(+), 7 deletions(-)
diff --git a/tools/perf/util/evlist.c b/tools/perf/util/evlist.c
index
From: Namhyung Kim
The error path of calling perf_target__parse_uid wrongly went to
out_free_fd. Also add missing evlist cleanup routines.
Signed-off-by: Namhyung Kim
---
tools/perf/builtin-record.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git
From: Namhyung Kim
Add missing perf_evlist__close() function.
Cc: Jiri Olsa
Signed-off-by: Namhyung Kim
---
tools/perf/tests/perf-record.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/tools/perf/tests/perf-record.c b/tools/perf/tests/perf-record.c
index
From: Namhyung Kim
Use perf_evsel__free_* because they do the same thing and ensures the
pointer has NULL value at the end.
Signed-off-by: Namhyung Kim
---
tools/perf/util/evsel.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/tools/perf/util/evsel.c
From: Namhyung Kim
Add missing evlist cleanup functions.
Cc: Jiri Olsa
Signed-off-by: Namhyung Kim
---
tools/perf/tests/open-syscall-tp-fields.c | 8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/tools/perf/tests/open-syscall-tp-fields.c
On Fri, 2013-03-15 at 13:19 +0800, Stephen Warren wrote:
> On 03/14/2013 04:58 AM, Bill Huang wrote:
> > Hook up "pm_power_off" to palmas power off routine if there is DT
> > property "ti,system-power-controller" defined, so platform which is
> > powered by this regulator can be powered off
On 3/15/2013 10:51 AM, Philip, Avinash wrote:
> On Fri, Mar 15, 2013 at 10:38:58, Nori, Sekhar wrote:
>> On 3/15/2013 10:27 AM, Philip, Avinash wrote:
>>> On Thu, Mar 14, 2013 at 18:31:52, Nori, Sekhar wrote:
On 3/14/2013 4:07 PM, Philip Avinash wrote:
> da850 platforms require TBCLK
On Fri, 2013-03-15 at 13:22 +0800, Stephen Warren wrote:
> On 03/14/2013 07:20 PM, Bill Huang wrote:
> > On Fri, 2013-03-15 at 01:54 +0800, Stephen Warren wrote:
> >> On 03/14/2013 03:28 AM, Bill Huang wrote:
> >>> On Thu, 2013-03-14 at 17:21 +0800, Peter De Schrijver wrote:
> On Thu, Mar 14,
Hi Linus,
Please pull hwmon patches for Linux 3.9-rc3 from signed tag:
git://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging.git
hwmon-for-linus
Thanks,
Guenter
--
The following changes since commit f6161aa153581da4a3867a2d1a7caf4be19b6ec9:
Linux 3.9-rc2 (2013-03-10
Hi all,
Changes since 20130314:
The l2-mtd tree gained conflicts against the mtd tree.
The staging tree gained a conflict against Linus' tree.
The gpio tree still had its build failure for which I reverted a commit
On 03/14/2013 03:08 AM, Hiroshi Doyu wrote:
> Make this depend on CONFIG_PM. This protection is necessary to not
> cause any build errors with any combination of PM features especially
> when supporting a new SoC where each PM features are being enabled
> one-by-one during its depelopment.
Looks
On 03/14/2013 07:20 PM, Bill Huang wrote:
> On Fri, 2013-03-15 at 01:54 +0800, Stephen Warren wrote:
>> On 03/14/2013 03:28 AM, Bill Huang wrote:
>>> On Thu, 2013-03-14 at 17:21 +0800, Peter De Schrijver wrote:
On Thu, Mar 14, 2013 at 03:15:11AM +0100, Bill Huang wrote:
> I don't
On Fri, Mar 15, 2013 at 10:38:58, Nori, Sekhar wrote:
> On 3/15/2013 10:27 AM, Philip, Avinash wrote:
> > On Thu, Mar 14, 2013 at 18:31:52, Nori, Sekhar wrote:
> >> On 3/14/2013 4:07 PM, Philip Avinash wrote:
> >>> da850 platforms require TBCLK synchronization in CFG_CHIP1 register for
> >>> TBCLK
From: "Steven Rostedt (Red Hat)"
The latency tracers require the buffers to be in overwrite mode,
otherwise they get screwed up. Force the buffers to stay in overwrite
mode when latency tracers are enabled.
Added a flag_changed() method to the tracer structure to allow
the tracers to see what
Ingo,
Here's take two of the last patch series I sent. The only difference
with this series is that I encapsulate the max_tr reference with
the #ifdef CONFIG_TRACER_MAX_TRACE. Other than that, it's the same.
Here's the recap:
The first patch fixes a long standing bug where the changing of
the
From: "Steven Rostedt (Red Hat)"
Seems that the tracer flags have never been protected from
synchronous writes. Luckily, admins don't usually modify the
tracing flags via two different tasks. But if scripts were to
be used to modify them, then they could get corrupted.
Move the trace_types_lock
Fixes the following checkpatch error:
ERROR: space required before the open parenthesis '('
Signed-off-by: Sachin Kamat
---
drivers/pinctrl/pinctrl-coh901.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/pinctrl/pinctrl-coh901.c
From: "Steven Rostedt (Red Hat)"
Changing the overwrite mode for the ring buffer via the trace
option only sets the normal buffer. But the snapshot buffer could
swap with it, and then the snapshot would be in non overwrite mode
and the normal buffer would be in overwrite mode, even though the
On 03/14/2013 04:58 AM, Bill Huang wrote:
> Hook up "pm_power_off" to palmas power off routine if there is DT
> property "ti,system-power-controller" defined, so platform which is
> powered by this regulator can be powered off properly.
> diff --git a/drivers/mfd/palmas.c b/drivers/mfd/palmas.c
于 2013年03月15日 12:52, Michael Neuling 写道:
> Yep it's a known problem but no one has bothered to fix it since it
> doesn't happen in a config that anyone cares about like
> pseries_defconfig and ppc64_defconfig. We've been moving code around in
> this area a lot recently hence the breakage.
>
> It
On Fri, Mar 15, 2013 at 02:09:14PM +0900, J. R. Okajima wrote:
> If so, it has a big disadvantage for the layer-fs (or branch-fs) to have
> to implement a new method for whiteout.
>
> Overlayfs implements whiteout as symlink+xattr which consumes an
> inode. And you don't like it, right?
> What I
Fixes the following type of checkpatch errors:
ERROR: space required before the open parenthesis '('
Signed-off-by: Sachin Kamat
---
drivers/pinctrl/pinconf-generic.c |6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/pinctrl/pinconf-generic.c
Al Viro:
> > +- whiteout is hardlinked in order to reduce the consumption of inodes
> > + on branch
>
> *blink* Whiteouts have no inodes at all. Filesystem has an additional
> kind of directory entries, recognizable as whiteouts. How they are
> done is up to filesystem in question.
"no inodes
On 3/15/2013 10:27 AM, Philip, Avinash wrote:
> On Thu, Mar 14, 2013 at 18:31:52, Nori, Sekhar wrote:
>> On 3/14/2013 4:07 PM, Philip Avinash wrote:
>>> da850 platforms require TBCLK synchronization in CFG_CHIP1 register for
>>> TBCLK enable in EHRPWM modules. Enabling of TBCLK is done only if
Satoru Takeuchi writes:
> At Thu, 14 Mar 2013 17:11:21 +1030,
> Rusty Russell wrote:
>>
>> Satoru Takeuchi writes:
>> > Hi Rusty,
>> >
>> > At Tue, 12 Mar 2013 15:43:33 -0700,
>> > Greg Kroah-Hartman wrote:
>> >> @@ -307,6 +312,14 @@ int hwrng_register(struct hwrng *rng)
>> >>
>> >>
'conf_items' is used only in this file. Silences the below
sparse warning:
drivers/pinctrl/pinconf-generic.c:37:24: warning:
symbol 'conf_items' was not declared. Should it be static?
Signed-off-by: Sachin Kamat
---
drivers/pinctrl/pinconf-generic.c |2 +-
1 files changed, 1 insertions(+),
James Hogan writes:
> On 14/03/13 04:00, Rusty Russell wrote:
>> From: Rusty Russell
>> Subject: CONFIG_SYMBOL_PREFIX: cleanup.
...
> Reviewed-by: James Hogan
> Tested-by: James Hogan (metag)
Thanks.
> The only other special case of symbol prefixing I'm aware of is in
>
Andy Lutomirski writes:
> Current parameter behavior is odd. Boot parameters that have values
> and don't match anything become environment variables, with no
> warning. Boot parameters without values that don't match anything
> go into argv_init. Everything goes into /proc/cmdline.
>
> The
Stephen Rothwell writes:
> Hi Al,
>
> Today's linux-next merge of the signal tree got a conflict in
> include/asm-generic/unistd.h between commit 837718bfd28b
> ("CONFIG_SYMBOL_PREFIX: cleanup") from the modules tree and commit
> e1b5bb6d1236 ("consolidate cond_syscall and SYSCALL_ALIAS
trace,
>> suggesting a use-after-free bugs. They may all be different manifestations
>> of the same underlying bug if there's some kind of refcounting bug perhaps.
>> (This may also be why telling it to do just mkdirat isn't triggering it,
>> if it's racing with some
Paul Gortmaker writes:
> The existing comment indicated what was desired, but it didn't
> necessarily convey the reasoning behind it in an effective way.
>
> Cc: Rusty Russell
> Signed-off-by: Paul Gortmaker
> ---
> include/linux/export.h | 5 +++--
> 1 file changed, 3 insertions(+), 2
On Thu, Mar 14, 2013 at 01:08:00PM +0530, Santosh Shilimkar wrote:
> Will,
Hi guys,
I'm out of the office at the moment and have really terrible connectivity,
so I can't do too much until next week. However, I don't think adding the
has_ossr check is the right fix for this problem.
> On
On Thu, Mar 14, 2013 at 18:31:52, Nori, Sekhar wrote:
> On 3/14/2013 4:07 PM, Philip Avinash wrote:
> > da850 platforms require TBCLK synchronization in CFG_CHIP1 register for
> > TBCLK enable in EHRPWM modules. Enabling of TBCLK is done only if EHRPWM
> > DT node status is set to "okay" DT blob.
> do next-* tree support powerpc POWER7 with allmodconfig ?
>
> I met an issue, can we bear it (or I need additional trying) ?
>
>
> Compiling:
> make V=1 EXTRA_CFLAGS=-W ARCH=powerpc allmodconfig
> set cpu type POWER7 in menuconfig.
> set cross-compiler in menuconfig.
>
On Thu, Mar 14, 2013 at 12:59:57PM +, Chris Wilson wrote:
> In order to prevent a potential NULL deference with hostile userspace,
> we need to check whether the ioctl was passed an invalid args pointer.
>
> Reported-by: Tommi Rantala
> Link:
>
Fixes the following types of checkpatch errors:
ERROR: "foo * bar" should be "foo *bar"
ERROR: "foo* bar" should be "foo *bar"
ERROR: space required before the open parenthesis '('
ERROR: "(foo*)" should be "(foo *)"
ERROR: space required after that ',' (ctx:WxV)
ERROR: "(foo*const*)" should be
const declared twice. Fixes the following sparse warning:
drivers/pinctrl/pinctrl-at91.c:815:21: warning: duplicate const
drivers/pinctrl/pinctrl-at91.c:849:21: warning: duplicate const
Signed-off-by: Sachin Kamat
---
drivers/pinctrl/pinctrl-at91.c |4 ++--
1 files changed, 2 insertions(+),
On Thu, Mar 14, 2013 at 12:59:57PM +, Chris Wilson wrote:
> In order to prevent a potential NULL deference with hostile userspace,
> we need to check whether the ioctl was passed an invalid args pointer.
>
> Reported-by: Tommi Rantala
> Link:
>
On Fri, Mar 15, 2013 at 01:15:36PM +0900, J. R. Okajima wrote:
> +- whiteout is hardlinked in order to reduce the consumption of inodes
> + on branch
*blink* Whiteouts have no inodes at all. Filesystem has an additional
kind of directory entries, recognizable as whiteouts. How they are
done
On Thu, Mar 14, 2013 at 08:52:43PM +0900, Masami Hiramatsu wrote:
> Currently kprobes check whether the copied instruction modifies
> IF (interrupt flag) on each probe hit. This means not only
> introducing overhead but also involving inat_get_opcode_attribute
> into kprobes hot path, and it can
On Thu, Mar 14, 2013 at 08:52:30PM +0900, Masami Hiramatsu wrote:
> Because hash_64() is called from the get_kprobe() inside
> int3 handler, kernel causes int3 recursion and crashes if
> kprobes user puts a probe on it.
>
> Usually hash_64() is inlined into caller function, but in
> some cases,
> On 14 March 2013 01:34, Alexander Shiyan wrote:
> > This patch allow using syscon driver from the platform data, i.e.
> > possibility using driver on systems without oftree support.
> > For search syscon device from the client drivers,
> > "syscon_regmap_lookup_by_pdevname" function was added.
On Fri, Mar 15, 2013 at 12:07:14AM -0400, Sasha Levin wrote:
> Hi all,
>
> While fuzzing with trinity inside a KVM tools guest running latest -next
> kernel
> I've stumbled on the following.
>
> Dave Jones reported something similar, but that seemed to involve cgroup's
> mutex
> and didn't
On 3/14/2013 9:14 PM, Peter Korsgaard wrote:
>> "Sekhar" == Sekhar Nori writes:
>
> >> Required properties:
> >> -- compatible: Must be "ti,am33xx-ecap"
> >> +- compatible: Must be "ti,am33xx-ecap" or "ti,da850-ecap"
> >> - #pwm-cells: Should be 3. Number of cells being used to specify
Al Viro:
> Umm... I would prefer it to go through vfs.git, with serious modifications.
> I really don't like the idea of xattr-based whiteouts, for example.
I'd ask you how do you think another whiteout approach?
Here is a part of a posts which describes about aufs2 in 2009
Hi Greg,
Today's linux-next merge of the staging tree got a conflict in
drivers/staging/ccg/f_fs.c between commit 7f78e0351394 ("fs: Limit
sys_mount to only request filesystem modules") from Linus' tree and
commit 515e6dd20b3f ("Staging: ccg: delete it from the tree") from the
staging tree.
The
] ==
[ 549.400084] [ INFO: possible circular locking dependency detected ]
[ 549.400084] 3.9.0-rc2-next-20130314-sasha-00046-g3897511 #295 Tainted: G
W
[ 549.400084] ---
[ 549.420729] can: request_module (can
Hi,
I am a newbie on Linux.
I am trying to read the CPU information through "acpitool -c". And
I get a message as: " Function Show_CPU_Info : could not read directory
/proc/acpi/processor/ Make sure your kernel has ACPI processor support
enabled.
"
I went to the kernel configuration,
. The best I can offer
> right now is that it seems to trigger *something* bad quickly, even if it's
> not necessarily the exact same trace.
I've hit something similar, but I suspect it's the same issue:
[ 350.140100] general protection fault: [#1] PREEMPT SMP DEBUG_PAGEALLOC
[ 35
On Fri, Mar 15, 2013 at 12:24 AM, Oleg Nesterov wrote:
>> From: Ming Lei
>> Subject: atomic: improve
>> atomic_inc_unless_negative/atomic_dec_unless_positive
>>
>> Generally, both atomic_inc_unless_negative() and
>> atomic_dec_unless_positive() need at least two atomic_cmpxchg() to
>> complete
On Thu, 2013-03-14 at 17:33 -0400, Steven Rostedt wrote:
> Anyway, here's hopefully my final series of changes for 3.9.
> (Famous last words)
And there's a bug in this patch set. Thanks to Fangguang's auto tests,
it showed a bug in my new work, which points out a bug in this patch
set. The
The msm timer binding I wrote is bad. First off, the clock
frequency in the binding for the dgt is wrong. Software divides
down the input rate by 4 to achieve the rate listed in the
binding. We also treat each individual timer as a separate
hardware component, when in reality there is one timer
This patchset cleans up some bugs in the msm timer code and overhauls
the DT binding. I don't think we'll need to radically change it again,
and we haven't shipped any devices with these bindings so we should
be ok. The important thing is that the binding is consolidated and
more clearly describes
If the clockevent is forcibly reprogrammed to have a different
match value we mistakenly assume the timer is not ticking and
program a new match value while the timer is running. Although we
clear the timer before programming a new match, it's better to
stop the timer before clearing it so that
Without looping on the status bit, there is no way to guarantee
that a clear of the timer has actually completed. This can cause
us to enable the timer before the count has cleared and miss a
timer interrupt. To simplify this patch, remove the timer
register setup done during timer init, since
On Friday, March 15, 2013 12:16 PM, Doug Anderson wrote:
>
> The ehci_vbus_gpio is requested but never freed. This can cause
> problems with deferred probes and would cause problems if
> s5p_ehci_remove was ever called. Use devm to fix this.
>
> Signed-off-by: Doug Anderson
Acked-by: Jingoo
Add support for
devm_sysfs_create_file
devm_sysfs_remove_file
devm_sysfs_create_group
devm_sysfs_remove_group
Signed-off-by: Guenter Roeck
---
fs/sysfs/file.c | 51 +++
fs/sysfs/group.c | 53
Add support for devm_device_create_file and devm_device_remove_file.
Signed-off-by: Guenter Roeck
---
drivers/base/core.c| 18 ++
include/linux/device.h |4
2 files changed, 22 insertions(+)
diff --git a/drivers/base/core.c b/drivers/base/core.c
index
Provide devres functions for device_create_file, sysfs_create_file,
and sysfs_create_group plus the respective remove functions.
Idea is to be able to drop calls to the remove functions from the various
drivers using those calls.
Potential savings are substantial. There are more than 700 calls
I have 4 Toshiba nand chips which can not be parsed out by the
id data. We can not get the oob size from the id data. So add them
as the full-id nand chips in the first of nand_flash_ids.
The comment for the full-id items is from Brian.
Signed-off-by: Huang Shijie
---
As time goes on, we begin to meet the situation that we can not get enough
information from some nand chips's id data. Take some Toshiba's nand chips
for example. I have 4 Toshiba's nand chips in my hand:
TC58NVG2S0F, TC58NVG3S0F, TC58NVG5D2, TC58NVG6D2
When we read these chips'
When we meet a full-id nand type whose @id_len is not zero, we can use
the find_full_id_nand() to parse out the necessary information for a
nand chip.
If we meet a non full-id nand type, we can handle it in the legacy way.
Signed-off-by: Huang Shijie
---
drivers/mtd/nand/nand_base.c | 35
The ehci_vbus_gpio is requested but never freed. This can cause
problems with deferred probes and would cause problems if
s5p_ehci_remove was ever called. Use devm to fix this.
Signed-off-by: Doug Anderson
---
Changes in v2:
- >dev => dev elsewhere in s5p_setup_vbus_gpio()
Jingoo,
On Thu, Mar 14, 2013 at 5:30 PM, Jingoo Han wrote:
> Would you replace other '>dev' with 'dev' in s5p_setup_vbus_gpio()
> as below? It seems to be better for readability.
Yes, of course. That was silly of me not to add the "dev" local and
not update the other places... Thanks for your
On Fri, Mar 15, 2013 at 1:50 AM, Kirill A. Shutemov
wrote:
> + if (PageTransTail(page)) {
> + page_cache_release(page);
> + page = find_get_page(mapping,
> + index & ~HPAGE_CACHE_INDEX_MASK);
check
On Friday, March 15, 2013 8:01 AM, Doug Anderson wrote:
>
> The exynox4210-ehci and exynos4210-ohci nodes need a clock specified
> using the common clock framework. Document it.
>
> Signed-off-by: Doug Anderson
It looks good.
Acked-by: Jingoo Han
Best regards,
Jingoo Han
> ---
> Changes
As time goes on, we begin to meet the situation that we can not
get enough information from some nand chips's id data.
Take some Toshiba's nand chips for example.
I have 4 Toshiba's nand chips in my hand:
TC58NVG2S0F, TC58NVG3S0F, TC58NVG5D2, TC58NVG6D2
When we read these chips'
On Thu, Mar 14, 2013 at 6:06 PM, Wei Yongjun wrote:
> From: Wei Yongjun
>
> sizeof() when applied to a pointer typed expression gives the
> size of the pointer, not that of the pointed data.
>
> Signed-off-by: Wei Yongjun
> ---
> arch/xtensa/platforms/iss/network.c | 2 +-
> 1 file changed, 1
The exynox4210-ehci and exynos4210-ohci nodes need a clock specified
using the common clock framework. Document it.
Signed-off-by: Doug Anderson
---
Changes in v2:
- Fixed embarrassing typo adc=>usb. Thanks Jingoo!
Documentation/devicetree/bindings/usb/exynos-usb.txt | 10 ++
1 file
On 03/14/2013 01:08 PM, Namjae Jeon wrote:
> 2013/3/14, Sergey Yanovich :
>> MMC hosts are added asynchronously. We need to wait until detect returns to
>> avoid failed root filesystem mounts.
>> ---8<---
>> VFS: Cannot open root device "mmcblk0p1" or unknown-block(0,0): error -6
>> Please append
Hello Maintainers:
do next-* tree support powerpc POWER7 with allmodconfig ?
I met an issue, can we bear it (or I need additional trying) ?
Compiling:
make V=1 EXTRA_CFLAGS=-W ARCH=powerpc allmodconfig
set cpu type POWER7 in menuconfig.
set cross-compiler in menuconfig.
* Eric Wong (normalper...@yhbt.net) wrote:
> Mathieu Desnoyers wrote:
> > * Eric Wong (normalper...@yhbt.net) wrote:
> > > Mathieu Desnoyers wrote:
> > > > The advantage of using splice() over dequeue() is that you will reduce
> > > > the amount of interactions between concurrent enqueue and
Changelog:
v2 -> v3:
* increment/decrement zcache_[eph|pers]_zpages for zero-filled pages, spotted
by Dan
* replace "zero" or "zero page" by "zero_filled_page", spotted by Dan
v1 -> v2:
* avoid changing tmem.[ch] entirely, spotted by Dan.
* don't accumulate [eph|pers]pageframe and
Increment/decrement zcache_[eph|pers]_zpages for zero-filled pages,
the main point of the counters for zpages and pageframes is to be
able to calculate density == zpages/pageframes. A zero-filled page
becomes a zpage that "compresses" to zero bytes and, as a result,
requires zero pageframes for
Compression of zero-filled pages can unneccessarily cause internal
fragmentation, and thus waste memory. This special case can be
optimized.
This patch captures zero-filled pages, and marks their corresponding
zcache backing page entry as zero-filled. Whenever such zero-filled
page is retrieved,
Introduce zero-filled page statistics to monitor the number of
zero-filled pages.
Acked-by: Dan Magenheimer
Signed-off-by: Wanpeng Li
---
drivers/staging/zcache/zcache-main.c |7 +++
1 files changed, 7 insertions(+), 0 deletions(-)
diff --git a/drivers/staging/zcache/zcache-main.c
Cleanup TODO list since support zero-filled pages more efficiently has
already done by this patchset.
Acked-by: Dan Magenheimer
Signed-off-by: Wanpeng Li
---
drivers/staging/zcache/TODO |3 +--
1 files changed, 1 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/zcache/TODO
Introduce zero-filled pages handler to capture and handle zero pages.
Acked-by: Dan Magenheimer
Signed-off-by: Wanpeng Li
---
drivers/staging/zcache/zcache-main.c | 26 ++
1 files changed, 26 insertions(+), 0 deletions(-)
diff --git
On Fri, Mar 15, 2013 at 1:50 AM, Kirill A. Shutemov
wrote:
> +#ifdef CONFIG_TRANSPARENT_HUGEPAGE
> +struct page *grab_cache_huge_page_write_begin(struct address_space *mapping,
> + pgoff_t index, unsigned flags);
> +#else
> +static inline struct page
在 2013-03-15五的 09:43 +0800，Li Zefan写道：
> On 2013/3/15 9:26, li guang wrote:
> > 在 2013-03-15五的 09:01 +0800，Li Zefan写道：
> >> On 2013/3/15 8:20, li guang wrote:
> >>> 在 2013-03-14四的 15:43 +0100，Oleg Nesterov写道：
> On 03/14, liguang wrote:
> >
> > Signed-off-by: liguang
> > ---
>
On Fri, Mar 15, 2013 at 1:50 AM, Kirill A. Shutemov
wrote:
> + if (PageTransHuge(page)) {
> + int i;
> +
> + for (i = 0; i < HPAGE_CACHE_NR; i++)
> + radix_tree_delete(>page_tree, page->index +
> i);
Move the below page_cache_release for
On Thu, Sep 13, 2012 at 7:18 AM, Daniel Vetter wrote:
> Hi Dave,
>
> The big ticket item here is the new i915 modeset infrastructure.
> Shockingly it didn't not blow up all over the place (i.e. I've managed to
> fix the ugly issues before merging). 1-2 smaller corner cases broke, but
> we have
* Peter Hurley (pe...@hurleysoftware.com) wrote:
> On Mon, 2013-03-11 at 17:36 -0400, Mathieu Desnoyers wrote:
> > +/*
> > + * Do not put head and tail on the same cache-line if concurrent
> > + * enqueue/dequeue are expected from many CPUs. This eliminates
> > + * false-sharing between enqueue
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/14/2013 06:07 PM, Andrew Morton wrote:
> huh. What is the user-visible effect of this bug? Just a memory
> leak or something more serious?
Not serious, but user-visible in that the partition devnodes still
show up after detaching the backing
On 03/05/13 00:31, Arnd Bergmann wrote:
> On Monday 04 March 2013, Stephen Boyd wrote:
>> Scorpion processors have always been v7 CPUs. Fix the Kconfig
>> text to reflect this.
>>
>> Reported-by: Stepan Moskovchenko
>> Signed-off-by: Stephen Boyd
>> ---
>> arch/arm/Kconfig |4 ++--
>> 1
On 2013/3/15 9:26, li guang wrote:
> 在 2013-03-15五的 09:01 +0800，Li Zefan写道：
>> On 2013/3/15 8:20, li guang wrote:
>>> 在 2013-03-14四的 15:43 +0100，Oleg Nesterov写道：
On 03/14, liguang wrote:
>
> Signed-off-by: liguang
> ---
> kernel/task_work.c |3 ++-
> 1 files changed,
On Thursday, March 14, 2013 2:18 AM, Doug Anderson wrote:
>
> This is a fixup to two device tree nodes that have already landed but
> without clock nodes since the transition to common clock happened at
> the same time.
>
> Signed-off-by: Doug Anderson
The clock number and name are right.
On Thu, Mar 14, 2013 at 03:26:19PM +, Dimitris Papastamos wrote:
> There is no point having this. The space gains are trivial if there
> are any at all.
Applied, but numbers would have been nice and...
> Change-Id: Ib4b1320420f780dcf5b9a1e4b05f5805691c4d9f
...this shouldn't be in upstream
On Thu, Mar 14, 2013 at 02:52:35PM +, Dimitris Papastamos wrote:
> if (rbnode) {
> reg_tmp = (reg - rbnode->base_reg) / map->reg_stride;
> + /* Does this register exist? If not bail out. */
> + if (!(rbtree_ctx->reg_present[BIT_WORD(reg)] &
于 2013年03月14日 22:05, Greg KH 写道:
On Thu, Mar 14, 2013 at 09:51:34PM +0800, Shuge wrote:
Hi all,
When the kernel printk too many log, the cpu is failed to come online.
The problem is this:
For example, cpu0 bring up cpu1:
a. cpu0 call cpu_up:
cpu_up()
->_cpu_up()
On Fri, Mar 15, 2013 at 1:50 AM, Kirill A. Shutemov
wrote:
> + page_cache_get(page);
> + spin_lock_irq(>tree_lock);
> + page->mapping = mapping;
> + page->index = offset;
> + error = radix_tree_insert(>page_tree, offset, page);
> + if (unlikely(error))
> +
On Friday, March 15, 2013 8:01 AM, Doug Anderson wrote:
>
> The exynox4210-ehci and exynos4210-ohci nodes need a clock specified
> using the common clock framework. Document it.
>
> Signed-off-by: Doug Anderson
> ---
> Documentation/devicetree/bindings/usb/exynos-usb.txt | 10 ++
> 1
在 2013-03-15五的 09:01 +0800，Li Zefan写道：
> On 2013/3/15 8:20, li guang wrote:
> > 在 2013-03-14四的 15:43 +0100，Oleg Nesterov写道：
> >> On 03/14, liguang wrote:
> >>>
> >>> Signed-off-by: liguang
> >>> ---
> >>> kernel/task_work.c |3 ++-
> >>> 1 files changed, 2 insertions(+), 1 deletions(-)
> >>>
This driver supports host initiated backup of the guest. On Windows guests,
the host can generate application consistent backups using the Windows VSS
framework. On Linux, we ensure that the backup will be file system consistent.
This driver allows the host to initiate a "Freeze" operation on all
On Thu, Mar 14, 2013 at 02:43:32PM +0100, Miklos Szeredi wrote:
> > Either way, I suggest the next step is to ask Stephen to line this up
> > in linux-next.
>
> Al, are you okay with that? Or do you want it to go though -vfs?
Umm... I would prefer it to go through vfs.git, with serious
On Fri, 2013-03-15 at 01:54 +0800, Stephen Warren wrote:
> On 03/14/2013 03:28 AM, Bill Huang wrote:
> > On Thu, 2013-03-14 at 17:21 +0800, Peter De Schrijver wrote:
> >> On Thu, Mar 14, 2013 at 03:15:11AM +0100, Bill Huang wrote:
> >>
> >>> I don't think deferring will work either, considering
On Thu, Mar 14, 2013 at 5:24 PM, Stephane Eranian wrote:
>
> I bet if you force the affinity of your perf record to be on
> a CPU other than CPU0, you will not get the crash.
>
> This is what I am seeing now. I appears on resume,
> CPU0 hotplug callbacks for perf_events are not invoked
> leaving
On 2013/3/15 8:20, li guang wrote:
> 在 2013-03-14四的 15:43 +0100，Oleg Nesterov写道：
>> On 03/14, liguang wrote:
>>>
>>> Signed-off-by: liguang
>>> ---
>>> kernel/task_work.c |3 ++-
>>> 1 files changed, 2 insertions(+), 1 deletions(-)
>>>
>>> diff --git a/kernel/task_work.c b/kernel/task_work.c
Hi Artem,
Today's linux-next merge of the l2-mtd tree got a conflict in
include/linux/mtd/nand.h between commit 5bc7c33ca93a ("mtd: nand:
reintroduce NAND_NO_READRDY as NAND_NEED_READRDY") from the mtd tree and
commit edac3311879c ("mtd: nand: remove AG-AND support") from the l2-mtd
tree.
I
1 - 100 of 1528 matches
Mail list logo
