On 05.08.2018 03:03, Matthew Wilcox wrote:
> On Sat, Aug 04, 2018 at 09:42:05PM +0300, Kirill Tkhai wrote:
>> This is exactly the thing the patch makes. Instead of inserting a shrinker
>> pointer
>> to idr, it inserts a fake value SHRINKER_REGISTERING there. The patch makes
>> impossible
>> to
On 05.08.2018 03:03, Matthew Wilcox wrote:
> On Sat, Aug 04, 2018 at 09:42:05PM +0300, Kirill Tkhai wrote:
>> This is exactly the thing the patch makes. Instead of inserting a shrinker
>> pointer
>> to idr, it inserts a fake value SHRINKER_REGISTERING there. The patch makes
>> impossible
>> to
On Sat, 2018-08-04 at 14:25 +0200, Mike Galbraith wrote:
>
> Besides, there are more interesting fish in the arm64 sea than kvm.
>
> virgin 4.16.18-rt12-rt
>
> [ 537.236131] ITS queue timeout (65440 65504 4640)
> [ 537.236150] ITS cmd its_build_inv_cmd failed
FWIW, I had thought that
On Sat, 2018-08-04 at 14:25 +0200, Mike Galbraith wrote:
>
> Besides, there are more interesting fish in the arm64 sea than kvm.
>
> virgin 4.16.18-rt12-rt
>
> [ 537.236131] ITS queue timeout (65440 65504 4640)
> [ 537.236150] ITS cmd its_build_inv_cmd failed
FWIW, I had thought that
Some LED controllers have support for autonomously controlling
brightness over time, according to some preprogrammed pattern or
function.
This patch adds pattern trigger that LED device can configure the
pattern and trigger it.
Signed-off-by: Raphael Teysseyre
Signed-off-by: Baolin Wang
---
Some LED controllers have support for autonomously controlling
brightness over time, according to some preprogrammed pattern or
function.
This patch adds pattern trigger that LED device can configure the
pattern and trigger it.
Signed-off-by: Raphael Teysseyre
Signed-off-by: Baolin Wang
---
Hi Michal and David,
AFAICS, the null pointer is the task_struct of p in the dump_header.
Why don't we just add a if before printing the victim task's
informaiton.
diff --git a/mm/oom_kill.c b/mm/oom_kill.c
--- a/mm/oom_kill.c
+++ b/mm/oom_kill.c
@@ -438,14 +438,6 @@ static void
Hi Michal and David,
AFAICS, the null pointer is the task_struct of p in the dump_header.
Why don't we just add a if before printing the victim task's
informaiton.
diff --git a/mm/oom_kill.c b/mm/oom_kill.c
--- a/mm/oom_kill.c
+++ b/mm/oom_kill.c
@@ -438,14 +438,6 @@ static void
On Sat, Aug 04, 2018 at 11:04:40PM +0200, Wolfram Sang wrote:
> On Wed, Aug 01, 2018 at 11:32:28PM +0530, Manivannan Sadhasivam wrote:
> > Add pinctrl definition for Actions Semiconductor S900 I2C controller.
> > Pinctrl definitions are only available for I2C0, I2C1, and I2C2.
> >
> >
On Sat, Aug 04, 2018 at 11:04:40PM +0200, Wolfram Sang wrote:
> On Wed, Aug 01, 2018 at 11:32:28PM +0530, Manivannan Sadhasivam wrote:
> > Add pinctrl definition for Actions Semiconductor S900 I2C controller.
> > Pinctrl definitions are only available for I2C0, I2C1, and I2C2.
> >
> >
Hi Jacek,
On 5 August 2018 at 05:41, Jacek Anaszewski wrote:
> Hi Baolin,
>
> Thank you for the new version of the patch set.
Thanks for your quick response.
>
> On 08/04/2018 06:51 PM, Baolin Wang wrote:
>> Some LED controllers have support for autonomously controlling
>> brightness over
Hi Jacek,
On 5 August 2018 at 05:41, Jacek Anaszewski wrote:
> Hi Baolin,
>
> Thank you for the new version of the patch set.
Thanks for your quick response.
>
> On 08/04/2018 06:51 PM, Baolin Wang wrote:
>> Some LED controllers have support for autonomously controlling
>> brightness over
2018-07-27 18:06 GMT+08:00 Will Deacon :
> On Thu, Jul 26, 2018 at 05:01:47PM -0400, Dongjiu Geng wrote:
>> In order to remove the additional check before calling the
>> ghes_notify_sea(), make stub definition when !CONFIG_ACPI_APEI_SEA.
>>
>> Signed-off-by: Dongjiu Geng
>> ---
>
> Acked-by: Will
2018-07-27 18:06 GMT+08:00 Will Deacon :
> On Thu, Jul 26, 2018 at 05:01:47PM -0400, Dongjiu Geng wrote:
>> In order to remove the additional check before calling the
>> ghes_notify_sea(), make stub definition when !CONFIG_ACPI_APEI_SEA.
>>
>> Signed-off-by: Dongjiu Geng
>> ---
>
> Acked-by: Will
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
Addresses-Coverity-ID: 114713 ("Missing break in switch")
Signed-off-by: Gustavo A. R. Silva
---
kernel/power/hibernate.c | 1 +
1 file changed, 1 insertion(+)
diff --git
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
Addresses-Coverity-ID: 114713 ("Missing break in switch")
Signed-off-by: Gustavo A. R. Silva
---
kernel/power/hibernate.c | 1 +
1 file changed, 1 insertion(+)
diff --git
Hi Sebastian,
On 07/22/2018 05:17 PM, Sebastian Reichel wrote:
> Hi,
>
> On Wed, Jul 18, 2018 at 08:14:50AM +0200, Krzysztof Kozlowski wrote:
>> On 17 July 2018 at 23:47, Gustavo A. R. Silva wrote:
>>> It seems that a *break* is missing in order to avoid a fall-through.
>>> Otherwise, the
Hi Sebastian,
On 07/22/2018 05:17 PM, Sebastian Reichel wrote:
> Hi,
>
> On Wed, Jul 18, 2018 at 08:14:50AM +0200, Krzysztof Kozlowski wrote:
>> On 17 July 2018 at 23:47, Gustavo A. R. Silva wrote:
>>> It seems that a *break* is missing in order to avoid a fall-through.
>>> Otherwise, the
On Wed, 2018-08-01 at 19:54 +0200, Miguel Ojeda wrote:
> From the GCC manual:
>
> The nonstring variable attribute specifies that an object or member
> declaration with type array of char or pointer to char is intended to
> store character arrays that do not necessarily contain a terminating NUL
On Wed, 2018-08-01 at 19:54 +0200, Miguel Ojeda wrote:
> From the GCC manual:
>
> The nonstring variable attribute specifies that an object or member
> declaration with type array of char or pointer to char is intended to
> store character arrays that do not necessarily contain a terminating NUL
On 08/02/2018 02:15 PM, Jerry Hoemann wrote:
Bump version number to reflect recent bug fixes.
Signed-off-by: Jerry Hoemann
As usual, my recommendation is to drop version numbers. The version number is
reflected by the Linux kernel version and SHA. Yet, I understand that people
feel quite
On 08/02/2018 02:15 PM, Jerry Hoemann wrote:
Bump version number to reflect recent bug fixes.
Signed-off-by: Jerry Hoemann
As usual, my recommendation is to drop version numbers. The version number is
reflected by the Linux kernel version and SHA. Yet, I understand that people
feel quite
On 08/02/2018 02:15 PM, Jerry Hoemann wrote:
Print module parameters when the driver is loaded.
Signed-off-by: Jerry Hoemann
---
drivers/watchdog/hpwdt.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/drivers/watchdog/hpwdt.c b/drivers/watchdog/hpwdt.c
index
On 08/02/2018 02:15 PM, Jerry Hoemann wrote:
Print module parameters when the driver is loaded.
Signed-off-by: Jerry Hoemann
---
drivers/watchdog/hpwdt.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/drivers/watchdog/hpwdt.c b/drivers/watchdog/hpwdt.c
index
On 08/02/2018 02:15 PM, Jerry Hoemann wrote:
The hwpdt driver is overloaded for handling both the iLO
watchdog and the explicit "Generate NMI to System" virutal
button.
Claim the iLO NMI virtual button even if we are not claiming
the iLO watchdog pretimeout.
Signed-off-by: Jerry Hoemann
On 08/02/2018 02:15 PM, Jerry Hoemann wrote:
The hwpdt driver is overloaded for handling both the iLO
watchdog and the explicit "Generate NMI to System" virutal
button.
Claim the iLO NMI virtual button even if we are not claiming
the iLO watchdog pretimeout.
Signed-off-by: Jerry Hoemann
On 08/02/2018 02:15 PM, Jerry Hoemann wrote:
When the pretimeout is specified as a module parameter, the
value should be reflected in hpwdt_dev.pretimeout. The default
(on) case is correct. But, when disabling pretimeout, the value
should be set to zero in hpwdt_dev.
Signed-off-by: Jerry
On 08/02/2018 02:15 PM, Jerry Hoemann wrote:
When the pretimeout is specified as a module parameter, the
value should be reflected in hpwdt_dev.pretimeout. The default
(on) case is correct. But, when disabling pretimeout, the value
should be set to zero in hpwdt_dev.
Signed-off-by: Jerry
On Fri, Aug 03, 2018 at 11:20:49AM +0300, Peter Ujfalusi wrote:
> Hi,
>
> On 2018-08-03 10:19, Huang Shijie wrote:
> > All the patches are using dmaenginem_async_device_register to simplify code
> > except the last one:
> > dmaengine: add COMPILE_TEST for the drivers
> >
> > I use the last one
On Fri, Aug 03, 2018 at 11:20:49AM +0300, Peter Ujfalusi wrote:
> Hi,
>
> On 2018-08-03 10:19, Huang Shijie wrote:
> > All the patches are using dmaenginem_async_device_register to simplify code
> > except the last one:
> > dmaengine: add COMPILE_TEST for the drivers
> >
> > I use the last one
Return statements in functions returning bool should use true or false
instead of an integer value.
This issue was detected with the help of Coccinelle.
Signed-off-by: Gustavo A. R. Silva
---
drivers/soc/mediatek/mtk-pmic-wrap.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Return statements in functions returning bool should use true or false
instead of an integer value.
This issue was detected with the help of Coccinelle.
Signed-off-by: Gustavo A. R. Silva
---
drivers/soc/mediatek/mtk-pmic-wrap.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Return statements in functions returning bool should use true or false
instead of an integer value.
This issue was detected with the help of Coccinelle.
Signed-off-by: Gustavo A. R. Silva
---
drivers/s390/net/qeth_l3_main.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
Return statements in functions returning bool should use true or false
instead of an integer value.
This issue was detected with the help of Coccinelle.
Signed-off-by: Gustavo A. R. Silva
---
drivers/s390/net/qeth_l3_main.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
On 08/03/2018 09:47 PM, Masahiro Yamada wrote:
> 1/3 fixes the build failure reported by Randy.
> (I may have seen a similar report before, but I cannot recall it.)
>
> 2/3 and 3/3 clean-up the Makefile a bit more.
>
> I'd like to apply this series to kbuild tree.
> Ack from UML folks are
On 08/03/2018 09:47 PM, Masahiro Yamada wrote:
> 1/3 fixes the build failure reported by Randy.
> (I may have seen a similar report before, but I cannot recall it.)
>
> 2/3 and 3/3 clean-up the Makefile a bit more.
>
> I'd like to apply this series to kbuild tree.
> Ack from UML folks are
On Sunday, 5 August 2018 03:11:57 MSK Mikko Perttunen wrote:
> One potential issue is with host1x clients where userspace processes can
> submit jobs with invalid memory accesses (addresses not mapped to
> IOMMU). If when such a failure happens, we disable the DMA for the whole
> host1x client,
On Sunday, 5 August 2018 03:11:57 MSK Mikko Perttunen wrote:
> One potential issue is with host1x clients where userspace processes can
> submit jobs with invalid memory accesses (addresses not mapped to
> IOMMU). If when such a failure happens, we disable the DMA for the whole
> host1x client,
Return statements in functions returning bool should use true or false
instead of an integer value.
This code was detected with the help of Coccinelle.
Signed-off-by: Gustavo A. R. Silva
---
drivers/misc/genwqe/card_base.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Return statements in functions returning bool should use true or false
instead of an integer value.
This code was detected with the help of Coccinelle.
Signed-off-by: Gustavo A. R. Silva
---
drivers/misc/genwqe/card_base.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Return statements in functions returning bool should use true or false
instead of an integer value.
This code was detected with the help of Coccinelle.
Signed-off-by: Gustavo A. R. Silva
---
drivers/input/touchscreen/raydium_i2c_ts.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
Return statements in functions returning bool should use true or false
instead of an integer value.
This code was detected with the help of Coccinelle.
Signed-off-by: Gustavo A. R. Silva
---
drivers/input/touchscreen/raydium_i2c_ts.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
Return statements in functions returning bool should use true or false
instead of an integer value.
This code was detected with the help of Coccinelle.
Signed-off-by: Gustavo A. R. Silva
---
drivers/clk/qcom/clk-branch.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
On Fri, Aug 03, 2018 at 08:16:21PM -0500, Benjamin Herrenschmidt wrote:
> On Fri, 2018-08-03 at 22:07 +0300, Michael S. Tsirkin wrote:
> > On Fri, Aug 03, 2018 at 10:58:36AM -0500, Benjamin Herrenschmidt wrote:
> > > On Fri, 2018-08-03 at 00:05 -0700, Christoph Hellwig wrote:
> > > > > 2- Make
Return statements in functions returning bool should use true or false
instead of an integer value.
This code was detected with the help of Coccinelle.
Signed-off-by: Gustavo A. R. Silva
---
drivers/clk/qcom/clk-branch.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
On Fri, Aug 03, 2018 at 08:16:21PM -0500, Benjamin Herrenschmidt wrote:
> On Fri, 2018-08-03 at 22:07 +0300, Michael S. Tsirkin wrote:
> > On Fri, Aug 03, 2018 at 10:58:36AM -0500, Benjamin Herrenschmidt wrote:
> > > On Fri, 2018-08-03 at 00:05 -0700, Christoph Hellwig wrote:
> > > > > 2- Make
Return statements in functions returning bool should use true or false
instead of an integer value.
This code was detected with the help of Coccinelle.
Signed-off-by: Gustavo A. R. Silva
---
drivers/platform/x86/acer-wmi.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
Return statements in functions returning bool should use true or false
instead of an integer value.
This code was detected with the help of Coccinelle.
Signed-off-by: Gustavo A. R. Silva
---
drivers/platform/x86/acer-wmi.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
One potential issue is with host1x clients where userspace processes can
submit jobs with invalid memory accesses (addresses not mapped to
IOMMU). If when such a failure happens, we disable the DMA for the whole
host1x client, unrelated userspace processes may see failures even
though there is
One potential issue is with host1x clients where userspace processes can
submit jobs with invalid memory accesses (addresses not mapped to
IOMMU). If when such a failure happens, we disable the DMA for the whole
host1x client, unrelated userspace processes may see failures even
though there is
On Sat, Aug 04, 2018 at 09:42:05PM +0300, Kirill Tkhai wrote:
> This is exactly the thing the patch makes. Instead of inserting a shrinker
> pointer
> to idr, it inserts a fake value SHRINKER_REGISTERING there. The patch makes
> impossible
> to dereference a shrinker unless it's completely
On Sat, Aug 04, 2018 at 09:42:05PM +0300, Kirill Tkhai wrote:
> This is exactly the thing the patch makes. Instead of inserting a shrinker
> pointer
> to idr, it inserts a fake value SHRINKER_REGISTERING there. The patch makes
> impossible
> to dereference a shrinker unless it's completely
On Fri, 27 Jul 2018, zhaowu...@wingtech.com wrote:
> >On Thu, 26 Jul 2018 15:03:23 +0800 "zhaowu...@wingtech.com"
> > wrote:
> >
> >> >On Thu 26-07-18 10:21:40, zhaowu...@wingtech.com wrote:
> >> >[...]
> >> >> Our project really needs a fix to this issue
> >> >
> >> >Could you be more specific
On Fri, 27 Jul 2018, zhaowu...@wingtech.com wrote:
> >On Thu, 26 Jul 2018 15:03:23 +0800 "zhaowu...@wingtech.com"
> > wrote:
> >
> >> >On Thu 26-07-18 10:21:40, zhaowu...@wingtech.com wrote:
> >> >[...]
> >> >> Our project really needs a fix to this issue
> >> >
> >> >Could you be more specific
On Mon, Jul 16, 2018 at 03:03:31PM -0400, Rik van Riel wrote:
> The mm_struct always contains a cpumask bitmap, regardless of
> CONFIG_CPUMASK_OFFSTACK. That means the first step can be to
> simplify things, and simply have one bitmask at the end of the
> mm_struct for the mm_cpumask.
>
> This
On Mon, Jul 16, 2018 at 03:03:31PM -0400, Rik van Riel wrote:
> The mm_struct always contains a cpumask bitmap, regardless of
> CONFIG_CPUMASK_OFFSTACK. That means the first step can be to
> simplify things, and simply have one bitmask at the end of the
> mm_struct for the mm_cpumask.
>
> This
Return statements in functions returning bool should use true or false
instead of an integer value.
This code was detected with the help of Coccinelle.
Signed-off-by: Gustavo A. R. Silva
---
mm/kasan/kasan_init.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git
Return statements in functions returning bool should use true or false
instead of an integer value.
This code was detected with the help of Coccinelle.
Signed-off-by: Gustavo A. R. Silva
---
mm/kasan/kasan_init.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git
Return statements in functions returning bool should use true or false
instead of an integer value.
This code was detected with the help of Coccinelle.
Signed-off-by: Gustavo A. R. Silva
---
sound/soc/codecs/wm8903.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
Return statements in functions returning bool should use true or false
instead of an integer value.
This code was detected with the help of Coccinelle.
Signed-off-by: Gustavo A. R. Silva
---
sound/soc/codecs/wm8903.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
Return statements in functions returning bool should use true or false
instead of an integer value.
This code was detected with the help of Coccinelle.
Signed-off-by: Gustavo A. R. Silva
---
sound/soc/codecs/wm5100-tables.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
Return statements in functions returning bool should use true or false
instead of an integer value.
This code was detected with the help of Coccinelle.
Signed-off-by: Gustavo A. R. Silva
---
sound/soc/codecs/wm5100-tables.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
Return statements in functions returning bool should use true or false
instead of an integer value.
This code was detected with the help of Coccinelle.
Signed-off-by: Gustavo A. R. Silva
---
sound/soc/codecs/da9055.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
Return statements in functions returning bool should use true or false
instead of an integer value.
This code was detected with the help of Coccinelle.
Signed-off-by: Gustavo A. R. Silva
---
sound/soc/codecs/da9055.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
Return statements in functions returning bool should use true or false
instead of an integer value.
This code was detected with the help of Coccinelle.
Signed-off-by: Gustavo A. R. Silva
---
sound/soc/codecs/da7213.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
Return statements in functions returning bool should use true or false
instead of an integer value.
This code was detected with the help of Coccinelle.
Signed-off-by: Gustavo A. R. Silva
---
sound/soc/codecs/da7213.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
Return statements in functions returning bool should use true or false
instead of an integer value.
This code was detected with the help of Coccinelle.
Signed-off-by: Gustavo A. R. Silva
---
sound/soc/codecs/twl6040.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Return statements in functions returning bool should use true or false
instead of an integer value.
This code was detected with the help of Coccinelle.
Signed-off-by: Gustavo A. R. Silva
---
sound/soc/codecs/twl6040.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Return statements in functions returning bool should use true or false
instead of an integer value.
This code was detected with the help of Coccinelle.
Signed-off-by: Gustavo A. R. Silva
---
sound/soc/codecs/da7219.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
Return statements in functions returning bool should use true or false
instead of an integer value.
This code was detected with the help of Coccinelle.
Signed-off-by: Gustavo A. R. Silva
---
sound/soc/codecs/da7219.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
Return statements in functions returning bool should use true or false
instead of an integer value.
This code was detected with the help of Coccinelle.
Signed-off-by: Gustavo A. R. Silva
---
sound/soc/codecs/wm8996.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git
Return statements in functions returning bool should use true or false
instead of an integer value.
This code was detected with the help of Coccinelle.
Signed-off-by: Gustavo A. R. Silva
---
sound/soc/codecs/wm8996.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git
Return statements in functions returning bool should use true or false
instead of an integer value.
This code was detected with the help of Coccinelle.
Signed-off-by: Gustavo A. R. Silva
---
sound/soc/codecs/cs4270.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Return statements in functions returning bool should use true or false
instead of an integer value.
This code was detected with the help of Coccinelle.
Signed-off-by: Gustavo A. R. Silva
---
sound/soc/codecs/cs4270.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Return statements in functions returning bool should use true or false
instead of an integer value.
This code was detected with the help of Coccinelle.
Signed-off-by: Gustavo A. R. Silva
---
sound/soc/codecs/wm8990.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
Return statements in functions returning bool should use true or false
instead of an integer value.
This code was detected with the help of Coccinelle.
Signed-off-by: Gustavo A. R. Silva
---
sound/soc/codecs/wm8990.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
Return statements in functions returning bool should use true or false
instead of an integer value.
This code was detected with the help of Coccinelle.
Signed-off-by: Gustavo A. R. Silva
---
sound/soc/codecs/tda7419.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
Return statements in functions returning bool should use true or false
instead of an integer value.
This code was detected with the help of Coccinelle.
Signed-off-by: Gustavo A. R. Silva
---
sound/soc/codecs/tda7419.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
Return statements in functions returning bool should use true or false
instead of an integer value.
This code was detected with the help of Coccinelle.
Signed-off-by: Gustavo A. R. Silva
---
sound/soc/codecs/rt5631.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git
Return statements in functions returning bool should use true or false
instead of an integer value.
This code was detected with the help of Coccinelle.
Signed-off-by: Gustavo A. R. Silva
---
sound/soc/codecs/rt5631.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git
Return statements in functions returning bool should use true or false
instead of an integer value.
This code was detected with the help of Coccinelle.
Signed-off-by: Gustavo A. R. Silva
---
sound/soc/codecs/max9850.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
Return statements in functions returning bool should use true or false
instead of an integer value.
This code was detected with the help of Coccinelle.
Signed-off-by: Gustavo A. R. Silva
---
sound/soc/codecs/max9850.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
Hi all,
This patchset aims to replace the use of integer values with a
proper true or false in return statements for functions returning
bool.
Thanks
Gustavo A. R. Silva (12):
ASoC: max9850: use true and false for boolean values
ASoC: rt5631: use true and false for boolean values
ASoC:
Hi all,
This patchset aims to replace the use of integer values with a
proper true or false in return statements for functions returning
bool.
Thanks
Gustavo A. R. Silva (12):
ASoC: max9850: use true and false for boolean values
ASoC: rt5631: use true and false for boolean values
ASoC:
Hi Baolin,
Thank you for the new version of the patch set.
On 08/04/2018 06:51 PM, Baolin Wang wrote:
> Some LED controllers have support for autonomously controlling
> brightness over time, according to some preprogrammed pattern or
> function.
>
> This patch adds pattern trigger that LED
Hi Baolin,
Thank you for the new version of the patch set.
On 08/04/2018 06:51 PM, Baolin Wang wrote:
> Some LED controllers have support for autonomously controlling
> brightness over time, according to some preprogrammed pattern or
> function.
>
> This patch adds pattern trigger that LED
On Thu, Aug 2, 2018 at 3:58 PM, Dave Hansen wrote:
>
> From: Dave Hansen
>
> The kernel image is mapped into two places in the virtual address
> space (addresses without KASLR, of course):
>
> 1. The kernel direct map (0x8800)
> 2. The "high kernel map"
On Thu, Aug 2, 2018 at 3:58 PM, Dave Hansen wrote:
>
> From: Dave Hansen
>
> The kernel image is mapped into two places in the virtual address
> space (addresses without KASLR, of course):
>
> 1. The kernel direct map (0x8800)
> 2. The "high kernel map"
On Fri, 9 Mar 2018 23:15:55 +
Sergei Trofimovich wrote:
I tried to explain in more detail breakage mechanics
of unwinder and gcc code generation quirks at:
https://trofi.github.io/posts/210-ptrace-and-accidental-boot-fix-on-ia64.html
Hopefully it gives better intuition of code change
On Fri, 9 Mar 2018 23:15:55 +
Sergei Trofimovich wrote:
I tried to explain in more detail breakage mechanics
of unwinder and gcc code generation quirks at:
https://trofi.github.io/posts/210-ptrace-and-accidental-boot-fix-on-ia64.html
Hopefully it gives better intuition of code change
On Sat, Aug 04, 2018 at 07:04:56PM +0800, zhong jiang wrote:
> The err is not used after initalization. So just remove the variable.
>
> Signed-off-by: zhong jiang
I'll apply this patch, but how did you generate the diff? The
function name here is all wrong:
> diff --git a/fs/ext4/mballoc.c
On Sat, Aug 04, 2018 at 07:04:56PM +0800, zhong jiang wrote:
> The err is not used after initalization. So just remove the variable.
>
> Signed-off-by: zhong jiang
I'll apply this patch, but how did you generate the diff? The
function name here is all wrong:
> diff --git a/fs/ext4/mballoc.c
On Tue, Jul 24, 2018 at 01:36:15PM -0700, Jae Hyun Yoo wrote:
> This commit fixes this sparse warning:
> drivers/i2c/busses/i2c-aspeed.c:875:38: warning: incorrect type in assignment
> (different modifiers)
> drivers/i2c/busses/i2c-aspeed.c:875:38:expected unsigned int (
> *get_clk_reg_val
On Tue, Jul 24, 2018 at 01:36:15PM -0700, Jae Hyun Yoo wrote:
> This commit fixes this sparse warning:
> drivers/i2c/busses/i2c-aspeed.c:875:38: warning: incorrect type in assignment
> (different modifiers)
> drivers/i2c/busses/i2c-aspeed.c:875:38:expected unsigned int (
> *get_clk_reg_val
On Wed, Aug 01, 2018 at 11:32:32PM +0530, Manivannan Sadhasivam wrote:
> Add entry for Actions Semiconductor Owl I2C driver under ARM/ACTIONS
So, it goes upstream via arm-soc?
>
> Signed-off-by: Manivannan Sadhasivam
Acked-by: Wolfram Sang
signature.asc
Description: PGP signature
On Wed, Aug 01, 2018 at 11:32:28PM +0530, Manivannan Sadhasivam wrote:
> Add pinctrl definition for Actions Semiconductor S900 I2C controller.
> Pinctrl definitions are only available for I2C0, I2C1, and I2C2.
>
> Signed-off-by: Manivannan Sadhasivam
Note that I don't take DTS patches, so
On Wed, Aug 01, 2018 at 11:32:28PM +0530, Manivannan Sadhasivam wrote:
> Add pinctrl definition for Actions Semiconductor S900 I2C controller.
> Pinctrl definitions are only available for I2C0, I2C1, and I2C2.
>
> Signed-off-by: Manivannan Sadhasivam
Note that I don't take DTS patches, so
On Wed, Aug 01, 2018 at 11:32:32PM +0530, Manivannan Sadhasivam wrote:
> Add entry for Actions Semiconductor Owl I2C driver under ARM/ACTIONS
So, it goes upstream via arm-soc?
>
> Signed-off-by: Manivannan Sadhasivam
Acked-by: Wolfram Sang
signature.asc
Description: PGP signature
On Sat, Aug 4, 2018 at 2:43 PM, Greg Kroah-Hartman
wrote:
> On Sat, Aug 04, 2018 at 12:54:22PM +0200, Hauke Mehrtens wrote:
>> On 08/03/2018 12:30 PM, Greg Kroah-Hartman wrote:
>> > On Fri, Aug 03, 2018 at 03:33:38PM +0800, Wu, Songjun wrote:
>> This patch makes it possible to use it with the
On Sat, Aug 4, 2018 at 2:43 PM, Greg Kroah-Hartman
wrote:
> On Sat, Aug 04, 2018 at 12:54:22PM +0200, Hauke Mehrtens wrote:
>> On 08/03/2018 12:30 PM, Greg Kroah-Hartman wrote:
>> > On Fri, Aug 03, 2018 at 03:33:38PM +0800, Wu, Songjun wrote:
>> This patch makes it possible to use it with the
1 - 100 of 744 matches
Mail list logo
