On 04/03/2013 02:22 PM, Michael Wang wrote:
>> >
>> > If many tasks sleep long time, their runnable load are zero. And if they
>> > are waked up bursty, too light runnable load causes big imbalance among
>> > CPU. So such benchmark, like aim9 drop 5~7%.
>> >
>> > With this patch the losing is cov
Hi Minchan,
On Wed, Apr 3, 2013 at 8:16 AM, Michael Kerrisk (man-pages)
wrote:
> Hello Minchan
>
> On Wed, Apr 3, 2013 at 2:23 AM, Minchan Kim wrote:
>> Hey Michael,
>>
>> On Tue, Apr 02, 2013 at 03:25:25PM +0200, Michael Kerrisk wrote:
>>> Minchan,
>>>
>>> On Mon, Mar 25, 2013 at 7:21 AM, Minch
Hi all,
Changes since 20130402:
The nfsd tree gained a conflict against Linus' tree and a build failure
for which I reverted 2 commits.
The vfs tree lost its build failure but gained another so I used the
version from next-20130328.
The v4l-dvb tree gained conflicts against the i2c tree.
David Howells writes:
> CAI Qian wrote:
>
>> Just booted the latest mainline,
>>
>> [ 35.217698] Request for unknown module key 'Magrathea: Glacier signing
>> key: 8b7774b08bc4ee9637073434c10f0823f6fbe523' err -11
>
> Can you check back earlier in the dmesg to see whether the kernel tried to
>
On 3 April 2013 12:01, stratosk wrote:
> I'm sorry, I don't understand.
> The goal of this patch is not energy saving.
He probably misunderstood it...
> The goal is to detect CPU load as soon as possible to increase frequency.
>
> Could you please clarify this?
But he is looking for some number
Hi all,
After merging the final tree, today's linux-next build (arm defconfig)
failed like this:
fs/built-in.o: In function `nfsd_reply_cache_stats_show':
super.c:(.text+0x87308): undefined reference to `__udivdi3'
Probably caused by commit 187da2f90879 ("nfsd: keep track of the max and
average
Hello Jaegeuk,
+-- On Wed, 3 Apr 2013, Jaegeuk Kim wrote --+
| Therefore, I think f2fs_write_data_pages() is better to handle this. Please
| review the modified patch. Thanks,
|
| diff --git a/fs/f2fs/data.c b/fs/f2fs/data.c
| index 47a2d7c..cf9ff5f 100644
| --- a/fs/f2fs/data.c
| +++ b/fs/f2fs
Hi,
On Wednesday 03 April 2013 12:01 PM, David Miller wrote:
From: Kishon Vijay Abraham I
Date: Wed, 3 Apr 2013 11:29:53 +0530
Hi,
On Friday 29 March 2013 12:01 AM, David Miller wrote:
You really need to CC: net...@vger.kernel.org rather than me
explicitly
on this patch set.
I was CC'ing
From: Kishon Vijay Abraham I
Date: Wed, 3 Apr 2013 11:29:53 +0530
> Hi,
>
> On Friday 29 March 2013 12:01 AM, David Miller wrote:
>>
>> You really need to CC: net...@vger.kernel.org rather than me
>> explicitly
>> on this patch set.
>
> I was CC'ing whatever get_maintainer shows. I'll make sure
I'm sorry, I don't understand.
The goal of this patch is not energy saving.
The goal is to detect CPU load as soon as possible to increase frequency.
Could you please clarify this?
Thanks,
Stratos
"Rafael J. Wysocki" wrote:
>On Tuesday, April 02, 2013 06:49:14 PM Stratos Karafotis wrote:
>> On
On 03/24/2013 08:41 AM, Lubomir Rintel wrote:
> This enables a driver for random number generator present on Broadcom BCM2835
> SoC,
> used in Raspberry Pi and Roku 2 devices.
Squashed into bcm2835's for-3.10/defconfig branch.
(Lubomir: defconfig updates get squashed to avoid too many patches
ch
On 03/28/2013 12:12 AM, Lubomir Rintel wrote:
> This adds a device tree binding for random number generator present on
> Broadcom
> BCM2835 SoC, used in Raspberry Pi and Roku 2 devices.
Applied to bcm2835's for-3.10/dt tree, with some slight fixups to the
patch subject and description word-wrappi
Several functions in of/base.c have the same code duplicated for
finding and validating a property and value.
struct property *prop = of_find_property(np, propname, NULL);
if (!prop)
return -EINVAL;
if (!prop->value)
return -ENODATA;
if ( > prop->length)
return -EOVERFLOW;
v5 changes:
Changed as requested by Rob Herring:
Added of_find_property_value_of_size() to drivers/of/base.c to remove some
code that was being duplicated.
Changed as requested by Stephen Warren:
Redid the kfree(maps) code as devm_kzalloc would cause issues. We now kzalloc
maps all at once, and co
With the inclusion of the pin control driver, more GPIO pins have been
identified on the arch-vt8500 SoCs requiring an increase in the available
GPIOs.
Signed-off-by: Tony Prisk
---
arch/arm/Kconfig |3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/arch/arm/Kconfig b/arch/
Remove the gpio related devicetree nodes as these are no longer required
with the move to a combined pinctrl/gpio driver.
Signed-off-by: Tony Prisk
---
arch/arm/boot/dts/vt8500.dtsi |7 ---
arch/arm/boot/dts/wm8505.dtsi |7 ---
arch/arm/boot/dts/wm8650.dtsi |7 ---
arch/a
With the move to a combined pinctrl/gpio driver, the arch-vt8500
gpio driver is no longer required.
Signed-off-by: Tony Prisk
---
.../devicetree/bindings/gpio/gpio-vt8500.txt | 24 --
drivers/gpio/Kconfig |6 -
drivers/gpio/Makefile
This patch adds pinctrl nodes to the VIA VT8500 and Wondermedia SoC dtsi
files to support the pinctrl driver.
Signed-off-by: Tony Prisk
---
arch/arm/boot/dts/vt8500.dtsi |9 +
arch/arm/boot/dts/wm8505.dtsi |9 +
arch/arm/boot/dts/wm8650.dtsi |9 +
arch/arm/boo
This patch adds an of_property_read_u32_index() function to allow
reading a single indexed u32 value from a property containing multiple
u32 values.
Signed-off-by: Tony Prisk
Reviewed-by: Stephen Warren
---
drivers/of/base.c | 33 +
include/linux/of.h |9 +
On 04/03/2013 12:28 PM, Alex Shi wrote:
> On 04/03/2013 11:23 AM, Michael Wang wrote:
>> On 04/03/2013 10:56 AM, Alex Shi wrote:
>>> On 04/03/2013 10:46 AM, Michael Wang wrote:
[snip]
>
>
> From 4722a7567dccfb19aa5afbb49982ffb6d65e6ae5 Mon Sep 17 00:00:00 2001
> From: Alex Shi
> Date: Tue, 2 Apr
Hi Kishon,
On Wed, Apr 3, 2013 at 10:38 AM, Kishon Vijay Abraham I wrote:
> Hi,
>
>
> On Monday 01 April 2013 07:24 PM, Vivek Gautam wrote:
>>
>> Adding APIs to handle runtime power management on PHY
>> devices. PHY consumers may need to wake-up/suspend PHYs
>> when they work across autosuspend
Hello Minchan
On Wed, Apr 3, 2013 at 2:23 AM, Minchan Kim wrote:
> Hey Michael,
>
> On Tue, Apr 02, 2013 at 03:25:25PM +0200, Michael Kerrisk wrote:
>> Minchan,
>>
>> On Mon, Mar 25, 2013 at 7:21 AM, Minchan Kim wrote:
>> >
>> > Some pages could be shared by several processes. (ex, libc)
>> > In
Hi Andrew,
Today's linux-next merge of the akpm tree got a conflict in ipc/msg.c
between commit 2dc958fa2fe6 ("ipc: set msg back to -EAGAIN if copy wasn't
performed") from Linus' tree and commit "ipc: remove msg handling from
queue scan" from the akpm tree.
I fixed it up (I think - see below) and
On 2013년 04월 02일 20:18, Daniel Lezcano wrote:
> On 04/02/2013 01:07 PM, jonghwa3@samsung.com wrote:
>> On 2013년 04월 02일 19:08, Daniel Lezcano wrote:
>>
>>> On 04/02/2013 11:37 AM, jonghwa3@samsung.com wrote:
On 2013년 04월 02일 16:34, Daniel Lezcano wrote:
> On 04/02/2013 08:17
Signed-off-by: Wenyou Yang
Cc: li...@arm.linux.org.uk
Cc: linux-kernel@vger.kernel.org
---
arch/arm/boot/dts/at91sam9260.dtsi | 22 ++
arch/arm/boot/dts/at91sam9263.dtsi | 22 ++
arch/arm/boot/dts/at91sam9g45.dtsi | 22 ++
arch/arm
Hi Felipe,
On Tue, Apr 2, 2013 at 1:59 PM, Felipe Balbi wrote:
> On Mon, Apr 01, 2013 at 07:24:01PM +0530, Vivek Gautam wrote:
>> The current code in the dwc3 probe effectively disables runtime pm
>> from ever working because it calls a get() that was never put() until
>> device removal. Change
From: Richard Genoud
Signed-off-by: Richard Genoud
[wenyou.y...@atmel.com: added spi nodes for the sam9263ek, sam9g20ek,
sam9m10g45ek and sam9n12ek boards]
[wenyou.y...@atmel.com: submit the patch]
Signed-off-by: Wenyou Yang
Cc: li...@arm.linux.org.uk
Cc: linux-kernel@vger.kernel.org
---
arch
From: Richard Genoud
Signed-off-by: Richard Genoud
[wenyou.y...@atmel.com: add spi nodes for sam9260, sam9263, sam9g45 and sam9n12]
[wenyou.y...@atmel.com: remove spi property "cs-gpios" to the board dts files]
[wenyou.y...@atmel.com: submit the patch]
Signed-off-by: Wenyou Yang
Cc: li...@arm.l
From: Richard Genoud
Signed-off-by: Richard Genoud
[
Cc: li...@arm.linux.org.uk
Cc: li...@maxim.org.za
Cc: linux-kernel@vger.kernel.org
---
arch/arm/mach-at91/at91sam9260.c |2 ++
arch/arm/mach-at91/at91sam9g45.c |2 ++
arch/arm/mach-at91/at91sam9n12.c |2 ++
arch/arm/mach-at91/at91
On 04/03/2013 01:38 PM, Michael Wang wrote:
> On 04/03/2013 12:28 PM, Alex Shi wrote:
> [snip]
>>
>> but the patch may cause some unfairness if this/prev cpu are not burst at
>> same time. So could like try the following patch?
>
> I will try it later, some doubt below :)
>
> [snip]
>> +
>> +
From: Nicolas Ferre
Add dmaengine support.
Using "has_dma_support" member of struct is used to select
the transfer mode: dmaengine or pdc.
For the dmaengine transfer mode, it supports both 8 bits and 16 bits transfer.
For the dmaengine transfer mode, if it fails to config dmaengine,
or if the
From: Richard Genoud
Fix using PIO transfer mode only support 8 bits transfer, doesn't support 16
bits.
Signed-off-by: Richard Genoud
Cc: spi-devel-gene...@lists.sourceforge.net
Cc: linux-kernel@vger.kernel.org
[wenyou.y...@atmel.com: submit the patch]
Signed-off-by: Wenyou Yang
---
drivers/
Hi,
On Friday 29 March 2013 12:01 AM, David Miller wrote:
You really need to CC: net...@vger.kernel.org rather than me explicitly
on this patch set.
I was CC'ing whatever get_maintainer shows. I'll make sure to CC
net...@vger.kernel.org though there's nothing related to network in this
patc
2013/4/1, Jaegeuk Kim :
> When allocating a new segment under the LFS mode, we should keep the
> section
> boundary.
>
> Signed-off-by: Jaegeuk Kim
You can add
Reviewed-by: Namjae Jeon
Thanks!
> ---
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a messa
From: Nicolas Ferre
Will allow to drop the lock during DMA operations.
Replacing non-irqsave versions with irqsave versions of the lock
to make it correct in both pdc and dmaengine transfer mode
Signed-off-by: Nicolas Ferre
Cc: spi-devel-gene...@lists.sourceforge.net
Cc: linux-kernel@vger.kern
2013/4/1, Jaegeuk Kim :
> This patch adds a new condition that allocates free segments in the current
> active section even if SSR is needed.
> Otherwise, f2fs cannot allocate remained free segments in the section since
> SSR finds dirty segments only.
>
> Signed-off-by: Jaegeuk Kim
Looks good!
Re
From: Nicolas Ferre
Needed for future use with dmaengine enabled driver.
Signed-off-by: Nicolas Ferre
Cc: spi-devel-gene...@lists.sourceforge.net
Cc: linux-kernel@vger.kernel.org
[wenyou.y...@atmel.com: submit the patch]
Signed-off-by: Wenyou Yang
---
drivers/spi/spi-atmel.c |2 ++
1 file
hayeswang :
[...]
> Excuse me, I don't sure what is your question. Do you mean if the patch
> "[PATCH v2 net-next 5/8] r8169: Update the RTL8111G parameters" is necessary
> before the current patch? According to the settings from our hw engineers,
> some settings of the new chip are the same with
2013/4/1, Jaegeuk Kim :
> In get_node_page, we do not need to call lock_page all the time.
>
> If the node page is cached as uptodate,
>
> 1. grab_cache_page locks the page,
> 2. read_node_page unlocks the page, and
> 3. lock_page is called for further process.
>
> Let's avoid this.
Instead of remo
2013/4/1, Jaegeuk Kim :
> The foreground GCs are triggered under not enough free sections.
> So, we should not skip moving valid blocks in the victim segments.
>
> Signed-off-by: Jaegeuk Kim
Looks good to me~
Reviewed-by: Namjae Jeon
Thanks.
--
To unsubscribe from this list: send the line "unsub
2013/4/1, Jaegeuk Kim :
> In order to do GC more reliably, I'd like to lock the vicitm summary page
> until its GC is completed, and also prevent any checkpoint process.
>
> Signed-off-by: Jaegeuk Kim
> ---
> fs/f2fs/gc.c| 8 +---
> fs/f2fs/node.c | 2 +-
> fs/f2fs/super.c | 7 +--
>
On 04/03/2013 01:38 PM, Michael Wang wrote:
> On 04/03/2013 12:28 PM, Alex Shi wrote:
> [snip]
>>
>> but the patch may cause some unfairness if this/prev cpu are not burst at
>> same time. So could like try the following patch?
>
> I will try it later, some doubt below :)
>
> [snip]
>> +
>> +
2013/4/1, Jaegeuk Kim :
> This patch removes a bitmap for victim segments selected by foreground GC,
> and
> modifies the other bitmap for victim segments selected by background GC.
>
> 1) foreground GC bitmap
> : We don't need to manage this, since we just only one previous victim
> section
>
Please, try this patch maybe it can help localize your problem.
drivers/tty/n_tty.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/tty/n_tty.c b/drivers/tty/n_tty.c
index 05e72be..28f15d0 100644
--- a/drivers/tty/n_tty.c
+++ b/drivers/tty/n_tty.c
@@ -230,6 +230,7 @@ static void reset
struct rq *rq = cpu_rq(i);
>> +
>> +if (burst && rq->nr_running > 1)
>> +/* use nr_running as instant utilization */
>> +sgs->group_util += rq->nr_running;
>
> I guess multiplying FULL_UTIL to rq->nr_running here will remove
> special-cas
On 04/03/2013 12:28 PM, Alex Shi wrote:
[snip]
>
> but the patch may cause some unfairness if this/prev cpu are not burst at
> same time. So could like try the following patch?
I will try it later, some doubt below :)
[snip]
> +
> + if (cpu_rq(this_cpu)->avg_idle < sysctl_sched_migration_co
On Tue, Apr 02, 2013 at 10:17:29AM -0600, Toshi Kani wrote:
> Added release_mem_region_adjustable(), which releases a requested
> region from a currently busy memory resource. This interface
> adjusts the matched memory resource accordingly if the requested
> region does not match exactly but stil
On Wed, Apr 03, 2013 at 11:52:39AM +0800, Ming Lei wrote:
> On Wed, Apr 3, 2013 at 11:04 AM, Dave Jones wrote:
> > On Wed, Apr 03, 2013 at 10:58:23AM +0800, Ming Lei wrote:
> >
> > > diff --git a/fs/sysfs/dir.c b/fs/sysfs/dir.c
> > > index 1bf016b..328ef9b 100644
> > > --- a/fs/sysfs/dir.c
> >
On Tuesday 02 April 2013 09:10 PM, Stephen Warren wrote:
On 04/02/2013 02:37 AM, Kishon Vijay Abraham I wrote:
Hi,
On Thursday 28 March 2013 09:15 PM, Stephen Warren wrote:
On 03/27/2013 11:43 PM, Kishon Vijay Abraham I wrote:
The PHY framework provides a set of APIs for the PHY drivers to
cr
On 3 April 2013 04:27, Rafael J. Wysocki wrote:
> On Tuesday, April 02, 2013 08:29:12 PM Viresh Kumar wrote:
>> On 2 April 2013 20:25, Nathan Zimmer wrote:
>> > The lock is unneeded if we expect register and unregister driver to not be
>> > called from muliple threads at once. I didn't make that
> -Original Message-
> From: Joerg Roedel [mailto:j...@8bytes.org]
> Sent: Tuesday, April 02, 2013 8:40 PM
> To: Sethi Varun-B16395
> Cc: Yoder Stuart-B08248; Wood Scott-B07421; iommu@lists.linux-
> foundation.org; linuxppc-...@lists.ozlabs.org; linux-
> ker...@vger.kernel.org; ga...@kern
Kumar/Ben,
Any comments?
(Had checked with Ben (on IRC) sometime back, he was fine with this patch)
Regards
Varun
> -Original Message-
> From: Joerg Roedel [mailto:j...@8bytes.org]
> Sent: Tuesday, April 02, 2013 8:39 PM
> To: Sethi Varun-B16395
> Cc: Yoder Stuart-B08248; Wood Scott-B07
On 2 April 2013 23:41, Jacob Shin wrote:
> This allows for another [arch specific] driver to hook into existing
> powersave bias function of the ondemand governor. i.e. This allows AMD
> specific powersave bias function (in a separate AMD specific driver)
> to aid ondemand governor's frequency tra
> -Original Message-
> From: Wood Scott-B07421
> Sent: Wednesday, April 03, 2013 7:23 AM
> To: Timur Tabi
> Cc: Joerg Roedel; Sethi Varun-B16395; lkml; Kumar Gala; Yoder Stuart-
> B08248; io...@lists.linux-foundation.org; Benjamin Herrenschmidt;
> linuxppc-...@lists.ozlabs.org
> Subject:
Hi, Mark,
> -Original Message-
> From: Mark Brown [mailto:broo...@opensource.wolfsonmicro.com]
> Sent: 2013年4月1日 21:46
> To: Yang, Wenyou
> Cc: linux-arm-ker...@lists.infradead.org; grant.lik...@secretlab.ca;
> richard.gen...@gmail.com; plagn...@jcrosoft.com; Ferre, Nicolas; Lin, JM;
> spi
Hi,
On Monday 01 April 2013 07:24 PM, Vivek Gautam wrote:
Adding APIs to handle runtime power management on PHY
devices. PHY consumers may need to wake-up/suspend PHYs
when they work across autosuspend.
Signed-off-by: Vivek Gautam
---
include/linux/usb/phy.h | 141 +
Hi Alex,
On Sat, 30 Mar 2013 22:35:00 +0800, Alex Shi wrote:
> Sleeping task has no utiliation, when they were bursty waked up, the
> zero utilization make scheduler out of balance, like aim7 benchmark.
>
> rq->avg_idle is 'to used to accommodate bursty loads in a dirt simple
> dirt cheap manner'
On 03/30/2013 08:54 AM, Tejun Heo wrote:
> show_regs() is inherently arch-dependent but it does make sense to
> print generic debug information and some archs already do albeit in
> slightly different forms. This patch introduces a generic function to
> print debug information from show_regs() so
Hi Balbi,
On Tue, Apr 2, 2013 at 2:02 PM, Felipe Balbi wrote:
> Hi,
>
> On Mon, Apr 01, 2013 at 07:24:03PM +0530, Vivek Gautam wrote:
>> +#else
>> +#define dwc3_runtime_suspend NULL
>> +#define dwc3_runtime_resume NULL
>
> this #else branch is unnecessary. Look at the definition
On 18:46 Tue 02 Apr , Boris BREZILLON wrote:
> This patch fixes wrong clock request for TC block 2.
> The second block was using t0_clk, t1_clk and t2_clk clks instead of
> t3_clk, t4_clk and t5_clk clks.
>
this is intended as we have 3 clock per device
Best Regards,
J.
>
> Signed-off-by: Bo
On Tue, 2 Apr 2013 17:13:00 -0700
Greg KH wrote:
> On Tue, Apr 02, 2013 at 04:53:40PM -0700, Jacob Pan wrote:
> > On Tue, 2 Apr 2013 16:00:42 -0700
> > Greg KH wrote:
> >
> > > And, one final complaint, never use "raw" kobjects, for loads of
> > > good reasons, not the least being you just prev
On 07:20 Wed 03 Apr , Tony Prisk wrote:
Acked-by: Jean-Christophe PLAGNIOL-VILLARD
on the whole serie
Best Regards,
J.
> V3 Changes:
> Tidied up patch 1 as requested by Jean-Christophe - Makes the patch much
> simpler.
>
> V2 Changes:
> Split the SoC and board portions of the binding into th
Abhilash Kesavan wrote:
> >> > One concern is that I cannot apply Patch 1/4 directly as the .dts
> file isn't
> >> > available to me.
> >> > Do you intend to apply that patch to another tree and apply the other
> three
> >> > to devfreq tree?
> >> I have been merging the devfreq tree into Kgene's
On 04/03/2013 11:23 AM, Michael Wang wrote:
> On 04/03/2013 10:56 AM, Alex Shi wrote:
>> On 04/03/2013 10:46 AM, Michael Wang wrote:
>>> | 15 GB | 16 | 45110 | | 48091 |
>>> | 15 GB | 24 | 41415 | | 47415 |
>>> | 15 GB | 32 | 35988 | | 45749 | +27.12%
>>>
>>> Very nice
2013/4/3, Jaegeuk Kim :
> Hi,
> Thank you for your contribution.
>
> As I consider the null pointer check, generic_writepages() originally
> does so.
> Therefore, I think f2fs_write_data_pages() is better to handle this.
> Please review the modified patch.
> Thanks,
>
> ---
> From d3c811a51c7062fb1
This patch fixes compile warning in i386:
drivers/base/cpu.c: In function 'show_crash_notes_size':
drivers/base/cpu.c:142:2: warning: format '%lu' expects argument of type 'long
unsigned int', but argument 3 has type 'unsigned int' [-Wformat]
Reported-by: kbuild test robot
Signed-off-by: Zhang
On Mon, Apr 01, 2013 at 09:59:00PM -0700, Tony Chung wrote:
> Thanks Guenter!
> I agree with you. My first reaction was also about a small watchdog
> server that will start in early boot process. There are pros and
> cons. For example, there are many types of watchdog devices such as
> ipmi_wat
On Tue, Mar 26, 2013 at 01:46:56PM -0700, Andrew Morton wrote:
[...]
> > +The file memory.pressure_level is only used to setup an eventfd,
> > +read/write operations are no implemented.
[...]
> Did we tell people how to use the eventfd interface anywhere?
Good point. In v4 I added a detailed instr
On Wed, Mar 27, 2013 at 10:53:30AM +0900, Kamezawa Hiroyuki wrote:
[...]
> >+++ b/mm/memcontrol.c
> >@@ -49,6 +49,7 @@
> > #include
> > #include
> > #include
> >+#include
> > #include
> > #include
> > #include
> >@@ -376,6 +377,9 @@ struct mem_cgroup {
> > atomic_tnumainfo_
ters from 'unsigned int' to 'unsigned long',
this avoids possible overflows;
- Added Kamezawa's Ack, and rebased onto 3.9.0-rc5-next-20130402+.
In v3:
- No changes in the code, just updated commit message to incorporate the
answer to Minchan Kim's comment
On Wed, Apr 3, 2013 at 11:04 AM, Dave Jones wrote:
> On Wed, Apr 03, 2013 at 10:58:23AM +0800, Ming Lei wrote:
>
> > diff --git a/fs/sysfs/dir.c b/fs/sysfs/dir.c
> > index 1bf016b..328ef9b 100644
> > --- a/fs/sysfs/dir.c
> > +++ b/fs/sysfs/dir.c
> > @@ -268,6 +268,13 @@ void release_sysfs_dir
>> Yes, indeed you are very right - and thanks for looking at such depth.
>
> So what about the patch bellow? It seems that I provoked all this mess
> but my brain managed to push it away so I do not remember why I thought
> the parent needs reference drop... It is "only" 3.9 thing fortunately.
>
On 2013/4/2 21:32, Michal Hocko wrote:
> On Tue 02-04-13 16:22:23, Glauber Costa wrote:
>> On 04/02/2013 04:16 PM, Michal Hocko wrote:
>>> On Tue 02-04-13 15:35:28, Li Zefan wrote:
>>> [...]
@@ -6247,16 +6247,7 @@ mem_cgroup_css_online(struct cgroup *cont)
error = memcg_init_kme
On 2 April 2013 22:10, Olof Johansson wrote:
> On Wed, Mar 13, 2013 at 03:05:15PM +0530, Sachin Kamat wrote:
>> Fixes the following errors:
>> ERROR: do not initialise statics to 0 or NULL
>> ERROR: space required after that ',' (ctx:VxV)
>>
>> Signed-off-by: Sachin Kamat
>> ---
>> Compile tested
On 04/03/2013 10:56 AM, Alex Shi wrote:
> On 04/03/2013 10:46 AM, Michael Wang wrote:
>> | 15 GB | 16 | 45110 | | 48091 |
>> | 15 GB | 24 | 41415 | | 47415 |
>> | 15 GB | 32 | 35988 | | 45749 |+27.12%
>>
>> Very nice improvement, I'd like to test it with the wake-affi
On 04/02/2013 11:23 AM, Alex Shi wrote:
> Old function count the runnable avg on rq's nr_running even there is
> only rt task in rq. That is incorrect, so correct it to cfs_rq's
> nr_running.
this patch is incorrect and removed in
https://github.com/alexshi/power-scheduling.git runnablelb
On Tue, Apr 2, 2013 at 11:56 PM, Shawn Guo wrote:
> Ok, I'm seeing the error now on linux-next. It's not about compiler
> but the commit 3d5a965 (clocksource: make CLOCKSOURCE_OF_DECLARE type
> safe), which removes the semicolon at end of the
> CLOCKSOURCE_OF_DECLARE definition.
Right, the remov
From: David Jeffery
When checking if an autofs mount point is busy it isn't sufficient to
only check if it's a mount point.
For example, if the mount of an offset mountpoint in a tree is denied
for this host by its export and the dentry becomes a process working
directory the check incorrectly r
From: Claudiu Ghioc
Fixed the sparse warning:
* "fs/autofs4/root.c:411:5: warning:
symbol 'autofs4_d_manage' was not declared.
Should it be static?"
edit: imk
Clearly it should be static as the function is declared static at
the top of root.c.
end edit: imk
Signed-off-by: Claudiu Ghio
Hi,
Thank you for your contribution.
As I consider the null pointer check, generic_writepages() originally
does so.
Therefore, I think f2fs_write_data_pages() is better to handle this.
Please review the modified patch.
Thanks,
---
From d3c811a51c7062fb1b66bec910ed346447c02032 Mon Sep 17 00:00:00
Francois Romieu [mailto:rom...@fr.zoreil.com]
> Sent: Wednesday, April 03, 2013 6:27 AM
> To: Hayeswang
> Cc: net...@vger.kernel.org; linux-kernel@vger.kernel.org
> Subject: Re: [PATCH v2 net-next 6/8] r8169: add a new chip
> for RTL8111G
>
> Hayes Wang :
> > Add a new chip for RTL8111G series.
On Wed, Apr 03, 2013 at 10:58:23AM +0800, Ming Lei wrote:
> diff --git a/fs/sysfs/dir.c b/fs/sysfs/dir.c
> index 1bf016b..328ef9b 100644
> --- a/fs/sysfs/dir.c
> +++ b/fs/sysfs/dir.c
> @@ -268,6 +268,13 @@ void release_sysfs_dirent(struct sysfs_dirent * sd)
> */
> parent_sd = sd
It might be a kernel disaster if one sysfs entry is freed but
still referenced by sysfs tree.
Recently Dave and Sasha reported one use-after-free problem on
sysfs entry, and the problem has been troubleshooted with help
of debug message added in this patch.
Given sysfs_get_dirent/sysfs_put are ex
On 04/02/2013 10:30 PM, David Miller wrote:
> From: Alan Ott
> Date: Tue, 02 Apr 2013 22:25:28 -0400
>
>> The workqueue in mac802154 is only needed because the current mac802154
>> xmit() function is designed to be blocking and synchronous.
>>
>> Prior to my patch (#3/6), that very same workqueue
On 04/03/2013 10:46 AM, Michael Wang wrote:
> | 15 GB | 16 | 45110 | | 48091 |
> | 15 GB | 24 | 41415 | | 47415 |
> | 15 GB | 32 | 35988 | | 45749 | +27.12%
>
> Very nice improvement, I'd like to test it with the wake-affine throttle
> patch later, let's see what wil
On 3 April 2013 10:29, Shawn Guo wrote:
> On Tue, Apr 02, 2013 at 01:30:32PM -0300, Fabio Estevam wrote:
>> Fix the following build error:
>>
>> drivers/clocksource/mxs_timer.c:304:1: error: expected ',' or ';' at end of
>> input
>>
> What's your gcc version? I'm using gcc version 4.6.3 (Ubuntu/
- Original Message -
> From: "David Howells"
> To: "CAI Qian" , ru...@rustcorp.com.au
> Cc: dhowe...@redhat.com, "LKML"
> Sent: Wednesday, April 3, 2013 1:38:50 AM
> Subject: Re: NULL pointer at kset_find_obj
>
> CAI Qian wrote:
>
> > Just booted the latest mainline,
> >
> > [ 35.
Commit 201c373e8e ("sched/debug: Limit sd->*_idx range on sysctl")
was an incomplete bug fix. This patch fixs sd->*_idx limit range to
[0 ~ CPU_LOAD_IDX_MAX - 1] avioding array overflow caused by setting
sd->*_idx to CPU_LOAD_IDX_MAX on sysctl.
Signed-off-by: Libin
---
kernel/sched/core.c |2
On 04/02/2013 04:35 PM, Alex Shi wrote:
[snip]
>>
>> The reason may caused by wake_affine()'s higher overhead, and pgbench is
>> really sensitive to this stuff...
>
> Thanks for testing. Could you like to remove the last patch and test it
> again? I want to know if the last patch has effect on pgb
Hi all,
Today's linux-next merge of the drm-intel tree got a conflict in
drivers/gpu/drm/i915/intel_panel.c between commit b1289371fcd5 ("Revert
"drm/i915: write backlight harder"") from Linus' tree and commit
31ad8ec6a614 ("drm/i915: group backlight related stuff into a struct")
from the drm-inte
Reserving a large number of 1GB hugetlbfs pages at boot takes a very
long time due to the pages being memset to 0 during the reservation.
This is unneeded as the pages will be zeroed by clear_huge_page() when
being allocated by the user.
Large system sites would at times like to allocate a very la
Alan Ott wrote:
> 1. Most supported devices have only single packet output buffer, so
> blocking in the driver is the most straight-forward way to handle it.
> The alternative is to make each driver have a workqueue for xmit() (to
> lift the blocking out from atomic context). This makes each driver
On 04/03/2013 10:22 AM, Paul Turner wrote:
> On Tue, Apr 2, 2013 at 7:15 PM, Alex Shi wrote:
>> On 04/02/2013 05:02 PM, Namhyung Kim wrote:
> + cfs_util = (FULL_UTIL - rt_util) > rq->util ? rq->util
> + : (FULL_UTIL - rt_util);
> + nr_running = rq->nr_running ? rq->n
Signed-off-by: Axel Lin
---
drivers/regulator/ab8500.c |4
1 file changed, 4 insertions(+)
diff --git a/drivers/regulator/ab8500.c b/drivers/regulator/ab8500.c
index 73d84d8..d3170ae 100644
--- a/drivers/regulator/ab8500.c
+++ b/drivers/regulator/ab8500.c
@@ -3021,11 +3021,15 @@ static
Fix below build errors:
CC drivers/regulator/ab8500.o
drivers/regulator/ab8500.c: In function 'ab8500_regulator_probe':
drivers/regulator/ab8500.c:3018:3: error: 'match_size' undeclared (first use in
this function)
drivers/regulator/ab8500.c:3018:3: note: each undeclared identifier is repor
Both voltages and voltages_len are not exist in struct ab8500_regulator_info.
Signed-off-by: Axel Lin
---
drivers/regulator/ab8500.c |7 +--
1 file changed, 1 insertion(+), 6 deletions(-)
diff --git a/drivers/regulator/ab8500.c b/drivers/regulator/ab8500.c
index abdfbd4..bdd17e6 100644
The delay field is removed from struct ab8500_regulator_info in commit 29234928
"regulator: ab8500: Remove set_voltage_time_sel and delay setting".
In additional, current delay setting does not make sense at all.
ab8500_regulator_mode_ops is for fixed voltage only, which does not need
set_voltage_
From: Alan Ott
Date: Tue, 02 Apr 2013 22:25:28 -0400
> The workqueue in mac802154 is only needed because the current mac802154
> xmit() function is designed to be blocking and synchronous.
>
> Prior to my patch (#3/6), that very same workqueue would actually queue
> up packets (without bound). T
2013/4/2 Mark Brown :
> On Tue, Apr 02, 2013 at 08:39:53AM +0800, Axel Lin wrote:
>> This patch removes 'delay' field which does not exist in struct
>> ab8500_regulator_info. ( The 'delay' field was removed because fixed
>> regulator
>> does not need to implement set_voltage_time_sel. )
>> Fix mis
On Tue, Apr 02, 2013 at 01:30:32PM -0300, Fabio Estevam wrote:
> Fix the following build error:
>
> drivers/clocksource/mxs_timer.c:304:1: error: expected ',' or ';' at end of
> input
>
What's your gcc version? I'm using gcc version 4.6.3 (Ubuntu/Linaro
4.6.3-1ubuntu5), and do not see the compi
1 - 100 of 1039 matches
Mail list logo
