Xu Wang 于2020年7月13日周一 下午3:27写道：
>
> In case of error, the function clk_register() returns ERR_PTR()
> and never returns NULL. The NULL test in the return value check
> should be replaced with IS_ERR().
>
> Signed-off-by: Xu Wang
Acked-by: Barry Song
> ---
> drivers/clk/sirf/clk-atlas6.c | 2 +
tree/branch:
https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git
dev.2020.07.10a
branch HEAD: 475a5da3202544a8cbb3342f842a763df423b989 rcutorture: Add
CONFIG_PROVE_RCU_LIST to TREE05
elapsed time: 720m
configs tested: 108
configs skipped: 12
The following configs have been
On Wed, Jul 15, 2020 at 10:14:43AM +0200, pet...@infradead.org wrote:
> On Wed, Jul 15, 2020 at 10:12:22AM +0200, Peter Zijlstra wrote:
> > On Wed, Jul 15, 2020 at 07:56:50AM +0200, Ahmed S. Darwish wrote:
> > > On Wed, Jul 15, 2020 at 10:05:07AM +0800, Leo Yan wrote:
> > > > From: Peter Zijlstra
On Wed, Jul 15, 2020 at 4:26 AM Stephen Rothwell wrote:
> After merging the block tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
>
> block/blk-timeout.c: In function 'blk_round_jiffies':
> block/blk-timeout.c:96:14: error: 'CONFIG_HZ_ROUGH_MASK' undeclared (first
> us
On Wed, Jul 15, 2020 at 10:22:13AM +0800, Chen-Yu Tsai wrote:
> Hi Greg,
>
> On Wed, Jul 15, 2020 at 3:11 AM Greg Kroah-Hartman
> wrote:
> >
> > From: Maxime Ripard
> >
> > [ Upstream commit 842ec61f4006a6477a9deaedd69131e9f46e4cb5 ]
> >
> > The main DRM device is actually a virtual device so it
From: Bartosz Golaszewski
Use the managed variant of krealloc() and shrink the code a bit.
Signed-off-by: Bartosz Golaszewski
---
drivers/iio/adc/xilinx-xadc-core.c | 16
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/drivers/iio/adc/xilinx-xadc-core.c
b/driver
On Tue, Jul 14, 2020 at 02:08:02PM +0200, Joerg Roedel wrote:
> The #VC entry code now tries to pretend that the #VC handler does not
> use an IST stack by switching to the task stack if entered from
> user-mode or the SYSCALL entry path. When it is entered from
> kernel-mode it is doing its best t
From: Bartosz Golaszewski
Regular krealloc() obviously can't work with managed memory. This series
implements devm_krealloc() and adds the first users with hope that this
helper will be adopted by other drivers currently using non-managed
krealloc().
Some additional changes to the code modified
From: Bartosz Golaszewski
Implement the managed variant of krealloc(). This function works with
all memory allocated by devm_kmalloc() (or devres functions using it
implicitly like devm_kmemdup(), devm_kstrdup() etc.).
Managed realloc'ed chunks can be manually released with devm_kfree().
Signed
From: Bartosz Golaszewski
Shrink pmbus code by using devm_hwmon_device_register_with_groups()
and devm_krealloc() instead of their non-managed variants.
Signed-off-by: Bartosz Golaszewski
Acked-by: Guenter Roeck
---
drivers/hwmon/pmbus/pmbus_core.c | 28 +---
1 file ch
Hi Kees,
thanks for your reviews!
On Tue, Jul 14, 2020 at 06:40:30PM -0700, Kees Cook wrote:
> Eek, no. MSR_IA32_MISC_ENABLE_XD_DISABLE needs to be cleared very early
> during CPU startup; this can't just be skipped.
That MSR is Intel-only, right? The boot-path installed here is only used
for SE
On 30/06/2020 02:35, Martin K. Petersen wrote:
What happened to the suggestion to treat reboot=p like a poweroff
instead? That seems to be fundamentally the right thing to do.
I agree!
I've done that but so far it has been ignored:
https://lore.kernel.org/lkml/f4a7b539-eeac-1a59-2350-3eefc8c
nouveau_bo_alloc() misses to call kfree() in an error path. Add the
missed function call to fix it.
Signed-off-by: Jing Xiangfeng
---
drivers/gpu/drm/nouveau/nouveau_bo.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/nouveau/nouveau_bo.c
b/drivers/gpu/dr
On Wed, Jul 15, 2020 at 05:21:01AM -0400, B K Karthik wrote:
> On Wed, Jul 15, 2020 at 5:14 AM Greg Kroah-Hartman
> wrote:
> >
> > On Wed, Jul 15, 2020 at 04:41:52AM -0400, B K Karthik wrote:
> > > On Wed, Jul 15, 2020 at 4:31 AM Greg Kroah-Hartman
> > > wrote:
> > > >
> > > > On Wed, Jul 15, 202
ADXRS290 is a high performance MEMS pitch and roll (dual-axis in-plane)
angular rate sensor (gyroscope) designed for use in stabilization
applications. It also features an internal temperature sensor and
programmable high-pass and low-pass filters.
Add support for ADXRS290 in direct-access mode fo
Add devicetree binding document for ADXRS290, a dual-axis MEMS gyroscope.
Signed-off-by: Nishant Malpani
---
.../bindings/iio/gyroscope/adi,adxrs290.yaml | 52 +++
MAINTAINERS | 1 +
2 files changed, 53 insertions(+)
create mode 100644
Docume
On Wed, Jul 15, 2020 at 9:44 AM Brendan Higgins
wrote:
>
> On Sat, Jul 4, 2020 at 1:52 AM Ignat Korchagin wrote:
> >
> > It is possible to produce a statically linked UML binary with
> > UML_NET_VECTOR,
> > UML_NET_VDE and UML_NET_PCAP options enabled using alternative libc
> > implementations,
From: Pierre-Louis Bossart
Not sure how this went undetected for years.
Signed-off-by: Pierre-Louis Bossart
Reviewed-by: Guennadi Liakhovetski
Reviewed-by: Rander Wang
Signed-off-by: Bard Liao
---
include/linux/soundwire/sdw.h | 8
1 file changed, 4 insertions(+), 4 deletions(-)
d
From: Pierre-Louis Bossart
Table 110 "Port Data Modes" of the SoundWire 1.2 specification lists
PRBS as b01 and Static_1 as b11. The existing headers swapped the two
values, fix.
Signed-off-by: Pierre-Louis Bossart
Reviewed-by: Guennadi Liakhovetski
Reviewed-by: Rander Wang
Signed-off-by: Bar
If the header file containing a function's prototype isn't included by
the sourcefile containing the associated function, the build system
complains of missing prototypes.
Fixes the following W=1 kernel build warning(s):
drivers/usb/mtu3/mtu3_trace.c:13:6: warning: no previous prototype for
‘mt
The value obtained from GINTSTS2 should be masked with the GINTMSK2
value. Looks like this has been broken since
dwc2_gadget_wkup_alert_handler() was added back in 2018.
Also fixes the following W=1 warning:
drivers/usb/dwc2/gadget.c: In function ‘dwc2_gadget_wkup_alert_handler’:
drivers/usb/d
Fix PRBS/Static_1 swapped definitions and indentation in sdw.h
Pierre-Louis Bossart (2):
soundwire: sdw.h: fix PRBS/Static_1 swapped definitions
soundwire: sdw.h: fix indentation
include/linux/soundwire/sdw.h | 20 ++--
1 file changed, 10 insertions(+), 10 deletions(-)
--
2
A good attempt was made to document everything else.
Fixes the following W=1 kernel build warning(s):
drivers/usb/class/cdc-wdm.c:961: warning: Function parameter or member
'manage_power' not described in 'usb_cdc_wdm_register'
Cc: Oliver Neukum
Signed-off-by: Lee Jones
---
Changelog
v2: Fi
Kerneldoc headers should only be used to document functions and data
structures.
Cc: Chunfeng Yun
Cc: linux-media...@lists.infradead.org
Signed-off-by: Lee Jones
---
Changelog
v2: Removed unrelated reference to build warning
drivers/usb/mtu3/mtu3_trace.c | 2 +-
1 file changed, 1 insertion(+)
sisusb_init.h is included by multiple source files, but the big data
tables contained are only referenced by one of them, leaving the tables
'defined but not used' by the remainder. We have a choice to either
place them inside the source file, taking up may lines and potentially
overwhelming the s
This is the last of them.
Some have been re-written, others fixed-up.
See the in-patch changelog for the details.
Lee Jones (8):
usb: dwc2: gadget: Make use of GINTMSK2
usb: dwc2: gadget: Avoid pointless read of EP control register
usb: mtu3: mtu3_trace: Function headers are not suitable f
These are not referenced anywhere in the kernel.
Fixes the following W=1 kernel build warning(s):
drivers/usb/misc/sisusbvga/sisusb_init.h:171:29: warning:
‘ModeIndex_1280x1024’ defined but not used [-Wunused-const-variable=]
drivers/usb/misc/sisusbvga/sisusb_init.h:170:29: warning: ‘ModeIndex
No attempt has been made to document any of the functions here.
Fixes the following W=1 kernel build warning(s):
drivers/usb/c67x00/c67x00-hcd.c:237: warning: Function parameter or member
'sie' not described in 'c67x00_hcd_irq'
drivers/usb/c67x00/c67x00-hcd.c:237: warning: Function parameter o
On Tue, Jul 14, 2020 at 12:21 PM Lad Prabhakar
wrote:
> From: Marian-Cristian Rotariu
>
> Add support for RZ/G2H (R8A774E1) SoC IPMMUs.
>
> Signed-off-by: Marian-Cristian Rotariu
>
> Signed-off-by: Lad Prabhakar
Reviewed-by: Geert Uytterhoeven
Gr{oetje,eeting}s,
Gee
Commit ec1f9d9f01384 ("usb: dwc2: gadget: parity fix in isochronous mode") moved
these checks to dwc2_hsotg_change_ep_iso_parity() back in 2015. The assigned
value hasn't been read back since. Let's remove the unnecessary H/W read.
Fixes the following W=1 warning:
drivers/usb/dwc2/gadget.c: In
On Tue, Jul 14, 2020 at 12:21 PM Lad Prabhakar
wrote:
> Add an entry for r8a77961 in soc_rcar_gen3[] list so that we dont
> enable iommu unconditionally.
>
> Fixes: 17fe161816398 ("iommu/renesas: Add support for r8a77961")
> Signed-off-by: Lad Prabhakar
Reviewed-by: Geert Uytterhoeven
Gr{oetje
On Wed, Jul 15, 2020 at 11:24:56AM +0200, Peter Zijlstra wrote:
> Can we get some more words -- preferably in actual code comments, on
> when exactly #VC happens?
Sure, will add this as a comment before the actual runtime VC handler.
> Because the only thing I remember is that #VC could happen on
On Wed, Jul 15, 2020 at 11:25:26AM +0200, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski
>
> Implement the managed variant of krealloc(). This function works with
> all memory allocated by devm_kmalloc() (or devres functions using it
> implicitly like devm_kmemdup(), devm_kstrdup() etc.).
On Wed, Jul 15, 2020 at 5:29 AM Greg Kroah-Hartman
wrote:
>
> On Wed, Jul 15, 2020 at 05:21:01AM -0400, B K Karthik wrote:
> > On Wed, Jul 15, 2020 at 5:14 AM Greg Kroah-Hartman
> > wrote:
> > >
> > > On Wed, Jul 15, 2020 at 04:41:52AM -0400, B K Karthik wrote:
> > > > On Wed, Jul 15, 2020 at 4:3
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This automated bisection report was sent to you on the basis *
* that you may be involved with the breaking commit it has *
* found. No manual investigation has been done to verify it, *
* and the root cause of the problem
Hi Linus,
Here is the dmaengine pull request for v5.8. Please note dmaengine tree
has moved to kernel.org so you would need to pull from that now on.
The following changes since commit b3a9e3b9622ae10064826dccb4f7a52bd88c7407:
Linux 5.8-rc1 (2020-06-14 12:45:04 -0700)
are available in the Git
Hi Stephen,
On Mon, 13 Jul 2020 09:11:02 +1000, Stephen Rothwell wrote:
> Attempting to fetch the dmi tree gets this error:
>
> http://jdelvare.nerim.net/devel/linux/jdelvare-dmi/series:
> 2020-07-13 08:58:05 ERROR 403: Forbidden.
>
> I am still using the previously fetched quilt series.
Sorry
Hi Prabhakar,
CC Arnd
On Wed, Jul 8, 2020 at 8:54 PM Lad Prabhakar
wrote:
> Enable R-Car PCIe endpoint driver on RZ/G2E board, including enabling
> endpoint configurations CONFIG_PCI_ENDPOINT, CONFIG_PCI_ENDPOINT_CONFIGFS,
> CONFIG_PCI_EPF_TEST and CONFIG_PCI_ENDPOINT_TEST required to use and te
On Wed, Jul 15, 2020 at 10:42:07AM +0200, Peter Enderborg wrote:
> Since debugfs include sensitive information it need to be treated
> carefully. But it also has many very useful debug functions for userspace.
> With this option we can have same configuration for system with
> need of debugfs and a
Hi Rob,
On 01/07/2020 13:30, Grygorii Strashko wrote:
Convert the K3 NavigatorSS Ring Accelerator bindings documentation to
json-schema.
Cc: Rob Herring
Signed-off-by: Grygorii Strashko
---
.../devicetree/bindings/soc/ti/k3-ringacc.txt | 59 --
.../bindings/soc/ti/k3-ringacc.yaml
On Wed, 15 Jul 2020 at 00:16, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.19.133 release.
> There are 58 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Re
From: Jacopo Mondi
The IMI RDACM20 and IMI RDACM21 are Gigabit Multimedia Serial Link
(GMSL) camera capable of transmitting video and I2C control messages on
a coax cable physical link for automotive applications.
Document their device tree bindings.
Signed-off-by: Jacopo Mondi
Signed-off-by:
On 15-07-20, 09:26, Lee Jones wrote:
> Fixes the following W=1 kernel build warning(s):
>
> drivers/cpufreq/powernv-cpufreq.c:669:6: warning: no previous prototype for
> ‘gpstate_timer_handler’ [-Wmissing-prototypes]
> drivers/cpufreq/powernv-cpufreq.c:902:6: warning: no previous prototype for
Cc: Timur Tabi
Cc: Nicolin Chen
Cc: Xiubo Li
Cc: Fabio Estevam
Cc: linuxppc-...@lists.ozlabs.org
Signed-off-by: Lee Jones
---
sound/soc/fsl/fsl-asoc-card.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/sound/soc/fsl/fsl-asoc-card.c b/sound/soc/fsl/fsl-asoc-card.c
index f
On 15-07-20, 09:26, Lee Jones wrote:
> Kerneldoc format for attribute descriptions should be '@.*: '.
>
> Fixes the following W=1 kernel build warning(s):
>
> drivers/cpufreq/sti-cpufreq.c:49: warning: cannot understand function
> prototype: 'struct sti_cpufreq_ddata '
>
> Cc: Patrice Chotard
On 15-07-20, 09:26, Lee Jones wrote:
> This set is part of a larger effort attempting to clean-up W=1
> kernel builds, which are currently overwhelmingly riddled with
> niggly little warnings.
>
> After these patches are applied, the build system no longer
> complains about any W=0 nor W=1 level w
On Tue, Jul 14, 2020 at 10:31:56AM -0700, Alexander Duyck wrote:
> On Tue, Jul 14, 2020 at 1:45 AM Michael S. Tsirkin wrote:
> >
> > On Mon, Jul 13, 2020 at 08:10:14AM -0700, Alexander Duyck wrote:
> > > On Sun, Jul 12, 2020 at 8:10 AM Michael S. Tsirkin
> > > wrote:
> > > >
> > > > On Fri, Jul
On Tue, Jul 14, 2020 at 02:08:47PM +0200, Joerg Roedel wrote:
> @@ -489,6 +490,9 @@ DEFINE_IDTENTRY_RAW(exc_nmi)
> this_cpu_write(nmi_cr2, read_cr2());
> nmi_restart:
>
> + /* Needs to happen before DR7 is accessed */
> + sev_es_ist_enter(regs);
> +
> this_cpu_write(nmi_dr7,
On Wed, Jul 15, 2020 at 01:26:47PM +0800, Qing Zhang wrote:
> Convert clk_enable() to clk_prepare_enable() and clk_disable() to
> clk_disable_unprepare() respectively in the spi-coldfire-qspi.c.
Like I said on the previous version are you sure that ColdFire uses the
common clock framework and has
On Wed, Jul 15, 2020 at 10:31:09AM +0200, Pierre Morel wrote:
> If protected virtualization is active on s390, the virtio queues are
> not accessible to the host, unless VIRTIO_F_IOMMU_PLATFORM has been
> negotiated. Use the new arch_validate_virtio_features() interface to
> fail probe if that's no
On Wed, Jul 15, 2020 at 10:51:02AM +0900, Tetsuo Handa wrote:
> syzbot is reporting general protection fault in bitfill_aligned() [1]
> caused by integer underflow in bit_clear_margins(). The cause of this
> problem is when and how do_vc_resize() updates vc->vc_{cols,rows}.
>
> If vc_do_resize() f
Hello,
On 15/07/20 2:57 pm, Nishant Malpani wrote:
ADXRS290 is a high performance MEMS pitch and roll (dual-axis in-plane)
angular rate sensor (gyroscope) designed for use in stabilization
applications. It also features an internal temperature sensor and
programmable high-pass and low-pass filte
On 7/15/20 7:05 AM, js1...@gmail.com wrote:
> From: Joonsoo Kim
>
> new_non_cma_page() in gup.c requires to allocate the new page that is not
> on the CMA area. new_non_cma_page() implements it by using allocation
> scope APIs.
>
> However, there is a work-around for hugetlb. Normal hugetlb page
On Wed, Jul 15, 2020 at 11:13:37AM +0200, Joerg Roedel wrote:
> On Wed, Jul 15, 2020 at 10:47:52AM +0200, Peter Zijlstra wrote:
> > On Tue, Jul 14, 2020 at 02:09:05PM +0200, Joerg Roedel wrote:
> >
> > > @@ -1028,6 +1036,16 @@
> > > DEFINE_IDTENTRY_VC_SAFE_STACK(exc_vmm_communication)
> > > str
On Wed, Jul 15, 2020 at 11:23:45AM +0200, Ahmed S. Darwish wrote:
>
> Can we then please replace the raw_read_seqcount(), in the original
> patch which started this discussion, with raw_read_seqcount_latch()?
Separate patch please, but ACK for making the change.
On 15-07-20, 05:37, Bard Liao wrote:
> Fix PRBS/Static_1 swapped definitions and indentation in sdw.h
Applied both, thanks
--
~Vinod
Linux kernel only supports logical block sizes which are power of two,
at least 512 bytes and no more that PAGE_SIZE.
Check this instead of crashing later on.
Note that there is no need to check physical block size since it is
only a hint, and virtio-blk already only supports power of two values.
On Wed, Jul 15, 2020 at 11:34:26AM +0200, Joerg Roedel wrote:
> On Wed, Jul 15, 2020 at 11:24:56AM +0200, Peter Zijlstra wrote:
> > Can we get some more words -- preferably in actual code comments, on
> > when exactly #VC happens?
>
> Sure, will add this as a comment before the actual runtime VC h
Hi Linus,
Small fixes for this, v5.8 cycle in PDx86. No conflicts found.
Thanks,
With Best Regards,
Andy Shevchenko
The following changes since commit b3a9e3b9622ae10064826dccb4f7a52bd88c7407:
Linux 5.8-rc1 (2020-06-14 12:45:04 -0700)
are available in the Git repository at:
git://git.inf
On Tue, Jul 14, 2020 at 3:02 PM Vadim Pasternak wrote:
>
> The patchset adds new features for the existing Mellanox systems.
>
> Patch #1 add string helpers for upper/lower conversion.
> Patch #2 add tests for these helpers.
> Patch #3 updates license for module 'mlxreg-hotplug'.
> Patch #4 allows
On Tue, Jul 14, 2020 at 10:07 PM Alexander A. Klimov
wrote:
>
> Rationale:
> Reduces attack surface on kernel devs opening the links for MITM
> as HTTPS traffic is much harder to manipulate.
>
> Deterministic algorithm:
> For each file:
> If not .svg:
> For each line:
> If doesn't cont
Hi All,
On 07/07/2020 10:02, Peter Ujfalusi wrote:
On 01/07/2020 13.18, Grygorii Strashko wrote:
On 19/06/2020 19:25, Grygorii Strashko wrote:
Select TI chip id driver for TI's SoCs based on K3 architecture to
provide
this information to user space and Kernel as it is required by other
drivers
syzbot has bisected this issue to:
commit 4977caef05aa154f5e45a232fc4f0e1c74a0c739
Author: Zhang Qiang
Date: Tue Jul 7 02:29:47 2020 +
kthread: work could not be queued when worker being destroyed
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=12c58f5710
start commit
Hi Lorenzo,
On 2020/07/14 22:27, Lorenzo Pieralisi wrote:
On Thu, Jun 18, 2020 at 05:38:09PM +0900, Kunihiko Hayashi wrote:
The misc interrupts consisting of PME, AER, and Link event, is handled
by INTx handler, however, these interrupts should be also handled by
MSI handler.
Define what you
On Tue, Jul 14, 2020 at 10:07 PM Alexander A. Klimov
wrote:
>
> Rationale:
> Reduces attack surface on kernel devs opening the links for MITM
> as HTTPS traffic is much harder to manipulate.
>
> Deterministic algorithm:
> For each file:
> If not .svg:
> For each line:
> If doesn't cont
On 7/15/20 11:39 AM, Greg Kroah-Hartman wrote:
> On Wed, Jul 15, 2020 at 10:42:07AM +0200, Peter Enderborg wrote:
>> Since debugfs include sensitive information it need to be treated
>> carefully. But it also has many very useful debug functions for userspace.
>> With this option we can have same c
On Wed, Jul 15, 2020 at 12:55:18PM +0300, Maxim Levitsky wrote:
> Linux kernel only supports logical block sizes which are power of two,
> at least 512 bytes and no more that PAGE_SIZE.
>
> Check this instead of crashing later on.
>
> Note that there is no need to check physical block size since
Also, rename ERR_MEDIUM to MED_FAILURE.
I think that MEDIA_FAILURE looks better.
I think so too.
If so, should I change VOL_DIRTY to VOLUME_DIRTY?
Yes, maybe.
OK.
I'll rename both in v2.
- p_boot->vol_flags = cpu_to_le16(new_flag);
+ p_boot->vol_flags = cpu_to_le16(new_flag
On Wed, Jul 15, 2020 at 11:51:36AM +0200, Peter Zijlstra wrote:
> On Wed, Jul 15, 2020 at 11:13:37AM +0200, Joerg Roedel wrote:
> > Then my understanding of intrumentation_begin/end() is wrong, I thought
> > that the kernel will forbid setting breakpoints before
> > instrumentation_begin(), which i
On 10/07/2020 01:34, Drew Fustini wrote:
Modify omap_gpio_set_config() to handle pin config bias flags by calling
gpiochip_generic_config().
The pin group for the gpio line must have the corresponding pinconf
properties:
PIN_CONFIG_BIAS_PULL_UP requires "pinctrl-single,bias-pullup"
PIN_CONFI
On Wed, Jul 15, 2020 at 11:55:56AM +0200, Peter Zijlstra wrote:
> And recursive #VC was instant death, right? Because there's no way to
> avoid IST stack corruption in that case.
Right, a #VC exception while still on the IST stack must instantly kill
the VM. That needs an additional check which is
On Wed, Jul 15, 2020 at 12:08:08PM +0200, Joerg Roedel wrote:
> On Wed, Jul 15, 2020 at 11:51:36AM +0200, Peter Zijlstra wrote:
> > On Wed, Jul 15, 2020 at 11:13:37AM +0200, Joerg Roedel wrote:
> > > Then my understanding of intrumentation_begin/end() is wrong, I thought
> > > that the kernel will
On Wed, 15 Jul 2020, Viresh Kumar wrote:
> On 15-07-20, 09:26, Lee Jones wrote:
> > Fixes the following W=1 kernel build warning(s):
> >
> > drivers/cpufreq/powernv-cpufreq.c:669:6: warning: no previous prototype
> > for ‘gpstate_timer_handler’ [-Wmissing-prototypes]
> > drivers/cpufreq/powern
On Tue, 2020-07-14 at 15:11 -0600, Rob Herring wrote:
> On Tue, Jul 14, 2020 at 05:13:00PM +0100, Daniele Alessandrelli
> wrote:
> > From: Daniele Alessandrelli
> >
> > Document Intel Movidius SoC code-named Keem Bay, along with the
> > Keem Bay
> > EVM board.
> >
> > Reviewed-by: Dinh Nguyen
>
On 2020/7/15 下午5:50, Michael S. Tsirkin wrote:
On Wed, Jul 15, 2020 at 10:31:09AM +0200, Pierre Morel wrote:
If protected virtualization is active on s390, the virtio queues are
not accessible to the host, unless VIRTIO_F_IOMMU_PLATFORM has been
negotiated. Use the new arch_validate_virtio_fea
On 13/07/2020 19:26, Tony Lindgren wrote:
Carlos Hernandez reported that we now have a suspend and
resume regresssion on am3 and am4 compared to the earlier kernels. While
suspend and resume works with v5.8-rc3, we now get errors with rtcwake:
pm33xx pm33xx: PM: Could not transition all powe
On Mon, Jul 13, 2020 at 11:35 PM Lad Prabhakar
wrote:
> From: Marian-Cristian Rotariu
>
> Add RZ/G2H (R8A774E1) IPMMU nodes.
>
> Signed-off-by: Marian-Cristian Rotariu
>
> Signed-off-by: Lad Prabhakar
Reviewed-by: Geert Uytterhoeven
i.e. will queue in renesas-devel for v5.9.
Gr{oetje,eeting
Flavio Suligoi wrote:
> The wiki url is still the old "wireless.kernel.org"
> instead of the new "wireless.wiki.kernel.org"
>
> Signed-off-by: Flavio Suligoi
3 patches applied to wireless-drivers-next.git, thanks.
0ef2c2d1a9d0 wireless: fix wiki website url in main Kconfig
eb17a4f9acf1 atmel:
On Wed, 2020-07-15 at 06:06 -0400, Michael S. Tsirkin wrote:
> On Wed, Jul 15, 2020 at 12:55:18PM +0300, Maxim Levitsky wrote:
> > Linux kernel only supports logical block sizes which are power of
> > two,
> > at least 512 bytes and no more that PAGE_SIZE.
> >
> > Check this instead of crashing la
On Mon, Jul 13, 2020 at 11:35 PM Lad Prabhakar
wrote:
> From: Marian-Cristian Rotariu
>
> Add sys-dmac[0-2] device nodes for RZ/G2H (R8A774E1) SoC.
>
> Signed-off-by: Marian-Cristian Rotariu
>
> Signed-off-by: Lad Prabhakar
Reviewed-by: Geert Uytterhoeven
i.e. will queue in renesas-devel for
Flavio Suligoi wrote:
> In some Intesil files, the wiki url is still the old
> "wireless.kernel.org" instead of the new
> "wireless.wiki.kernel.org"
>
> Signed-off-by: Flavio Suligoi
Fails to apply:
fatal: corrupt patch at line 97
error: could not build fake ancestor
Applying: intersil: fix w
On 2020-07-15 08:06, Tomasz Nowicki wrote:
'cfg_probe' hook is called at the very end of configuration probing
procedure and therefore features override and workaround may become
complex like for ID register fixups. In preparation for adding Marvell
errata move 'cfg_probe' a bit earlier to have c
On Mon, Jul 13, 2020 at 11:36 PM Lad Prabhakar
wrote:
> From: Marian-Cristian Rotariu
>
> This patch adds the SoC specific part of the Ethernet AVB
> device tree node.
>
> Signed-off-by: Marian-Cristian Rotariu
>
> Signed-off-by: Lad Prabhakar
Reviewed-by: Geert Uytterhoeven
i.e. will queue
On Mon, Jul 13, 2020 at 11:35 PM Lad Prabhakar
wrote:
> From: Marian-Cristian Rotariu
>
> Add GPIO device nodes to the DT of the r8a774e1 SoC.
>
> Signed-off-by: Marian-Cristian Rotariu
>
> Signed-off-by: Lad Prabhakar
Reviewed-by: Geert Uytterhoeven
i.e. will queue in renesas-devel for v5.9
Kieran Bingham wrote:
> The word 'descriptor' is misspelled throughout the tree.
>
> Fix it up accordingly:
> decriptors -> descriptors
>
> Signed-off-by: Kieran Bingham
I recommend splitting wan and wireless changes to separate patches as I
cannot take changes to wan subsystem.
Patch se
Thank you for the review.
Add device-tree binding documentation to represent Tegra194
CPU Complex with compatible string under 'cpus' node. This
can be used by drivers like cpufreq which don't have their
node or CPU Complex node to bind to. Also, documenting
'nvidia,bpmp' property which points t
On Wed, 2020-07-15 at 00:51 +, Peter Chen wrote:
>
> > The Toradex Colibri iMX6ULL board has a special USB hardware design.
> > With runtime-pm enabled USB reset itself continuously. Furthermore
> > the OTG port
> > is also not enumerating devices if the Chipidea IP is in runtime
> > sleep mo
Chao,
I can't find fscrypt_zeroout_range_inline_crypt() function. Do you
mean we need to implement this one for inline encryption?
2020년 7월 15일 (수) 오후 4:17, Chao Yu 님이 작성:
>
> On 2020/7/15 14:54, Daeho Jeong wrote:
> > You mean we can support ZEROOUT option only for encrypted files of
> > non-mul
On Wed, Jul 15, 2020 at 11:47:02AM +0200, Peter Zijlstra wrote:
> On Tue, Jul 14, 2020 at 02:08:47PM +0200, Joerg Roedel wrote:
> DECLARE_STATIC_KEY_FALSE(sev_es_enabled_key);
>
> static __always_inline void sev_es_foo()
> {
> if (static_branch_unlikely(&sev_es_enabled_key))
>
Hi,
After upgrading from 3.14 to 4.14.173, I ran into exactly the same problem
that the starter topic described. Namely, sometimes kswapd starts to consume
100%
of the CPU, and the system freezes for several minutes.
Below is an example of such an event (orange - system cpu, red - total cpu):
h
On Wed, Jul 15, 2020 at 12:13:10PM +0200, Peter Zijlstra wrote:
> On Wed, Jul 15, 2020 at 12:08:08PM +0200, Joerg Roedel wrote:
> > Right, but the handler calls into various other functions. I actually
> > started to annotate them all with noinstr, but that was a can of worms
> > when calling into
On 2020-07-15 08:06, Tomasz Nowicki wrote:
From: Hanna Hawa
Due to erratum #582743, the Marvell Armada-AP806 can't access 64bit to
ARM SMMUv2 registers.
Provide implementation relevant hooks:
- split the writeq/readq to two accesses of writel/readl.
- mask the MMU_IDR2.PTFSv8 fields to not use
On Wed, Jul 15, 2020 at 5:55 PM Maxim Levitsky wrote:
>
> Linux kernel only supports logical block sizes which are power of two,
> at least 512 bytes and no more that PAGE_SIZE.
>
> Check this instead of crashing later on.
>
> Note that there is no need to check physical block size since it is
> o
On Wed, Jul 15, 2020 at 10:03:19AM +, Enderborg, Peter wrote:
> On 7/15/20 11:39 AM, Greg Kroah-Hartman wrote:
> > On Wed, Jul 15, 2020 at 10:42:07AM +0200, Peter Enderborg wrote:
> >> Since debugfs include sensitive information it need to be treated
> >> carefully. But it also has many very us
On 2020-07-15 08:06, Tomasz Nowicki wrote:
Add specific compatible string for Marvell usage due to errata of
accessing 64bits registers of ARM SMMU, in AP806.
AP806 SoC uses the generic ARM-MMU500, and there's no specific
implementation of Marvell, this compatible is used for errata only.
Revi
Kees Cook wrote:
> Using uninitialized_var() is dangerous as it papers over real bugs[1]
> (or can in the future), and suppresses unrelated compiler warnings (e.g.
> "unused variable"). If the compiler thinks it is uninitialized, either
> simply initialize the variable or make compiler changes. A
Flavio Suligoi wrote:
> Fix typo: "EZUSB_REQUEST_TRIGER" --> "EZUSB_REQUEST_TRIGGER"
>
> Signed-off-by: Flavio Suligoi
Patch applied to wireless-drivers-next.git, thanks.
ad806454c3cb orinoco_usb: fix spelling mistake
--
https://patchwork.kernel.org/patch/11613589/
https://wireless.wiki.ke
Vaibhav Gupta wrote:
> With the support of generic PM callbacks, drivers no longer need to use
> legacy .suspend() and .resume() in which they had to maintain PCI states
> changes and device's power state themselves. The required operations are
> done by PCI core.
>
> PCI drivers are not expecte
Vaibhav Gupta wrote:
> With legacy PM, drivers themselves were responsible for managing the
> device's power states and takes care of register states.
>
> After upgrading to the generic structure, PCI core will take care of
> required tasks and drivers should do only device-specific operations.
Vaibhav Gupta wrote:
> Earlier, drivers had to manage the device's power states, and related
> operations, themselves. With the generic approach, these are done by PCI
> core.
>
> The only driver-specific jobs, .suspend() and .resume() doing were invoking
> PCI helper functions pci_save/restore_
201 - 300 of 1399 matches
Mail list logo
