Hi Boris,
BTW, this series has a few conflicts with other things I have queued, so
you'll need to refresh.
On Thu, Dec 04, 2014 at 11:30:12PM +0100, Boris Brezillon wrote:
> The NAND and NFC (NAND Flash Controller) were linked together with a
> parent <-> child relationship.
>
> This model has
Hi Chen
On 02/01/2015 03:42 PM, Chen Gang S wrote:
st_rc_suspend() and st_rc_resume() depend on CONFIG_PM_SLEEP finally, so
they need CONFIG_PM_SLEEP instead of CONFIG_PM, or they will cause build
warning (with allmodconfig under xtensa):
CC [M] drivers/media/pci/smipcie/smipcie.o
On Wed, Jan 28, 2015 at 06:09:52PM +0100, Christoph Hellwig wrote:
> On Mon, Jan 26, 2015 at 10:16:53PM -0800, Omar Sandoval wrote:
> > get_acl gets a reference which we must release in the error cases.
> >
> > Signed-off-by: Omar Sandoval
>
> Looks good, but at this point goto-based unwinding
On Mon, Feb 02, 2015 at 10:30:09AM +0800, Mark yao wrote:
> On 2015年02月02日 10:07, Daniel Kurtz wrote:
> >Hi Mark, Heiko,
> >
> >On Sat, Jan 31, 2015 at 4:41 PM, Mark Yao wrote:
> >>Vop standby will take effect end of current frame,
> >>if dsp_hold_valid_irq happen, it means vop standby complete.
On POWER, storage caching is usually configured via the MMU - attributes
such as cache-inhibited are stored in the TLB and the hashed page table.
This makes correctly performing cache inhibited IO accesses awkward when
the MMU is turned off (real mode). Some CPU models provide special
registers
The dependence of VGA_CONSOLE is complicated.
We need clean up.
Signed-off-by: Yoshinori Sato
---
arch/alpha/Kconfig| 1 +
arch/arc/Kconfig | 1 +
arch/arm/Kconfig | 1 +
arch/c6x/Kconfig | 1 +
arch/hexagon/Kconfig | 1 +
In the source file fs/fcntl.c and also in the fcntl() man page one
can see that the FD_CLOEXEC flag can be manipulated via F_GETFD and
F_SETFD. Update the comment in accordingly.
Signed-off-by: Bart Van Assche
Cc: David Miller
Cc: Stephen Rothwell
---
include/uapi/asm-generic/fcntl.h | 2 +-
Hi Thomas,
Could you please also merge this patch? Since you have merged this patch
"x86, boot: Skip relocs when load address unchanged [commit f285f4a21]",
and this issue was raised because it broke kexec/kdump, then I posted
these 2 patches. Without this patch makedumpfile will be broken when
On Mon, 2015-02-02 at 08:24 +0100, Stefan Richter wrote:
> On Feb 01 Joe Perches wrote:
> > On Sun, 2015-02-01 at 21:30 +0100, Stefan Richter wrote:
> > > On Feb 01 Joe Perches wrote:
> > > > On Sun, 2015-02-01 at 20:59 +0100, Stefan Richter wrote:
> > > > > > ERROR: Please use 12 or more chars
On Mon, Feb 02, 2015 at 04:15:46PM +0900, Joonsoo Kim wrote:
> freepage with MIGRATE_CMA can be used only for MIGRATE_MOVABLE and
> they should not be expanded to other migratetype buddy list
> to protect them from unmovable/reclaimable allocation. Implementing
> these requirements in
On Sun, 2015-02-01 at 21:07 -0800, David Miller wrote:
> From: David Woodhouse
> Date: Sun, 01 Feb 2015 21:29:43 +
>
> > I really was looking for some way to push down something like an XFRM
> > state into the tun device and just say "shove them out here until I tell
> > you otherwise".
>
>
On Feb 01 Joe Perches wrote:
> On Sun, 2015-02-01 at 21:30 +0100, Stefan Richter wrote:
> > On Feb 01 Joe Perches wrote:
> > > On Sun, 2015-02-01 at 20:59 +0100, Stefan Richter wrote:
> > > > > ERROR: Please use 12 or more chars for the git commit ID like: 'Commit
> > > > > 01234567890ab ("commit
This is preparation step to use page allocator's anti fragmentation logic
in compaction. This patch just separates fallback freepage checking part
from fallback freepage management part. Therefore, there is no functional
change.
Signed-off-by: Joonsoo Kim
---
mm/page_alloc.c | 128
freepage with MIGRATE_CMA can be used only for MIGRATE_MOVABLE and
they should not be expanded to other migratetype buddy list
to protect them from unmovable/reclaimable allocation. Implementing
these requirements in __rmqueue_fallback(), that is, finding largest
possible block of freepage has bad
Compaction has anti fragmentation algorithm. It is that freepage
should be more than pageblock order to finish the compaction if we don't
find any freepage in requested migratetype buddy list. This is for
mitigating fragmentation, but, there is a lack of migratetype
consideration and it is too
From: Jassi Brar
Before polling we just need to see if the TXDONE_BY_POLL bit
is set in txdone_method. There may be another bit (method)
specified as well, like TXDONE_BY_ACK.
Signed-off-by: Jassi Brar
---
drivers/mailbox/mailbox.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
On Mon, Feb 2, 2015 at 3:04 PM, Jassi Brar wrote:
> On Mon, Dec 22, 2014 at 3:14 PM, Ley Foon Tan wrote:
> ...
>
>> diff --git a/drivers/mailbox/mailbox-altera.c
>> b/drivers/mailbox/mailbox-altera.c
>> new file mode 100644
>> index 000..8019795
>> --- /dev/null
>> +++
On Sat, Jan 31, 2015 at 11:58:03PM +0800, Zhang Yanfei wrote:
> At 2015/1/30 20:34, Joonsoo Kim wrote:
> > From: Joonsoo
> >
> > Compaction has anti fragmentation algorithm. It is that freepage
> > should be more than pageblock order to finish the compaction if we don't
> > find any freepage in
On Fri, Jan 30, 2015 at 03:43:27PM +0100, Vlastimil Babka wrote:
> On 01/30/2015 01:34 PM, Joonsoo Kim wrote:
> > From: Joonsoo
> >
> > Compaction has anti fragmentation algorithm. It is that freepage
> > should be more than pageblock order to finish the compaction if we don't
> > find any
On 02/02/2015 12:07 AM, Brian Norris wrote:
> On Sun, Feb 01, 2015 at 02:08:50AM +0100, Niklas Cassel wrote:
>> Calling mtd_device_parse_register with the same mtd_info
>> (e.g. registering several partitions on a single device)
>> would add the same reboot notifier twice, causing an
>> infinte
tree: git://git.kernel.org/pub/scm/linux/kernel/git/dgc/linux-xfs
xfs-ioctl-setattr-cleanup
head: 9b94fcc39822b450af823b3d8cbef6b53ce87ed9
commit: 23bd0735cfdf5322170a9ef48c7d47c2e6567ba8 [11/12] xfs: factor projid
hint checking out of xfs_ioctl_setattr
reproduce:
# apt-get install sparse
fs/xfs/xfs_ioctl.c:1146:1: sparse: symbol 'xfs_ioctl_setattr_check_projid' was
not declared. Should it be static?
Signed-off-by: Fengguang Wu
---
xfs_ioctl.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/xfs/xfs_ioctl.c b/fs/xfs/xfs_ioctl.c
index 1f186d2..1060513
On (02/02/15 15:18), Minchan Kim wrote:
> > a quick idea:
> > can we additionally move all bd flush and put work after
> > zram_reset_device(zram, true)
> > and, perhaps, replace ->bd_holders with something else?
> >
> > zram_reset_device() will not return until we have active IOs, pending IOs
On Mon, Dec 22, 2014 at 3:14 PM, Ley Foon Tan wrote:
...
> diff --git a/drivers/mailbox/mailbox-altera.c
> b/drivers/mailbox/mailbox-altera.c
> new file mode 100644
> index 000..8019795
> --- /dev/null
> +++ b/drivers/mailbox/mailbox-altera.c
> @@ -0,0 +1,385 @@
> +/*
> + * Copyright Altera
On Sat, Jan 31, 2015 at 08:38:10PM +0800, Zhang Yanfei wrote:
> At 2015/1/30 20:34, Joonsoo Kim wrote:
> > From: Joonsoo
> >
> > This is preparation step to use page allocator's anti fragmentation logic
> > in compaction. This patch just separates steal decision part from actual
> > steal
fs/xfs/xfs_ioctl.c:1102:1: sparse: symbol 'xfs_ioctl_setattr_check_extsize' was
not declared. Should it be static?
Signed-off-by: Fengguang Wu
---
xfs_ioctl.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/xfs/xfs_ioctl.c b/fs/xfs/xfs_ioctl.c
index 9f80853..992b669
tree: git://git.kernel.org/pub/scm/linux/kernel/git/dgc/linux-xfs
xfs-ioctl-setattr-cleanup
head: 9b94fcc39822b450af823b3d8cbef6b53ce87ed9
commit: d4388d3c0988ec00787ad1f8e63b5e2a6abef1dc [10/12] xfs: factor extsize
hint checking out of xfs_ioctl_setattr
reproduce:
# apt-get install sparse
On Fri, Jan 30, 2015 at 03:27:50PM +0100, Vlastimil Babka wrote:
> On 01/30/2015 01:34 PM, Joonsoo Kim wrote:
> > From: Joonsoo
> >
> > This is preparation step to use page allocator's anti fragmentation logic
> > in compaction. This patch just separates steal decision part from actual
> > steal
Hello!
On Feb 2, 2015, at 12:37 AM, Dave Chinner wrote:
> On Sun, Feb 01, 2015 at 10:59:54PM -0500, gr...@linuxhacker.ru wrote:
>> From: Oleg Drokin
>>
>> leaf_dealloc uses vzalloc as a fallback to kzalloc(GFP_NOFS), so
>> it clearly does not want any shrinker activity within the fs itself.
>>
This patch set enable audio support on sama5d4ek.
It depends the patch [1] (ASoC: atmel-pcm-dma: won't check direction
when configure dma)
[1] https://patchwork.kernel.org/patch/5759441/
Bo Shen (4):
ARM: at91: dt: sama5d4: add ssc nodes
ARM: at91: dt: sama5d4ek: enable ssc0
ARM: at91: dt:
Enable SSC0 node, which will be used for audio.
Signed-off-by: Bo Shen
---
arch/arm/boot/dts/at91-sama5d4ek.dts | 4
1 file changed, 4 insertions(+)
diff --git a/arch/arm/boot/dts/at91-sama5d4ek.dts
b/arch/arm/boot/dts/at91-sama5d4ek.dts
index 9198b71..32e9a9a 100644
---
Add SSC 0 and 1 nodes.
Signed-off-by: Bo Shen
---
arch/arm/boot/dts/sama5d4.dtsi | 70 ++
1 file changed, 70 insertions(+)
diff --git a/arch/arm/boot/dts/sama5d4.dtsi b/arch/arm/boot/dts/sama5d4.dtsi
index b94995d..0b3e5f4 100644
---
Enable audio support for sama5d4ek board.
Signed-off-by: Bo Shen
---
arch/arm/boot/dts/at91-sama5d4ek.dts | 20
1 file changed, 20 insertions(+)
diff --git a/arch/arm/boot/dts/at91-sama5d4ek.dts
b/arch/arm/boot/dts/at91-sama5d4ek.dts
index 7f47d92..0df5f1b 100644
---
Add wm8904 codec node and enable it.
Signed-off-by: Bo Shen
---
arch/arm/boot/dts/at91-sama5d4ek.dts | 7 +++
1 file changed, 7 insertions(+)
diff --git a/arch/arm/boot/dts/at91-sama5d4ek.dts
b/arch/arm/boot/dts/at91-sama5d4ek.dts
index 32e9a9a..7f47d92 100644
---
On Fri, Jan 30, 2015 at 11:05 PM, Haiyang Zhang
wrote:
-Original Message-
From: Jason Wang [mailto:jasow...@redhat.com]
Sent: Friday, January 30, 2015 5:25 AM
> + if (ret != 0) {
> + if (section_index != NETVSC_INVALID_INDEX)
> +
As DMA framework request DMA using direction only in prep_slave
function, (The At91 xdma driver has adapted to this request).
So won't check direction when do DMA configuration.
Signed-off-by: Bo Shen
---
sound/soc/atmel/atmel-pcm-dma.c | 12 +---
1 file changed, 5 insertions(+), 7
On Mon, 2015-02-02 at 10:40 +0530, Preeti U Murthy wrote:
> The device tree now exposes the residency values for different idle states.
> Read
> these values instead of calculating residency from the latency values. The
> values
> exposed in the DT are validated for optimal power efficiency.
On Mon, 02/02 14:25, kbuild test robot wrote:
> drivers/vhost/scsi.c:1081:5: sparse: symbol 'vhost_skip_iovec_bytes' was not
> declared. Should it be static?
>
> Signed-off-by: Fengguang Wu
> ---
> scsi.c |2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git
Hi Nicholas,
Today's linux-next merge of the target-updates tree got a conflict in
drivers/vhost/scsi.c between commit 46243860806b ("vhost-scsi: Add
missing virtio-scsi -> TCM attribute conversion") from Linus' tree and
commit 6df22d68ecaf ("vhost/scsi: Add ANY_LAYOUT prerequisites") from
the
On Thu, 29 Jan 2015, Peter Zijlstra wrote:
> That said, it does need to do that sibling first leaders later install
> order too. So I've put the below on top.
so I've lost track of exactly which patches I should be running (do I need
to apply both of the additional patches?)
Meanwhile my
tree: git://git.kernel.org/pub/scm/linux/kernel/git/nab/target-pending.git
for-next
head: 2936f1d4f3e8247bd519feba7892371d5e4c6603
commit: 105acf608f25d5e0d9fef669299a5438b7b114ee [16/21] vhost/scsi: Add
ANY_LAYOUT vhost_skip_iovec_bytes helper
reproduce:
# apt-get install sparse
git
drivers/vhost/scsi.c:1081:5: sparse: symbol 'vhost_skip_iovec_bytes' was not
declared. Should it be static?
Signed-off-by: Fengguang Wu
---
scsi.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/vhost/scsi.c b/drivers/vhost/scsi.c
index d888bd9..8ac003f 100644
Hahahaha! Is that you :)
http://tinyurl.com/kz7tdon
No more such info? Simply answer
--
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 http://vger.kernel.org/majordomo-info.html
On Mon, Feb 02, 2015 at 02:59:23PM +0900, Sergey Senozhatsky wrote:
> On (02/02/15 12:41), Minchan Kim wrote:
> > > If we use zram as block device itself(not a fs or swap) and open the
> > > block device as !FMODE_EXCL, bd_holders will be void.
> > >
> > > Another topic: As I didn't see enough
We explicitly mark the task running after returning from
a __rt_mutex_slowlock() call, which does the actual sleeping
via wait-wake-trylocking. As such, this patch does two things:
(1) refactors the code so that setting current to TASK_RUNNING
is done by __rt_mutex_slowlock(), and not by the
On Sun, 1 Feb 2015 21:08:12 -0800 Linus Torvalds
wrote:
> On Sun, Feb 1, 2015 at 3:03 PM, NeilBrown wrote:
> >
> > I guess I could
> > __set_current_state(TASK_RUNNING);
> > somewhere to defeat the warning, and add a comment explaining why.
> >
> > Would that be a good thing?
>
> Use
Preeti U Murthy writes:
> The device tree now exposes the residency values for different idle states.
> Read
> these values instead of calculating residency from the latency values. The
> values
> exposed in the DT are validated for optimal power efficiency. However to
> maintain
>
On (02/02/15 12:41), Minchan Kim wrote:
> > If we use zram as block device itself(not a fs or swap) and open the
> > block device as !FMODE_EXCL, bd_holders will be void.
> >
> > Another topic: As I didn't see enough fs/block_dev.c bd_holders in zram
> > would be mess. I guess we need to study
On Sun, Feb 01, 2015 at 09:36:52PM -0800, Linus Torvalds wrote:
> On Feb 1, 2015 9:29 PM, "Dave Chinner" wrote:
> >
> > So what's the outcome here? I'm running v3.19-rc7 kernel and
> > xfstests::generic/036 is still tripping this warning from the aio
> > code:
>
> So for the aio case, I suspect
Hi Russell,
On 30 January 2015 at 00:56, Russell King - ARM Linux
wrote:
> On Thu, Jan 29, 2015 at 01:52:09PM -0500, Rob Clark wrote:
>> Quite possibly for some of these edge some of cases, some of the
>> dma-buf exporters are going to need to get more clever (ie. hand off
>> different
On 02/02/2015 12:33 AM, Eddie Huang wrote:
> Hi Peter,
>
> On Sun, 2015-02-01 at 21:24 -0800, Greg Kroah-Hartman wrote:
>> On Mon, Feb 02, 2015 at 12:15:31AM -0500, Peter Hurley wrote:
>>> On 02/01/2015 11:28 PM, Greg Kroah-Hartman wrote:
On Sun, Feb 01, 2015 at 10:45:12PM -0500, Peter
Hi Eduardo,
On Sun, Feb 1, 2015 at 12:54 AM, Eduardo Valentin wrote:
> On Tue, Jan 27, 2015 at 11:18:22AM +0530, Abhilash Kesavan wrote:
>> Add registers, bit fields and compatible strings for Exynos7 TMU
>> (Thermal Management Unit). Following are a few of the differences
>> in the Exynos7 TMU
On Sun, Feb 01, 2015 at 10:59:54PM -0500, gr...@linuxhacker.ru wrote:
> From: Oleg Drokin
>
> leaf_dealloc uses vzalloc as a fallback to kzalloc(GFP_NOFS), so
> it clearly does not want any shrinker activity within the fs itself.
> convert vzalloc into __vmalloc(GFP_NOFS|__GFP_ZERO) to better
Correct Philipp's email address in the Cc list.
Liu Ying
On Mon, Feb 02, 2015 at 10:17:45AM +0800, Liu Ying wrote:
> Hi,
>
> This version has been submitted for a while.
> And, it looks there is no comments on this version.
> Can the maintainers consider to take this?
>
> Mike, any comments on
On Sun, Feb 01, 2015 at 05:18:17PM -0800, Linus Torvalds wrote:
> On Sun, Feb 1, 2015 at 4:16 PM, Benjamin LaHaise wrote:
> >>
> >> What's the bug you think could happen?
> >
> > The bug would be in code that gets run via mutex_lock(), kmap(), or (more
> > likely) in the random mm or filesystem
Function __flush_tlb_page() must only be called for user contexts, so
put in extra hardening to warn on calling it for kernel context.
Signed-off-by: Arseny Solokha
---
arch/powerpc/mm/tlb_nohash.c | 9 -
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git
On (02/02/15 14:18), Minchan Kim wrote:
> Everything are fixed. Ready to send a patch.
> But before sending, hope we fix umount race issue first.
>
Thanks a lot, Minchan!
OK, surely I don't mind to fix the umount race first, I just didn't want
to interrupt you in the middle of locking rework.
On Mon, Feb 02, 2015 at 12:15:31AM -0500, Peter Hurley wrote:
> On 02/01/2015 11:28 PM, Greg Kroah-Hartman wrote:
> > On Sun, Feb 01, 2015 at 10:45:12PM -0500, Peter Hurley wrote:
> >> On 02/01/2015 10:16 PM, Eddie Huang wrote:
>
> >> I'll respin proper patches on top of Greg's tty-testing branch
Hi all,
On Sun, 1 Feb 2015 21:16:48 -0800 Linus Torvalds
wrote:
>
> Everything seems to be fairly calm and normal, so this is likely to be
> the last rc unless something unexpected suddenly comes up. Which means
> that I'd like to see more people test-booting and running this puppy
> just to
On Mon, Feb 02, 2015 at 02:09:12PM +0900, Sergey Senozhatsky wrote:
>
> the patch mosly looks good, except for one place:
>
> On (02/02/15 13:28), Minchan Kim wrote:
> > @@ -783,6 +812,8 @@ static ssize_t disksize_store(struct device *dev,
> > goto out_destroy_comp;
> > }
> >
>
Everything seems to be fairly calm and normal, so this is likely to be
the last rc unless something unexpected suddenly comes up. Which means
that I'd like to see more people test-booting and running this puppy
just to check things out.
Fairly normal rc statistics - about 50% drivers, 20% arch
On 02/01/2015 11:28 PM, Greg Kroah-Hartman wrote:
> On Sun, Feb 01, 2015 at 10:45:12PM -0500, Peter Hurley wrote:
>> On 02/01/2015 10:16 PM, Eddie Huang wrote:
>> I'll respin proper patches on top of Greg's tty-testing branch with reverts
>> for the noinit options. I noticed that one of the
The device tree now exposes the residency values for different idle states. Read
these values instead of calculating residency from the latency values. The
values
exposed in the DT are validated for optimal power efficiency. However to
maintain
compatibility with the older firmware code which
Hi Mohammad,
> This patch replaces the shifting operations by BIT macro
>
> Signed-off-by: Mohammad Jamal
> ---
> drivers/net/ieee802154/cc2520.c |6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
patch has been applied to bluetooth-next tree.
Regards
Marcel
--
To unsubscribe
Hi Mohammad,
> This patch removes the warnings (space before , ) shown by
> checkpatch.pl
>
> Signed-off-by: Mohammad Jamal
> ---
> drivers/net/ieee802154/cc2520.c |4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
patch has been applied to bluetooth-next tree.
Regards
Marcel
--
On Mon, Feb 02, 2015 at 01:28:47PM +0900, Minchan Kim wrote:
> On Mon, Feb 02, 2015 at 01:01:24PM +0900, Sergey Senozhatsky wrote:
> > On (02/02/15 11:44), Minchan Kim wrote:
> > > > sure, I did think about this. and I actually didn't find any reason not
> > > > to use ->refcount there. if user
the patch mosly looks good, except for one place:
On (02/02/15 13:28), Minchan Kim wrote:
> @@ -783,6 +812,8 @@ static ssize_t disksize_store(struct device *dev,
> goto out_destroy_comp;
> }
>
> + init_waitqueue_head(>io_done);
> + zram_meta_get(zram);
it was
+
On Sun, Feb 1, 2015 at 3:03 PM, NeilBrown wrote:
>
> I guess I could
> __set_current_state(TASK_RUNNING);
> somewhere to defeat the warning, and add a comment explaining why.
>
> Would that be a good thing?
Use "sched_annotate_sleep()" instead, but yes, add a comment about why it's ok.
Hi Roger,
On 01/30/2015 11:03 PM, Roger Quadros wrote:
> On 30/01/15 02:11, Chanwoo Choi wrote:
>> Hi Roger,
>>
>> On 01/28/2015 09:15 PM, Roger Quadros wrote:
>>> This driver observes the USB ID pin connected over a GPIO and
>>> updates the USB cable extcon states accordingly.
>>>
>>> The
From: David Woodhouse
Date: Sun, 01 Feb 2015 21:29:43 +
> I really was looking for some way to push down something like an XFRM
> state into the tun device and just say "shove them out here until I tell
> you otherwise".
People decided to use TUN and push VPN stuff back into userspace,
and
> On Fri, 2015-01-30 at 19:08 +0700, Arseny Solokha wrote:
>> MMU_NO_CONTEXT is conditionally defined as 0 or (unsigned int)-1. However,
>> in __flush_tlb_page() a corresponding variable is only tested for open
>> coded 0, which can cause NULL pointer dereference if `mm' argument was
>>
Hi all,
Today's linux-next merge of the kvm tree got a conflict in
arch/arm64/kvm/sys_regs.c between commit 3c1e71650833 ("arm/arm64: KVM:
Use set/way op trapping to track the state of the caches") from Linus'
tree and commit 6d52f35af10c ("arm64: KVM: add SGI generation register
emulation") from
Hi Roger,
On 01/30/2015 11:05 PM, Roger Quadros wrote:
> Hi,
>
> On 30/01/15 13:04, Roger Quadros wrote:
>> Felipe & Chanwoo,
>>
>> On 26/01/15 14:15, Roger Quadros wrote:
>>> The recommended name for USB-Host cable state is "USB-Host" and not
>>> "USB-HOST" as per drivers/extcon/extcon-class.c
Hi all,
Today's linux-next merge of the kvm tree got a conflict in
arch/arm/kvm/mmu.c between commits 363ef89f8e9b ("arm/arm64: KVM:
Invalidate data cache on unmap") and 0d3e4d4fade6 ("arm/arm64: KVM: Use
kernel mapping to perform invalidation on page fault") from Linus' tree
and commits
(high-jacking the thread a bit... I don't have the patch that I want to reply
to still in my mail box: the subject still matches...)
I just got a might-sleep warning in my own testing.
This was introduced by
commit e22b886a8a43b147e1994a9f970f678fc0df2033
Author: Peter Zijlstra
Date: Wed
Hi Andrew,
Could you please pick these patches up through your tree?
Thanks,
Cyril
On Fri, 2015-01-09 at 14:34 +1100, Cyril Bur wrote:
> When the hypervisor pauses a virtualised kernel the kernel will observe a jump
> in timebase, this can cause spurious messages from the softlockup detector.
On 2 February 2015 at 10:15, ethan zhao wrote:
> On 2015/2/2 12:26, Viresh Kumar wrote:
> But there is no checking against refcount in or before
>
> cpufreq_policy_free(), that is one issue I mentioned.
As I said earlier, the completion will only fire once the refcount
is zero. And so there
On 2015/2/2 12:26, Viresh Kumar wrote:
On 2 February 2015 at 09:46, ethan zhao wrote:
We am talking about the policy allocation and de-allocation. right ?
I showed you the cpufreq_policy_free(policy) doesn't check kobject
refcount as above.
Hmmm, you are still sleeping in the
On Mon, Feb 02, 2015 at 01:01:24PM +0900, Sergey Senozhatsky wrote:
> On (02/02/15 11:44), Minchan Kim wrote:
> > > sure, I did think about this. and I actually didn't find any reason not
> > > to use ->refcount there. if user wants to reset the device, he first
> > > should umount it to make
From: Heba Aamer
Improve the format specifier test by removing any %% before
looking for any remaining % format specifier.
Signed-off-by: Heba Aamer
Signed-off-by: Joe Perches
---
scripts/checkpatch.pl | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git
On Sun, Feb 01, 2015 at 10:45:12PM -0500, Peter Hurley wrote:
> On 02/01/2015 10:16 PM, Eddie Huang wrote:
> > Hi Peter,
> >
> > On Sun, 2015-02-01 at 13:26 -0500, Peter Hurley wrote:
> >> On 02/01/2015 11:27 AM, Peter Hurley wrote:
> >>> Hi Eddie,
> >>>
> >>> On 01/12/2015 08:08 AM, Eddie Huang
Some prefer code to have spaces around arithmetic so instead of:
a = b*c+d;
suggest
a = b * c + d;
Signed-off-by: Joe Perches
---
scripts/checkpatch.pl | 17 -
1 file changed, 16 insertions(+), 1 deletion(-)
diff --git a/scripts/checkpatch.pl
The preferred style for a commit reference in a commit log is:
commit ("")
A recent commit removed this check for parentheses. Add it back.
Signed-off-by: Joe Perches
---
scripts/checkpatch.pl | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/scripts/checkpatch.pl
Code like:
if (a < sizeof() &&
and
{ .len = sizeof() },
incorrectly emits that warning, so add more exceptions to avoid
the warning.
Signed-off-by: Joe Perches
---
scripts/checkpatch.pl | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/checkpatch.pl
Just neatening...
Signed-off-by: Joe Perches
---
scripts/checkpatch.pl | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
index a9baaab..bf23264 100755
--- a/scripts/checkpatch.pl
+++ b/scripts/checkpatch.pl
@@ -3243,7 +3243,7 @@
Heba Aamer (1):
checkpatch: Improve seq_print->seq_puts suggestion
Joe Perches (4):
checkpatch: Improve "no space necessary after cast" test
checkpatch: Neaten printk_ratelimited message position
checkpatch: Add --strict test for spaces around arithmetic
checkpatch: Make sure a commit
On 2 February 2015 at 09:46, ethan zhao wrote:
> We am talking about the policy allocation and de-allocation. right ?
> I showed you the cpufreq_policy_free(policy) doesn't check kobject
> refcount as above.
>
> Hmmm, you are still sleeping in the kobject, wake up and don't mix
> water
Greetings,
0day kernel testing robot got the below dmesg and the first bad commit is
git://git.kernel.org/pub/scm/linux/kernel/git/zohar/linux-integrity.git
initramfs
commit 8dd45530cb1353fbd058d42a3e6d32bde811429b
Author: Mimi Zohar
AuthorDate: Tue Dec 23 18:27:34 2014 -0500
Commit:
On 2015/2/2 12:09, Viresh Kumar wrote:
On 2 February 2015 at 09:36, ethan zhao wrote:
Is that an idea it supposed to be or fact ?
if (!cpufreq_suspended)
cpufreq_policy_free(policy);
static void cpufreq_policy_free(struct cpufreq_policy *policy)
{
On 2 February 2015 at 09:36, ethan zhao wrote:
> Is that an idea it supposed to be or fact ?
>
> if (!cpufreq_suspended)
> cpufreq_policy_free(policy);
>
> static void cpufreq_policy_free(struct cpufreq_policy *policy)
> {
> free_cpumask_var(policy->related_cpus);
>
On 2015/2/2 11:59, Viresh Kumar wrote:
On 2 February 2015 at 09:26, ethan zhao wrote:
How to prevent the policy to be freed between
cpufreq_cpu_get() and cpufreq_cpu_put() ?
kobject_get() increases the reference count of a policy and the policy
will only be freed when this is zero. And
Hi ykk,
On Sat, Jan 31, 2015 at 10:34 PM, Yang Kuankuan wrote:
>
> On 01/31/2015 06:48 AM, Russell King - ARM Linux wrote:
>>
>>> +void hdmi_audio_clk_enable(struct dw_hdmi *hdmi)
>>> +{
>>> + if (hdmi->audio_enable)
>>> + return;
>>> +
>>> + mutex_lock(>audio_mutex);
On 1 February 2015 at 00:29, Eduardo Valentin wrote:
> From: Arnd Bergmann
>
> The exynos cpufreq driver code recently gained a dependency on the
> cooling code, which may be a loadable module. This breaks an ARM
> allmodconfig build:
>
> drivers/built-in.o: In function `exynos_cpufreq_probe':
>
From: Oleg Drokin
Signed-off-by: Oleg Drokin
---
fs/coda/coda_linux.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/coda/coda_linux.h b/fs/coda/coda_linux.h
index d6f7a76..537754b 100644
--- a/fs/coda/coda_linux.h
+++ b/fs/coda/coda_linux.h
@@ -73,7 +73,7 @@ void
On (02/02/15 11:44), Minchan Kim wrote:
> > sure, I did think about this. and I actually didn't find any reason not
> > to use ->refcount there. if user wants to reset the device, he first
> > should umount it to make bdev->bd_holders check happy. and that's where
> > IOs will be failed. so it
On 2 February 2015 at 09:26, ethan zhao wrote:
> How to prevent the policy to be freed between
>
> cpufreq_cpu_get() and cpufreq_cpu_put() ?
kobject_get() increases the reference count of a policy and the policy
will only be freed when this is zero. And it will only be zero once all
From: Oleg Drokin
leaf_dealloc uses vzalloc as a fallback to kzalloc(GFP_NOFS), so
it clearly does not want any shrinker activity within the fs itself.
convert vzalloc into __vmalloc(GFP_NOFS|__GFP_ZERO) to better achieve
this goal.
Signed-off-by: Oleg Drokin
---
fs/gfs2/dir.c | 3 ++-
1 file
On 2015/2/2 11:43, Viresh Kumar wrote:
On 2 February 2015 at 09:08, ethan zhao wrote:
We take cpufreq_driver_lock() here, and so this will
block thread B.
No, there is no cpufreq_driver_lock acquired between
cpufreq_cpu_get() and cpufreq_cpu_put()
I am not saying that the lock is
This patch change non-atomic bitops,
add a if() condition to test it, before set/clear the bit.
so that we don't need dirty the cache line, if this bit
have been set or clear. On SMP system, dirty cache line will
need invalidate other processors cache line, this will have
some impact on SMP
On (02/02/15 11:45), Minchan Kim wrote:
> On Mon, Feb 02, 2015 at 10:59:40AM +0900, Sergey Senozhatsky wrote:
> > On (02/02/15 10:43), Minchan Kim wrote:
> > > > static inline int init_done(struct zram *zram)
> > > > {
> > > > - return zram->meta != NULL;
> > > > + return
1 - 100 of 650 matches
Mail list logo
