This series of patches arise from discovering that:
ipvsadm --start-daemon backup --mcast-group IPv6_address ...
would always fail.
The first patch resolves the problem. The second and third patches are
optimizations that were noticed while investigating the original problem.
The fourth patch
This series of patches arise from discovering that:
ipvsadm --start-daemon backup --mcast-group IPv6_address ...
would always fail.
The first patch resolves the problem. The second and third patches are
optimizations that were noticed while investigating the original problem.
The fourth patch
Move the block testing result < 0 to avoid the test immediately
after setting result = 0
Signed-off-by: Quentin Armitage
---
net/netfilter/ipvs/ip_vs_sync.c |8
1 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/net/netfilter/ipvs/ip_vs_sync.c
Move the block testing result < 0 to avoid the test immediately
after setting result = 0
Signed-off-by: Quentin Armitage
---
net/netfilter/ipvs/ip_vs_sync.c |8
1 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/net/netfilter/ipvs/ip_vs_sync.c
When using HEAD from
https://git.kernel.org/cgit/utils/kernel/ipvsadm/ipvsadm.git/,
the command:
ipvsadm --start-daemon backup --mcast-interface eth0.60 --mcast-group ff01::1:81
fails with the error message:
Argument list too long
whereas both:
ipvsadm --start-daemon master --mcast-interface
On 10/06/2016 11:51 PM, Krzysztof Kozlowski wrote:
On 06/10/2016 02:32 PM, Chris Lapa wrote:
From: Chris Lapa
Signed-off-by: Chris Lapa
---
.../devicetree/bindings/power/max8903-charger.txt | 30 ++
1 file changed, 30 insertions(+)
When using HEAD from
https://git.kernel.org/cgit/utils/kernel/ipvsadm/ipvsadm.git/,
the command:
ipvsadm --start-daemon backup --mcast-interface eth0.60 --mcast-group ff01::1:81
fails with the error message:
Argument list too long
whereas both:
ipvsadm --start-daemon master --mcast-interface
On 10/06/2016 11:51 PM, Krzysztof Kozlowski wrote:
On 06/10/2016 02:32 PM, Chris Lapa wrote:
From: Chris Lapa
Signed-off-by: Chris Lapa
---
.../devicetree/bindings/power/max8903-charger.txt | 30 ++
1 file changed, 30 insertions(+)
create mode 100644
Optimise starting sync daemons by using the result of the first call to
__dev_get_by_name() and pass the result or ifindex to subsequent functions
to avoid them having to call __dev_get_by_name() again.
Signed-off-by: Quentin Armitage
---
net/netfilter/ipvs/ip_vs_sync.c
When other settings are changed in the socket it is locked, so
lock the socket before setting SK_CAN_REUSE.
Signed-off-by: Quentin Armitage
---
net/netfilter/ipvs/ip_vs_sync.c |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git
Optimise starting sync daemons by using the result of the first call to
__dev_get_by_name() and pass the result or ifindex to subsequent functions
to avoid them having to call __dev_get_by_name() again.
Signed-off-by: Quentin Armitage
---
net/netfilter/ipvs/ip_vs_sync.c | 66
When other settings are changed in the socket it is locked, so
lock the socket before setting SK_CAN_REUSE.
Signed-off-by: Quentin Armitage
---
net/netfilter/ipvs/ip_vs_sync.c |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/net/netfilter/ipvs/ip_vs_sync.c
On Tue, Jun 7, 2016 at 9:47 AM, Stephen Boyd wrote:
> From: Vikram Mulukutla
>
> Some low memory systems with complex peripherals cannot afford to
> have the relatively large firmware images taking up valuable
> memory during suspend and resume.
On Tue, Jun 7, 2016 at 9:47 AM, Stephen Boyd wrote:
> From: Vikram Mulukutla
>
> Some low memory systems with complex peripherals cannot afford to
> have the relatively large firmware images taking up valuable
> memory during suspend and resume. Change the internal
> implementation of
Signed-off-by: Guolin Yang
Signed-off-by: Shrikrishna Khare
---
drivers/net/vmxnet3/vmxnet3_defs.h | 22 +-
1 file changed, 21 insertions(+), 1 deletion(-)
diff --git a/drivers/net/vmxnet3/vmxnet3_defs.h
Signed-off-by: Guolin Yang
Signed-off-by: Shrikrishna Khare
---
drivers/net/vmxnet3/vmxnet3_defs.h | 22 +-
1 file changed, 21 insertions(+), 1 deletion(-)
diff --git a/drivers/net/vmxnet3/vmxnet3_defs.h
b/drivers/net/vmxnet3/vmxnet3_defs.h
index 8345e0c..a26a69d 100644
Hi Krzysztof,
Appreciate the feedback, working on the fixups you pointed out now.
I'll ensure I send v3 of the patches to the actual maintainers and not
just the list. Still getting my head around the lists mechanics :)
Thanks,
Chris:
On 11/06/2016 12:02 AM, Krzysztof Kozlowski wrote:
On
Signed-off-by: Sriram Rangarajan
Signed-off-by: Shrikrishna Khare
---
drivers/net/vmxnet3/vmxnet3_defs.h| 12 +++-
drivers/net/vmxnet3/vmxnet3_drv.c | 55 ++-
drivers/net/vmxnet3/vmxnet3_ethtool.c | 9 +++---
Hi Krzysztof,
Appreciate the feedback, working on the fixups you pointed out now.
I'll ensure I send v3 of the patches to the actual maintainers and not
just the list. Still getting my head around the lists mechanics :)
Thanks,
Chris:
On 11/06/2016 12:02 AM, Krzysztof Kozlowski wrote:
On
Signed-off-by: Sriram Rangarajan
Signed-off-by: Shrikrishna Khare
---
drivers/net/vmxnet3/vmxnet3_defs.h| 12 +++-
drivers/net/vmxnet3/vmxnet3_drv.c | 55 ++-
drivers/net/vmxnet3/vmxnet3_ethtool.c | 9 +++---
drivers/net/vmxnet3/vmxnet3_int.h |
On 06/13/2016 11:36 AM, Ben Hutchings wrote:
This is the start of the stable review cycle for the 3.16.36 release.
There are 114 patches in this series, which will be posted as responses
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be
On 06/13/2016 11:36 AM, Ben Hutchings wrote:
This is the start of the stable review cycle for the 3.16.36 release.
There are 114 patches in this series, which will be posted as responses
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be
This patchset upgrades vmxnet3 to version 3.
Changes in v2:
- Following patch is updated. See that patch for details:
Driver: Vmxnet3: Add support for get_coalesce, set_coalesce ethtool
Changes in v3:
- fix subject line to use vmxnet3: instead of Driver:Vmxnet3
- resubmit when net-next is
On Mon, May 30, 2016 at 01:15:29PM +0200, Johannes Thumshirn wrote:
> On Tue, May 10, 2016 at 12:39:43PM +0200, Johannes Thumshirn wrote:
> > Hi Greg,
> >
> > Here are two additional fixes for MCB from me, which would be good to have
> > in
> > v4.7.
> >
> > One fixes a panic when doing a
Hi Herbert,
Today's linux-next merge of the crypto tree got a conflict in:
arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi
between commit:
fab6b48ccab3 ("ARM64: dts: amlogic: Add hiu and periphs buses")
from the amlogic tree and commit:
e434cd2dc4de ("ARM64: dts: meson-gxbb: Add Hardware
This patchset upgrades vmxnet3 to version 3.
Changes in v2:
- Following patch is updated. See that patch for details:
Driver: Vmxnet3: Add support for get_coalesce, set_coalesce ethtool
Changes in v3:
- fix subject line to use vmxnet3: instead of Driver:Vmxnet3
- resubmit when net-next is
On Mon, May 30, 2016 at 01:15:29PM +0200, Johannes Thumshirn wrote:
> On Tue, May 10, 2016 at 12:39:43PM +0200, Johannes Thumshirn wrote:
> > Hi Greg,
> >
> > Here are two additional fixes for MCB from me, which would be good to have
> > in
> > v4.7.
> >
> > One fixes a panic when doing a
Hi Herbert,
Today's linux-next merge of the crypto tree got a conflict in:
arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi
between commit:
fab6b48ccab3 ("ARM64: dts: amlogic: Add hiu and periphs buses")
from the amlogic tree and commit:
e434cd2dc4de ("ARM64: dts: meson-gxbb: Add Hardware
Hi David,
I have additional comments on this.
On Thu, 2 Jun 2016 23:26:19 -0400
David Long wrote:
> +/*
> + * The D-flag (Debug mask) is set (masked) upon deug exception entry.
deug -> debug
> + * Kprobes needs to clear (unmask) D-flag -ONLY- in case of recursive
> + *
Hi David,
I have additional comments on this.
On Thu, 2 Jun 2016 23:26:19 -0400
David Long wrote:
> +/*
> + * The D-flag (Debug mask) is set (masked) upon deug exception entry.
deug -> debug
> + * Kprobes needs to clear (unmask) D-flag -ONLY- in case of recursive
> + * probe i.e. when probe
On Tue, Jun 14, 2016 at 12:53 AM, Kees Cook wrote:
> On Mon, Jun 13, 2016 at 3:15 PM, Rafael J. Wysocki wrote:
>> On Monday, June 13, 2016 02:58:57 PM Kees Cook wrote:
>>> On Mon, Jun 13, 2016 at 6:42 AM, Rafael J. Wysocki
>>>
On Tue, Jun 14, 2016 at 12:53 AM, Kees Cook wrote:
> On Mon, Jun 13, 2016 at 3:15 PM, Rafael J. Wysocki wrote:
>> On Monday, June 13, 2016 02:58:57 PM Kees Cook wrote:
>>> On Mon, Jun 13, 2016 at 6:42 AM, Rafael J. Wysocki
>>> wrote:
>>> > From: Rafael J. Wysocki
>>> >
[cut]
>>>
>>>
Hi,
[auto build test ERROR on gpio/for-next]
[also build test ERROR on v4.7-rc3 next-20160609]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
On Tue, Jun 07, 2016 at 07:20:33PM +0100, Ben Dooks wrote:
> The helper function usb_of_get_child_node() is defined in the
> header but this was not included. Fix the warning
> about usb_of_get_child_node() not being declared by adding the
> right include. Fixes:
>
> drivers/usb/core/of.c:31:20:
On Tue, Jun 07, 2016 at 07:20:33PM +0100, Ben Dooks wrote:
> The helper function usb_of_get_child_node() is defined in the
> header but this was not included. Fix the warning
> about usb_of_get_child_node() not being declared by adding the
> right include. Fixes:
>
> drivers/usb/core/of.c:31:20:
Hi,
[auto build test ERROR on gpio/for-next]
[also build test ERROR on v4.7-rc3 next-20160609]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
On 06/13/16 at 04:08pm, Thiago Jung Bauermann wrote:
> Hello Dave,
>
> Thanks for the quick review and for your comments.
>
> I'll separate the change to add arch_walk_system_ram and the change to add
> kexec_locate_mem_hole into different patches, and add error handling for
> KEXEC_ON_CRASH.
On 06/13/16 at 04:08pm, Thiago Jung Bauermann wrote:
> Hello Dave,
>
> Thanks for the quick review and for your comments.
>
> I'll separate the change to add arch_walk_system_ram and the change to add
> kexec_locate_mem_hole into different patches, and add error handling for
> KEXEC_ON_CRASH.
On Mon, 13 Jun 2016 19:20:19 -0400
Steven Rostedt wrote:
> On Mon, 13 Jun 2016 19:13:45 -0400
> Steven Rostedt wrote:
>
>
> > > # cd /sys/kernel/debug/tracing
> > > # echo p copy_user_enhanced_fast_string+5 > kprobe_events
> > > # echo 1 >
On Mon, 13 Jun 2016 19:20:19 -0400
Steven Rostedt wrote:
> On Mon, 13 Jun 2016 19:13:45 -0400
> Steven Rostedt wrote:
>
>
> > > # cd /sys/kernel/debug/tracing
> > > # echo p copy_user_enhanced_fast_string+5 > kprobe_events
> > > # echo 1 > events/kprobes/enable
> > >
> > > And you'll
On (06/13/16 12:37), Minchan Kim wrote:
>
> Please fold it to zsmalloc: page migration support.
I like the change and the removal of get_first_obj_offset().
thanks.
-ss
On (06/13/16 12:37), Minchan Kim wrote:
>
> Please fold it to zsmalloc: page migration support.
I like the change and the removal of get_first_obj_offset().
thanks.
-ss
-on-Quark/20160613-220941
config: x86_64-randconfig-s3-06140616 (attached as .config)
compiler: gcc-6 (Debian 6.1.1-1) 6.1.1 20160430
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by >>):
drivers/built-in.o: In fu
-on-Quark/20160613-220941
config: x86_64-randconfig-s3-06140616 (attached as .config)
compiler: gcc-6 (Debian 6.1.1-1) 6.1.1 20160430
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by >>):
drivers/built-in.o: In fu
On Thu, Jun 09, 2016 at 05:56:56PM +0100, Kieran Bingham wrote:
> Appologies for the resend, I very cleverly sent this cover letter detailing
> the
> dependencies only to my e-mail address. And I already know the dependencies!
>
> Following two patches are the same, sorry for the noise.
>
>
On Thu, Jun 09, 2016 at 05:56:56PM +0100, Kieran Bingham wrote:
> Appologies for the resend, I very cleverly sent this cover letter detailing
> the
> dependencies only to my e-mail address. And I already know the dependencies!
>
> Following two patches are the same, sorry for the noise.
>
>
在 2016/6/14 8:43, Doug Anderson 写道:
Hi,
On Mon, Jun 13, 2016 at 5:14 PM, Shawn Lin wrote:
It's broken when reading capabilities reg on RK3399 platform
which means you should get it via clk framework. But you should consider
the non-broken case.
I'm afraid I don't
在 2016/6/14 8:43, Doug Anderson 写道:
Hi,
On Mon, Jun 13, 2016 at 5:14 PM, Shawn Lin wrote:
It's broken when reading capabilities reg on RK3399 platform
which means you should get it via clk framework. But you should consider
the non-broken case.
I'm afraid I don't understand. Can you
Hi Trond,
After merging the nfs tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
fs/nfs/direct.c: In function 'nfs_direct_write_reschedule':
fs/nfs/direct.c:652:32: error: 'struct pnfs_ds_commit_info' has no member named
'nbuckets'
for (i = 0; i <
Hi Trond,
After merging the nfs tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
fs/nfs/direct.c: In function 'nfs_direct_write_reschedule':
fs/nfs/direct.c:652:32: error: 'struct pnfs_ds_commit_info' has no member named
'nbuckets'
for (i = 0; i <
Shawn,
On Mon, Jun 13, 2016 at 5:24 PM, Shawn Lin wrote:
>>> From the public Arasan datasheet they seem to indicate +/- 15 MHz is
>>
>> sane. Does that sound OK? Presuming that all of your numbers
>> (50/100/150/200) are centers, that means that we could support clock
Shawn,
On Mon, Jun 13, 2016 at 5:24 PM, Shawn Lin wrote:
>>> From the public Arasan datasheet they seem to indicate +/- 15 MHz is
>>
>> sane. Does that sound OK? Presuming that all of your numbers
>> (50/100/150/200) are centers, that means that we could support clock
>> rates of:
>>
>> 35 MHz
On Mon, 13 Jun 2016 11:22:47 -0400
David Long wrote:
> On 06/13/2016 02:50 AM, Masami Hiramatsu wrote:
> > On Mon, 13 Jun 2016 00:10:29 -0400
> > David Long wrote:
> >
> ---
> arch/arm64/Kconfig | 1 +
>
On Mon, 13 Jun 2016 11:22:47 -0400
David Long wrote:
> On 06/13/2016 02:50 AM, Masami Hiramatsu wrote:
> > On Mon, 13 Jun 2016 00:10:29 -0400
> > David Long wrote:
> >
> ---
> arch/arm64/Kconfig | 1 +
> arch/arm64/include/asm/debug-monitors.h | 5 +
This patch to add a generic PHY driver for rockchip PCIe PHY.
Access the PHY via registers provided by GRF (general register
files) module.
Signed-off-by: Shawn Lin
---
Changes in v2: None
drivers/phy/Kconfig | 7 +
drivers/phy/Makefile| 1
This patch to add a generic PHY driver for rockchip PCIe PHY.
Access the PHY via registers provided by GRF (general register
files) module.
Signed-off-by: Shawn Lin
---
Changes in v2: None
drivers/phy/Kconfig | 7 +
drivers/phy/Makefile| 1 +
This patch adds a binding that describes the Rockchip PCIe PHY
found on Rockchip SoCs PCIe interface.
Signed-off-by: Shawn Lin
---
Changes in v2:
- add clk and reset description
- remove unit-address
.../devicetree/bindings/phy/rockchip-pcie-phy.txt | 32
This patch adds a binding that describes the Rockchip PCIe PHY
found on Rockchip SoCs PCIe interface.
Signed-off-by: Shawn Lin
---
Changes in v2:
- add clk and reset description
- remove unit-address
.../devicetree/bindings/phy/rockchip-pcie-phy.txt | 32 ++
1 file
Hi,
On Mon, Jun 13, 2016 at 5:14 PM, Shawn Lin wrote:
>>> It's broken when reading capabilities reg on RK3399 platform
>>> which means you should get it via clk framework. But you should consider
>>> the non-broken case.
>>
>>
>> I'm afraid I don't understand. Can you
Hi,
On Mon, Jun 13, 2016 at 5:14 PM, Shawn Lin wrote:
>>> It's broken when reading capabilities reg on RK3399 platform
>>> which means you should get it via clk framework. But you should consider
>>> the non-broken case.
>>
>>
>> I'm afraid I don't understand. Can you elaborate? Are you saying
Hi,
[auto build test ERROR on gpio/for-next]
[also build test ERROR on v4.7-rc3 next-20160609]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
Hi,
[auto build test ERROR on gpio/for-next]
[also build test ERROR on v4.7-rc3 next-20160609]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
在 2016/6/14 7:04, Douglas Anderson 写道:
There's no reason to store the return value of rockchip_emmc_phy_power()
in a variable nor to check it. Just return it.
Signed-off-by: Douglas Anderson
---
Changes in v2:
- Move code cleanup before set phyctrl_frqsel based on card
在 2016/6/14 7:04, Douglas Anderson 写道:
There's no reason to store the return value of rockchip_emmc_phy_power()
in a variable nor to check it. Just return it.
Signed-off-by: Douglas Anderson
---
Changes in v2:
- Move code cleanup before set phyctrl_frqsel based on card clock (Shawn)
Looks
在 2016/6/14 7:04, Douglas Anderson 写道:
As can be seen in Arasan's datasheet [1] there are several "corecfg"
settings in their SDHCI IP Block that are supposed to be controlled by
software. Although the datasheet referenced is a bit vague about how to
access corecfg, in Figure 5 you can see that
在 2016/6/14 7:04, Douglas Anderson 写道:
As can be seen in Arasan's datasheet [1] there are several "corecfg"
settings in their SDHCI IP Block that are supposed to be controlled by
software. Although the datasheet referenced is a bit vague about how to
access corecfg, in Figure 5 you can see that
在 2016/6/14 7:04, Douglas Anderson 写道:
In commit 802ac39a5566 ("mmc: sdhci-of-arasan: fix set_clock when a phy
is supported") we added code to power the PHY off and on whenever the
clock was changed but we avoided doing the power cycle code when the
clock was low speed. Let's now do it always.
在 2016/6/14 7:04, Douglas Anderson 写道:
In commit 802ac39a5566 ("mmc: sdhci-of-arasan: fix set_clock when a phy
is supported") we added code to power the PHY off and on whenever the
clock was changed but we avoided doing the power cycle code when the
clock was low speed. Let's now do it always.
在 2016/6/14 7:04, Douglas Anderson 写道:
Previous PHY code waited a fixed amount of time for the DLL to lock at
power on time. Unfortunately, the time for the DLL to lock is actually
a bit more dynamic and can be longer if the card clock is slower.
Instead of waiting a fixed 30 us, let's now
在 2016/6/14 7:04, Douglas Anderson 写道:
Previous PHY code waited a fixed amount of time for the DLL to lock at
power on time. Unfortunately, the time for the DLL to lock is actually
a bit more dynamic and can be longer if the card clock is slower.
Instead of waiting a fixed 30 us, let's now
在 2016/6/14 7:05, Doug Anderson 写道:
Shawn,
On Mon, Jun 13, 2016 at 1:54 AM, Shawn Lin wrote:
On 2016/6/8 6:44, Douglas Anderson wrote:
The "phyctrl_frqsel" is described in the Arasan datasheet [1] as "the
frequency range of DLL operation". Although the Rockchip
在 2016/6/14 7:05, Doug Anderson 写道:
Shawn,
On Mon, Jun 13, 2016 at 1:54 AM, Shawn Lin wrote:
On 2016/6/8 6:44, Douglas Anderson wrote:
The "phyctrl_frqsel" is described in the Arasan datasheet [1] as "the
frequency range of DLL operation". Although the Rockchip variant of
this PHY has
On Tue, Jun 14, 2016 at 2:06 AM, Jacob Pan
wrote:
> On Mon, 13 Jun 2016 23:56:18 +0200
> "Rafael J. Wysocki" wrote:
>
>> On Monday, June 13, 2016 11:32:10 PM Rafael J. Wysocki wrote:
>> > On Monday, May 23, 2016 09:45:42 AM Jacob Pan wrote:
>> >
On Tue, Jun 14, 2016 at 2:06 AM, Jacob Pan
wrote:
> On Mon, 13 Jun 2016 23:56:18 +0200
> "Rafael J. Wysocki" wrote:
>
>> On Monday, June 13, 2016 11:32:10 PM Rafael J. Wysocki wrote:
>> > On Monday, May 23, 2016 09:45:42 AM Jacob Pan wrote:
>> > > SKX RAPL interface is similar to HSX/BDX.
>> > >
Hi,
[auto build test ERROR on gpio/for-next]
[also build test ERROR on v4.7-rc3 next-20160609]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
Hi,
[auto build test ERROR on gpio/for-next]
[also build test ERROR on v4.7-rc3 next-20160609]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
Hi,
[auto build test ERROR on gpio/for-next]
[also build test ERROR on v4.7-rc3 next-20160609]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
Hi,
[auto build test ERROR on gpio/for-next]
[also build test ERROR on v4.7-rc3 next-20160609]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
Add ro_after_init support for modules by adding a new page-aligned section
in the module layout (after rodata) for ro_after_init data and enabling RO
protection for that section after module init runs.
Signed-off-by: Jessica Yu
---
include/linux/module.h | 2 ++
Add ro_after_init support for modules by adding a new page-aligned section
in the module layout (after rodata) for ro_after_init data and enabling RO
protection for that section after module init runs.
Signed-off-by: Jessica Yu
---
include/linux/module.h | 2 ++
include/uapi/linux/elf.h | 1
Hi,
This patch adds ro_after_init support for modules by adding an additional
page-aligned section in the module layout. This new ro_after_init section
sits between rodata and writable data.
So, the new module layout looks like:
[text] [rodata] [ro_after_init] [writable data]
RO after init
Hi,
This patch adds ro_after_init support for modules by adding an additional
page-aligned section in the module layout. This new ro_after_init section
sits between rodata and writable data.
So, the new module layout looks like:
[text] [rodata] [ro_after_init] [writable data]
RO after init
在 2016/6/14 7:06, Doug Anderson 写道:
Shawn,
On Mon, Jun 13, 2016 at 1:36 AM, Shawn Lin wrote:
在 2016/6/8 6:44, Douglas Anderson 写道:
In the the earlier change in this series ("Documentation: mmc:
sdhci-of-arasan: Add soc-ctl-syscon for corecfg regs") we can see the
在 2016/6/14 7:06, Doug Anderson 写道:
Shawn,
On Mon, Jun 13, 2016 at 1:36 AM, Shawn Lin wrote:
在 2016/6/8 6:44, Douglas Anderson 写道:
In the the earlier change in this series ("Documentation: mmc:
sdhci-of-arasan: Add soc-ctl-syscon for corecfg regs") we can see the
mechansim for specifying a
On Mon, 13 Jun 2016 23:56:18 +0200
"Rafael J. Wysocki" wrote:
> On Monday, June 13, 2016 11:32:10 PM Rafael J. Wysocki wrote:
> > On Monday, May 23, 2016 09:45:42 AM Jacob Pan wrote:
> > > SKX RAPL interface is similar to HSX/BDX.
> > >
> > > Signed-off-by: Jacob Pan
On Mon, 13 Jun 2016 23:56:18 +0200
"Rafael J. Wysocki" wrote:
> On Monday, June 13, 2016 11:32:10 PM Rafael J. Wysocki wrote:
> > On Monday, May 23, 2016 09:45:42 AM Jacob Pan wrote:
> > > SKX RAPL interface is similar to HSX/BDX.
> > >
> > > Signed-off-by: Jacob Pan
> > > ---
> > >
Denverton micro server is Atom based but RAPL interface
is compatible with Core based CPUs.
Signed-off-by: Jacob Pan
---
drivers/powercap/intel_rapl.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/powercap/intel_rapl.c b/drivers/powercap/intel_rapl.c
Denverton micro server is Atom based but RAPL interface
is compatible with Core based CPUs.
Signed-off-by: Jacob Pan
---
drivers/powercap/intel_rapl.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/powercap/intel_rapl.c b/drivers/powercap/intel_rapl.c
index 4aa8168..7977fbf 100644
On Mon, Jun 13, 2016 at 4:59 PM, Kani, Toshimitsu wrote:
> On Mon, 2016-06-13 at 16:18 -0700, Dan Williams wrote:
>> Thanks Toshi!
>>
>> On Mon, Jun 13, 2016 at 3:21 PM, Toshi Kani wrote:
>> >
>> > This patch-set adds DAX support to device-mapper dm-linear
On Mon, Jun 13, 2016 at 4:59 PM, Kani, Toshimitsu wrote:
> On Mon, 2016-06-13 at 16:18 -0700, Dan Williams wrote:
>> Thanks Toshi!
>>
>> On Mon, Jun 13, 2016 at 3:21 PM, Toshi Kani wrote:
>> >
>> > This patch-set adds DAX support to device-mapper dm-linear devices
>> > used by LVM. It works
On Mon, 2016-06-13 at 16:18 -0700, Dan Williams wrote:
> Thanks Toshi!
>
> On Mon, Jun 13, 2016 at 3:21 PM, Toshi Kani wrote:
> >
> > This patch-set adds DAX support to device-mapper dm-linear devices
> > used by LVM. It works with LVM commands as follows:
> > - Creation
On Mon, 2016-06-13 at 16:18 -0700, Dan Williams wrote:
> Thanks Toshi!
>
> On Mon, Jun 13, 2016 at 3:21 PM, Toshi Kani wrote:
> >
> > This patch-set adds DAX support to device-mapper dm-linear devices
> > used by LVM. It works with LVM commands as follows:
> > - Creation of a logical volume
On Mon, Jun 13, 2016 at 4:53 PM, Kees Cook wrote:
> On Mon, Jun 13, 2016 at 4:40 PM, Stephen Rothwell
> wrote:
>> Hi Kees,
>>
>> As of today, there are four duplicate patches (different commits)
>> in the kspp and kbuild trees.
>>
>> Shared library
On Mon, Jun 13, 2016 at 4:53 PM, Kees Cook wrote:
> On Mon, Jun 13, 2016 at 4:40 PM, Stephen Rothwell
> wrote:
>> Hi Kees,
>>
>> As of today, there are four duplicate patches (different commits)
>> in the kspp and kbuild trees.
>>
>> Shared library support
>> GCC plugin infrastructure
>>
On Mon, Jun 13, 2016 at 4:40 PM, Stephen Rothwell wrote:
> Hi Kees,
>
> As of today, there are four duplicate patches (different commits)
> in the kspp and kbuild trees.
>
> Shared library support
> GCC plugin infrastructure
> Add Cyclomatic complexity GCC plugin
>
On Mon, Jun 13, 2016 at 4:40 PM, Stephen Rothwell wrote:
> Hi Kees,
>
> As of today, there are four duplicate patches (different commits)
> in the kspp and kbuild trees.
>
> Shared library support
> GCC plugin infrastructure
> Add Cyclomatic complexity GCC plugin
> Add sancov plugin
>
>
Hi Michal,
On Tue, Jun 14, 2016 at 3:46 AM, Michal Suchanek wrote:
> Signed-off-by: Michal Suchanek
> ---
> .../devicetree/bindings/spi/spi-sun4i.txt | 21 ++-
> .../devicetree/bindings/spi/spi-sun6i.txt | 24
>
Hi Michal,
On Tue, Jun 14, 2016 at 3:46 AM, Michal Suchanek wrote:
> Signed-off-by: Michal Suchanek
> ---
> .../devicetree/bindings/spi/spi-sun4i.txt | 21 ++-
> .../devicetree/bindings/spi/spi-sun6i.txt | 24
> --
> 2 files changed, 11
Xing,
On Sun, Jun 12, 2016 at 8:10 PM, Xing Zheng wrote:
> Hi Doug,
>
>
> On 2016年06月13日 05:32, Doug Anderson wrote:
>>
>> Xing,
>>
>> On Sun, Jun 12, 2016 at 2:48 AM, Xing Zheng
>> wrote:
>>>
>>> The pclk_vio_grf supply power for GRF IOs, if
Xing,
On Sun, Jun 12, 2016 at 8:10 PM, Xing Zheng wrote:
> Hi Doug,
>
>
> On 2016年06月13日 05:32, Doug Anderson wrote:
>>
>> Xing,
>>
>> On Sun, Jun 12, 2016 at 2:48 AM, Xing Zheng
>> wrote:
>>>
>>> The pclk_vio_grf supply power for GRF IOs, if it is disabled, will
>>> cause abnormal operation of
201 - 300 of 2388 matches
Mail list logo