A /proc/sched_debug bug fix and a couple of other schedstats-related
cleanups.
Josh Poimboeuf (3):
sched/debug: fix /proc/sched_debug regression
sched/debug: always show nr_migrations
sched/debug: remove unnecessary CONFIG_SCHEDSTATS checks
kernel/sched/debug.c | 24
A /proc/sched_debug bug fix and a couple of other schedstats-related
cleanups.
Josh Poimboeuf (3):
sched/debug: fix /proc/sched_debug regression
sched/debug: always show nr_migrations
sched/debug: remove unnecessary CONFIG_SCHEDSTATS checks
kernel/sched/debug.c | 24
On Fri, 2016-06-03 at 15:02 -0500, Nishanth Menon wrote:
> In some functions, returning a -ve decimal value is actually a valid
> return condition when the function is returning a value, however, it
> can also be misused for returning an error value that should ideally
> be a valid error code
On Fri, Jun 03, 2016 at 10:23:07AM +0200, Boris Brezillon wrote:
> The PWM attached to a PWM regulator device might have been previously
> configured by the bootloader.
> Make sure the bootloader and linux config are in sync, and adjust the PWM
> config if that's not the case.
>
> Signed-off-by:
On Fri, Jun 03, 2016 at 10:23:07AM +0200, Boris Brezillon wrote:
> The PWM attached to a PWM regulator device might have been previously
> configured by the bootloader.
> Make sure the bootloader and linux config are in sync, and adjust the PWM
> config if that's not the case.
>
> Signed-off-by:
On Fri, 2016-06-03 at 15:02 -0500, Nishanth Menon wrote:
> In some functions, returning a -ve decimal value is actually a valid
> return condition when the function is returning a value, however, it
> can also be misused for returning an error value that should ideally
> be a valid error code
On Fri, Jun 03, 2016 at 05:10:18PM -0300, Daniel Bristot de Oliveira wrote:
| Currently, a schedule while atomic error prints the stack trace to the
| kernel log and the system continue running.
|
| Although it is possible to collect the kernel log messages and analyze
| it, often more
On Fri, Jun 03, 2016 at 05:10:18PM -0300, Daniel Bristot de Oliveira wrote:
| Currently, a schedule while atomic error prints the stack trace to the
| kernel log and the system continue running.
|
| Although it is possible to collect the kernel log messages and analyze
| it, often more
Example of a portable connector port for the BB_RELAY_4PORT cape
Signed-off-by: Pantelis Antoniou
---
arch/arm/boot/dts/am335x-bone-common.dtsi | 48 +++
1 file changed, 48 insertions(+)
diff --git
Example of a portable connector port for the BB_RELAY_4PORT cape
Signed-off-by: Pantelis Antoniou
---
arch/arm/boot/dts/am335x-bone-common.dtsi | 48 +++
1 file changed, 48 insertions(+)
diff --git a/arch/arm/boot/dts/am335x-bone-common.dtsi
On Fri, Jun 03, 2016 at 10:23:06AM +0200, Boris Brezillon wrote:
> The current logic will disable the PWM clk even if a PWM was left
> enabled by the bootloader (because it's controlling a critical device
> like a regulator for example).
> Keep the PWM clk enabled if at least one PWM is enabled to
On Fri, Jun 03, 2016 at 10:23:06AM +0200, Boris Brezillon wrote:
> The current logic will disable the PWM clk even if a PWM was left
> enabled by the bootloader (because it's controlling a critical device
> like a regulator for example).
> Keep the PWM clk enabled if at least one PWM is enabled to
Introducing the portable device tree based connector.
It is a method of describing an expansion connector in such a way
that the hardware definition for devices present on the connector
are portable between any board that has a hardware compatible connector.
The connector will maintain the
Update the DTS with the information required for defining the
P8/P9 connector of the beaglebone.
Signed-off-by: Pantelis Antoniou
---
arch/arm/boot/dts/am335x-bone-common.dtsi | 1630 +
1 file changed, 1630 insertions(+)
diff --git
Introducing the portable device tree based connector.
It is a method of describing an expansion connector in such a way
that the hardware definition for devices present on the connector
are portable between any board that has a hardware compatible connector.
The connector will maintain the
Update the DTS with the information required for defining the
P8/P9 connector of the beaglebone.
Signed-off-by: Pantelis Antoniou
---
arch/arm/boot/dts/am335x-bone-common.dtsi | 1630 +
1 file changed, 1630 insertions(+)
diff --git
This patchset introduces a portable device tree based connector.
It allows definition of a connector in a portable format so that
hardware expansion boards that utilize it can use the same
DT hardware definitions unchanged for all the boards that
have the same kind of connector.
It completely
This patchset introduces a portable device tree based connector.
It allows definition of a connector in a portable format so that
hardware expansion boards that utilize it can use the same
DT hardware definitions unchanged for all the boards that
have the same kind of connector.
It completely
On Fri, Jun 03, 2016 at 10:23:04AM +0200, Boris Brezillon wrote:
> Implement the ->apply() function to add support for atomic update.
>
> Signed-off-by: Boris Brezillon
> Tested-by: Heiko Stuebner
> ---
> drivers/pwm/pwm-rockchip.c | 84
>
On Fri, Jun 03, 2016 at 10:23:04AM +0200, Boris Brezillon wrote:
> Implement the ->apply() function to add support for atomic update.
>
> Signed-off-by: Boris Brezillon
> Tested-by: Heiko Stuebner
> ---
> drivers/pwm/pwm-rockchip.c | 84
> --
> 1
On Fri, 20 May 2016 16:39:36 +0300
Jani Nikula wrote:
> Add an extension to handle kernel-doc directives, to call kernel-doc
> according to the arguments and parameters given to the reStructuredText
> directive.
>
> The syntax for the kernel-doc directive is:
>
> ..
On Fri, 20 May 2016 16:39:36 +0300
Jani Nikula wrote:
> Add an extension to handle kernel-doc directives, to call kernel-doc
> according to the arguments and parameters given to the reStructuredText
> directive.
>
> The syntax for the kernel-doc directive is:
>
> .. kernel-doc:: FILENAME
>
Add check to power_supply_read_temp() to only use the power_supply
get_property() callback if the use_cnt is > 0. The use_cnt will
be incremented at the end of __power_supply_register, so this will
block to case where get_property can be called before the supply
is fully registered. This fixes the
Add check to power_supply_read_temp() to only use the power_supply
get_property() callback if the use_cnt is > 0. The use_cnt will
be incremented at the end of __power_supply_register, so this will
block to case where get_property can be called before the supply
is fully registered. This fixes the
On Fri, Jun 3, 2016 at 4:24 PM, Richard Guy Briggs wrote:
> On 16/06/03, Paul Moore wrote:
>> On Wed, Jun 1, 2016 at 6:50 PM, Richard Guy Briggs wrote:
>> > RFE: add additional fields for use in audit filter exclude rules
>> >
On Fri, Jun 3, 2016 at 4:24 PM, Richard Guy Briggs wrote:
> On 16/06/03, Paul Moore wrote:
>> On Wed, Jun 1, 2016 at 6:50 PM, Richard Guy Briggs wrote:
>> > RFE: add additional fields for use in audit filter exclude rules
>> > https://github.com/linux-audit/audit-kernel/issues/5
>> >
>> >
Hi,
Just noticed a few things:
On Fri, Jun 03, 2016 at 10:23:03AM +0200, Boris Brezillon wrote:
> The current logic will disable the PWM clk even if the PWM was left
> enabled by the bootloader (because it's controlling a critical device
> like a regulator for example).
> Keep the PWM clk
Hi,
Just noticed a few things:
On Fri, Jun 03, 2016 at 10:23:03AM +0200, Boris Brezillon wrote:
> The current logic will disable the PWM clk even if the PWM was left
> enabled by the bootloader (because it's controlling a critical device
> like a regulator for example).
> Keep the PWM clk
On Fri, 3 Jun 2016 22:24:03 +0200
Daniel Vetter wrote:
> > This is maybe a job for a separate tool. A related issue is the (fairly
> > frequent) "oh look, none of the comments in $FILE are being used"
> > realization that seems to happen fairly often. It would be nice
On Fri, 3 Jun 2016 22:24:03 +0200
Daniel Vetter wrote:
> > This is maybe a job for a separate tool. A related issue is the (fairly
> > frequent) "oh look, none of the comments in $FILE are being used"
> > realization that seems to happen fairly often. It would be nice to check
> > for that,
In certain cases it makes sense to create cascaded GPIO which
are not real GPIOs, merely point to the real backend GPIO chip.
In order to support this, cascaded of_xlate lookup need to be
performed.
For example let's take a connector that we want to abstract
having two GPIO pins from different
Cascaded GPIO chips modify gpiospec to pass along
the next gpio chip to match against. Remove the const
specifier to make it possible.
Change all in kernel users also.
Signed-off-by: Pantelis Antoniou
---
drivers/gpio/gpio-brcmstb.c | 2 +-
In certain cases it makes sense to create cascaded GPIO which
are not real GPIOs, merely point to the real backend GPIO chip.
In order to support this, cascaded of_xlate lookup need to be
performed.
For example let's take a connector that we want to abstract
having two GPIO pins from different
Cascaded GPIO chips modify gpiospec to pass along
the next gpio chip to match against. Remove the const
specifier to make it possible.
Change all in kernel users also.
Signed-off-by: Pantelis Antoniou
---
drivers/gpio/gpio-brcmstb.c | 2 +-
drivers/gpio/gpio-davinci.c | 2 +-
These two patches enable GPIO cascades where a match may be
retried until the finalr real GPIO is located.
The first patch removes the const specifier from gpiospec at of_xlate(),
while the second introduces the new method of_gpiochip_find() that
performs the cascade operation.
Pantelis Antoniou
These two patches enable GPIO cascades where a match may be
retried until the finalr real GPIO is located.
The first patch removes the const specifier from gpiospec at of_xlate(),
while the second introduces the new method of_gpiochip_find() that
performs the cascade operation.
Pantelis Antoniou
On 16/06/03, Paul Moore wrote:
> On Wed, Jun 1, 2016 at 6:50 PM, Richard Guy Briggs wrote:
> > RFE: add additional fields for use in audit filter exclude rules
> > https://github.com/linux-audit/audit-kernel/issues/5
> >
> > Re-factor audit_filter_type() to use
On Fri, Jun 3, 2016 at 10:16 PM, Jonathan Corbet wrote:
>
>> Second, we lose support for the !C docproc directive to check
>> that all kernel-doc comments in a file are used. This is probably
>> something we'd like to have back in the future, but at this time I think
>> it's an
On Fri, Jun 3, 2016 at 10:16 PM, Jonathan Corbet wrote:
>
>> Second, we lose support for the !C docproc directive to check
>> that all kernel-doc comments in a file are used. This is probably
>> something we'd like to have back in the future, but at this time I think
>> it's an acceptable
On 16/06/03, Paul Moore wrote:
> On Wed, Jun 1, 2016 at 6:50 PM, Richard Guy Briggs wrote:
> > RFE: add additional fields for use in audit filter exclude rules
> > https://github.com/linux-audit/audit-kernel/issues/5
> >
> > Re-factor audit_filter_type() to use audit_filter_user_rules() to enable
Add regulators to the Tegra210 Smaug DTS file including
support for the max77620 PMIC.
Signed-off-by: Rhyland Klein
---
arch/arm64/boot/dts/nvidia/tegra210-smaug.dts | 350 ++
1 file changed, 350 insertions(+)
diff --git
Add regulators to the Tegra210 Smaug DTS file including
support for the max77620 PMIC.
Signed-off-by: Rhyland Klein
---
arch/arm64/boot/dts/nvidia/tegra210-smaug.dts | 350 ++
1 file changed, 350 insertions(+)
diff --git a/arch/arm64/boot/dts/nvidia/tegra210-smaug.dts
On Fri, Jun 03, 2016 at 10:23:02AM +0200, Boris Brezillon wrote:
> Implement the ->get_state() function to expose initial state.
>
> Signed-off-by: Boris Brezillon
> ---
> drivers/pwm/pwm-rockchip.c | 67
> ++
> 1
On Thu 2016-05-19 15:44:54, Heikki Krogerus wrote:
> The purpose of this class is to provide unified interface for user
> space to get the status and basic information about USB Type-C
> Connectors in the system, control data role swapping, and when USB PD
> is available, also power role swapping
On Fri, Jun 03, 2016 at 10:23:02AM +0200, Boris Brezillon wrote:
> Implement the ->get_state() function to expose initial state.
>
> Signed-off-by: Boris Brezillon
> ---
> drivers/pwm/pwm-rockchip.c | 67
> ++
> 1 file changed, 67 insertions(+)
>
>
On Thu 2016-05-19 15:44:54, Heikki Krogerus wrote:
> The purpose of this class is to provide unified interface for user
> space to get the status and basic information about USB Type-C
> Connectors in the system, control data role swapping, and when USB PD
> is available, also power role swapping
[So I'm finally trying to get into this for real, hopefully I won't be
interrupted too many times...expect a few mails as I catch up.]
On Fri, 20 May 2016 16:39:31 +0300
Jani Nikula wrote:
> There are a few tradeoffs, of course. First, this requires that the
>
[So I'm finally trying to get into this for real, hopefully I won't be
interrupted too many times...expect a few mails as I catch up.]
On Fri, 20 May 2016 16:39:31 +0300
Jani Nikula wrote:
> There are a few tradeoffs, of course. First, this requires that the
> EXPORT_SYMBOL markers are placed
Hi,
[auto build test ERROR on hid/for-next]
[also build test ERROR on v4.7-rc1 next-20160603]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Andrew-Duggan/HID-rmi-Make-hid-rmi-a-transport
Hi,
[auto build test ERROR on hid/for-next]
[also build test ERROR on v4.7-rc1 next-20160603]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Andrew-Duggan/HID-rmi-Make-hid-rmi-a-transport
Currently, a schedule while atomic error prints the stack trace to the
kernel log and the system continue running.
Although it is possible to collect the kernel log messages and analyze
it, often more information are needed. Furthermore, keep the system
running is not always the best choice. For
Currently, a schedule while atomic error prints the stack trace to the
kernel log and the system continue running.
Although it is possible to collect the kernel log messages and analyze
it, often more information are needed. Furthermore, keep the system
running is not always the best choice. For
On Fri, Jun 03, 2016 at 02:35:41PM -0400, Oleg Drokin wrote:
> >> [ 2642.364383] BUG: unable to handle kernel paging request at
> >> 880113f82000
> >> [ 2642.365014] IP: [] bad_gs+0xd1d/0x1ba9
> >
> > *ow*
> > Could you dump your vmlinux (and System.map) somewhere on anonftp?
> > This
On Fri, Jun 03, 2016 at 02:35:41PM -0400, Oleg Drokin wrote:
> >> [ 2642.364383] BUG: unable to handle kernel paging request at
> >> 880113f82000
> >> [ 2642.365014] IP: [] bad_gs+0xd1d/0x1ba9
> >
> > *ow*
> > Could you dump your vmlinux (and System.map) somewhere on anonftp?
> > This
On Fri, Jun 03, 2016 at 10:23:02AM +0200, Boris Brezillon wrote:
> Implement the ->get_state() function to expose initial state.
>
> Signed-off-by: Boris Brezillon
> ---
> drivers/pwm/pwm-rockchip.c | 67
> ++
> 1
On Fri, Jun 03, 2016 at 10:23:02AM +0200, Boris Brezillon wrote:
> Implement the ->get_state() function to expose initial state.
>
> Signed-off-by: Boris Brezillon
> ---
> drivers/pwm/pwm-rockchip.c | 67
> ++
> 1 file changed, 67 insertions(+)
> -Original Message-
> From: Vitaly Kuznetsov [mailto:vkuzn...@redhat.com]
> Sent: Friday, June 3, 2016 3:15 AM
> To: de...@linuxdriverproject.org
> Cc: linux-kernel@vger.kernel.org; KY Srinivasan ; Haiyang
> Zhang
> Subject: [PATCH] Drivers:
> -Original Message-
> From: Vitaly Kuznetsov [mailto:vkuzn...@redhat.com]
> Sent: Friday, June 3, 2016 3:15 AM
> To: de...@linuxdriverproject.org
> Cc: linux-kernel@vger.kernel.org; KY Srinivasan ; Haiyang
> Zhang
> Subject: [PATCH] Drivers: hv: fix infinite wait when channel open
Linus,
please pull the latest irq-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
irq-urgent-for-linus
This update constains:
- A few simple fixes for fallout from the recent gic-v3 changes
- A workaround for a Cavium thunderX erratum
-
Linus,
please pull the latest irq-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
irq-urgent-for-linus
This update constains:
- A few simple fixes for fallout from the recent gic-v3 changes
- A workaround for a Cavium thunderX erratum
-
On Fri, Jun 03, 2016 at 10:23:01AM +0200, Boris Brezillon wrote:
> The current implementation always round down the duty and period
> values, while it would be better to round them to the closest integer.
Agreed. As I noted to you elsewhere, not having this change can cause
problems where doing a
On Fri, Jun 03, 2016 at 10:23:01AM +0200, Boris Brezillon wrote:
> The current implementation always round down the duty and period
> values, while it would be better to round them to the closest integer.
Agreed. As I noted to you elsewhere, not having this change can cause
problems where doing a
In some functions, returning a -ve decimal value is actually a valid
return condition when the function is returning a value, however, it
can also be misused for returning an error value that should ideally
be a valid error code defined in include/uapi/asm-generic/errno-base.h
or
In some functions, returning a -ve decimal value is actually a valid
return condition when the function is returning a value, however, it
can also be misused for returning an error value that should ideally
be a valid error code defined in include/uapi/asm-generic/errno-base.h
or
Linus,
please pull the latest timers-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
timers-urgent-for-linus
A single bugfix for the error check wreckage we introduced in the merge
window.
Thanks,
tglx
-->
John Stultz (1):
Linus,
please pull the latest timers-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
timers-urgent-for-linus
A single bugfix for the error check wreckage we introduced in the merge
window.
Thanks,
tglx
-->
John Stultz (1):
On Sun, 29 May 2016 23:45:10 +0800
Andy Deng wrote:
> Chinese version CodingStyle is a little outdate, it should be updated.
>
> This patch sync with the latest CodingStyle of all changes,
> new chapters (chapter 19 and chapter 20) have been translated.
Applied to the
On Sun, 29 May 2016 23:45:10 +0800
Andy Deng wrote:
> Chinese version CodingStyle is a little outdate, it should be updated.
>
> This patch sync with the latest CodingStyle of all changes,
> new chapters (chapter 19 and chapter 20) have been translated.
Applied to the docs tree, thanks.
jon
On Thu, Jun 02, 2016 at 02:48:10PM +0800, Frank Wang wrote:
> The newer SoCs (rk3366, rk3399) take a different usb-phy IP block
> than rk3288 and before, and most of phy-related registers are also
> different from the past, so a new phy driver is required necessarily.
>
> Signed-off-by: Frank
On Thu, Jun 02, 2016 at 02:48:10PM +0800, Frank Wang wrote:
> The newer SoCs (rk3366, rk3399) take a different usb-phy IP block
> than rk3288 and before, and most of phy-related registers are also
> different from the past, so a new phy driver is required necessarily.
>
> Signed-off-by: Frank
On Thu, Jun 02, 2016 at 02:48:10PM +0800, Frank Wang wrote:
> The newer SoCs (rk3366, rk3399) take a different usb-phy IP block
> than rk3288 and before, and most of phy-related registers are also
> different from the past, so a new phy driver is required necessarily.
>
> Signed-off-by: Frank
On Thu, Jun 02, 2016 at 02:48:10PM +0800, Frank Wang wrote:
> The newer SoCs (rk3366, rk3399) take a different usb-phy IP block
> than rk3288 and before, and most of phy-related registers are also
> different from the past, so a new phy driver is required necessarily.
>
> Signed-off-by: Frank
On Wed, May 11, 2016 at 02:43:44PM +0200, Maxime Ripard wrote:
> On Wed, May 11, 2016 at 01:23:12PM +0800, Chen-Yu Tsai wrote:
> > Hi Arnd, Olof,
> >
> > Here are 2 last minute fixes for 4.6. The 2 patches drop constaints on
> > the dc1sw regulator for 2 A31s tablets. I checked with Maxime and he
On Wed, Jun 01, 2016 at 10:39:58AM +0900, Chanho Min wrote:
> Add dtsi file to support lg1313 SoC which based on Cortex-A53.
> Also add dts file to support lg1312 reference board which based
> on lg1313 SoC.
>
> Signed-off-by: Chanho Min
Thanks, applied to next/dt64 for 4.8.
On Wed, May 11, 2016 at 02:43:44PM +0200, Maxime Ripard wrote:
> On Wed, May 11, 2016 at 01:23:12PM +0800, Chen-Yu Tsai wrote:
> > Hi Arnd, Olof,
> >
> > Here are 2 last minute fixes for 4.6. The 2 patches drop constaints on
> > the dc1sw regulator for 2 A31s tablets. I checked with Maxime and he
On Wed, Jun 01, 2016 at 10:39:58AM +0900, Chanho Min wrote:
> Add dtsi file to support lg1313 SoC which based on Cortex-A53.
> Also add dts file to support lg1312 reference board which based
> on lg1313 SoC.
>
> Signed-off-by: Chanho Min
Thanks, applied to next/dt64 for 4.8.
-Olof
On Wed, Jun 01, 2016 at 08:37:46PM +0900, Masahiro Yamada wrote:
> Commit 307d40c56b0c ("ARM: uniphier: rework SMP code to support new
> System Bus binding") added a new DT binding for SMP code, but still
> kept old code for the backward compatibility.
>
> Linux 4.6 was out with both bindings
On Mon, May 16, 2016 at 04:45:52PM +0200, Maxime Ripard wrote:
> On Fri, May 13, 2016 at 09:57:16PM +0200, Olliver Schinagl wrote:
> > commit 27dd9af6bc000ab21fd ("ARM: dts: sunxi: Add a olinuxino-lime2-emmc")
> > added the new emmc equipped lime2 but forgot its Makefile.
> >
> > This patch adds
On Wed, Jun 01, 2016 at 10:39:59AM +0900, Chanho Min wrote:
> This patch enables the cadence MACB/GEM support that is needed
> by lg1k SoCs.
>
> Signed-off-by: Chanho Min
> ---
> arch/arm64/configs/defconfig |1 +
> 1 file changed, 1 insertion(+)
Thanks, applied to
On Wed, Jun 01, 2016 at 08:37:46PM +0900, Masahiro Yamada wrote:
> Commit 307d40c56b0c ("ARM: uniphier: rework SMP code to support new
> System Bus binding") added a new DT binding for SMP code, but still
> kept old code for the backward compatibility.
>
> Linux 4.6 was out with both bindings
On Mon, May 16, 2016 at 04:45:52PM +0200, Maxime Ripard wrote:
> On Fri, May 13, 2016 at 09:57:16PM +0200, Olliver Schinagl wrote:
> > commit 27dd9af6bc000ab21fd ("ARM: dts: sunxi: Add a olinuxino-lime2-emmc")
> > added the new emmc equipped lime2 but forgot its Makefile.
> >
> > This patch adds
On Wed, Jun 01, 2016 at 10:39:59AM +0900, Chanho Min wrote:
> This patch enables the cadence MACB/GEM support that is needed
> by lg1k SoCs.
>
> Signed-off-by: Chanho Min
> ---
> arch/arm64/configs/defconfig |1 +
> 1 file changed, 1 insertion(+)
Thanks, applied to next/arm64 for 4.8.
On Mon, May 30, 2016 at 11:12:33AM +0900, Masahiro Yamada wrote:
> Tree-wide replacement was done by commit 2ef7d5f342c1 (ARM, ARM64:
> dts: drop "arm,amba-bus" in favor of "simple-bus"), but we have some
> new users of "arm,amba-bus" at Linux 4.7-rc1. Eliminate them now.
>
> Signed-off-by:
On Mon, May 30, 2016 at 11:12:33AM +0900, Masahiro Yamada wrote:
> Tree-wide replacement was done by commit 2ef7d5f342c1 (ARM, ARM64:
> dts: drop "arm,amba-bus" in favor of "simple-bus"), but we have some
> new users of "arm,amba-bus" at Linux 4.7-rc1. Eliminate them now.
>
> Signed-off-by:
On Mon, May 30, 2016 at 08:20:48AM +0200, Krzysztof Kozlowski wrote:
> Hi,
>
> A couple of fixes from Arnd for this release cycle.
>
>
> Best regards,
> Krzysztof
>
>
> The following changes since commit 2dcd0af568b0cf583645c8a317dd12e344b1c72a:
>
> Linux 4.6 (2016-05-15 15:43:13 -0700)
>
On Mon, May 30, 2016 at 08:20:48AM +0200, Krzysztof Kozlowski wrote:
> Hi,
>
> A couple of fixes from Arnd for this release cycle.
>
>
> Best regards,
> Krzysztof
>
>
> The following changes since commit 2dcd0af568b0cf583645c8a317dd12e344b1c72a:
>
> Linux 4.6 (2016-05-15 15:43:13 -0700)
>
Em Fri, Jun 03, 2016 at 09:06:29AM +0200, Jiri Olsa escreveu:
> On Fri, Jun 03, 2016 at 03:33:09AM +, He Kuang wrote:
> > v9:
> > - Change function unwind__register_ops() to static.
> > - Move up unwind__prepare_access() in thread__insert_map() and save
> >map_groups__remove() call.
> >
Em Fri, Jun 03, 2016 at 09:06:29AM +0200, Jiri Olsa escreveu:
> On Fri, Jun 03, 2016 at 03:33:09AM +, He Kuang wrote:
> > v9:
> > - Change function unwind__register_ops() to static.
> > - Move up unwind__prepare_access() in thread__insert_map() and save
> >map_groups__remove() call.
> >
On 06/03/2016 12:28 PM, Dave Hansen wrote:
> On 06/02/2016 05:26 PM, Michael Kerrisk (man-pages) wrote:
>> On 06/01/2016 07:17 PM, Dave Hansen wrote:
>>> On 06/01/2016 05:11 PM, Michael Kerrisk (man-pages) wrote:
If I read this right, it doesn't actually remove any pkey
On 06/03/2016 12:28 PM, Dave Hansen wrote:
> On 06/02/2016 05:26 PM, Michael Kerrisk (man-pages) wrote:
>> On 06/01/2016 07:17 PM, Dave Hansen wrote:
>>> On 06/01/2016 05:11 PM, Michael Kerrisk (man-pages) wrote:
If I read this right, it doesn't actually remove any pkey
On 03.06.16 22:13, Grygorii Strashko wrote:
On 06/03/2016 09:25 PM, Ivan Khoronzhuk wrote:
On 03.06.16 19:50, Grygorii Strashko wrote:
On 06/03/2016 01:43 AM, Ivan Khoronzhuk wrote:
There is no reason to hold s/w dependent parameter in device tree.
Even more, there is no reason in this
On 03.06.16 22:13, Grygorii Strashko wrote:
On 06/03/2016 09:25 PM, Ivan Khoronzhuk wrote:
On 03.06.16 19:50, Grygorii Strashko wrote:
On 06/03/2016 01:43 AM, Ivan Khoronzhuk wrote:
There is no reason to hold s/w dependent parameter in device tree.
Even more, there is no reason in this
On Thu, 19 May 2016 21:54:51 -0700
Mike Danese wrote:
> The compilation emits a warning in function ‘snprintf’,
> inlined from ‘set_cmdline’ at
> ../Documentation/mic/mpssd/mpssd.c:1541:9:
> /usr/include/x86_64-linux-gnu/bits/stdio2.h:64:10:
> warning: call to
On Thu, 19 May 2016 21:54:51 -0700
Mike Danese wrote:
> The compilation emits a warning in function ‘snprintf’,
> inlined from ‘set_cmdline’ at
> ../Documentation/mic/mpssd/mpssd.c:1541:9:
> /usr/include/x86_64-linux-gnu/bits/stdio2.h:64:10:
> warning: call to
On 5/25/2016 9:07 PM, Frederic Weisbecker wrote:
I don't remember how much I answered this email, but I need to finish that :-)
Sorry for the slow response - it's been a busy week.
On Fri, Apr 08, 2016 at 12:34:48PM -0400, Chris Metcalf wrote:
On 4/8/2016 9:56 AM, Frederic Weisbecker wrote:
On 5/25/2016 9:07 PM, Frederic Weisbecker wrote:
I don't remember how much I answered this email, but I need to finish that :-)
Sorry for the slow response - it's been a busy week.
On Fri, Apr 08, 2016 at 12:34:48PM -0400, Chris Metcalf wrote:
On 4/8/2016 9:56 AM, Frederic Weisbecker wrote:
On Wed, Jun 1, 2016 at 6:50 PM, Richard Guy Briggs wrote:
> RFE: add additional fields for use in audit filter exclude rules
> https://github.com/linux-audit/audit-kernel/issues/5
>
> Re-factor audit_filter_type() to use audit_filter_user_rules() to enable
> exclude filter to
On Wed, Jun 1, 2016 at 6:50 PM, Richard Guy Briggs wrote:
> RFE: add additional fields for use in audit filter exclude rules
> https://github.com/linux-audit/audit-kernel/issues/5
>
> Re-factor audit_filter_type() to use audit_filter_user_rules() to enable
> exclude filter to additionally filter
Colin King writes:
> From: Colin Ian King
>
> path_b_ok is being assigned but immediately after path_a_ok is being
> compared to the value 0x03. This appears to be a typo on the
> variable name, compare path_b_ok instead.
>
> Signed-off-by:
Colin King writes:
> From: Colin Ian King
>
> path_b_ok is being assigned but immediately after path_a_ok is being
> compared to the value 0x03. This appears to be a typo on the
> variable name, compare path_b_ok instead.
>
> Signed-off-by: Colin Ian King
> ---
>
401 - 500 of 1732 matches
Mail list logo