> -Original Message-
> From: Guenter Roeck [mailto:groe...@gmail.com] On Behalf Of Guenter
> Roeck
> Sent: Tuesday, December 17, 2013 7:40 PM
> To: Rajat Jain
> Cc: Bjorn Helgaas; Rajat Jain; Kenji Kaneshige; Alex Williamson; Yijing
> Wang; linux-...@vger.kernel.org;
Hi:
It seems that the card-reader was removed during suspend or resume, is
that right? or did you removed by hand?
I want to know with Thomas' patch, after resume, is the card-reader and
card-reader driver still exist?
if not exist, I also want to know which function called first,
Hi Andi,
On Mon, 16 Dec 2013 07:45:27 -0800, Andi Kleen wrote:
>> My hope has always been that we can make a userspace function graph tracer
>> out of its dumps. And I think we can, I'm pretty sure that would be a useful
>> tool.
>
> I wrote one, based on the __fentry__, like the kernel:
>
On Tue, 2013-12-17 at 16:01 -0500, Mark Hounschell wrote:
> I hope it is OK to ask a newbie question here. I'm trying to better
> understand the boot process. I can't seem to find where in the kernel
> sources the cpu_active_mask (defined in include/linux/cpumask.h) gets
> populated. I can see
Because the local variable of st_int_ioctl function, such as long ltmp
be assigned by arg.
I think we should limit the parameter arg of st_int_ioctl function to
the range of 24-bit signed integer.
Yong Jianxu, please update your patch.
2013/12/18 "Kai Mäkisara (Kolumbus)" :
> On 17.12.2013, at
Hi Jens,
Today's linux-next merge of the block tree got a conflict in
fs/f2fs/data.c between commits from the f2fs tree and commits 2c30c71bd653
("block: Convert various code to bio_for_each_segment()") and
4f024f3797c4 ("block: Abstract out bvec iterator") from the block tree.
I fixed it up (I
On 12/18/2013 05:38 AM, Michael Ellerman wrote:
> On Fri, 2013-12-13 at 13:50 +0530, Anshuman Khandual wrote:
>> On 12/09/2013 11:51 AM, Michael Ellerman wrote:
>>>
>>> As I said in my comments on version 3 which you ignored:
>>>
>>> I think it would be clearer if we actually checked for the
Dear RT Folks,
I'm pleased to announce the 3.4.74-rt92 stable release.
This release is just an update to the new stable 3.4.74 version
and no RT specific changes have been made.
You can get this release via the git tree at:
Dear RT Folks,
I'm pleased to announce the 3.8.13.14-rt27 stable release.
This release is just an update to the new stable 3.8.13.14 version
and no RT specific changes have been made.
You can get this release via the git tree at:
Dear RT Folks,
I'm pleased to announce the 3.10.24-rt22 stable release.
This release is just an update to the new stable 3.10.24 version
and no RT specific changes have been made.
You can get this release via the git tree at:
On Tue, 2013-07-09 at 16:03 +0800, Tiejun Chen wrote:
> In commit 96f013f, "powerpc/kexec: Add kexec "hold" support for Book3e
> processors", requires that GPR4 survive the "hold" process, for IBM Blue
> Gene/Q with with some very strange firmware. But for FSL Book3E, r4 = 1
> to indicate that the
On Tue, 2013-07-09 at 16:03 +0800, Tiejun Chen wrote:
> Book3e is always aligned 1GB to create TLB so we should
> use (KERNELBASE - MEMORY_START) as VIRT_PHYS_OFFSET to
> get __pa/__va properly while boot kdump.
What if MEMORY_START - PHYSICAL_START >= 1 GiB?
What about the comment that says we
This driver adds support for elan i2c/smbus touchpad found on some laptops PC
Signed-off-by: Duson Lin
---
drivers/input/mouse/Kconfig| 10 +
drivers/input/mouse/Makefile |1 +
drivers/input/mouse/elan_i2c.c | 890
3 files changed, 901
On Tue, 2013-07-09 at 16:03 +0800, Tiejun Chen wrote:
> ppc64 kexec mechanism has a different implementation with ppc32.
>
> Signed-off-by: Tiejun Chen
Could you describe the relevant differences?
-Scott
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body
On Tue, 2013-07-09 at 16:03 +0800, Tiejun Chen wrote:
> We need to introduce a flag to indicate we're already running
> a kexec kernel then we can go proper path. For example, We
> shouldn't access spin_table from the bootloader to up any secondary
> cpu for kexec kernel, and kexec kernel already
On Wed, Dec 18, 2013 at 03:20:58AM +, Rajat Jain wrote:
>
>
> > -Original Message-
> > From: Bjorn Helgaas [mailto:bhelg...@google.com]
> >
> > [+cc ying...@kernel.org (seems to be Yinghai's preferred email]
> >
> > On Tue, Dec 17, 2013 at 12:06:05PM -0800, Rajat Jain wrote:
> > >
On Tue, 2013-07-09 at 16:03 +0800, Tiejun Chen wrote:
> book3e have no real MMU mode so we have to create a 1:1 TLB
> mapping to make sure we can access the real physical address.
> And correct something to support this pseudo real mode on book3e.
>
> Signed-off-by: Tiejun Chen
Why do we need
Hi Mark,
> -Original Message-
> From: Mark Brown [mailto:broo...@kernel.org]
> Sent: Tuesday, December 17, 2013 8:38 PM
> To: Yang, Wenyou
> Cc: lgirdw...@gmail.com; linux-kernel@vger.kernel.org;
> grant.lik...@linaro.org; rob.herr...@calxeda.com; linux-
> d...@vger.kernel.org;
Hi Mark,
Thank you very much.
> -Original Message-
> From: Mark Brown [mailto:broo...@kernel.org]
> Sent: Tuesday, December 17, 2013 9:07 PM
> To: Yang, Wenyou
> Cc: lgirdw...@gmail.com; linux-kernel@vger.kernel.org;
> grant.lik...@linaro.org; rob.herr...@calxeda.com; linux-
>
On Tue, 2013-07-09 at 16:03 +0800, Tiejun Chen wrote:
> We need to active KEXEC for book3e and bypass or convert non-book3e stuff
> in kexec coverage.
>
> Signed-off-by: Tiejun Chen
> ---
> arch/powerpc/Kconfig |2 +-
> arch/powerpc/kernel/machine_kexec_64.c | 148
>
On 12/17/2013 10:23 PM, Wanpeng Li wrote:
- mlock_vma_page(page); /* no-op if already mlocked */
- if (page == check_page)
+ if (page != check_page && trylock_page(page)) {
+ mlock_vma_page(page);
On Tue, 2013-07-09 at 16:03 +0800, Tiejun Chen wrote:
> book3e is different with book3s since 3s includes the exception
> vectors code in head_64.S as it relies on absolute addressing
> which is only possible within this compilation unit. So we have
> to get that label address with got.
>
> And
Hi Mark,
> -Original Message-
> From: Mark Brown [mailto:broo...@kernel.org]
> Sent: Tuesday, December 17, 2013 8:48 PM
> To: Yang, Wenyou
> Cc: lgirdw...@gmail.com; linux-kernel@vger.kernel.org;
> grant.lik...@linaro.org; rob.herr...@calxeda.com; linux-
> d...@vger.kernel.org;
> -Original Message-
> From: Bjorn Helgaas [mailto:bhelg...@google.com]
>
> [+cc ying...@kernel.org (seems to be Yinghai's preferred email]
>
> On Tue, Dec 17, 2013 at 12:06:05PM -0800, Rajat Jain wrote:
> > We need future link up events for hot-add, thus don't disable the link
> >
Hi Tejun,
I suppose there is a fault in the patch of https://lkml.org/lkml/2013/1/16/546.
I know you made a new patch for latest kernel which don't move the entry
between pending and running list that remove the code I mentioned, but our
kernel is based on v3.8.13 that has the code.
In my
This patch fixes wrong curly bracket position reporting when function
declarations have only one void argument.
Missing error (ERROR: space required before the open brace '{') on this
situation :
int foo(void){
...
}
Signed-off-by: Jean-Baptiste Theou
---
scripts/checkpatch.pl | 2 +-
On Tue, 2013-07-09 at 16:03 +0800, Tiejun Chen wrote:
> We can rename 'interrupt_end_book3e' with '__end_interrupts' then
> book3s/book3e can share this unique label to make sure we can use
> this conveniently.
>
> Signed-off-by: Tiejun Chen
What users of this do you plan to share between
This patch fixes wrong curly bracket position reporting when function
declarations have only one void argument.
Missing error (ERROR: space required before the open brace '{') on this
situation :
int foo(void){
...
}
Signed-off-by: Jean-Baptiste Theou
---
scripts/checkpatch.pl | 2 +-
> -Original Message-
> From: netdev-ow...@vger.kernel.org [mailto:netdev-
> ow...@vger.kernel.org] On Behalf Of Stephen Rothwell
> Sent: Tuesday, December 17, 2013 2:52 PM
> To: David Miller; net...@vger.kernel.org
> Cc: linux-n...@vger.kernel.org; linux-kernel@vger.kernel.org;
Hi all,
Today's linux-next merge of the drm-intel tree got a conflict in
drivers/gpu/drm/i915/intel_pm.c between commit fec8cba306f9 ("drm/i915:
use crtc_htotal in watermark calculations to match fastboot v2") from
Linus' tree and commit 96f90c5421aa ("drm/i915: Move ILK/SNB/IVB over to
the HSW
On Wed, 2013-10-23 at 17:31 +0800, Tiejun Chen wrote:
> 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 | 22 +++---
> 1 file changed, 19
On Wed, 2013-10-23 at 17:31 +0800, Tiejun Chen wrote:
> In lazy EE magic, we may have a lazy interrupt occured while
> entering kgdb, but we really don't want to replay that interrupt
> for kgdb, so we have to clear the PACA_IRQ_HARD_DIS force to
> make sure we can exit directly from this debug
The patch should be sent to jffs2 mainling list, which is
linux-...@lists.infradead.org.
It's not needed to cc stable mailing list. Actually I think it's
better not to.
On 2013/12/18 10:14, Wang Nan wrote:
> From: Wang Guoli
>
> If jffs2_new_inode() succeeds, it returns with f->sem held, and
>
From: David Miller
Date: Tue, 17 Dec 2013 21:21:45 -0500 (EST)
> I'll try to fix this up, thanks for the report.
Here's what I committed, thanks again Stephen:
[PATCH] lib: Add missing arch generic-y entries for asm-generic/hash.h
Reported-by: Stephen Rothwell
From: Stephen Rothwell
Date: Wed, 18 Dec 2013 12:56:43 +1100
> After merging the net-next tree, today's linux-next build (powerpc
> ppc64_defconfig) failed like this:
>
> In file included from include/linux/hashtable.h:12:0,
> from include/linux/elevator.h:5,
>
Hi Jeff,
On Tue, 17 Dec 2013 17:56:09 -0800 Jeff Kirsher
wrote:
>
> Your fix is fine, what I have in my tree is the following, so if you
> want to modify your change so that the resultant code looks like this:
>
> struct rtnl_link_stats64 *vsi_stats =
> i40e_get_vsi_stats_struct(vsi);
From: Wang Guoli
If jffs2_new_inode() succeeds, it returns with f->sem held, and
the caller is responsible for releasing the lock. If it fails,
it still returns with the lock held, but the caller won't release
the lock, which will lead to deadlock.
Fix it by releasing the lock in
On Tue, Dec 17, 2013 at 6:05 PM, Jason Wang wrote:
> On 12/17/2013 05:13 PM, Zhi Yong Wu wrote:
>> On Tue, Dec 17, 2013 at 4:49 PM, Jason Wang wrote:
>>> > On 12/17/2013 03:26 PM, Zhi Yong Wu wrote:
>> From: Zhi Yong Wu
>>
>> The flow cache is an extremely broken concept, and it
On 12/17/13 at 04:58pm, Borislav Petkov wrote:
> On Tue, Dec 17, 2013 at 02:34:36PM +0800, Dave Young wrote:
> > They are moved to efi.c efi_setup_init(), I'm not sure if I expained
> > clear enough, in current code parse_efi_setup only accept one argument
> > phys_addr so I will mapping it with
From: Micky Ching
rtl8402 is much like rtl8411, so just add it to rtl8411.c
Signed-off-by: Micky Ching
---
drivers/mfd/rtl8411.c | 44
drivers/mfd/rtsx_pcr.c |5 +
drivers/mfd/rtsx_pcr.h |1 +
3 files changed, 46 insertions(+), 4
On 12/18/2013 06:51 AM, Frederic Weisbecker wrote:
> So this is what this series brings, more details following:
>
> * Some code, naming and whitespace cleanups
>
> * Allow all CPUs outside the nohz_full range to handle the timekeeping
> duty, not just CPU 0. Balancing the timekeeping duty
On 13-12-16 05:17 AM, Linus Walleij wrote:
On Sat, Dec 14, 2013 at 2:16 AM, Sherman Yin wrote:
+- bias-pull-up:Integer. Pull up strength in Ohm:
+ 1: 1.2 kOhm
+ 2: 1.8 kOhm
+
From: Micky Ching
add set pull control macro to reduce code for setting pull control, and
use a common init function to reduce code for rtl8411.c. So this patch
is used to just simplify code.
Signed-off-by: Micky Ching
---
drivers/mfd/rtl8411.c | 53
From: Micky Ching
we add a macro to simplify setting pull control, and use a common init
function to init the common params for 8411-like chips. at last we add
support for rtl8402 chip.
Micky Ching (2):
mfd: rtsx: add set pull control macro and simplify rtl8411
mfd: rtsx: add support for
On Wed, 2013-12-18 at 12:46 +1100, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the net-next tree got a conflict in
> drivers/net/ethernet/intel/i40e/i40e_main.c between commit 3c325ced6aef
> ("i40e: fix null dereference") from Linus' tree and commit bc7d338fbb3f
> ("i40e:
break any architecture other than
x86 :-(
I have used the net-next tree from next-20131217 for today.
--
Cheers,
Stephen Rothwells...@canb.auug.org.au
pgp7AF7mbe0_6.pgp
Description: PGP signature
On Wed, Dec 18, 2013 at 3:04 AM, Gerd Hoffmann wrote:
> DRM driver for (virtual) vga cards using the bochs dispi
> interface, such as the qemu standard vga (qemu -vga std).
>
> Don't bother supporting anything but 32bpp for now, even
> though the virtual hardware is able to do that.
Hi Gerd,
Hi all,
Today's linux-next merge of the net-next tree got a conflict in
drivers/net/ethernet/intel/i40e/i40e_main.c between commit 3c325ced6aef
("i40e: fix null dereference") from Linus' tree and commit bc7d338fbb3f
("i40e: reinit flow for the main VSI") from the net-next tree.
I fixed it up
On 2013/12/17 17:31, Li Wang wrote:
> This extension is just add-on extension. The original debugging
> capability is still there, and more flexible debugging is now allowed.
>
but you intent is to let applications use this interface for
non-debugging purpose.
--
To unsubscribe from this list:
I've been using an external monitor with my retina Macbook and sometimes I see
the warning below. I think it happens when I unplug the monitor from the
thunderbolt port (I use a converter to VGA).
[10906.327043] [ cut here ]
[10906.327059] WARNING: CPU: 3 PID: 643 at
Both 'drop_caches' and 'vfs_cache_pressure' do coarse granularity
control. Sometimes these do not help much for those performance
sensitive applications. General and simple algorithms are good
regarding its application independence and working for normal
situations. However, since applications
Hi Thierry,
On 12/17/2013 06:30 PM, Thierry Reding wrote:
On Fri, Dec 13, 2013 at 02:41:48PM +0800, Bo Shen wrote:
This patch series add Atmel PWM controller driver support.
Changes in v9:
- Address the comments from Thierry Reding
Hi,
I've pushed a slightly modified version of this
When running with the latest kernel, we get the following kmemleak message:
unreferenced object 0x8800c2a36100 (size 256):
comm "modprobe", pid 629, jiffies 4294676002 (age 1531.115s)
hex dump (first 32 bytes):
00 00 00 00 ad 4e ad de ff ff ff ff 00 00 00 00 .N..
ff ff
On 12/17/2013 03:28 PM, Dan Carpenter wrote:
On Tue, Dec 17, 2013 at 10:36:58AM +0800, micky_ch...@realsil.com.cn wrote:
diff --git a/drivers/mfd/rtsx_pcr.h b/drivers/mfd/rtsx_pcr.h
index 947e79b..26b52ec 100644
--- a/drivers/mfd/rtsx_pcr.h
+++ b/drivers/mfd/rtsx_pcr.h
@@ -63,4 +63,12 @@ static
On Tue, Dec 17, 2013 at 5:04 PM, John Stultz wrote:
> RT_MUTEXES can be configured out of the kernel, causing compile
> problems with ION.
>
> To quote Colin:
> "rt_mutexes were added with the deferred freeing feature. Heaps need
> to return zeroed memory to userspace, but zeroing the memory on
RT_MUTEXES can be configured out of the kernel, causing compile
problems with ION.
To quote Colin:
"rt_mutexes were added with the deferred freeing feature. Heaps need
to return zeroed memory to userspace, but zeroing the memory on every
allocation was causing performance issues. We added a
directory
> #include
>^
>
> Caused by commit a99493647c1a ("Merge branch 'acpi-cleanup' into
> linux-next") which incorrectly reintroduced the include of
> linux/acpi_io.h.
>
> I have used the pm tree from next-20131217 for today.
Sorry for the
On Tuesday, December 17, 2013 08:00:55 PM Josh Boyer wrote:
> On Tue, Dec 17, 2013 at 7:52 PM, Rafael J. Wysocki wrote:
> > On Tuesday, December 17, 2013 11:04:46 AM Josh Boyer wrote:
> >> On Tue, Dec 17, 2013 at 11:03 AM, Josh Boyer
> >> wrote:
> >> > On Fri, May 25, 2012 at 3:13 PM, Rafael J.
[+cc ying...@kernel.org (seems to be Yinghai's preferred email]
On Tue, Dec 17, 2013 at 12:06:05PM -0800, Rajat Jain wrote:
> We need future link up events for hot-add, thus don't disable
> the link permanently during device removal. Also, remove the static
> functions that are now left unused.
there is an overflow in the code :
cyz_polling_cycle = (arg * HZ) / 1000,
the multiplicator arg comes from user, so it may be an overflow if
arg is a big number. And the value of cyc_polling_cycle will be
wrong when it is used next time.
Reported-by: Qixue Xiao
Suggested-by: Yongjian Xu
On Tue, Dec 17, 2013 at 7:52 PM, Rafael J. Wysocki wrote:
> On Tuesday, December 17, 2013 11:04:46 AM Josh Boyer wrote:
>> On Tue, Dec 17, 2013 at 11:03 AM, Josh Boyer
>> wrote:
>> > On Fri, May 25, 2012 at 3:13 PM, Rafael J. Wysocki wrote:
>> >> On Friday, May 25, 2012, Josh Boyer wrote:
>>
eanup' into
linux-next") which incorrectly reintroduced the include of
linux/acpi_io.h.
I have used the pm tree from next-20131217 for today.
--
Cheers,
Stephen Rothwells...@canb.auug.org.au
pgpS82htQHd4h.pgp
Description: PGP signature
On Tuesday, December 17, 2013 12:25:18 PM Josh Triplett wrote:
> On Tue, Dec 17, 2013 at 05:35:46PM +, Moore, Robert wrote:
> > I'm not sure what version of ACPICA you are looking at, but in the master
> > git tree for ACPICA, the file accommon.h includes "acutils.h".
>
> This is the version
Hi Kamil,
> Hi Anton,
>
> > From: Anton Tikhomirov [mailto:av.tikhomi...@samsung.com]
> > Sent: Tuesday, December 10, 2013 3:43 AM
> >
> > Hi Kamil,
> >
> > Same USB2.0 PHY may be used by several HCDs, for example EHCI and
> OHCI.
> > Consider the situation, when EHCI stops using the PHY and
On Wed, Dec 18, 2013 at 10:42 AM, Linus Torvalds
wrote:
> On Tue, Dec 17, 2013 at 4:33 PM, Dave Airlie wrote:
>>
>> are available in the git repository at:
>>
>> git://people.freedesktop.org/~airlied/linux
>
> Nope.
>
> I assume you meant the 'drm-fixes' branch, but you didn't actually
> *say*
On Tuesday, December 17, 2013 07:50:42 AM Tejun Heo wrote:
> Hello,
>
> Rafael, if you're okay with the workaround, I'll route it through
> libata/for-3.13-fixes.
>
> Thanks.
> --- 8< ---
> Freezable kthreads and workqueues are fundamentally problematic in
> that they effectively
On 12/17/2013 09:00 PM, Vlastimil Babka wrote:
>
> I would prefer that too but patch 3 needs it again, so I left it as it is
> here.
> As for comment, here's a revised patch that adds it:
>
Thanks.
> --8<--
> From: Vlastimil Babka
> Date: Fri, 13 Dec 2013 14:25:21 +0100
> Subject:
On Tue, Dec 17, 2013 at 4:33 PM, Dave Airlie wrote:
>
> are available in the git repository at:
>
> git://people.freedesktop.org/~airlied/linux
Nope.
I assume you meant the 'drm-fixes' branch, but you didn't actually
*say* that, and when I pull it I don't get the same diffstat you
claim, so
On Tuesday, December 17, 2013 11:04:46 AM Josh Boyer wrote:
> On Tue, Dec 17, 2013 at 11:03 AM, Josh Boyer
> wrote:
> > On Fri, May 25, 2012 at 3:13 PM, Rafael J. Wysocki wrote:
> >> On Friday, May 25, 2012, Josh Boyer wrote:
> >>> On Fri, Feb 17, 2012 at 3:59 PM, Rafael J. Wysocki wrote:
>
On Mon, Dec 16, 2013 at 07:56:04AM -0500, Tejun Heo wrote:
> On Mon, Dec 16, 2013 at 07:51:24AM -0500, Tejun Heo wrote:
> > On Mon, Dec 16, 2013 at 02:56:52PM +1100, Dave Chinner wrote:
> > > > What are you suggesting? Implementing separate warm and hot unplug
> > > > paths? That makes no sense
Ingo,
Please queue in x86/ras branch for next merge window.
Thanks
-Tony
The following changes since commit 319e2e3f63c348a9b66db4667efa73178e18b17d:
Linux 3.13-rc4 (2013-12-15 12:31:33 -0800)
are available in the git repository at:
Definitely seems quieter this week,
radeon, intel, intel broadwell, vmwgfx, ttm, armada, and a couple of core
fixes, one revert in radeon
most of these are either going to stable or fixes for things introduced in
the merge window,
Dave.
The following changes since commit
On Mon, Dec 16, 2013 at 09:34:59AM +0100, Alexander Gordeev wrote:
> Device drivers can use this interface to obtain maximum number
> of MSI interrupts the device supports and use that number i.e.
> in a following call to pci_enable_msi_block() interface.
>
> Signed-off-by: Alexander Gordeev
>
On Mon, Dec 16, 2013 at 09:35:02AM +0100, Alexander Gordeev wrote:
> Currently many device drivers need contiguously call functions
> pci_enable_msix() for MSI-X or pci_enable_msi_block() for MSI
> in a loop until success or failure. This update generalizes
> this usage pattern and introduces
On Tuesday, December 17, 2013 07:34:57 AM Tejun Heo wrote:
> Hello, Rafael.
>
> On Tue, Dec 17, 2013 at 03:34:00AM +0100, Rafael J. Wysocki wrote:
> > No, it isn't. [I guess it was originally, but it has not been the case
> > for a very long time.] It is about getting user space interactions
Per commit "net_dma: mark broken" net_dma is no longer used and there is no
plan to fix it.
Cc: Dave Jiang
Cc: Vinod Koul
Cc: David Whipple
Cc: Alexander Duyck
Signed-off-by: Dan Williams
---
Documentation/ABI/removed/net_dma |8 +
Documentation/networking/ip-sysctl.txt |6 -
Record actively mapped pages and provide an api for other parts of the kernel
to check that a given page is dma inactive before taking action. Verified to
catch the misuse of the dma-api in the NET_DMA implementation.
Cc: Vinod Koul
Cc: Andrew Morton
Signed-off-by: Dan Williams
---
NET_DMA violates the expectation of the dma-mapping api by allowing the
cpu to touch receive buffer memory while dma is active. If this
activity triggers a copy-on-write event the application may see missing
data as the dma completes to the old mapping.
[PATCH 1/3] net_dma: mark broken
Detail
net_dma can cause data to be copied to a stale mapping if a
copy-on-write fault occurs during dma. The application sees missing
data.
The following trace is triggered by modifying the kernel to WARN if it
ever triggers copy-on-write on a page that is undergoing dma:
WARNING: CPU: 24 PID: 2529
Chris Wilson writes:
> Ok, so as no vgaarb_clients have yet been registered and so the call to
> grab the IO resource does not actually disable VGA IO routing to the
> nvidia card.
Yikes! This explains a lot.
> If you care to update the changelog to explain the problem is that
> vgaarb is
Change log from v1:
o fix NOSPC error handling
>From b8511a74fe98b67247a9feeed58441e8f5ffd705 Mon Sep 17 00:00:00 2001
From: Jaegeuk Kim
Date: Mon, 16 Dec 2013 19:04:05 +0900
Subject: [PATCH] f2fs: introduce a new direct_IO write path
Cc: linux-fsde...@vger.kernel.org,
On Tuesday, December 17, 2013 07:36:43 AM Tejun Heo wrote:
> Hello, Rafael.
>
> On Tue, Dec 17, 2013 at 03:38:05AM +0100, Rafael J. Wysocki wrote:
> > On Friday, December 13, 2013 03:40:34 PM Tejun Heo wrote:
> > > Hello,
> > >
> > > So, this is the laughable workaround that I came up with.
On Fri, 2013-12-13 at 13:50 +0530, Anshuman Khandual wrote:
> On 12/09/2013 11:51 AM, Michael Ellerman wrote:
> >
> > As I said in my comments on version 3 which you ignored:
> >
> > I think it would be clearer if we actually checked for the
> > possibilities we
> > allow and let
On Tue, Dec 17, 2013 at 03:43:40PM -0800, Mike Turquette wrote:
> Quoting Guenter Roeck (2013-12-14 08:33:27)
> > On 10/02/2013 04:17 PM, Mike Turquette wrote:
> > > Quoting Sören Brinkmann (2013-10-02 10:20:38)
> > >> Hi Mike,
> > >>
> > >> could you please comment on this/apply it to clk-next?
>
On Wed 2013-12-18 10:31:52, Dave Chinner wrote:
> On Wed, Dec 18, 2013 at 12:08:43AM +0100, Pavel Machek wrote:
> > Hi!
> >
> > > >>> Did this patch ever wind up going anywhere? Fedora has it sitting in
> > > >>> our tree with a comment that says "rebase" and I don't see it in the
> > > >>>
I hate to be that guy and keep bugging you guys. Can I get an
acknowledgment of the original patch? It fixed a very real issue for
fscache users that occurs semi-frequently under moderate concurrency.
- M
On Mon, Dec 16, 2013 at 12:20 PM, Milosz Tanski wrote:
> Hey guys it looks like this patch
Hi Jonas,
On Tue, Dec 17, 2013 at 04:38:34PM +0100, Jonas Jensen wrote:
> Add a generic (dtsi) include file for MOXA ART SoCs.
>
> Also add a file for UC-7112-LX.
>
> Signed-off-by: Jonas Jensen
> ---
> Documentation/devicetree/bindings/arm/moxart.txt | 12 ++
> arch/arm/boot/dts/Makefile
The latest maintenance release Git v1.8.5.2 is now available at
the usual places.
The release tarballs are found at:
http://code.google.com/p/git-core/downloads/list
and their SHA-1 checksums are:
3a09d6d5d4e31c702f17e664a527b4c2f6e84faf git-1.8.5.2.tar.gz
Hello,
Following the fix I submitted a few weeks ago, here is a set of
patches that adds USB support for the Ingenic JZ4740 MIPS SoC.
The JZ4740 is found in the Ben NanoNote handheld computer which is
built by the Qi-Hardware community.
Even though Ben NanoNote is already supported in the
Add support for Ingenic JZ4740 USB Device Controller through a
specific musb glue layer.
The platform data already available in tree for that USB Device
Controller was previously used by an out-of-tree USB gadget driver
which was not relying on the musb driver and was written by Ingenic
and the
JZ4740 USB Device Controller is not OTG compatible and does not have
DEVCTL register in silicon.
During ethernet-over-usb transactions, on reset, musb driver tries to
read from DEVCTL and consequently sets device as host (A-Device)
instead of peripheral (B-Device), which makes it a composite
Add defconfig for the Ben NanoNote handheld computer which is built
around QI_LB60 board and Ingenic JZ4740 MIPS SoC.
Signed-off-by: Apelete Seketeli
---
arch/mips/configs/qi_lb60_defconfig | 188 +++
1 file changed, 188 insertions(+)
create mode 100644
On Tue, Dec 17, 2013 at 11:51:23PM +0100, Frederic Weisbecker wrote:
> Now that we have an API to determine if a CPU is allowed to handle
> timekeeping duty, use it now on timekeeper selection time for clarity.
>
> Signed-off-by: Frederic Weisbecker
> Cc: Thomas Gleixner
> Cc: Ingo Molnar
>
Hello Dear,
I am Mr.Emmanuel Broni. the head of business management Department of
Ghana National Petroleum Corporation ( G.N.P.C ) and responsible for the
award of contract relating to oil business.
I want us to enter into confidential and binding business agreement where
by I will be
On Tue, Dec 17, 2013 at 11:51:25PM +0100, Frederic Weisbecker wrote:
> When a full dynticks CPU wakes up while the whole rest of the system
> is idle, we need to wake up the CPU in charge of the timekeeping duty
> handling.
>
> As of today, the CPU that maintains this duty is CPU 0 when
>
On Tue, Dec 17, 2013 at 11:51:26PM +0100, Frederic Weisbecker wrote:
> We need the default timekeeping CPU to be able to receive IPIs sent
> from full dynticks CPUs when they wake up from full system idle state.
>
> Therefore we need an entrypoint from the scheduler IPI so that the
> need to poll
On Tue, Dec 17, 2013 at 03:34:54PM -0800, Paul E. McKenney wrote:
> On Tue, Dec 17, 2013 at 11:51:30PM +0100, Frederic Weisbecker wrote:
> > When a full dynticks CPU wakes up from sysidle state, which means that
> > all full dynticks CPUs were previously sleeping, it's possible that
> > all the
On Tue, Dec 17, 2013 at 11:51:28PM +0100, Frederic Weisbecker wrote:
> When all full dynticks CPUs are idle, as detected by RCU's sysidle
> detection, there is no need to keep the timekeeping CPU's tick alive
> anymore. So lets shut it down when we meet this favourable state. The
> timekeeper will
On Tue, Dec 17, 2013 at 03:27:14PM -0800, Paul E. McKenney wrote:
> On Tue, Dec 17, 2013 at 11:51:22PM +0100, Frederic Weisbecker wrote:
> > The purpose of the full system idle detection is to notify the CPU
> > handling the timekeeping when the rest of the system is idle so that it
> > can sleep
Quoting Guenter Roeck (2013-12-14 08:33:27)
> On 10/02/2013 04:17 PM, Mike Turquette wrote:
> > Quoting Sören Brinkmann (2013-10-02 10:20:38)
> >> Hi Mike,
> >>
> >> could you please comment on this/apply it to clk-next?
> >
> > It looks good and is in the queue. Will show up in clk-next in a few
101 - 200 of 1784 matches
Mail list logo
