__compiletime_assert_fallback() is supposed to stop building earlier
by using the negative-array-size method in case the compiler does not
support "error" attribute, but has never worked like that.
You can try this simple code:
#include
void foo(void)
{
BUILD_BUG_ON(1);
__compiletime_assert_fallback() is supposed to stop building earlier
by using the negative-array-size method in case the compiler does not
support "error" attribute, but has never worked like that.
You can try this simple code:
#include
void foo(void)
{
BUILD_BUG_ON(1);
Randy Dunlap wrote:
On 08/18/2018 05:48 PM, Linda Walsh wrote:
Is CLANG required for building now?
Looks like this patch should fix it:
https://marc.info/?l=linux-kbuild=153447099313149=2
---
Thanks much!
Randy Dunlap wrote:
On 08/18/2018 05:48 PM, Linda Walsh wrote:
Is CLANG required for building now?
Looks like this patch should fix it:
https://marc.info/?l=linux-kbuild=153447099313149=2
---
Thanks much!
>
> > On Tue, Jul 31, 2018 at 09:35:32AM +0300, Tomas Winkler wrote:
> > > This series adds an alternative method for transferring data between
> > > the mei driver and the device via a DMA ring. The DMA ring allows
> > > transferring data in bigger chunks, up to 128K, than the HW ring 512B.
>
>
> > On Tue, Jul 31, 2018 at 09:35:32AM +0300, Tomas Winkler wrote:
> > > This series adds an alternative method for transferring data between
> > > the mei driver and the device via a DMA ring. The DMA ring allows
> > > transferring data in bigger chunks, up to 128K, than the HW ring 512B.
>
On Sat, Aug 18, 2018 at 01:24:51PM +1000, Benjamin Herrenschmidt wrote:
> On Fri, 2018-08-17 at 10:44 -0500, Bjorn Helgaas wrote:
> > On Fri, Aug 17, 2018 at 02:48:57PM +1000, Benjamin Herrenschmidt wrote:
> > > This reverts commit 44bda4b7d26e9fffed6d7152d98a2e9edaeb2a76.
> >
> > Just to be
On Sat, Aug 18, 2018 at 01:24:51PM +1000, Benjamin Herrenschmidt wrote:
> On Fri, 2018-08-17 at 10:44 -0500, Bjorn Helgaas wrote:
> > On Fri, Aug 17, 2018 at 02:48:57PM +1000, Benjamin Herrenschmidt wrote:
> > > This reverts commit 44bda4b7d26e9fffed6d7152d98a2e9edaeb2a76.
> >
> > Just to be
On 08/18/2018 05:48 PM, Linda Walsh wrote:
> Is CLANG required for building now?
>
> when I did a "make xconfig" (or any make, for that matter), I get:
>
>> make xconfig
> scripts/kconfig/qconf Kconfig
> invocation line: ./scripts/clang-version.sh gcc ## debug line I added
>
On 08/18/2018 05:48 PM, Linda Walsh wrote:
> Is CLANG required for building now?
>
> when I did a "make xconfig" (or any make, for that matter), I get:
>
>> make xconfig
> scripts/kconfig/qconf Kconfig
> invocation line: ./scripts/clang-version.sh gcc ## debug line I added
>
Is CLANG required for building now?
when I did a "make xconfig" (or any make, for that matter), I get:
make xconfig
scripts/kconfig/qconf Kconfig
invocation line: ./scripts/clang-version.sh gcc ## debug line I added
./scripts/clang-version.sh: line 15: ./COPYING: Permission denied
Is CLANG required for building now?
when I did a "make xconfig" (or any make, for that matter), I get:
make xconfig
scripts/kconfig/qconf Kconfig
invocation line: ./scripts/clang-version.sh gcc ## debug line I added
./scripts/clang-version.sh: line 15: ./COPYING: Permission denied
Hi Yoshinori,
On Sun, 19 Aug 2018 01:35:47 +0900 Yoshinori Sato
wrote:
>
> > Commit
> >
> > 85f866b60ba7 ("h8300: switch to NO_BOOTMEM")
> >
> > is missing a Signed-off-by from its committer.
>
> OK. Fixed it.
This last one is still missing your Signed-off-by ...
(it is commit
Hi Yoshinori,
On Sun, 19 Aug 2018 01:35:47 +0900 Yoshinori Sato
wrote:
>
> > Commit
> >
> > 85f866b60ba7 ("h8300: switch to NO_BOOTMEM")
> >
> > is missing a Signed-off-by from its committer.
>
> OK. Fixed it.
This last one is still missing your Signed-off-by ...
(it is commit
On Sat, Aug 18, 2018 at 11:57:00PM +0200, Rafael J. Wysocki wrote:
[...]
> > > > Otherwise we can have something like this:
> > > >
> > > > diff --git a/kernel/time/tick-sched.c b/kernel/time/tick-sched.c
> > > > index da9455a..408c985 100644
> > > > --- a/kernel/time/tick-sched.c
> > > > +++
On Sat, Aug 18, 2018 at 11:57:00PM +0200, Rafael J. Wysocki wrote:
[...]
> > > > Otherwise we can have something like this:
> > > >
> > > > diff --git a/kernel/time/tick-sched.c b/kernel/time/tick-sched.c
> > > > index da9455a..408c985 100644
> > > > --- a/kernel/time/tick-sched.c
> > > > +++
Hi all,
On Tue, 26 Jun 2018 12:18:53 +1000 Stephen Rothwell
wrote:
>
> Today's linux-next merge of the nvdimm tree got a conflict in:
>
> arch/x86/kernel/cpu/mcheck/mce.c
>
> between commit:
>
> d3d6923cd1ae ("x86/mce: Carve out the crashing_cpu check")
>
> from the tip tree and commit:
Hi all,
On Tue, 26 Jun 2018 12:18:53 +1000 Stephen Rothwell
wrote:
>
> Today's linux-next merge of the nvdimm tree got a conflict in:
>
> arch/x86/kernel/cpu/mcheck/mce.c
>
> between commit:
>
> d3d6923cd1ae ("x86/mce: Carve out the crashing_cpu check")
>
> from the tip tree and commit:
Hi all,
On Wed, 11 Jul 2018 13:14:45 +1000 Stephen Rothwell
wrote:
>
> Today's linux-next merge of the driver-core tree got a conflict in:
>
> drivers/iommu/ipmmu-vmsa.c
>
> between commits:
>
> 0b8ac1409641 ("iommu/ipmmu-vmsa: Hook up r8a7796 DT matching code")
> 3701c123e1c1
Hi all,
On Wed, 11 Jul 2018 13:14:45 +1000 Stephen Rothwell
wrote:
>
> Today's linux-next merge of the driver-core tree got a conflict in:
>
> drivers/iommu/ipmmu-vmsa.c
>
> between commits:
>
> 0b8ac1409641 ("iommu/ipmmu-vmsa: Hook up r8a7796 DT matching code")
> 3701c123e1c1
--
donation of $3 to you, contact hams@hotmail.com to verefly
--
donation of $3 to you, contact hams@hotmail.com to verefly
With the special case handling for Blackfin and Metag was removed by
commit 94e58e0ac312 ("export.h: remove code for prefixing symbols with
underscore"), VMLINUX_SYMBOL() is no-no.
Replace the remaining usages, then remove the definition of
VMLINUX_SYMBOL() and VMLINUX_SYMBOL_STR().
no longer
With the special case handling for Blackfin and Metag was removed by
commit 94e58e0ac312 ("export.h: remove code for prefixing symbols with
underscore"), VMLINUX_SYMBOL() is no-no.
Replace the remaining usages, then remove the definition of
VMLINUX_SYMBOL() and VMLINUX_SYMBOL_STR().
no longer
On 18.08.2018 13:26, Thomas Gleixner wrote:
> On Thu, 16 Aug 2018, Heiner Kallweit wrote:
>
>> Recently I started to get warning "NOHZ: local_softirq_pending 202" and
>> I think it's related to mentioned commit (didn't bisect it yet).
>> See log from suspending.
>>
>> I have no reason to think
On 18.08.2018 13:26, Thomas Gleixner wrote:
> On Thu, 16 Aug 2018, Heiner Kallweit wrote:
>
>> Recently I started to get warning "NOHZ: local_softirq_pending 202" and
>> I think it's related to mentioned commit (didn't bisect it yet).
>> See log from suspending.
>>
>> I have no reason to think
KINDLY REPLY stemlightresour...@gmail.com URGENTLY
KINDLY REPLY stemlightresour...@gmail.com URGENTLY
Hello,
syzbot found the following crash on:
HEAD commit:1f7a4c73a739 Merge tag '9p-for-4.19-2' of git://github.com..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=16c46d9a40
kernel config: https://syzkaller.appspot.com/x/.config?x=68e80edb3c9718c5
Hello,
syzbot found the following crash on:
HEAD commit:1f7a4c73a739 Merge tag '9p-for-4.19-2' of git://github.com..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=16c46d9a40
kernel config: https://syzkaller.appspot.com/x/.config?x=68e80edb3c9718c5
On Fri, Aug 17, 2018 at 4:12 PM Frederic Weisbecker wrote:
>
> On Fri, Aug 17, 2018 at 11:32:07AM +0200, Rafael J. Wysocki wrote:
> > On Thursday, August 16, 2018 3:27:24 PM CEST Frederic Weisbecker wrote:
> > > On Thu, Aug 09, 2018 at 07:08:34PM +0200, Rafael J. Wysocki wrote:
> > > > From:
On Fri, Aug 17, 2018 at 4:12 PM Frederic Weisbecker wrote:
>
> On Fri, Aug 17, 2018 at 11:32:07AM +0200, Rafael J. Wysocki wrote:
> > On Thursday, August 16, 2018 3:27:24 PM CEST Frederic Weisbecker wrote:
> > > On Thu, Aug 09, 2018 at 07:08:34PM +0200, Rafael J. Wysocki wrote:
> > > > From:
With a little cooperation from fixdep, we can rather easily quantify the
header bloat phenomenon.
While computing CONFIG_ dependencies, fixdep opens all the headers used
by a given translation unit anyway, so it's rather cheap to have it
record the number and total size of those in the generated
With a little cooperation from fixdep, we can rather easily quantify the
header bloat phenomenon.
While computing CONFIG_ dependencies, fixdep opens all the headers used
by a given translation unit anyway, so it's rather cheap to have it
record the number and total size of those in the generated
In the example for the pwm-vibrator bindings, pwm8 is the direction pin,
and pwm9 is the enable pin. The pwm-names on the vibrator node has these
two values swapped. This patch corrects the values for pwm-names.
Signed-off-by: Brian Masney
---
arch/arm/boot/dts/omap4-droid4-xt894.dts is actual
In the example for the pwm-vibrator bindings, pwm8 is the direction pin,
and pwm9 is the enable pin. The pwm-names on the vibrator node has these
two values swapped. This patch corrects the values for pwm-names.
Signed-off-by: Brian Masney
---
arch/arm/boot/dts/omap4-droid4-xt894.dts is actual
On Fri, Aug 17, 2018 at 7:45 PM Jason Gunthorpe wrote:
>
> Linus would prefer that __deprecated never produce a warning in an
> allyesconfig compile. Since we have been at this state for some time,
> the option no longer has a purpose.
I got rid of the option, but of the code too, and - trying
On Fri, Aug 17, 2018 at 7:45 PM Jason Gunthorpe wrote:
>
> Linus would prefer that __deprecated never produce a warning in an
> allyesconfig compile. Since we have been at this state for some time,
> the option no longer has a purpose.
I got rid of the option, but of the code too, and - trying
This patch removed function named rtw_malloc2d.
I removed this function because this function is used exactly once and
function call have some overhead also.
Maybe this will improve code runtime slightly.
Signed-off-by: Bhaskar Singh
---
drivers/staging/rtl8188eu/core/rtw_efuse.c| 10
This patch removed function named rtw_malloc2d.
I removed this function because this function is used exactly once and
function call have some overhead also.
Maybe this will improve code runtime slightly.
Signed-off-by: Bhaskar Singh
---
drivers/staging/rtl8188eu/core/rtw_efuse.c| 10
On Fri, 2018-08-17 at 23:48 +0100, Greg KH wrote:
> On Fri, Aug 17, 2018 at 08:40:06AM -0700, Rodrigo Vivi wrote:
> > Hi Greg, Ben, and all
> >
> > Is https://www.kernel.org/category/releases.html updated in terms of EOL?
>
> As of right now, for the kernels I maintain, yes, it is correct.
>
>
On Fri, 2018-08-17 at 23:48 +0100, Greg KH wrote:
> On Fri, Aug 17, 2018 at 08:40:06AM -0700, Rodrigo Vivi wrote:
> > Hi Greg, Ben, and all
> >
> > Is https://www.kernel.org/category/releases.html updated in terms of EOL?
>
> As of right now, for the kernels I maintain, yes, it is correct.
>
>
'additional' was misspelled as 'addional'. Fixed it. It is a coding
style change which should have no impact on runtime execution of code.
Signed-off-by: Faisal Mehmood
---
drivers/cdrom/gdrom.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/cdrom/gdrom.c
'additional' was misspelled as 'addional'. Fixed it. It is a coding
style change which should have no impact on runtime execution of code.
Signed-off-by: Faisal Mehmood
---
drivers/cdrom/gdrom.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/cdrom/gdrom.c
'length' was misspelled as 'lenth'. Fixed it. It is a coding style
change which should have no impact on runtime execution of code.
Signed-off-by: Faisal Mehmood
---
drivers/hid/hid-logitech-hidpp.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
'length' was misspelled as 'lenth'. Fixed it. It is a coding style
change which should have no impact on runtime execution of code.
Signed-off-by: Faisal Mehmood
---
drivers/hid/hid-logitech-hidpp.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Keep hdac hdmi codec to be in runtime suspended while entering to
system wide suspend. Currently hdac hdmi codec driver using its
suspend and resume operation in prepare and complete PM callbacks,
and it resumes the hd audio controller (parent of self) from runtime
suspend and blocks the direct
Keep hdac hdmi codec to be in runtime suspended while entering to
system wide suspend. Currently hdac hdmi codec driver using its
suspend and resume operation in prepare and complete PM callbacks,
and it resumes the hd audio controller (parent of self) from runtime
suspend and blocks the direct
Current implementation of hdac hdmi codec driver uses its
suspend/resume operation callback in its prepare/complete callback
which has issues with hdac direct-complete, it has been reviewed earlier
that hdac hdmi codec driver requires a rework
(https://patchwork.kernel.org/patch/10276021/),
but as
Current implementation of hdac hdmi codec driver uses its
suspend/resume operation callback in its prepare/complete callback
which has issues with hdac direct-complete, it has been reviewed earlier
that hdac hdmi codec driver requires a rework
(https://patchwork.kernel.org/patch/10276021/),
but as
On Fri, Aug 17, 2018 at 1:28 PM Palmer Dabbelt wrote:
>
> I remember having sent this on Wednesday, but for some reason I don't see it
> in
> your tree or my outbox so I might be crazy.
You might indeed have been having hallucinations. I don't see any
other pull request from you in my mailbox
On Fri, Aug 17, 2018 at 1:28 PM Palmer Dabbelt wrote:
>
> I remember having sent this on Wednesday, but for some reason I don't see it
> in
> your tree or my outbox so I might be crazy.
You might indeed have been having hallucinations. I don't see any
other pull request from you in my mailbox
We have a need to override the definition of
barrier_before_unreachable() for MIPS, which means we either need to add
architecture-specific code into linux/compiler-gcc.h or we need to allow
the architecture to provide a header that can define the macro before
the generic definition. The latter
Some versions of GCC for the MIPS architecture suffer from a bug which
can lead to instructions from beyond an unreachable statement being
incorrectly reordered into earlier branch delay slots if the unreachable
statement is the only content of a case in a switch statement. This can
lead to
We have a need to override the definition of
barrier_before_unreachable() for MIPS, which means we either need to add
architecture-specific code into linux/compiler-gcc.h or we need to allow
the architecture to provide a header that can define the macro before
the generic definition. The latter
Some versions of GCC for the MIPS architecture suffer from a bug which
can lead to instructions from beyond an unreachable statement being
incorrectly reordered into earlier branch delay slots if the unreachable
statement is the only content of a case in a switch statement. This can
lead to
This series overrides barrier_before_unreachable() for MIPS to add a
.insn assembler directive.
Due to the subsequent __builtin_unreachable(), the assembler can't tell
that a label on the empty inline asm is code rather than data, so any
microMIPS branches targeting it (which sadly can't be
This series overrides barrier_before_unreachable() for MIPS to add a
.insn assembler directive.
Due to the subsequent __builtin_unreachable(), the assembler can't tell
that a label on the empty inline asm is code rather than data, so any
microMIPS branches targeting it (which sadly can't be
Hello Stephen,
I will test these changes and get back.
On 8/18/2018 7:42 AM, Stephen Boyd wrote:
Quoting Taniya Das (2018-08-10 18:53:54)
[v4]
* Add recalc_clk_ops to calculate the clock frequency reading the current
perf state, also add CLK_GET_RATE_NOCACHE flag.
* Cleanup
Hello Stephen,
I will test these changes and get back.
On 8/18/2018 7:42 AM, Stephen Boyd wrote:
Quoting Taniya Das (2018-08-10 18:53:54)
[v4]
* Add recalc_clk_ops to calculate the clock frequency reading the current
perf state, also add CLK_GET_RATE_NOCACHE flag.
* Cleanup
On Sat, Aug 18, 2018 at 8:57 AM Greg KH wrote:
>
> Note, you will have a merge problem with a device tree IIO file and the
> MAINTAINERS file, both resolutions are easy, just take all changed.
Heh, no. In neither case should I take all changes: the IIO was
"delete both sides"), and in the
On Sat, Aug 18, 2018 at 8:57 AM Greg KH wrote:
>
> Note, you will have a merge problem with a device tree IIO file and the
> MAINTAINERS file, both resolutions are easy, just take all changed.
Heh, no. In neither case should I take all changes: the IIO was
"delete both sides"), and in the
On Fri, 3 Aug 2018 22:53:36 +0100
Jonathan Cameron wrote:
> On Thu, 2 Aug 2018 20:18:58 -0400
> Brian Masney wrote:
>
> > The Avago APDS9930 has the same register set as the TAOS/AMS TSL2772 so
> > this patch adds the correct bindings and the appropriate LUX table
> > values derived from the
On Fri, 3 Aug 2018 22:53:36 +0100
Jonathan Cameron wrote:
> On Thu, 2 Aug 2018 20:18:58 -0400
> Brian Masney wrote:
>
> > The Avago APDS9930 has the same register set as the TAOS/AMS TSL2772 so
> > this patch adds the correct bindings and the appropriate LUX table
> > values derived from the
On Thu, 2 Aug 2018 20:19:00 -0400
Brian Masney wrote:
> This patch adds device tree bindings for the tsl2772 ALS / proximity
> sensor for the LG Nexus 5 (hammerhead) phone.
>
> Signed-off-by: Brian Masney
> Signed-off-by: Jonathan Marek
Acked-by: Jonathan Cameron
The precursors are working
On Thu, 2 Aug 2018 20:19:00 -0400
Brian Masney wrote:
> This patch adds device tree bindings for the tsl2772 ALS / proximity
> sensor for the LG Nexus 5 (hammerhead) phone.
>
> Signed-off-by: Brian Masney
> Signed-off-by: Jonathan Marek
Acked-by: Jonathan Cameron
The precursors are working
On Tue, 7 Aug 2018 11:21:01 -0600
Rob Herring wrote:
> On Thu, Aug 02, 2018 at 08:18:59PM -0400, Brian Masney wrote:
> > This patch adds avago,apds9930 to the tsl2772 bindings.
> >
> > Signed-off-by: Brian Masney
> > ---
> > Documentation/devicetree/bindings/iio/light/tsl2772.txt | 1 +
> > 1
On Tue, 7 Aug 2018 11:21:01 -0600
Rob Herring wrote:
> On Thu, Aug 02, 2018 at 08:18:59PM -0400, Brian Masney wrote:
> > This patch adds avago,apds9930 to the tsl2772 bindings.
> >
> > Signed-off-by: Brian Masney
> > ---
> > Documentation/devicetree/bindings/iio/light/tsl2772.txt | 1 +
> > 1
On Thu, 2 Aug 2018 20:18:54 -0400
Brian Masney wrote:
> This patch adds support for optionally reading the proximity led diode
> and current settings from device tree. This was tested using a LG
> Nexus 5 (hammerhead) which requires a different diode than the driver
> default for the IR LED.
>
On Thu, 2 Aug 2018 20:18:54 -0400
Brian Masney wrote:
> This patch adds support for optionally reading the proximity led diode
> and current settings from device tree. This was tested using a LG
> Nexus 5 (hammerhead) which requires a different diode than the driver
> default for the IR LED.
>
On Tue, 7 Aug 2018 11:20:28 -0600
Rob Herring wrote:
> On Fri, Aug 03, 2018 at 10:51:23PM +0100, Jonathan Cameron wrote:
> > On Thu, 2 Aug 2018 20:18:57 -0400
> > Brian Masney wrote:
> >
> > > This patch adds device tree bindings to the tsl2772 driver for the
> > > regulator framework.
> >
On Tue, 7 Aug 2018 11:20:28 -0600
Rob Herring wrote:
> On Fri, Aug 03, 2018 at 10:51:23PM +0100, Jonathan Cameron wrote:
> > On Thu, 2 Aug 2018 20:18:57 -0400
> > Brian Masney wrote:
> >
> > > This patch adds device tree bindings to the tsl2772 driver for the
> > > regulator framework.
> >
On Tue, 7 Aug 2018 10:54:26 -0600
Rob Herring wrote:
> On Fri, Aug 03, 2018 at 10:48:38PM +0100, Jonathan Cameron wrote:
> > On Thu, 2 Aug 2018 20:18:55 -0400
> > Brian Masney wrote:
> >
> > > This patch adds the new properties amstaos,proximity-diodes and
> > > led-max-microamp to the
On Tue, 7 Aug 2018 10:54:26 -0600
Rob Herring wrote:
> On Fri, Aug 03, 2018 at 10:48:38PM +0100, Jonathan Cameron wrote:
> > On Thu, 2 Aug 2018 20:18:55 -0400
> > Brian Masney wrote:
> >
> > > This patch adds the new properties amstaos,proximity-diodes and
> > > led-max-microamp to the
On Sat, 4 Aug 2018 08:55:06 +0200
Marcus Folkesson wrote:
> Hi Andy and Jonathan,
>
>
> On Fri, Aug 03, 2018 at 11:09:22PM +0100, Jonathan Cameron wrote:
> > On Thu, 2 Aug 2018 22:52:00 +0300
> > Andy Shevchenko wrote:
> >
> > > On Thu, Aug 2, 2018 at 10:15 PM, Marcus Folkesson
> > >
On Sat, 4 Aug 2018 08:55:06 +0200
Marcus Folkesson wrote:
> Hi Andy and Jonathan,
>
>
> On Fri, Aug 03, 2018 at 11:09:22PM +0100, Jonathan Cameron wrote:
> > On Thu, 2 Aug 2018 22:52:00 +0300
> > Andy Shevchenko wrote:
> >
> > > On Thu, Aug 2, 2018 at 10:15 PM, Marcus Folkesson
> > >
On Sat, 18 Aug 2018 23:30:05 +0900,
Stephen Rothwell wrote:
>
> [1 ]
> Hi Yoshinori,
>
> Commits
>
> 785b0958b55d ("h8300: gcc-8.1 fix")
> 8eabc2d5fae0 ("h8300: Add missing output register.")
>
> are missing a Signed-off-by from their authors and committers.
>
> Commit
>
>
On Sat, 18 Aug 2018 23:30:05 +0900,
Stephen Rothwell wrote:
>
> [1 ]
> Hi Yoshinori,
>
> Commits
>
> 785b0958b55d ("h8300: gcc-8.1 fix")
> 8eabc2d5fae0 ("h8300: Add missing output register.")
>
> are missing a Signed-off-by from their authors and committers.
>
> Commit
>
>
On Sat, 2018-08-18 at 19:21 +0300, Sergei Shtylyov wrote:
> On 08/18/2018 07:15 PM, Joe Perches wrote:
> > > > We should use NULL to compare with pointer-typed value rather than
> > > > 0. The issue is detected with the help of Coccinelle.
> > >
> > >Your description stopped to match the
On Sat, 2018-08-18 at 19:21 +0300, Sergei Shtylyov wrote:
> On 08/18/2018 07:15 PM, Joe Perches wrote:
> > > > We should use NULL to compare with pointer-typed value rather than
> > > > 0. The issue is detected with the help of Coccinelle.
> > >
> > >Your description stopped to match the
Hello,
syzbot found the following crash on:
HEAD commit:1f7a4c73a739 Merge tag '9p-for-4.19-2' of git://github.com..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=10cccef240
kernel config: https://syzkaller.appspot.com/x/.config?x=68e80edb3c9718c5
On 08/18/2018 06:53 PM, Sergei Shtylyov wrote:
>> We should use NULL to compare with pointer-typed value rather than
>> 0. The issue is detected with the help of Coccinelle.
>
>Your description stopped to match the patch in v2.
And your subject as well...
>Actually, this X == NULL
Hello,
syzbot found the following crash on:
HEAD commit:1f7a4c73a739 Merge tag '9p-for-4.19-2' of git://github.com..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=10cccef240
kernel config: https://syzkaller.appspot.com/x/.config?x=68e80edb3c9718c5
On 08/18/2018 06:53 PM, Sergei Shtylyov wrote:
>> We should use NULL to compare with pointer-typed value rather than
>> 0. The issue is detected with the help of Coccinelle.
>
>Your description stopped to match the patch in v2.
And your subject as well...
>Actually, this X == NULL
On 08/18/2018 07:15 PM, Joe Perches wrote:
>>> We should use NULL to compare with pointer-typed value rather than
>>> 0. The issue is detected with the help of Coccinelle.
>>
>>Your description stopped to match the patch in v2.
>>Actually, this X == NULL to !x preference is largely
On 08/18/2018 07:15 PM, Joe Perches wrote:
>>> We should use NULL to compare with pointer-typed value rather than
>>> 0. The issue is detected with the help of Coccinelle.
>>
>>Your description stopped to match the patch in v2.
>>Actually, this X == NULL to !x preference is largely
On Sat, 2018-08-18 at 18:53 +0300, Sergei Shtylyov wrote:
> On 08/18/2018 09:16 AM, zhong jiang wrote:
>
> > We should use NULL to compare with pointer-typed value rather than
> > 0. The issue is detected with the help of Coccinelle.
>
>Your description stopped to match the patch in v2.
>
On Sat, 2018-08-18 at 18:53 +0300, Sergei Shtylyov wrote:
> On 08/18/2018 09:16 AM, zhong jiang wrote:
>
> > We should use NULL to compare with pointer-typed value rather than
> > 0. The issue is detected with the help of Coccinelle.
>
>Your description stopped to match the patch in v2.
>
Initially Common Clock Framework isn't aware of the clock-enable status,
this results in enabling of clocks that were enabled by bootloader. This
is not a big deal for a regular clock-gates, but for PLL's it may have
some unpleasant consequences. Thus re-enabling PLLX (the main CPU parent
clock)
Currently all PLL's on Tegra20 use a hardcoded delay despite of having
a lock-status bit. The lock-status polling was disabled ~7 years ago
because apparently some PLL was failing to lock. That issue isn't
observable with the modern kernel, hence let's assume it was some
unrelated bug and enable
Initially Common Clock Framework isn't aware of the clock-enable status,
this results in enabling of clocks that were enabled by bootloader. This
is not a big deal for a regular clock-gates, but for PLL's it may have
some unpleasant consequences. Thus re-enabling PLLX (the main CPU parent
clock)
Currently all PLL's on Tegra20 use a hardcoded delay despite of having
a lock-status bit. The lock-status polling was disabled ~7 years ago
because apparently some PLL was failing to lock. That issue isn't
observable with the modern kernel, hence let's assume it was some
unrelated bug and enable
Add a built-in bluetooth 5 support for MT7622.
Signed-off-by: Ryder Lee
Acked-by: Sean Wang
---
arch/arm64/boot/dts/mediatek/mt7622.dtsi | 7 +++
1 file changed, 7 insertions(+)
diff --git a/arch/arm64/boot/dts/mediatek/mt7622.dtsi
b/arch/arm64/boot/dts/mediatek/mt7622.dtsi
index
Add a built-in bluetooth 5 support for MT7622.
Signed-off-by: Ryder Lee
Acked-by: Sean Wang
---
arch/arm64/boot/dts/mediatek/mt7622.dtsi | 7 +++
1 file changed, 7 insertions(+)
diff --git a/arch/arm64/boot/dts/mediatek/mt7622.dtsi
b/arch/arm64/boot/dts/mediatek/mt7622.dtsi
index
Add support for the bananapi R64 (BPI-R64) development board from
BIPAI KEJI. Detailed hardware information for BPI-R64 which could be
found on http://wiki.banana-pi.org/Banana_Pi_BPI-R64
Signed-off-by: Ryder Lee
---
changes since v1:
- add missing sata nodes.
- fix pinctrl-0 for pcie@1,0.
-
Add support for the bananapi R64 (BPI-R64) development board from
BIPAI KEJI. Detailed hardware information for BPI-R64 which could be
found on http://wiki.banana-pi.org/Banana_Pi_BPI-R64
Signed-off-by: Ryder Lee
---
changes since v1:
- add missing sata nodes.
- fix pinctrl-0 for pcie@1,0.
-
Update binding document for bananapi BPI-R64 board being supported.
Signed-off-by: Ryder Lee
Reviewed-by: Rob Herring
---
Documentation/devicetree/bindings/arm/mediatek.txt | 3 +++
1 file changed, 3 insertions(+)
diff --git a/Documentation/devicetree/bindings/arm/mediatek.txt
Update binding document for bananapi BPI-R64 board being supported.
Signed-off-by: Ryder Lee
Reviewed-by: Rob Herring
---
Documentation/devicetree/bindings/arm/mediatek.txt | 3 +++
1 file changed, 3 insertions(+)
diff --git a/Documentation/devicetree/bindings/arm/mediatek.txt
Fix ram size to 512 megabytes and sort nodes in alphabetical order.
Signed-off-by: Ryder Lee
Acked-by: Sean Wang
---
arch/arm64/boot/dts/mediatek/mt7622-rfb1.dts | 196 +--
1 file changed, 98 insertions(+), 98 deletions(-)
diff --git
Fix ram size to 512 megabytes and sort nodes in alphabetical order.
Signed-off-by: Ryder Lee
Acked-by: Sean Wang
---
arch/arm64/boot/dts/mediatek/mt7622-rfb1.dts | 196 +--
1 file changed, 98 insertions(+), 98 deletions(-)
diff --git
1 - 100 of 432 matches
Mail list logo
