Fixes checkpatch.pl warnings:
CHECK: spaces preferred around that '-' (ctx:VxV)
CHECK: spaces preferred around that '+' (ctx:VxV)
CHECK: spaces preferred around that '*' (ctx:VxV)
CHECK: spaces preferred around that '|' (ctx:VxV)
Signed-off-by: Valentin Vidic
---
On Wed, 2019-09-04 at 20:50 +0200, Roberto Sassu wrote:
> This patch fixes two issues introduced with commit 0b6cf6b97b7e ("tpm: pass
> an array of tpm_extend_digest structures to tpm_pcr_extend()").
>
> It initializes the algorithm in init_digests() for trusted keys, and moves
> the algorithm
On Sat, 2019-09-07 at 22:02 +0300, Jarkko Sakkinen wrote:
> On Wed, 2019-09-04 at 20:50 +0200, Roberto Sassu wrote:
> > This patch fixes two issues introduced with commit 0b6cf6b97b7e ("tpm: pass
> > an array of tpm_extend_digest structures to tpm_pcr_extend()").
> >
> > It initializes the
On Fri, 6 Sep 2019, Julius Werner wrote:
> FWIW, I found a suitable workaround now to get my use case working
> with existing kernels: I can do the mode switch from userspace, then
> after the device reenumerates I can manually disable any interfaces I
> don't like by writing 0 to their
On Sat, Sep 7, 2019 at 8:00 AM Thomas Gleixner wrote:
>
> Ok let me find a testbox to figure out whats wrong there.
Honestly, it looks like we should just revert that commit, since we
never used to clear the LDR bits before either, and the bug it "fixes"
doesn't really seem to be a bug (well,
On Sat, 2019-09-07 at 18:58 +, Valentin Vidic wrote:
> Fixes checkpatch.pl warnings:
>
> CHECK: No space is necessary after a cast
Please always try to improve the code rather
than shutup checkpatch warnings.
> diff --git a/drivers/staging/exfat/exfat_core.c
>
On Sat, 2019-09-07 at 18:42 +0100, Greg KH wrote:
> On Sat, Sep 07, 2019 at 07:35:42PM +0200, Sandro Volery wrote:
> >
> > > > > On 7 Sep 2019, at 19:29, Greg KH wrote:
> > > > On Sat, Sep 07, 2019 at 07:23:59PM +0200, Sandro Volery wrote:
> > > > Dear Greg,
> > > > I am pretty sure the issue
On Sat, Sep 7, 2019 at 12:17 PM Linus Torvalds
wrote:
>
> I'm really not clear on why it's a good idea to clear the LDR bits on
> shutdown, and commit 558682b52919 ("x86/apic: Include the LDR when
> clearing out APIC registers") just looks pointless. And now it has
> proven to break some
> Here's a couple of updates for the MMP2 SoC devicetree files.
> I'm wondering if they could be applied to the armsoc tree?
>
> Compared to previous submission, the only change is the addition of
> Acks from Pavel.
Any news here? Having up-to-date dts is kind-of useful
Best regards,
On Thu, Sep 5, 2019 at 5:24 PM Arnd Bergmann wrote:
> diff --git a/arch/sparc/kernel/sys_sparc_64.c
> b/arch/sparc/kernel/sys_sparc_64.c
> index ccc88926bc00..5ad0494df367 100644
> --- a/arch/sparc/kernel/sys_sparc_64.c
> +++ b/arch/sparc/kernel/sys_sparc_64.c
> @@ -340,21 +340,21 @@
Is there any objection from anybody to applying the first two patches, the
reverts of the reverts that went into 5.3-rc5, for 5.3 and pursuing
discussion and development using the last two patches in this series as a
starting point for a sane allocation policy that just works by default for
> On 7 Sep 2019, at 21:27, Joe Perches wrote:
>
> On Sat, 2019-09-07 at 18:42 +0100, Greg KH wrote:
>>> On Sat, Sep 07, 2019 at 07:35:42PM +0200, Sandro Volery wrote:
>>>
>> On 7 Sep 2019, at 19:29, Greg KH wrote:
> On Sat, Sep 07, 2019 at 07:23:59PM +0200, Sandro Volery wrote:
On Sat, Sep 7, 2019 at 12:51 PM David Rientjes wrote:
>
> Andrea acknowledges the swap storm that he reported would be fixed with
> the last two patches in this series
The problem is that even you aren't arguing that those patches should
go into 5.3.
So those fixes aren't going in, so "the swap
On Sat, Sep 7, 2019 at 9:40 PM Pavel Machek wrote:
>
>
> > Here's a couple of updates for the MMP2 SoC devicetree files.
> > I'm wondering if they could be applied to the armsoc tree?
> >
> > Compared to previous submission, the only change is the addition of
> > Acks from Pavel.
>
> Any news
On Sat, 2019-09-07 at 21:51 +0200, Sandro Volery wrote:
> > On 7 Sep 2019, at 21:27, Joe Perches wrote:
[]
> > As long as git diff -w shows no difference and a compiled
> > object comparison before and after the change shows no
> > difference, I think it's fine.
>
> My thoughts, too. I didn't
On Sat, 2019-09-07 at 11:09 +0200, volery wrote:
> There were a lot of styling problems using space then tab or spaces
> instead of tabs in that file. Especially the entire function at line
> 2677.
> Also added a space before the : on line 2221.
You do not have an appropriate subject line.
This
On Sat, 7 Sep 2019, Chris Wilson wrote:
> Quoting Thomas Gleixner (2019-09-07 16:00:17)
> > Does this only happen with that CPU0 hotplug stuff enabled or on CPUs other
> > than CPU0 as well? That hotplug CPU0 stuff is a bandaid so I wouldn't be
> > surprised if we broke that somehow.
>
> If I
On Sat, Sep 7, 2019 at 9:15 PM Joe Perches wrote:
>
> Standard integer promotion is already done and %hx and %hhx is useless
> so do not encourage the use of %hh[xudi] or %h[xudi].
>
> As Linus said in:
> Link:
>
Sakari,
> Convert the remaining %pf users to %ps to prepare for the removal of
> the old %pf conversion specifier support.
Applied to 5.4/scsi-queue, thanks!
--
Martin K. Petersen Oracle Linux Engineering
Sandro V
>> On 7 Sep 2019, at 22:04, Joe Perches wrote:
>>
>> On Sat, 2019-09-07 at 11:09 +0200, volery wrote:
>> There were a lot of styling problems using space then tab or spaces
>> instead of tabs in that file. Especially the entire function at line
>> 2677.
>> Also added a space before
Bjorn,
> This series adds a new ufs vops to allow platform specific methods for
> resetting an attached UFS device, then implements this for the
> Qualcomm driver. This reset seems to be necessary for the majority of
> Dragonboard845c devices.
Applied to 5.4/scsi-queue, thanks!
--
Martin K.
YueHaibing,
> Use kmemdup rather than duplicating its implementation
Applied to 5.4/scsi-queue. Thanks!
--
Martin K. Petersen Oracle Linux Engineering
YueHaibing,
> Use devm_platform_ioremap_resource() to simplify the code a bit.
> This is detected by coccinelle.
Applied to 5.4/scsi-queue, thanks.
--
Martin K. Petersen Oracle Linux Engineering
YueHaibing,
> Use devm_platform_ioremap_resource() to simplify the code a bit.
> This is detected by coccinelle.
Applied to 5.4/scsi-queue, thanks.
--
Martin K. Petersen Oracle Linux Engineering
YueHaibing,
> Use devm_platform_ioremap_resource() to simplify the code a bit.
> This is detected by coccinelle.
Applied to 5.4/scsi-queue, thanks.
--
Martin K. Petersen Oracle Linux Engineering
On Sat, 7 Sep 2019, Linus Torvalds wrote:
> On Sat, Sep 7, 2019 at 8:00 AM Thomas Gleixner wrote:
>
> So why wouldn't we just revert it?
That's what I just replied to Chris. Can you do it right away or should I queue
it up?
Thanks,
tglx
On Sat 2019-09-07 21:57:42, Arnd Bergmann wrote:
> On Sat, Sep 7, 2019 at 9:40 PM Pavel Machek wrote:
> >
> >
> > > Here's a couple of updates for the MMP2 SoC devicetree files.
> > > I'm wondering if they could be applied to the armsoc tree?
> > >
> > > Compared to previous submission, the only
Fixed open parenthesis at the end of the line on line 327.
Signed-off-by: Sandro Volery
---
drivers/staging/wlan-ng/cfg80211.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/staging/wlan-ng/cfg80211.c
b/drivers/staging/wlan-ng/cfg80211.c
index
kunit wrapper script ('kunit.py') receives a sub-command (only 'run' for
now) as its argument. If no sub-command is given, it prints help
message and just quit. However, an example command in the kunit
documentation for a verification of kunit is missing the sub-command.
This commit fixes the
On 06.09.2019 18:10, Arnd Bergmann wrote:
> On architectures such as ARM that have a list of symbols exported
> from assembler in a separate C file, we get a lot of new warnings:
>
> WARNING: "__ashrdi3" [vmlinux] is a static (unknown) WARNING:
> "__lshrdi3" [vmlinux] is a static (unknown)
On 9/6/19 4:17 PM, Joel Fernandes wrote:
On Thu, Sep 05, 2019 at 03:25:45PM +0200, Viktor Rosendahl wrote:
+
+__init static int latency_fsnotify_init(void)
+{
+ fsnotify_wq = alloc_workqueue("tr_max_lat_wq",
+ WQ_UNBOUND | WQ_HIGHPRI, 0);
+ if
On Sat, Sep 7, 2019 at 1:44 PM Thomas Gleixner wrote:
>
> That's what I just replied to Chris. Can you do it right away or should I
> queue it up?
Done.
Thanks,
Linus
On Sat, 7 Sep 2019, Markus Heiser wrote:
> Am 07.09.19 um 20:04 schrieb Mauro Carvalho Chehab:
> > No idea. I would actually prefer to just remove the restriction, and let
> > the SPDX header to be anywhere inside the first comment block inside a
> > file [2].
>
> > That's basically how this
On Fri, 2019-09-06 at 14:37 +0200, Jan Lübbe wrote:
> This is due to the SPI accesses performed by tis_int_handler (which
> will sleep). Switching to devm_request_threaded_irq fixes this and
> leads to a successful IRQ probe.
Aah, right through tpm_tis_read32/write32(). This is definitely a new
On Thu, Sep 05, 2019 at 04:22:21PM -0700, Brendan Shanks wrote:
> Add emulation of the sgdt, sidt, and smsw instructions for 64-bit
> processes.
>
> Wine users have encountered a number of 64-bit Windows games that use
> these instructions (particularly sgdt), and were crashing when run on
>
__online_page_set_limits() is a dummy function and an extra call
to this function can be avoided.
Signed-off-by: Souptick Joarder
---
drivers/xen/balloon.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/xen/balloon.c b/drivers/xen/balloon.c
index 4e11de6..05b1f7e 100644
---
As both the callers of this dummy __online_page_set_limits()
is removed, this can be removed permanently.
Signed-off-by: Souptick Joarder
---
include/linux/memory_hotplug.h | 1 -
mm/memory_hotplug.c| 5 -
2 files changed, 6 deletions(-)
diff --git
__online_page_set_limits() is a dummy function and an extra call
to this function can be avoided.
Signed-off-by: Souptick Joarder
---
drivers/hv/hv_balloon.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/hv/hv_balloon.c b/drivers/hv/hv_balloon.c
index 6fb4ea5..9bab443 100644
---
__online_page_set_limits() is a dummy function and an extra call
to this can be avoided.
As both of the callers are now removed, __online_page_set_limits()
can be removed permanently.
Souptick Joarder (3):
hv_ballon: Avoid calling dummy function __online_page_set_limits()
xen/ballon: Avoid
Hi Shuah,
On Fri, Sep 6, 2019 at 5:36 PM Shuah Khan wrote:
>
> Hi Rafael,
>
> Please pull the following update for Linux 5.4-rc1 or 5.4-rc2 depending
> on your pull request schedule for Linus.
>
> This cpupower update for Linux 5.4-rc1 consists of bug fixes and
> German translation updates from
Use constants and fix checkpatch.pl warnings:
CHECK: No space is necessary after a cast
Signed-off-by: Valentin Vidic
---
v2: Use constants where possible
drivers/staging/exfat/exfat_core.c | 94 ++---
drivers/staging/exfat/exfat_super.c | 66 ++--
2
On Wed, 2019-09-04 at 22:03 +0300, ivan.laz...@gmail.com wrote:
> From: Ivan Lazeev
>
> Bug link: https://bugzilla.kernel.org/show_bug.cgi?id=195657
>
> cmd/rsp buffers are expected to be in the same ACPI region.
> For Zen+ CPUs BIOS's might report two different regions, some of
> them also
Dear sir/madam
My name is Mrs. Mariam Kabore. I have decided to seek a confidential
co-operation with you for the execution of the deal described
hereunder for our mutual benefit. I Hope you will keep it a secret due
to the nature of the transaction. During the course of our audit last
month, I
On Sat, 07 Sep 2019 09:14:49 -0700, Theodore Dubois said:
> If Iâm reading this right, this is a sampling event which overflows 4000
> times a second. But perf then does a poll call which wakes up on this FD with
> POLLIN after 1.637 seconds, instead of 0.00025 seconds.
No, it *takes a sample*
On Sat, Sep 07, 2019 at 09:55:18PM +0300, Jarkko Sakkinen wrote:
On Tue, 2019-09-03 at 15:43 -0400, Sasha Levin wrote:
Right. I gave a go at backporting a few patches and this happens to be
one of them. It will be a while before it goes in a stable tree
(probably way after after LPC).
It
On Sat, 07 Sep 2019 09:14:49 -0700, Theodore Dubois said:
Reading what it actually says rather than what I thought it said.. :)
Events come in two flavors: counting and sampled. A counting event is
one that is used for counting the aggregate number of events that
The pull request you sent on Sat, 7 Sep 2019 19:40:33 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc.git
> tags/char-misc-5.3-rc8
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/b3a9964cfa690150e49ae75ba16416ccaac3a8ba
Thank you!
--
On Sat, Sep 7, 2019 at 2:05 AM John Hubbard wrote:
> While building with !CONFIG_GPIOLIB, I experienced a build failure,
> because driver.h in that configuration supplies both a static and
> a non-static version of these routines:
I think this is fixed in my latest version of the "devel"
On Sep 7, 2019, at 3:45 PM, Valdis Klētnieks wrote:
> So an entry is made in the buffer. It's not clear that this immediately
> triggers
> a signal…
I think the documentation says it does when wakeup_events is 1. The code for
perf backs this up:
On Sat, Sep 07, 2019 at 11:12:59PM +0200, Viktor Rosendahl wrote:
> On 9/6/19 4:17 PM, Joel Fernandes wrote:
> > On Thu, Sep 05, 2019 at 03:25:45PM +0200, Viktor Rosendahl wrote:
>
> > > +
> > > +__init static int latency_fsnotify_init(void)
> > > +{
> > > + fsnotify_wq =
The recently introduced haltpoll driver is largely only useful with
haltpoll governor. To allow drivers to associate with a particular idle
behaviour, add a @governor property to 'struct cpuidle_driver' and thus
allow a cpuidle driver to switch to a *preferred* governor on idle driver
Right now, guest current governors have the following ratings:
* ladder-> 10
* teo -> 19
* menu -> 20
* haltpoll -> 21
* ladder + nohz=off -> 25
haltpoll governor got introduced and it is now the default governor given
its highest rating --
cpuidle-haltpoll can be built as a module to allow optional late load.
Given we are setting @owner to THIS_MODULE, cpuidle will attempt to grab a
module reference every time a cpuidle_device is registered -- so
essentially all online cpus get a reference.
This prevents for the module to be
When a user loads cpuidle-haltpoll on a non KVM guest the module will
successfully load, even though idle driver registration didn't take
place.
We should instead return -ENODEV signaling the user that the driver can't
be loaded, like other error paths in haltpoll_init(). An example of such
Hey,
Presented herewith a series with aims to tie in together the haltpoll
idle driver and governor, without sacrificing previous governor setups.
In addition, there are a few fixes with respect to module loading for
cpuidle-haltpoll.
The series is organized as follows:
Patch 1: Allows idle
Hi Yuehaibing,
> >> Use devm_platform_ioremap_resource() to simplify the code a bit.
> >> This is detected by coccinelle.
> >>
> >> Reported-by: Hulk Robot
> >
> > This tag does not look real... First of all where is the report?
>
> It is our internal CI robot, which is unavailable to external
On Sun, 2019-09-08 at 00:49 +0300, Jarkko Sakkinen wrote:
> On Wed, 2019-09-04 at 22:03 +0300, ivan.laz...@gmail.com wrote:
> > From: Ivan Lazeev
> >
> > Bug link: https://bugzilla.kernel.org/show_bug.cgi?id=195657
> >
> > cmd/rsp buffers are expected to be in the same ACPI region.
> > For Zen+
Hi Han,
FYI, the error/warning still remains.
tree:
https://kernel.googlesource.com/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 950b07c14e8c59444e2359f15fd70ed5112e11a0
commit: 7a78a7f7695bf9ef9cef3c06fbc5fa4573fd0eef power: reset:
nvmem-reboot-mode: use NVMEM as reboot mode
The arch special options are a little long, so create a submenu for them.
Signed-off-by: Changbin Du
---
lib/Kconfig.debug | 4
1 file changed, 4 insertions(+)
diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
index 868fa64a0901..96047140be93 100644
--- a/lib/Kconfig.debug
+++
Move error injection, coverage, testing options to a new submenu
'Kernel Testing and Coverage'. They are all for test purpose.
Signed-off-by: Changbin Du
---
lib/Kconfig.debug | 485 +++---
1 file changed, 245 insertions(+), 240 deletions(-)
diff --git
Group generic kernel debugging instruments sysrq/kgdb/ubsan together into
a new submenu.
Signed-off-by: Changbin Du
---
lib/Kconfig.debug | 12
1 file changed, 8 insertions(+), 4 deletions(-)
diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
index 5960e2980a8a..868fa64a0901
This series is a trivial improvment for the layout of 'kernel hacking'
configuration menu. Now we have many items in it which makes takes
a little time to look up them since they are not well structured yet.
Early discussion is here:
https://lkml.org/lkml/2019/9/1/39
Changbin Du (8):
Group these similar runtime data structures verification options together.
Signed-off-by: Changbin Du
---
lib/Kconfig.debug | 24 ++--
1 file changed, 14 insertions(+), 10 deletions(-)
diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
index 96047140be93..3c9674483ec2
They are similar options so place them together.
Signed-off-by: Changbin Du
---
lib/Kconfig.debug | 58 +++
1 file changed, 29 insertions(+), 29 deletions(-)
diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
index ca2083350178..99c6dbd64ce7 100644
I think DEBUG_BUGVERBOSE is a dmesg option which gives more debug info
to dmesg.
Signed-off-by: Changbin Du
---
lib/Kconfig.debug | 18 +-
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
index 740ada6744f6..bb82a02f6172 100644
They are both memory debug options to debug kernel stack issues.
Signed-off-by: Changbin Du
---
lib/Kconfig.debug | 24
1 file changed, 12 insertions(+), 12 deletions(-)
diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
index 99c6dbd64ce7..458d2a4435a4 100644
---
Create a submenu 'Scheduler Debugging' for scheduler debugging options.
Signed-off-by: Changbin Du
---
lib/Kconfig.debug | 4
1 file changed, 4 insertions(+)
diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
index 458d2a4435a4..740ada6744f6 100644
--- a/lib/Kconfig.debug
+++
This is a preview:
│ ┌───┐ │
│ │printk and dmesg options ---> │ │
│ │Compile-time checks and compiler options ---> │ │
│ │Generic Kernel Debugging Instruments
On Sat, 7 Sep 2019, Linus Torvalds wrote:
> > Andrea acknowledges the swap storm that he reported would be fixed with
> > the last two patches in this series
>
> The problem is that even you aren't arguing that those patches should
> go into 5.3.
>
For three reasons: (a) we lack a test result
syzbot has found a reproducer for the following crash on:
HEAD commit:a2c11b03 kcm: use BPF_PROG_RUN
git tree: bpf-next
console output: https://syzkaller.appspot.com/x/log.txt?x=13d46ec160
kernel config: https://syzkaller.appspot.com/x/.config?x=cf0c85d15c20ade3
dashboard link:
Use rdev->regmap/>dev instead of lp87565->regmap/lp87565->dev.
In additional, the lp87565->dev actually is the parent mfd device,
so the dev_err message is misleading here with lp87565->dev.
Signed-off-by: Axel Lin
---
drivers/regulator/lp87565-regulator.c | 5 ++---
1 file changed, 2
Use rdev->regmap/>dev instead of lp87565->regmap/lp87565->dev.
In additional, the lp87565->dev actually is the parent mfd device,
so the dev_err message is misleading here with lp87565->dev.
Signed-off-by: Axel Lin
---
v2: Add lp87565 prefix in subject line
If v4l2_m2m_init() fails, m2m_dev pointer will be set ERR_PTR(-ENOMEM),
then kfree m2m_dev will triger BUG_ON, see below, fix it by setting m2m_dev
to NULL.
vim2m vim2m.0: Failed to init mem2mem device
[ cut here ]
kernel BUG at mm/slub.c:3944!
invalid opcode:
> On Sep 7, 2019, at 9:47 PM, Greg Kroah-Hartman
> wrote:
>
> On Tue, Aug 20, 2019 at 01:26:38PM -0700, Nadav Amit wrote:
>> Francois reported that VMware balloon gets stuck after a balloon reset,
>> when the VMCI doorbell is removed. A similar error can occur when the
>> balloon driver is
On 07.09.19 23:47, Souptick Joarder wrote:
__online_page_set_limits() is a dummy function and an extra call
to this function can be avoided.
Signed-off-by: Souptick Joarder
Reviewed-by: Juergen Gross
Juergen
> Subject: [PATCHv2] nvme: Assign subsy instance from first ctrl
I'm not sure but, I have not seen 'subsy' thing before. Maybe
s/sybsy/subsys/ ?
>
> The namespace disk names must be unique for the lifetime of the
> subsystem. This was accomplished by using their parent subsystems'
> instances
> Am 06.09.2019 um 22:46 schrieb H. Nikolaus Schaller :
>
> Hi,
>
>> Am 06.09.2019 um 05:01 schrieb Viresh Kumar :
>>
>> On 05-09-19, 07:32, Tony Lindgren wrote:
>>> * H. Nikolaus Schaller [190904 08:54]:
This adds code and tables to read the silicon revision and
eFuse (speed
For the ti-cpufreq driver we need a clear separation between omap34 and omap36
families
since they have different silicon revisions and efuses.
So far ti,omap3630/ti,omap36xx is just an additional flag to ti,omap3 while
omap34 has no
required entry.
Therefore we can not match omap34 boards
* clarify that we now need either "ti,omap3430" or "ti,omap3630" or "ti,am3517"
for omap3 chips
* clarify that "ti,omap3" has no default
* clarify that AM33x is not an "ti,omap3"
* clarify that the list of boards is incomplete
* remove some "ti,am33xx", "ti,omap3"
* add some missing "ti,omap4"
This adds code and tables to read the silicon revision and
eFuse (speed binned / 720 MHz grade) bits for selecting
opp-v2 table entries.
Since these bits are not always part of the syscon register
range (like for am33xx, am43, dra7), we add code to directly
read the register values using
In addition, move omap3 from whitelist to blacklist in cpufreq-dt-platdev
in the same patch, because doing either first breaks operation and
may make trouble in bisect.
We also can remove opp-v1 table for omap3-n950-n9 since it is now
automatically detected.
We also fix a wrong OPP4 voltage for
Changes PATCH V1:
* fix typo in omap3-ldp.dts
(reported by Tony Lindgren )
* extend commit message to describe the bit patterns needed
for opp-supported-hw
* add error check to ioremap()
(suggested by Christ van Willegen )
* update Documentation/devicetree/bindings/arm/omap/omap.txt
* change
* Qian Cai wrote:
> The commit 108c14858b9e ("locking/lockdep: Add support for dynamic
> keys") introduced a boot warning on powerpc below, because since the
> commit 2d4f567103ff ("KVM: PPC: Introduce kvm_tmp framework") adds
> kvm_tmp[] into the .bss section and then free the rest of unused
On Fri, 6 Sep 2019 22:46:49 +0200
"H. Nikolaus Schaller" wrote:
> Hi,
>
> > Am 06.09.2019 um 05:01 schrieb Viresh Kumar :
> >
> > On 05-09-19, 07:32, Tony Lindgren wrote:
> >> * H. Nikolaus Schaller [190904 08:54]:
> >>> This adds code and tables to read the silicon revision and
> >>>
On Fri, Sep 06, 2019 at 05:10:10PM +0200, Arnd Bergmann wrote:
> On kernels without CONFIG_MMU, we get a link error for the siw
> driver:
>
> drivers/infiniband/sw/siw/siw_mem.o: In function `siw_umem_get':
> siw_mem.c:(.text+0x4c8): undefined reference to `can_do_mlock'
>
> I don't know whether
Hi Adam,
> Am 02.09.2019 um 23:10 schrieb Adam Ford :
>
> On Mon, Sep 2, 2019 at 10:46 AM H. Nikolaus Schaller
> wrote:
>>
>>
>>
>> But my tests show that decoding works now. So you already might give it a
>> try.
>
> I am traveling all this week, but I have an omap3530, DM3730
>
From: Colin Ian King
Don't populate the array pd on the stack but instead make it
static const. Makes the object code smaller by 100 bytes.
Before:
textdata bss dec hex filename
51463 13016 128 64607fc5f sound/soc/codecs/rt1011.o
After:
textdata bss
> Am 07.09.2019 um 08:56 schrieb H. Nikolaus Schaller :
>
> This adds code and tables to read the silicon revision and
> eFuse (speed binned / 720 MHz grade) bits for selecting
> opp-v2 table entries.
>
> Since these bits are not always part of the syscon register
> range (like for am33xx,
From: Colin Ian King
Don't populate the array pd on the stack but instead make it
static const. Makes the object code smaller by 93 bytes.
Before:
textdata bss dec hex filename
389619784 64 48809bea9 sound/soc/codecs/rt1305.o
After:
textdata bss
From: Colin Ian King
Don't populate the array pd on the stack but instead make it
static const. Makes the object code smaller by 82 bytes.
Before:
textdata bss dec hex filename
265487288 64 33900846c sound/soc/codecs/rt1308.o
After:
textdata bss
On 06-09-19, 13:38, Stephen Boyd wrote:
> Quoting Vinod Koul (2019-09-05 21:56:59)
> > Update the gcc qcs404 clock driver to use floor ops for sdcc clocks. As
> > disuccsed in [1] it is good idea to use floor ops for sdcc clocks as we
> > dont want the clock rates to do round up.
> >
> > [1]:
>
Hi Dave,
here's a pull request to net-next for v5.4, more info below. Please let
me know if there are any problems.
Kalle
The following changes since commit 67538eb5c00f08d7fe27f1bb703098b17302bdc0:
Merge branch 'mvpp2-per-cpu-buffers' (2019-09-02 12:07:46 -0700)
are available in the git
Heya Linus,
I would like you to pull for couple of simple dmaengine driver fixes we
got in last few days.
The following changes since commit d1abaeb3be7b5fa6d7a1fbbd2e14e3310005c4c1:
Linux 5.3-rc5 (2019-08-18 14:31:08 -0700)
are available in the Git repository at:
From: Rain River
Many FORCEDETH NICs are used in our hosts. Several bugs are fixed and
some features are developed for FORCEDETH NICs. And I have been
reviewing patches for FORCEDETH NIC for several months. Mark me as the
FORCEDETH NIC maintainer. I will send out the patches and maintain
On Wed, Aug 28, 2019 at 9:55 AM Bartosz Golaszewski
wrote:
> śr., 28 sie 2019 o 09:44 Sekhar Nori napisał(a):
>
> Actually I tested this without the clocksource conversion and it works
> - the previous driver still selects relevant config options. But I
> think you're right - it's worth picking
From: Kalle Valo
Date: Sat, 07 Sep 2019 11:01:15 +0300
> here's a pull request to net-next for v5.4, more info below. Please let
> me know if there are any problems.
Pulled, thanks Kalle.
From: "George G. Davis"
A side of affect of commit "selftests: watchdog: Add optional file
argument" is that arbitrary files may be opened for watchdog testing, e.g.
/dev/null. To prevent watchdog-test from operating on non-watchdog device
files, commit "selftests: watchdog: Validate optional
From: "George G. Davis"
As reported by Eugeniu Rosca, the newly added optional file
argument does not validate if the file is indeed a watchdog, e.g.:
./watchdog-test -f /dev/zero
Watchdog Ticking Away!
Fix it by confirming that the WDIOC_GETSUPPORT ioctl succeeds.
Reported-by: Eugeniu Rosca
On Sat, Sep 7, 2019 at 4:33 AM shuah wrote:
>
> On 9/6/19 7:16 PM, Brendan Higgins wrote:
> > On Fri, Sep 6, 2019 at 9:12 AM SeongJae Park wrote:
> >>
> >> Running kunit with '--build_dir' option gives following error message:
> >>
> >> ```
> >> $ ./tools/testing/kunit/kunit.py run --build_dir
There were a lot of styling problems using space then tab or spaces
instead of tabs in that file. Especially the entire function at line
2677.
Also added a space before the : on line 2221.
Signed-off-by: Sandro Volery
---
drivers/tty/tty_io.c | 60 ++--
1
1 - 100 of 241 matches
Mail list logo
