On Tue, Dec 17, 2013 at 07:17:01AM +, Gupta, Pekon wrote:
> All I said was using company names in Headers or MODULE_AUTHOR of
> *generic frameworks*. A generic framework is maintained and updated
> by community at large. And over course of time other people contribute
> more than the author.
On Tue, 17 Dec 2013 15:26:22 +0800
Zhi Yong Wu wrote:
> From: Zhi Yong Wu
>
> The flow cache is an extremely broken concept, and it usually brings up
> growth issues and DoS attacks, so this patch is trying to remove it from
> the tuntap driver, and insteadly use a simpler way for its flow
On Mon, Dec 16, 2013 at 8:47 PM, Michal Hocko wrote:
> On Sat 14-12-13 12:15:33, Vladimir Davydov wrote:
>> The mem_cgroup structure contains nr_node_ids pointers to
>> mem_cgroup_per_node objects, not the objects themselves.
>
> Ouch! This is 2k per node which is wasted. What a shame I haven't
>
On 12/17/2013 02:44 PM, Wanpeng Li wrote:
> BUG_ON(!vma) assumption is introduced by commit 0bf598d8 (mbind: add
> BUG_ON(!vma)
> in new_vma_page()), however, even if address = __vma_address(page, vma); and
> vma->start < address < vma->end; page_address_in_vma() may still return
> -EFAULT
>
On Tue, Dec 17, 2013 at 02:44:17PM +0800, Wanpeng Li wrote:
> BUG_ON(!vma) assumption is introduced by commit 0bf598d8 (mbind: add
> BUG_ON(!vma)
> in new_vma_page()), however, even if address = __vma_address(page, vma); and
> vma->start < address < vma->end; page_address_in_vma() may still
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 inline u8 map_sd_drive(int idx)
>
Hello Chanho,
On Mon, Dec 16, 2013 at 02:30:26PM +0900, Chanho Min wrote:
> This patch removes synchronous wait for the up-to-date of buffer in the
> file system level. Instead all operations after submit_bh are moved into
> the End-of-IO handler and its associated workeque. It
On Mon, Dec 16, 2013 at 9:07 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
If we do wanna equip fadvise() with directory level page cache cleaning,
this could be solved by invoking (inode_permission() ||
capable(CAP_SYS_ADMIN)) before manipulating the page cache of that inode.
We think the current extension to 'drop_caches' has a complete back
compatibility, the old
Acked-by: Colin Cross
On Mon, Dec 16, 2013 at 9:07 PM, John Stultz wrote:
> The kbuild test robot reported a build issue w/ ION on m68k:
>
> drivers/staging/android/ion/ion.c: In function 'ion_reserve':
> drivers/staging/android/ion/ion.c:1526:4: error: implicit declaration of
> function
On Mon, Dec 16, 2013 at 9:07 PM, John Stultz wrote:
> The kbuild test robot reported:
>
> drivers/staging/android/ion/ion_system_heap.c:122 alloc_largest_available()
> error: potential null dereference 'info'. (kmalloc returns null)
>
> Where the pointer returned from kmalloc goes unchecked for
From: Zhi Yong Wu
The flow cache is an extremely broken concept, and it usually brings up
growth issues and DoS attacks, so this patch is trying to remove it from
the tuntap driver, and insteadly use a simpler way for its flow control.
Signed-off-by: Zhi Yong Wu
---
drivers/net/tun.c | 208
Hi Shawn,
>From: Shawn Guo [mailto:shawn@linaro.org]
>>On Tue, Dec 17, 2013 at 05:00:53AM +, Gupta, Pekon wrote:
>> >From: Huang Shijie [mailto:b32...@freescale.com]
>>> >On Tue, Dec 17, 2013 at 04:08:33AM +, Gupta, Pekon wrote:
[...]
>> >> As much base code is copied from m25p90.c,
Hi Sebastian,
Looks like there's a booboo here:
On Mon, 2013-12-16 at 10:14 +0100, Sebastian Andrzej Siewior wrote:
> diff --git a/kernel/sched/core.c b/kernel/sched/core.c
> index 22fa2e2..9c87a17 100644
> --- a/kernel/sched/core.c
> +++ b/kernel/sched/core.c
> @@ -1115,9 +1129,11 @@ unsigned
On Tue, 17 Dec 2013, Li Zefan wrote:
> On 2013/12/17 9:41, Hugh Dickins wrote:
> > On Mon, 16 Dec 2013, Tejun Heo wrote:
> >> On Mon, Dec 16, 2013 at 06:19:37PM +0100, Michal Hocko wrote:
> >>> I have to think about it some more (the brain is not working anymore
> >>> today). But what we really
On 5 December 2013 13:14, Bill Huang wrote:
> Re-model Tegra cpufreq driver to support all Tegra series of SoCs.
>
> * Make tegra-cpufreq.c a generic Tegra cpufreq driver.
> * Move Tegra20 specific codes into tegra20-cpufreq.c.
> * Bind Tegra cpufreq dirver with a fake device so defer probe would
On 12/17/13 at 02:24pm, Dave Young wrote:
> On 12/16/13 at 04:35pm, Matt Fleming wrote:
> > On Mon, 16 Dec, at 05:30:35PM, Dave Young wrote:
> > > kdump kernel will use memmap=exactmap kernel cmdline, but __va does not
> > > work in case memmap=exactmap, so let's always use ioremap_cache.
> > >
>
BUG_ON(!vma) assumption is introduced by commit 0bf598d8 (mbind: add
BUG_ON(!vma)
in new_vma_page()), however, even if address = __vma_address(page, vma); and
vma->start < address < vma->end; page_address_in_vma() may still return -EFAULT
because of many other conditions in it. As a result the
Hi, I am trying to maintain an initrd for a homebrew Linux distro. I'm
having a problem where kernel modules are gradually shifting from
linux/firmware to /lib/firmware, which breaks my initrd (which currently
uses CONFIG_FIRMWARE_IN_KERNEL). I am looking for a way to extract a
list of needed
On 12/17/2013 12:15 AM, John Stultz wrote:
On 12/12/2013 11:13 AM, John Stultz wrote:
On 12/12/2013 11:05 AM, Sasha Levin wrote:
On 12/12/2013 01:59 PM, John Stultz wrote:
On 12/12/2013 10:32 AM, Sasha Levin wrote:
On 12/12/2013 11:34 AM, Sasha Levin wrote:
On 12/11/2013 02:11 PM, John
On 12/16/13 at 12:33pm, Borislav Petkov wrote:
> On Mon, Dec 16, 2013 at 10:00:10AM +0800, Dave Young wrote:
> > > > - print_efi_memmap();
> > > > + if (efi_setup) {
> > > > + int s;
> > > > + struct efi_setup_data *data;
> > > > +
> > > > + s
On 5 December 2013 13:14, Bill Huang wrote:
> Move the call from module_init to Tegra machine codes so it won't be
> called in a multi-platform kernel running on non-Tegra SoCs.
>
> Signed-off-by: Bill Huang
> ---
> arch/arm/mach-tegra/tegra.c |2 ++
> drivers/cpufreq/tegra-cpufreq.c |
On 5 December 2013 13:14, Bill Huang wrote:
> This patch series remodel Tegra cpufreq driver to make it more easy to
> add new SoC support, in addition to that, adding probe function in the
> driver to let probe defer can be used to control init sequence when we
> are going to support DVFS.
>
>
On 12/16/13 at 04:35pm, Matt Fleming wrote:
> On Mon, 16 Dec, at 05:30:35PM, Dave Young wrote:
> > kdump kernel will use memmap=exactmap kernel cmdline, but __va does not
> > work in case memmap=exactmap, so let's always use ioremap_cache.
> >
> > Signed-off-by: Dave Young
> > ---
> >
Add my copyright to the zsmalloc source code which I maintain.
Cc: Nitin Gupta
Signed-off-by: Minchan Kim
---
include/linux/zsmalloc.h |1 +
mm/zsmalloc.c|1 +
2 files changed, 2 insertions(+)
diff --git a/include/linux/zsmalloc.h b/include/linux/zsmalloc.h
index
This patch adds maintainer information for zram into the MAINTAINERS
file.
Cc: Nitin Gupta
Signed-off-by: Minchan Kim
---
MAINTAINERS |8
1 file changed, 8 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index d077c89b0440..7b32aa4b5f04 100644
--- a/MAINTAINERS
+++
This patch adds maintainer information for zsmalloc into
the MAINTAINERS file.
Cc: Nitin Gupta
Signed-off-by: Minchan Kim
---
MAINTAINERS |8
1 file changed, 8 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 7b32aa4b5f04..af237d331765 100644
--- a/MAINTAINERS
+++
On 12/16/13 at 03:09pm, Matt Fleming wrote:
> On Mon, 16 Dec, at 05:30:29PM, Dave Young wrote:
> > @@ -899,6 +928,11 @@ void __init efi_enter_virtual_mode(void)
> > return;
> > }
> >
> > +#ifdef CONFIG_EFI_RUNTIME_MAP
> > + efi_runtime_map_setup(efi_runtime_map,
Hi all,
Changes since 20131216:
Linus' tree still had its build failure for which I added a patch.
The powerpc tree still had its build failure for which I applied a
supplied patch.
The device-mapper tree gained a conflict against the block tree.
The mmc tree still had its build failure so I
Add my copyright to the zram source code which I maintain.
Cc: Nitin Gupta
Signed-off-by: Minchan Kim
---
drivers/block/zram/zram_drv.c |1 +
drivers/block/zram/zram_drv.h |1 +
2 files changed, 2 insertions(+)
diff --git a/drivers/block/zram/zram_drv.c b/drivers/block/zram/zram_drv.c
I and Nitin discussed how to maintain zsmalloc and zram.
Nitin wanted me to maintain zram because he doesn't have enough
bandwidth to quickly handle any issues that might arise and
I have maintained zram/zsmalloc during last two years so he
will be listed as co-maintainer.
Minchan Kim (5):
This patch removes old private compcache project address so
upcoming patches should be sent to LKML because we Linux kernel
community will take care.
Cc: Nitin Gupta
Signed-off-by: Minchan Kim
---
Documentation/blockdev/zram.txt |6 --
drivers/block/zram/Kconfig |1 -
Hi all,
After merging the final tree, today's linux-next build (powerpc
allyesconfig) failed like this:
drivers/rtc/rtc-hym8563.c:90:17: error: field 'clkout_hw' has incomplete type
struct clk_hw clkout_hw;
^
In file included from include/asm-generic/bug.h:13:0,
Le 16/12/2013 23:57, Scott Wood a écrit :
On Wed, 2013-12-11 at 00:36 +0100, leroy christophe wrote:
Le 11/12/2013 00:18, Scott Wood a écrit :
There wasn't previously an ifdef specifically around the setting of
SPRN_MD_CTR. That's new. There was an ifdef around the entire block,
which has
Hi all,
After merging the final tree, today's linux-next build (powerpc
allnoconfig) failed like this:
arch/powerpc/mm/mem.c: In function 'do_init_bootmem':
arch/powerpc/mm/mem.c:212:49: error: 'memblock_memory' undeclared (first use in
this function)
memblock_set_node(0,
Signed-off-by: Wenyou Yang
---
drivers/regulator/Kconfig |8 +
drivers/regulator/Makefile|1 +
drivers/regulator/act8865-regulator.c | 381 +
include/linux/regulator/act8865.h | 55 +
4 files changed, 445 insertions(+)
Signed-off-by: Wenyou Yang
---
.../bindings/regulator/act8865-regulator.txt | 56
1 file changed, 56 insertions(+)
create mode 100644
Documentation/devicetree/bindings/regulator/act8865-regulator.txt
diff --git
Hi Connor,
On Tue, Dec 17, 2013 at 12:28 AM, Connor Behan wrote:
> Thanks for the detailed answer. I have tried your patch and updated the
> wiki page. Would a 950 or 950Q be safer to buy next time?
The 950 has long since been obsoleted. You cannot buy them anymore.
The 950q though is well
Signed-off-by: Wenyou Yang
---
arch/arm/boot/dts/sama5d3xcm.dtsi | 46 +
1 file changed, 46 insertions(+)
diff --git a/arch/arm/boot/dts/sama5d3xcm.dtsi
b/arch/arm/boot/dts/sama5d3xcm.dtsi
index 726a0f3..634adf5 100644
---
Hi Mark,
Thanks a lot for quickly feedbacks. According to your advice, I prepared the
new version.
The patch set is to add act8865 PMIC driver.
The active-semi act8865 is designed as a PMIC for Atmel sama5d3x and at91sam9
series.
Its datasheet is available at:
Thanks for the detailed answer. I have tried your patch and updated the
wiki page. Would a 950 or 950Q be safer to buy next time?
On 14/12/13 05:17 PM, Devin Heitmueller wrote:
> I had a patch kicking around which fixed part of the issue, but it
> didn't completely work because of the lgdt3305
On Mon, Dec 16, 2013 at 9:28 PM, Magnus Damm wrote:
> Hi Olof,
>
> On Mon, Dec 16, 2013 at 2:39 PM, Olof Johansson wrote:
>> On Fri, Dec 13, 2013 at 07:12:58PM +0900, Magnus Damm wrote:
>>> Hi Olof,
>>>
>>> On Thu, Dec 12, 2013 at 10:05 AM, Olof Johansson wrote:
>>> > Hi,
>>> >
>>> > A couple
Hi Olof,
On Mon, Dec 16, 2013 at 2:39 PM, Olof Johansson wrote:
> On Fri, Dec 13, 2013 at 07:12:58PM +0900, Magnus Damm wrote:
>> Hi Olof,
>>
>> On Thu, Dec 12, 2013 at 10:05 AM, Olof Johansson wrote:
>> > Hi,
>> >
>> > A couple of small comments below.
>>
>> Thanks for your feedback!
>>
>> >
hi,
On Mon, Dec 16, 2013 at 11:08:22PM -0600, Felipe Balbi wrote:
> > > On Mon, Dec 09, 2013 at 02:58:03PM +1100, Stephen Rothwell wrote:
> > > >
> > > > After merging the usb-gadget tree, today's linux-next build (x86_64
> > > > allmodconfig) failed like this:
> > > >
> > > >
On 12/12/2013 11:13 AM, John Stultz wrote:
> On 12/12/2013 11:05 AM, Sasha Levin wrote:
>> On 12/12/2013 01:59 PM, John Stultz wrote:
>>> On 12/12/2013 10:32 AM, Sasha Levin wrote:
On 12/12/2013 11:34 AM, Sasha Levin wrote:
> On 12/11/2013 02:11 PM, John Stultz wrote:
>> As part of
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
The kbuild test robot reported a build issue w/ ION on m68k:
drivers/staging/android/ion/ion.c: In function 'ion_reserve':
drivers/staging/android/ion/ion.c:1526:4: error: implicit declaration of
function 'memblock_alloc_base' [-Werror=implicit-function-declaration]
On Tue, Dec 17, 2013 at 03:36:25PM +1100, Stephen Rothwell wrote:
> Hi Felipe,
>
> On Sun, 8 Dec 2013 22:11:52 -0600 Felipe Balbi wrote:
> >
> > On Mon, Dec 09, 2013 at 02:58:03PM +1100, Stephen Rothwell wrote:
> > >
> > > After merging the usb-gadget tree, today's linux-next build (x86_64
> >
The kbuild test robot reported:
drivers/staging/android/ion/ion_system_heap.c:122 alloc_largest_available()
error: potential null dereference 'info'. (kmalloc returns null)
Where the pointer returned from kmalloc goes unchecked for failure.
This patch checks the return for NULL, and reworks
Since the ION patchset landed in staging-next, there have
been a few build issue reports, and this patchset tries
to address them.
Dropped the RFC, as I think the first two are good to go, but
I'd still like to get acks from Colin or someone else on the
Android team on all of these before merging
"Michael S. Tsirkin" writes:
> On Mon, Dec 16, 2013 at 06:23:38AM -0800, Josh Triplett wrote:
>> On Mon, Dec 16, 2013 at 04:54:08PM +0530, Rashika Kheria wrote:
>> > Mark the function virtballoon_migratepage() as static in
>> > virtio_balloon.c because it is not used outside this file.
>> >
>> >
Hi Felipe,
On Sun, 8 Dec 2013 22:11:52 -0600 Felipe Balbi wrote:
>
> On Mon, Dec 09, 2013 at 02:58:03PM +1100, Stephen Rothwell wrote:
> >
> > After merging the usb-gadget tree, today's linux-next build (x86_64
> > allmodconfig) failed like this:
> >
> > drivers/built-in.o: In function
Hi Filipe,
On Mon, 16 Dec 2013 17:38:15 -0600 Felipe Balbi wrote:
>
> It's long, sorry, basically what I did was this:
>
> - ret = usb_phy_gen_create_phy(dev, _phy->usb_phy_gen,
> - USB_PHY_TYPE_USB2, 0, false);
> + ret = usb_phy_gen_create_phy(dev,
This is the SGTL5000 codec based audio driver supported with both
playback and capture dai link implemention.
This implementation is only compatible with device tree definition.
Signed-off-by: Xiubo Li
Signed-off-by: Alison Wang
+#include
+#include
+#include
+#include
+
+#include
This patch adds and enables the SAI device.
Signed-off-by: Xiubo Li
---
arch/arm/boot/dts/vf610-twr.dts | 6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm/boot/dts/vf610-twr.dts b/arch/arm/boot/dts/vf610-twr.dts
index c8047ca..e60c20c 100644
--- a/arch/arm/boot/dts/vf610-twr.dts
Fix the description of one comment.
This adds Freescale SAI ASoC Audio support.
This implementation is only compatible with device tree definition.
Features:
o Supports playback/capture
o Supports 16/20/24 bit PCM
o Supports 8k - 96k sample rates
o Supports master and slave mode.
Signed-off-by:
This patch adds the SAI's edma mux Tx and Rx support.
Signed-off-by: Jingchang Lu
Signed-off-by: Xiubo Li
---
arch/arm/boot/dts/vf610.dtsi | 3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/arm/boot/dts/vf610.dtsi b/arch/arm/boot/dts/vf610.dtsi
index e84d84c..2d6ddd0 100644
---
This adds the Document for Freescale VF610 sound driver under
Documentation/devicetree/bindings/sound/.
Signed-off-by: Xiubo Li
---
.../bindings/sound/vf610-audio-sgt15000.txt| 46 ++
1 file changed, 46 insertions(+)
create mode 100644
This patch adds and enables SGTL5000 codec support, and also specified
the corresponding SAI node.
Signed-off-by: Xiubo Li
---
arch/arm/boot/dts/vf610-twr.dts | 33 +
1 file changed, 33 insertions(+)
diff --git a/arch/arm/boot/dts/vf610-twr.dts
This adds the Document for Freescale SAI driver under
Documentation/devicetree/bindings/sound/.
Signed-off-by: Xiubo Li
---
.../devicetree/bindings/sound/fsl-sai.txt | 40 ++
1 file changed, 40 insertions(+)
create mode 100644
This patch series is mostly Freescale's SAI SoC Digital Audio Interface
driver implementation. And the implementation is only compatible with
device tree definition.
This patch series is based on linux-next and has been tested on Vybrid
VF610 Tower board using device tree.
Changed in v3:
- Add
On Tue, Dec 17, 2013 at 11:08:16AM +0800, Li Wang wrote:
> As far as we know, fadvise(DONTNEED) does not support metadata
> cache cleaning. We think that is desirable under massive small files
> situations. Another thing is that do people accept the behavior
> of feeding a directory fd to fadvise
The local variable 'bi' comes from userspace. If userspace passed a
large number to 'bi.data.calibrate', there would be an integer overflow
in the following line:
s->hdlctx.calibrate = bi.data.calibrate * s->par.bitrate / 16;
Signed-off-by: Wenliang Fan
---
As far as we know, fadvise(DONTNEED) does not support metadata
cache cleaning. We think that is desirable under massive small files
situations. Another thing is that do people accept the behavior
of feeding a directory fd to fadvise will recusively clean all
page caches of files inside that
Hi Chris,
Please drop fc4fafac9656 ("ARM: dts: sabresd: add usdhc4 support") from
your tree. It should go via my tree (with a rebase). Sorry, I did not
notice it early.
Shawn
On Tue, Dec 17, 2013 at 11:07:19AM +0800, Dong Aisheng wrote:
> Hi Stephen,
>
> Sorry, i just see this mail.
> It
On 2013/12/17 9:41, Hugh Dickins wrote:
> On Mon, 16 Dec 2013, Tejun Heo wrote:
>> On Mon, Dec 16, 2013 at 06:19:37PM +0100, Michal Hocko wrote:
>>> I have to think about it some more (the brain is not working anymore
>>> today). But what we really need is that nobody gets the same id while
>>>
print the error message and then return -ENOMEM.
Signed-off-by: Gao feng
---
kernel/audit.c | 9 -
1 file changed, 4 insertions(+), 5 deletions(-)
diff --git a/kernel/audit.c b/kernel/audit.c
index 2a0ed0b..041b951 100644
--- a/kernel/audit.c
+++ b/kernel/audit.c
@@ -1083,12 +1083,11
NETLINK_CB(skb).sk is the socket of user space process,
netlink_unicast in kauditd_send_skb wants the kernel
side socket. Since the sk_state of audit netlink socket
is not NETLINK_CONNECTED, so the netlink_getsockbyportid
doesn't return -ECONNREFUSED.
And the socket of userspace process can be
Hi Stephen,
Sorry, i just see this mail.
It seems the imx pinctrl dt binding has changes since Chris pick my patch.
I will fix it ASAP.
Regards
Dong Aisheng
On Tue, Dec 17, 2013 at 10:28 AM, Stephen Rothwell
wrote:
> Hi Chris,
>
> ping?
>
> On Fri, 13 Dec 2013 12:57:16 +1100 Stephen Rothwell
Use poll(2) to wait for a message. If a client/server cannot send a message for
any reasons, the current server/client will wait in a blocking read operation.
So, we use poll(2) for avoiding remaining in a blocking state.
Signed-off-by: Yoshihiro YUNOMAE
---
trace-msg.c | 42
Hi Steven,
This is a v3 patch set for realizing a part of "Integrated trace" feature which
is a trace merging system for a virtualization environment. Currently, trace-cmd
does not have following features yet:
a) Server and client for a virtualization environment
b) Structured message platform
Split out binding a port and fork reader from open_udp() for avoiding duplicate
codes between listen mode and virt-server mode.
Changes in V2: Add a comment in open_udp()
Signed-off-by: Yoshihiro YUNOMAE
---
trace-listen.c | 38 ++
1 file changed, 30
On Mon, Dec 16, 2013 at 06:37:48PM +0800, Nicolin Chen wrote:
> This patch adds spdif support for imx6qdl-sabreauto by inserting the cpu dai
> node with pinctrl group and its ASoC dai link node.
>
> Signed-off-by: Nicolin Chen
Applied, thanks.
--
To unsubscribe from this list: send the line
On Mon, Dec 16, 2013 at 11:32:08AM -0800, Randy Dunlap wrote:
> On 12/16/13 11:30, Randy Dunlap wrote:
> > On 12/15/13 12:59, Josh Triplett wrote:
> >> Most of the mechanical portions of SubmittingPatches exist to help patch
> >> submitters replicate the output of git. Mention this explicitly,
Add the virt-server mode for a virtualization environment based on the listen
mode for networking. This mode works like client/server mode over TCP/UDP,
but it uses virtio-serial channel instead of IP network. Using networking for
collecting trace data of guests is generally high overhead caused
Add --dom option which makes a domain directory to virt-server. When a user
already knows domain name of a guest before running virt-server, trace-cmd
should automatically set up I/Fs of the guest. By adding --dom option,
trace-cmd creates a domain directory with 0710 and qemu group.
This patch
Add --virt option for record mode for a virtualization environment.
If we use this option on a guest, we can send trace data in low-overhead.
This is because guests can send trace data to a host without copying the data
by using splice(2).
The format is:
trace-cmd record --virt -e sched*
Apply trace-msg protocol for communication between a server and clients.
Currently, trace-listen(server) and trace-record -N(client) operate as follows:
listen to socket fd
connect to socket fd
accept the client
send
Hi, Mark
Thanks for your quick reply, see below inline:
Best Regards.
Anson huang 黄勇才
Freescale Semiconductor Shanghai
上海浦东新区亮景路192号A座2楼
201203
Tel:021-28937058
>-Original Message-
>From: Mark Brown [mailto:broo...@kernel.org]
>Sent: Tuesday, December 17, 2013 2:58 AM
>To:
From: Magnus Damm
Rework _GP_GPIO to take banksize as argument, introduce
_GP_GPIO32 for SoCs with 32-bit GPIO banks.
Signed-off-by: Magnus Damm
---
Developed on top of renesas git tag renesas-devel-v3.13-rc3-20131214v2
drivers/pinctrl/sh-pfc/sh_pfc.h |9 +
1 file changed, 5
From: Micky Ching
With the recent added support request of yet another device, the
burden of duplicated code was becoming a little messy. To rectify is,
we init rtl8411-like chips to 8411 param first, then modify the
different values according each chip. And rtl8402 is supported from
this patch.
On 12/16/2013 05:14 PM, Bjorn Helgaas wrote:
On Mon, Dec 16, 2013 at 10:39 AM, Guenter Roeck wrote:
On Sun, Dec 15, 2013 at 05:18:26PM -0700, Bjorn Helgaas wrote:
On Sun, Dec 15, 2013 at 4:24 PM, Rajat Jain wrote:
Once again: the way I interpret this is: * Always enable Link events.
*
From: Magnus Damm
Introduce macros that allow description of one pin per line.
Compared to the other ways of doing this, using this style
we can compresses the description of each pin from 9 to 1 line.
Signed-off-by: Magnus Damm
---
This patch uses RZ_PMX_GROUP and RZ_GROUPS, thanks Laurent!
pinctrl: sh-pfc: r7s72100 support V2
[PATCH 01/05 v2] pinctrl: sh-pfc: Rework _GP_GPIO, introduce _GP_GPIO32
[PATCH 02/05 v2] pinctrl: sh-pfc: r7s72100 base support
[PATCH 03/05 v2] pinctrl: sh-pfc: r7s72100 single pin macros
[PATCH 04/05 v2] pinctrl: sh-pfc: r7s72100 SCIF support
[PATCH 05/05
From: Micky Ching
Add card reader rtl8042, rtl8402 is much like rtl8411, so just add it to
rtl8411.c
Signed-off-by: Micky Ching
---
drivers/mfd/rtl8411.c | 28
drivers/mfd/rtsx_pcr.c |5 +
drivers/mfd/rtsx_pcr.h |1 +
3 files changed, 30
From: Micky Ching
in order to remove duplicated code in rtl8411, we make 8411 as the base
init params, and other like-8411 chips will just change the different
value with 8411, this can save some source code.
Signed-off-by: Lee Jones
Signed-off-by: Micky Ching
---
drivers/mfd/rtl8411.c |
From: Magnus Damm
Add support for SCIF functions SCK, TXD, RXD, CTS and RTS to the
r7s72100 PINCTRL code. There are two possible pins that can be used
for TXD (Port 3 Pin 0 Function 6 and Port 3 Pin 1 Function 4) and
because of that are pins broken out into separate functions.
Signed-off-by:
From: Magnus Damm
Add r7s72100 PINCTRL support via sh-pfc V2. At this point the code
provides enough support to allow use together with the gpio-rz
driver. Incremental per-device patches will in the future be
submitted on top of this base patch to allow PINCTRL enablement
for each individual
From: Magnus Damm
Add compatible strings for r7s72100 and r8a7791.
Signed-off-by: Magnus Damm
---
Documentation/devicetree/bindings/pinctrl/renesas,pfc-pinctrl.txt |2 ++
1 file changed, 2 insertions(+)
--- 0001/Documentation/devicetree/bindings/pinctrl/renesas,pfc-pinctrl.txt
+++
regmap_bulk_write() should decay to performing individual writes
if we're using a "no-bus" regmap. Unfortunately, it returns an
error because there is no map->bus pointer. Fix it.
Signed-off-by: Stephen Boyd
---
On 12/16, Mark Brown wrote:
> On Fri, Dec 13, 2013 at 01:37:07PM -0800, Stephen
On Mon, 16 Dec 2013, Michal Hocko wrote:
> On Mon 16-12-13 00:36:05, Hugh Dickins wrote:
> [...]
>
> OK, I went through the patch and it looks good except for suspicious
> ctrl->lock handling in swap_cgroup_reassign (see below). I am just
> suggesting to split it into 4 parts
Thanks a lot for
Hi Chris,
ping?
On Fri, 13 Dec 2013 12:57:16 +1100 Stephen Rothwell
wrote:
>
> After merging the mmc tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
>
> ERROR (phandle_references): Reference to non-existent node or label
> "pinctrl_usdhc4_1"
>
> ERROR: Input tree
On Friday, December 13, 2013 03:40:34 PM Tejun Heo wrote:
> Hello,
>
> So, this is the laughable workaround that I came up with. Seriously,
> this is tragic. :(
>
> Thanks.
>
> --- 8< ---
> Freezable kthreads and workqueues are fundamentally problematic in
> that they effectively
On Sunday, December 15, 2013 08:21:36 AM Nigel Cunningham wrote:
> Hi.
>
> On 15/12/13 07:36, Tejun Heo wrote:
> > On Sat, Dec 14, 2013 at 03:31:21PM -0500, Tejun Heo wrote:
> >> So, all this is about hibernation? Does that mean that it's safe to
> >> unfreeze before invoking resume? ie. we
On Saturday, December 14, 2013 03:31:21 PM Tejun Heo wrote:
> Hello, Nigel.
>
> On Sat, Dec 14, 2013 at 10:15:21AM +1100, Nigel Cunningham wrote:
> > My understanding is that the point is ensuring that - particularly
> > in the case of hibernation - we don't cause filesystem corruption by
> >
Hi all,
Today's linux-next merge of the device-mapper tree got a conflict in
drivers/md/dm-thin.c between commit 4f024f3797c4 ("block: Abstract out
bvec iterator") from the block tree and commit 1d8b40855c42 ("dm thin:
requeue bios to DM core if may_requeue_bios and in read-only mode") from
the
Hi Sander,
On Mon, Dec 16, 2013 at 11:56 PM, Sander Eikelenboom
wrote:
>
> Monday, December 16, 2013, 12:37:47 PM, you wrote:
>
>> On 12/16/2013 12:22 PM, Sander Eikelenboom wrote:
>>>
>>> Wednesday, December 11, 2013, 7:38:50 PM, you wrote:
>>>
On Wed, Dec 11, 2013 at 7:11 PM, Sander
Hi,
On Tue, Dec 17, 2013 at 02:31:00AM +0100, Apelete Seketeli wrote:
> On 16-Dec-13, Felipe Balbi wrote:
> > On Sat, Dec 14, 2013 at 04:48:38AM +0100, Apelete Seketeli wrote:
> > > JZ4740 USB Device Controller is not OTG compatible and does not have
> > > DEVCTL
> > > register in silicon.
> > >
Dear RT Folks,
I'm pleased to announce the 3.4.72-rt90 stable release.
You can get this release via the git tree at:
git://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-stable-rt.git
branch: v3.4-rt
Head SHA1: 691eae354832e65db69742765fc5c20e9ffbb5ee
Or to build 3.4.72-rt90
Dear RT Folks,
I'm pleased to announce the 3.8.13.13-rt26 stable release.
You can get this release via the git tree at:
git://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-stable-rt.git
branch: v3.8-rt
Head SHA1: 97e7e161945d7fa1c3641d6c2f7ec1e7ef7d2eb8
Or to build 3.8.13.13-rt26
1 - 100 of 1446 matches
Mail list logo
