On Mon, Jan 21, 2013 at 02:27:29AM -0500, Chen Gong wrote:
> On Mon, Jan 21, 2013 at 02:38:41PM +0800, Feng Tang wrote:
> > Date: Mon, 21 Jan 2013 14:38:41 +0800
> > From: Feng Tang
> > To: Thomas Gleixner , John Stultz
> > , Ingo Molnar , "H. Peter Anvin"
> > , x...@kernel.org, Len Brown
On Sat, Jan 19, 2013 at 07:30:17PM +0900, Alexandre Courbot wrote:
> This series introduces a way to use pwm-backlight hooks with platforms
> that use the device tree through a subdriver system. It also adds support
> for the Tegra-based Ventana board, adding the last missing block to enable
> its
Currently we need to skip this for supporting KGDB.
Signed-off-by: Tiejun Chen
---
arch/powerpc/kernel/exceptions-64e.S |5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/arch/powerpc/kernel/exceptions-64e.S
b/arch/powerpc/kernel/exceptions-64e.S
index 423a936..6204681
This patchset is used to support kgdb/gdb on book3e.
v2:
* Make sure we cover CONFIG_PPC_BOOK3E_64 safely
* Use LOAD_REG_IMMEDIATE() to load properly
the value of the constant expression in load debug exception stack
* Copy thread infor form the kernel stack coming from usr
* Rebase
When we're in kgdb_singlestep(), we have to work around to get
thread_info by copying from the kernel stack before calling
kgdb_handle_exception(), then copying it back afterwards.
But for PPC64, we have a lazy interrupt implementation. So after
copying thread info frome kernle stack, if we need
On 01/21/2013 03:09 PM, Mike Galbraith wrote:
> On Mon, 2013-01-21 at 07:42 +0100, Mike Galbraith wrote:
>> On Mon, 2013-01-21 at 13:07 +0800, Michael Wang wrote:
>
>>> May be we could try change this back to the old way later, after the aim
>>> 7 test on my server.
>>
>> Yeah, something funny
gdb always need to generate a single step properly to invoke
a kgdb state. But with lazy interrupt, book3e can't always
trigger a debug exception with a single step since the current
is blocked for handling those pending exception, then we miss
that expected dbcr configuration at last to generate
We can't look up the address of the entry point of the function simply
via that function symbol for all architectures.
For PPC64 ABI, actually there is a function descriptors structure.
A function descriptor is a three doubleword data structure that contains
the following values:
* The
We need to store thread info to these exception thread info like something
we already did for PPC32.
Signed-off-by: Tiejun Chen
---
arch/powerpc/kernel/exceptions-64e.S | 15 +++
1 file changed, 15 insertions(+)
diff --git a/arch/powerpc/kernel/exceptions-64e.S
We always alloc critical/machine/debug check exceptions. This is
different from the normal exception. So we should load these exception
stack properly like we did for booke.
Signed-off-by: Tiejun Chen
---
arch/powerpc/kernel/exceptions-64e.S | 40 +++---
1 file
merged into cifs-2.6.git
On Wed, Jan 16, 2013 at 10:04 PM, Nickolai Zeldovich
wrote:
> On Wed, Jan 16, 2013 at 10:51 PM, Steve French wrote:
>> How did you discover this - did you have an ipv6 test case or by
>> inspection or ...?
>
> By mostly-automated inspection (i.e., with the help of a
On Mon, Jan 21, 2013 at 02:38:41PM +0800, Feng Tang wrote:
> Date: Mon, 21 Jan 2013 14:38:41 +0800
> From: Feng Tang
> To: Thomas Gleixner , John Stultz
> , Ingo Molnar , "H. Peter Anvin"
> , x...@kernel.org, Len Brown ,
> "Rafael J. Wysocki" ,
> linux-kernel@vger.kernel.org
> Cc: Feng Tang
On 01/19/2013 06:30 PM, Alexandre Courbot wrote:
> Add a PWM-backlight subdriver for Tegra boards, with support for
> Ventana.
>
> Signed-off-by: Alexandre Courbot
> ---
[...]
>
> + backlight {
> + compatible = "pwm-backlight-ventana";
> + brightness-levels = <0 16
On Mon, Jan 21, 2013 at 02:38:44PM +0800, Feng Tang wrote:
> Date: Mon, 21 Jan 2013 14:38:44 +0800
> From: Feng Tang
> To: Thomas Gleixner , John Stultz
> , Ingo Molnar , "H. Peter Anvin"
> , x...@kernel.org, Len Brown ,
> "Rafael J. Wysocki" ,
> linux-kernel@vger.kernel.org
> Cc: Feng Tang
On 01/21/2013 02:42 PM, Mike Galbraith wrote:
> On Mon, 2013-01-21 at 13:07 +0800, Michael Wang wrote:
>
>> That seems like the default one, could you please show me the numbers in
>> your datapoint file?
>
> Yup, I do not touch the workfile. Datapoints is what you see in the
> tabulated
The test of KBUILD_OUTPUT in "rpm-pkg rpm" target is useless.
KBUILD_OUTPUT is always empty here.
Signed-off-by: Bin Wang
---
scripts/package/Makefile | 6 --
1 file changed, 6 deletions(-)
diff --git a/scripts/package/Makefile b/scripts/package/Makefile
index 87bf080..ba073a6 100644
---
On Sun, Jan 20, 2013 at 04:42:55PM +0100, Daniel Vetter wrote:
> On Sun, Jan 20, 2013 at 4:08 PM, Rob Clark wrote:
> > One thing I've run into in the past when trying to make changes in drm
> > core, and Daniel Vetter has mentioned the same, is that it is a bit of
> > a pain to compile test
This patch make sure bootmem will not allocate memory from areas that
may be ZONE_MOVABLE. The map info is from movablecore_map boot option.
Signed-off-by: Tang Chen
Reviewed-by: Wen Congyang
Reviewed-by: Lai Jiangshan
Tested-by: Lin Feng
---
include/linux/memblock.h |2 +
mm/memblock.c
On Sun, Jan 20, 2013 at 11:39 PM, Greg KH wrote:
> On Sun, Jan 20, 2013 at 07:08:28PM +0100, Thomas De Schampheleire wrote:
>> [plaintext and fixed address of David Brownell]
>
> David passed away a year or so ago, so that's really not going to help :(
So sorry to hear that, I was not aware...
Hi,
2013/1/18 Oleg Nesterov :
>
> I can't understand why do you dislike Ivo's simple patch. There are
> a lot of "if (waitqueue_active) wake_up" examples. Even if we add the
> new helpers (personally I don't think this makes sense) , we can do
> this later. Why should we delay this fix?
>
FYI:
Hi Stephen,
On 01/21/2013 02:08 PM, Stephen Rothwell wrote:
Hi all,
After merging the final tree, today's linux-next build (arm defconfig)
failed like this:
mm/memblock.c: In function 'memblock_find_in_range_node':
mm/memblock.c:104:2: error: invalid use of undefined type 'struct
Hello, Minchan.
On Thu, Jan 17, 2013 at 08:59:22AM +0900, Minchan Kim wrote:
> Hi Joonsoo,
>
> On Wed, Jan 16, 2013 at 05:08:55PM +0900, Joonsoo Kim wrote:
> > If object is on boundary of page, zs_map_object() copy content of object
> > to pre-allocated page and return virtual address of
>
>
On Mon, 2013-01-21 at 07:42 +0100, Mike Galbraith wrote:
> On Mon, 2013-01-21 at 13:07 +0800, Michael Wang wrote:
> > May be we could try change this back to the old way later, after the aim
> > 7 test on my server.
>
> Yeah, something funny is going on.
Never entering balance path kills the
On Mon, Jan 21, 2013 at 09:54:39AM +0900, Simon Horman wrote:
> On Fri, Jan 18, 2013 at 08:16:12AM +0100, Thierry Reding wrote:
> > The asm/hardware/gic.h header does no longer exist and the corresponding
> > functionality was moved to linux/irqchip.h and linux/irqchip/arm-gic.h
> > respectively.
From: Vivek Goyal
Subject: Re: [RFC PATCH v1 0/3] kdump, vmcore: Map vmcore memory in direct
mapping region
Date: Fri, 18 Jan 2013 15:54:13 -0500
> On Fri, Jan 18, 2013 at 11:06:59PM +0900, HATAYAMA Daisuke wrote:
>
> [..]
>> > These are impressive improvements. I missed the discussion on
On Saturday 19 January 2013 08:39 AM, Al Viro wrote:
> Please, collapse your #36--#40 into that one (and I'd probably fold #17
> here as well, to simplify that reordering). Sure, it's not a bisection
> hazard, but...
>
I kept #16 and #17 distinct and
* squashed
On Sun, Jan 20, 2013 at 3:23 PM, Rafael J. Wysocki wrote:
> On Thursday, January 17, 2013 11:53:22 PM Yinghai Lu wrote:
>> We want to put created pci device in the device tree as soon as possible.
>> - just after we find it and create pci_dev struct for it.
>> so for_pci_dev iteration will not
Hi Felipe,
On Mon, Jan 14, 2013 at 6:29 PM, Vivek Gautam wrote:
> Changes from v2:
> - Renaming 'samsung-usbphy.c' driver to 'samsung-usb2.c' indicating
>usb 2.0 phy controller's driver for Samsung's SoCs.
> - Moving the register definitions and strcuture definitions to
>common header
On Mon, 2013-01-21 at 13:07 +0800, Michael Wang wrote:
> That seems like the default one, could you please show me the numbers in
> your datapoint file?
Yup, I do not touch the workfile. Datapoints is what you see in the
tabulated result...
1
1
1
5
5
5
10
10
10
...
so it does three
2013/1/21, OGAWA Hirofumi :
> Namjae Jeon writes:
>
>> 2013/1/20, OGAWA Hirofumi :
>>> Namjae Jeon writes:
>>>
From: Namjae Jeon
When searching a directory for names, we can stop checking for further
entries if we detect End of Directory, i.e. if (de->name[0] ==
There are some new processors whose TSC clocksource won't stop during
suspend. Currently, after system resumes from sleep state, kernel will
use persistent clock or RTC to compensate the sleep time, but for those
new types of clocksources, we could skip the special compensation from
external
Signed-off-by: Feng Tang
---
arch/x86/kernel/tsc.c |6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/arch/x86/kernel/tsc.c b/arch/x86/kernel/tsc.c
index 06ccb50..4cc33ca 100644
--- a/arch/x86/kernel/tsc.c
+++ b/arch/x86/kernel/tsc.c
@@ -767,7 +767,8 @@ static cycle_t
On our x86 platform, we see a failure case of calling clocksource_cyc2ns(),
which return a negative value. The reason is the time interval was large
(more than 1000 seconds), while its TSC frequency is 2GHz, so the following
fomular overflowed:
((u64) cycles * mult) >> shift
So enlarge
Hi All,
On some new Intel Atom processors (Penwell and Cloverview), there is
a feature that the TSC won't stop S3, say the TSC value won't be
reset to 0 after resume. This feature makes TSC a more reliable
clocksource and could benefit the timekeeping code during system
suspend/resume cycles.
On some new Intel Atom processors (Penwell and Cloverview), there is
a feature that the TSC won't stop S3, say the TSC value won't be
reset to 0 after resume. This feature makes TSC a more reliable
clocksource and could benefit the timekeeping code during system
suspend/resume cycle, so add a flag
Some x86 processors have a TSC clocksource, which continue to work when
system is suspend. Add a feature flag so that it could be utilized.
Signed-off-by: Feng Tang
---
include/linux/clocksource.h |1 +
1 file changed, 1 insertion(+)
diff --git a/include/linux/clocksource.h
I found KBUILD_OUTPUT variable is useless in the rpm-pkg and rpm target.
Yes there is a comment said:
# Note that the rpm-pkg target cannot be used with KBUILD_OUTPUT,
# but the binrpm-pkg target can; for some reason O= gets ignored.
It does not say for what reason. Also, the code under rpm-pkg
From: Lad, Prabhakar
Add OF_DEV_AUXDATA for eth0 driver in da850 board dt
file to use emac clock.
Signed-off-by: Lad, Prabhakar
Cc: linux-arm-ker...@lists.infradead.org
Cc: linux-kernel@vger.kernel.org
Cc: davinci-linux-open-sou...@linux.davincidsp.com
Cc: net...@vger.kernel.org
Cc:
From: Lad, Prabhakar
Add eth0 device tree node information to da850 by
providing interrupt details and local mac address of eth0.
Signed-off-by: Lad, Prabhakar
Cc: linux-arm-ker...@lists.infradead.org
Cc: linux-kernel@vger.kernel.org
Cc: davinci-linux-open-sou...@linux.davincidsp.com
Cc:
From: Lad, Prabhakar
This patch set enables Ethernet support through device tree model.
Patches are available on [1] for testing.
[1]
http://git.linuxtv.org/mhadli/v4l-dvb-davinci_devices.git/shortlog/refs/heads/da850_dt
Lad, Prabhakar (2):
ARM: davinci: da850: add DT node for eth0.
ARM:
Hi all,
Changes since 20130118:
The powerpc tree still had a build failure.
The security tree gained a conflict against Linus' tree.
The driver-core tree lost its build failure.
The tty tree gained a conflict against Linus' tree.
The usb tree gained a conflict against Linus' tree and a build
I'm not a network developer, so correct me if I'm wrong.
Since commit 406a3c638ce8b17d9704052c07955490f732c2b8
("net: netprio_cgroup: rework update socket logic"), sock->sk->sk_cgrp_prioidx
is set when the socket is created, and won't be updated unless the task is
moved to another cgroup.
Now
Hi all,
After merging the final tree, today's linux-next build (arm defconfig)
failed like this:
mm/memblock.c: In function 'memblock_find_in_range_node':
mm/memblock.c:104:2: error: invalid use of undefined type 'struct
movablecore_map'
mm/memblock.c:123:4: error: invalid use of undefined type
On Sun, Jan 20, 2013 at 06:39:09PM -0800, Linus Torvalds wrote:
> And right now, that HAVE_SYSCALL_WRAPPERS does make it much harder to
> think about the header file changes.
Agreed.
> > FWIW, there's another bit of ugliness around that area - all these
> > #define __SC_BLAH3, etc., all of the
On Fri, Jan 18, 2013 at 11:46:02PM -0500, Konrad Rzeszutek Wilk wrote:
> On Fri, Jan 18, 2013 at 07:11:32PM -0600, Matt Sealey wrote:
> > On Fri, Jan 18, 2013 at 3:08 PM, Russell King - ARM Linux
> > wrote:
> > > On Fri, Jan 18, 2013 at 02:24:15PM -0600, Matt Sealey wrote:
> > >> Hello all,
> >
Hi Shawn,
On Mon, 21 Jan 2013 14:20:13 +0800 Shawn Guo wrote:
>
> On Sat, Jan 19, 2013 at 10:40:45AM +1100, Stephen Rothwell wrote:
> >
> > On Fri, 18 Jan 2013 16:02:13 +0800 Shawn Guo wrote:
> > >
> > > My bad, sorry for that. I just sent a v2 in reply to this message
> > > for fixing the
On Sat, Jan 19, 2013 at 10:40:45AM +1100, Stephen Rothwell wrote:
> Hi Shawn,
>
> On Fri, 18 Jan 2013 16:02:13 +0800 Shawn Guo wrote:
> >
> > My bad, sorry for that. I just sent a v2 in reply to this message
> > for fixing the error. I spent some time trying to install a ppc64
> > toolchain
On Sunday 20 January 2013 11:45 AM, H. Peter Anvin wrote:
> On 01/18/2013 04:24 AM, Vineet Gupta wrote:
>> This patchset based off-of 3.8-rc4, adds the Linux kernel port to ARC700
>> processor family (750D and 770D) from Synopsys. I would be greatful for
>> further review and feedback.
>
> One
On Sat, Jan 19, 2013 at 7:28 AM, Rafael J. Wysocki wrote:
> On Friday, January 18, 2013 01:52:31 PM Nishanth Menon wrote:
>> Hi,
>> Despite being documented in function documentation and in
>> Documentation/power/opp.txt, many of the users of OPP APIs
>> dont honor RCU lock usage appropriately.
Hi Andrew,
Today's linux-next merge of the akpm tree got a conflict in
drivers/gpu/drm/drm_fb_helper.c between commit 848499032504 ("drm: add
drm_modeset_lock|unlock_all") from the drm tree and commit
"drivers/gpu/drm/drm_fb_helper.c: avoid sleeping in unblank_screen() if
oops in progress" from
Namjae Jeon writes:
> 2013/1/20, OGAWA Hirofumi :
>> Namjae Jeon writes:
>>
>>> From: Namjae Jeon
>>>
>>> When searching a directory for names, we can stop checking for further
>>> entries if we detect End of Directory, i.e. if (de->name[0] == 0x00).The
>>> current code traverses the cluster
> -Original Message-
> From: Mike Snitzer [mailto:snit...@redhat.com]
> Sent: Saturday, January 19, 2013 3:08 AM
> To: Darrick J. Wong
> Cc: device-mapper development; Amit Kale; linux-bca...@vger.kernel.org;
> kent.overstr...@gmail.com; LKML; lsf...@lists.linux-foundation.org; Joe
>
On Sun, Jan 20, 2013 at 3:15 PM, Rafael J. Wysocki wrote:
> On Thursday, January 17, 2013 11:53:21 PM Yinghai Lu wrote:
>> with that we could move out attaching driver for pci device,
>> out of device_add for pci hot add path.
>>
>> pci_bus_attach_device() will attach driver to pci device.
>
>
Lockdep complains about recursive deadlock of zram->init_lock.
[1] made it false positive because we can't request IO to zram
before setting disksize. Anyway, we should shut lockdep up to
avoid many reporting from user.
Cc: Jerome Marchand
Cc: Nitin Gupta
Signed-off-by: Minchan Kim
---
Now zram document syas "set disksize is optional"
but partly it's wrong. When you try to use zram firstly after
booting, you must set disksize, otherwise zram can't work because
zram gendisk's size is 0. But once you do it, you can use zram freely
after reset because reset doesn't reset to zero
Now zram allocates new page with GFP_KERNEL in zram I/O path
if IO is partial. Unfortunately, It may cuase deadlock with
reclaim path so this patch solves the problem.
Cc: Nitin Gupta
Cc: Jerome Marchand
Signed-off-by: Minchan Kim
---
We could use GFP_IO instead of GFP_ATOMIC in zram_bvec_read
1) User of zram normally do mkfs.xxx or mkswap before using
the zram block device(ex, normally, do it at booting time)
It ends up allocating such metadata of zram before real usage so
benefit of lazy initialzation would be mitigated.
2) Some user want to use zram when memory pressure is
On Fri, Jan 18, 2013 at 01:34:18PM -0800, Nitin Gupta wrote:
> On Wed, Jan 16, 2013 at 6:12 PM, Minchan Kim wrote:
> > Lockdep complains about recursive deadlock of zram->init_lock.
> > [1] made it false positive because we can't request IO to zram
> > before setting disksize. Anyway, we should
On Fri, Jan 18, 2013 at 02:14:15PM +0200, Andy Shevchenko wrote:
> The proper place for the main logic of the soft LLP mode is
> dwc_scan_descriptors. It prevents to get the transfer unexpectedly aborted in
> case the user calls dwc_tx_status.
>
> Signed-off-by: Andy Shevchenko
Applied, Thanks
On Thu, Jan 17, 2013 at 01:35:47PM +0530, Viresh Kumar wrote:
> On Thu, Jan 17, 2013 at 1:33 PM, Andy Shevchenko
> wrote:
> > The driver assumes that hardware has two AHB masters which might not be
> > always
> > true. In such cases we must not exceed number of the AHB masters present in
> >
On Wed, Jan 16, 2013 at 03:48:50PM +0200, Andy Shevchenko wrote:
> Currently descriptors are allocated from normal cacheable memory and that
> slows
> down filling the descriptors, as we need to call cache_coherency routines
> afterwards. It would be better to allocate memory for these
On 01/21/2013 12:38 PM, Mike Galbraith wrote:
> On Mon, 2013-01-21 at 10:50 +0800, Michael Wang wrote:
>> On 01/20/2013 12:09 PM, Mike Galbraith wrote:
>>> On Thu, 2013-01-17 at 13:55 +0800, Michael Wang wrote:
Hi, Mike
I've send out the v2, which I suppose it will fix the below
Hi Colin,
On Sat, 19 Jan 2013 16:36:54 +, Colin King wrote:
> From: Colin Ian King
>
> __perf_evsel__read_on_cpu() only bails out with -ENOMEM if
> evsel->counts is NULL and perf_evsel__alloc_counts() has returned
> an error. If perf_evsel__alloc_counts() does not return an error
> we get
Hi Kukjin,
Today's linux-next merge of the samsung tree got a conflict in
drivers/gpio/gpio-samsung.c between commit 6948ce588bd7 ("gpio: samsung:
skip gpio lib registration for EXYNOS5440") from the gpio-lw tree and
commit bda7f6d4e198 ("gpio: samsung: skip gpiolib registration if pinctrl
On Fri, Jan 04, 2013 at 09:31:09PM +0200, Pantelis Antoniou wrote:
> Introduce support for dynamic device tree resolution.
> Using it, it is possible to prepare a device tree that's
> been loaded on runtime to be modified and inserted at the kernel
> live tree.
>
> Signed-off-by: Pantelis
On Mon, 2013-01-21 at 10:50 +0800, Michael Wang wrote:
> On 01/20/2013 12:09 PM, Mike Galbraith wrote:
> > On Thu, 2013-01-17 at 13:55 +0800, Michael Wang wrote:
> >> Hi, Mike
> >>
> >> I've send out the v2, which I suppose it will fix the below BUG and
> >> perform better, please do let me know
On Sun, Jan 20, 2013 at 7:52 PM, Rusty Russell wrote:
>
> You've now conflated two completely different lock paths into a single
> unlock.
We have that elsewhere too. And it's what we used to have before too.
So the simple fact is that commit 1fb9341ac348 just introduced this
bug, and moving
Hi Mimi,
On Sun, 20 Jan 2013 22:10:23 -0500 Mimi Zohar wrote:
>
> Sorry Stephen, the merged result should look like what's contained in
> linux-integrity/next-upstreamed-patches:
>
> int ima_module_check(struct file *file)
> {
> if (!file) {
> if ((ima_appraise &
Hi Greg,
After merging the usb tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
drivers/usb/core/port.c: In function 'usb_port_device_release':
drivers/usb/core/port.c:25:2: error: implicit declaration of function 'kfree'
[-Werror=implicit-function-declaration]
From: Eric Dumazet
Date: Fri, 18 Jan 2013 22:13:16 -0800
> On Fri, 2013-01-18 at 21:54 -0800, Eric Dumazet wrote:
>
>>
>> Hmm, this might be already fixed in net-next tree, could you try it ?
>>
>
> Yes, running your program on net-next seems OK.
>
> David, we need the two following
From: YOSHIFUJI Hideaki
Date: Sun, 20 Jan 2013 17:03:07 +0900
> Signed-off-by: YOSHIFUJI Hideaki
Applied.
--
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
From: YOSHIFUJI Hideaki
Date: Sun, 20 Jan 2013 16:43:40 +0900
> It is wrong to set skb->ip_summed to CHECKSUM_UNNECESSARY unless
> the device has already checked it.
>
> Signed-off-by: YOSHIFUJI Hideaki
Applied.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the
On Mon, Jan 21, 2013 at 11:03 AM, Mulyadi Santosa
wrote:
> Hello everybody
>
> With the significant usage of virtualization in recent years, I
> personally think there might be a need to easily generate somewhat
> more optimal kernel for running as VM guest.
To make it clearer, it will be saved
2013/1/20, OGAWA Hirofumi :
> Namjae Jeon writes:
>
>> From: Namjae Jeon
>>
>> When searching a directory for names, we can stop checking for further
>> entries if we detect End of Directory, i.e. if (de->name[0] == 0x00).The
>> current code traverses the cluster chain of a directory until a hit
Hi Greg,
Today's linux-next merge of the usb tree got a conflict in
drivers/usb/serial/io_ti.c between commit 1ee0a224bc9a ("USB: io_ti: Fix
NULL dereference in chase_port()") from Linus' tree and commit
f40d781554ef ("USB: io_ti: kill custom closing_wait implementation") from
the usb tree.
I
From: Patrik Karlin
Date: Mon, 21 Jan 2013 00:12:55 +0100
> This patch fixes statement placement around if/else/for statments
> as suggested by checkpatch.pl
>
> Signed-off-by: Patrik Kårlin
This patch set is a good example of why nobody should
fix up coding style in such a robotic way in
Linus Torvalds writes:
> On Sun, Jan 20, 2013 at 5:20 PM, Rusty Russell wrote:
>> Dan Carpenter writes:
>>> We take the lock twice if we hit this goto.
>>>
>>> Signed-off-by: Dan Carpenter
>>
>> Damn, just pushed that to Linus: should have read mail first.
>>
>> I've added this, thanks.
>
>
Hi Linus,
A bunch of intel and radeon fixes, along with two fixes to TTM code.
The correct fix for the Intel ironlake failure is in this, and should make
things more stable, along with some misc radeon fixes.
Dave.
The following changes since commit 7b4cf994e4c6ba48872bb25253cc393b7fb74c82:
Hi Greg,
Today's linux-next merge of the tty tree got a conflict in
drivers/tty/serial/vt8500_serial.c between commit a6dd114e16cb ("tty:
serial: vt8500: fix return value check in vt8500_serial_probe()") from
Linus' tree and commit 12faa35ae5cb ("serial: vt8500: UART uses gated
clock rather than
Dear Greg:
> -Original Message-
> From: Greg KH [mailto:gre...@linuxfoundation.org]
> Sent: Saturday, January 19, 2013 7:42 AM
> To: Fangxiaozhi (Franko)
> Cc: linux-...@vger.kernel.org; linux-kernel@vger.kernel.org; Xueguiying
> (Zihan);
> Linlei (Lei Lin); Yili (Neil); Wangyuhua
On Sun, Jan 20, 2013 at 11:51:08AM -0500, Matt Porter wrote:
> The explanation in the cover letter mentions that dmaengine_slave_config() is
> required to be called prior to dmaengine_get_channel_caps(). If we
> switch to the alternative API, then that would go away including the
> dependency on
On Sun, Jan 20, 2013 at 11:37:35AM -0500, Matt Porter wrote:
> On Sun, Jan 20, 2013 at 12:37:34PM +, Vinod Koul wrote:
> > On Thu, Jan 10, 2013 at 02:07:03PM -0500, Matt Porter wrote:
> > > The call is implemented as follows:
> > >
> > > struct dmaengine_chan_caps
> > >
Dear Greg:
> -Original Message-
> From: Greg KH [mailto:g...@kroah.com]
> Sent: Saturday, January 19, 2013 7:44 AM
> To: Fangxiaozhi (Franko)
> Cc: linux-...@vger.kernel.org; linux-kernel@vger.kernel.org; Xueguiying
> (Zihan);
> Linlei (Lei Lin); Yili (Neil); Wangyuhua (Roger,
On 01/21/2013 10:40 AM, Preeti U Murthy wrote:
> Hi Alex,
> Thank you very much for running the below benchmark on
> blocked_load+runnable_load:) Just a few queries.
>
> How did you do the wake up balancing? Did you iterate over the L3
> package looking for an idle cpu? Or did you just query the
On Sun, Jan 20, 2013 at 6:57 PM, Rusty Russell wrote:
>
> I'm confused. The default argument is HEAD: what does it know about tag
> names?
Ugh. I actually thought that if you give it the tag name directly (as
the "end") it will use that.
But no. It figures it out with "git describe --exact"
When calculating amount of dirtyable memory, min_free_kbytes should be
subtracted because it is not intended for dirty pages.
Using an "extern int" because that is the only interface to some such
sysctl values.
(This patch does not solve the PAE OOM issue.)
Paul Szabo p...@maths.usyd.edu.au
On Mon, 2013-01-21 at 13:12 +1100, Stephen Rothwell wrote:
> Hi James,
>
> Today's linux-next merge of the security tree got a conflict in
> security/integrity/ima/ima_main.c between commit a7f2a366f623 ("ima:
> fallback to MODULE_SIG_ENFORCE for existing kernel module syscall") from
> Linus'
Ensure MAX_PAUSE is 4 or larger, so limits in
return clamp_val(t, 4, MAX_PAUSE);
(the only use of it) are not back-to-front.
(This patch does not solve the PAE OOM issue.)
Paul Szabo p...@maths.usyd.edu.au http://www.maths.usyd.edu.au/u/psz/
School of Mathematics and Statistics
Patch is applied OK on 3.8-rc4.
Hmmm.. But I think it's better to make the patch can be applied on
linux-next.
Mark
On 01/21/2013 10:09 AM, Mark Zhang wrote:
> Hi Alex,
>
> This patch set applies failed on tot linux-next(0118). Here is the log:
>
>
Linus Torvalds writes:
> On Sun, Jan 20, 2013 at 5:32 PM, Rusty Russell wrote:
>>
>> Due to the delay on git.kernel.org, git request-pull fails. It *looks*
>> like it succeeds, except the warning, but (as we learned last time I
>> screwed up), it doesn't put the branchname because it can't
On 01/18/2013 09:15 PM, Oleg Nesterov wrote:
> On 01/17, Preeti U Murthy wrote:
>>
>> On 01/16/2013 05:32 PM, Ivo Sieben wrote:
>>>
>>> I don't have a problem that there is a context switch to the high
>>> priority process: it has a higher priority, so it probably is more
>>> important.
>>> My
Hi Stephane,
On Sat, 19 Jan 2013 00:13:59 +0100, Stephane Eranian wrote:
> This patch adds a new printing mode for perf stat.
> It allows internval printing. That means perf stat
> can now print event deltas at regular time interval.
> This is useful to detect phases in programs.
>
> The -I
On 01/20/2013 12:09 PM, Mike Galbraith wrote:
> On Thu, 2013-01-17 at 13:55 +0800, Michael Wang wrote:
>> Hi, Mike
>>
>> I've send out the v2, which I suppose it will fix the below BUG and
>> perform better, please do let me know if it still cause issues on your
>> arm7 machine.
>
> s/arm7/aim7
>
> If that's the case:
>
> Acked-by: Rafael J. Wysocki
>
> but please say something like this in the changelog:
>
> "The result returned by acpiphp_get_num_slots() is meaningless, because
> the bridge the slots are under may be added after this function has been
> called, so drop
Hi Alex,
Thank you very much for running the below benchmark on
blocked_load+runnable_load:) Just a few queries.
How did you do the wake up balancing? Did you iterate over the L3
package looking for an idle cpu? Or did you just query the L2 package
for an idle cpu?
I think when you are using
On Sun, Jan 20, 2013 at 6:30 PM, Al Viro wrote:
>
> Neither do I, to be honest. It might be saving us a few cycles on
> some architectures, but I'd like to see examples of that. amd64
> doesn't seem to be one, at least...
I think that the inlining of the body should make it basically be
pretty
On Sun, Jan 20, 2013 at 3:00 PM, Rafael J. Wysocki wrote:
> On Thursday, January 17, 2013 11:53:19 PM Yinghai Lu wrote:
>> From: Tang Chen
>>
>> acpi_install_notify_handler() could fail. So check the exit status
>> and give a better debug info.
>>
>> Signed-off-by: Tang Chen
>> Signed-off-by:
On Sun, Jan 20, 2013 at 2:55 PM, Rafael J. Wysocki wrote:
> On Thursday, January 17, 2013 11:53:18 PM Yinghai Lu wrote:
>> We have partial hot-add support in acpiphp driver, and it is confusing.
>>
>> Move host bridge hot-add support to pci_root.c, and keep acpiphp simple,
>> also add hot-remove
On Sun, Jan 20, 2013 at 05:40:28PM -0800, Linus Torvalds wrote:
> On Sun, Jan 20, 2013 at 5:22 PM, Al Viro wrote:
> >
> > Anyway, that's a separate story - semctl(2) is going to be ugly, no matter
> > what we do, but the rest of those guys doesn't have to. How about the
> > following (completely
2013/1/19, Cong Ding :
> On Sat, Jan 19, 2013 at 11:17:14AM +0900, Namjae Jeon wrote:
>> From: Namjae Jeon
>>
>> This patch implements extent caching in case of file reading.
>> While reading a file, currently, UDF reads metadata serially
>> which takes a lot of time depending on the number of
1 - 100 of 608 matches
Mail list logo
