The original CPU voltage value for load L1 is too low for Armada 37xx SoC
when base CPU frequency is 1000 or 1200 MHz. It leads to instabilities
where CPU gets stuck soon after dynamic voltage scaling from load L1 to L0.
Update the CPU voltage value for load L1 accordingly when base frequency is
1
From: Marek Behún
Remove the .set_parent method in clk_pm_cpu_ops.
This method was supposed to be needed by the armada-37xx-cpufreq driver,
but was never actually called due to wrong assumptions in the cpufreq
driver. After this was fixed in the cpufreq driver, this method is not
needed anymore.
It was observed that the workaround introduced by commit 61c40f35f5cd
("clk: mvebu: armada-37xx-periph: Fix switching CPU rate from 300Mhz to
1.2GHz") when base CPU frequency is 1.2 GHz is also required when base
CPU frequency is 1 GHz. Otherwise switching CPU frequency directly from
L2 (250 MHz) t
Variable cur_frequency in armada37xx_cpufreq_driver_init() is unused.
Signed-off-by: Pali Rohár
Tested-by: Tomasz Maciej Nowak
Tested-by: Anders Trier Olesen
Tested-by: Philip Soares
---
drivers/cpufreq/armada-37xx-cpufreq.c | 10 +-
1 file changed, 1 insertion(+), 9 deletions(-)
dif
When CPU frequency is at 250 MHz and set_rate() is called with 500 MHz (L1)
quickly followed by a call with 1 GHz (L0), the CPU does not necessarily
stay in L1 for at least 20ms as is required by Marvell errata.
This situation happens frequently with the ondemand cpufreq governor and
can be also r
When current CPU load is not L0 then loading armada-37xx-cpufreq.ko driver
fails with following error:
# modprobe armada-37xx-cpufreq
[ 502.702097] Unsupported CPU frequency 250 MHz
This issue was partially fixed by commit 8db82563451f ("cpufreq:
armada-37xx: fix frequency calculation fo
Commit 8db82563451f ("cpufreq: armada-37xx: fix frequency calculation for
opp") changed calculation of frequency passed to the dev_pm_opp_add()
function call. But the code for dev_pm_opp_remove() function call was not
updated, so the driver cleanup phase does not work when registration fails.
This
This driver is missing module_exit hook. Add proper driver exit function
which unregisters the platform device and cleans up the data.
Signed-off-by: Pali Rohár
Tested-by: Tomasz Maciej Nowak
Tested-by: Anders Trier Olesen
Tested-by: Philip Soares
---
drivers/cpufreq/armada-37xx-cpufreq.c | 2
BCM6368 devices need to reset the in order to generate true random numbers.
This is what BCM6368 produces without a reset:
root@OpenWrt:/# cat /dev/hwrng | rngtest -c 1000
rngtest 6.10
Copyright (c) 2004 by Henrique de Moraes Holschuh
This is free software; see the source for copying conditions. T
Hi Kishon,
I love your patch! Yet something to improve:
[auto build test ERROR on robh/for-next]
[also build test ERROR on linus/master v5.11 next-20210222]
[cannot apply to phy/next]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to
Hi Sharath,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on net-next/master]
url:
https://github.com/0day-ci/linux/commits/Sharath-Chandra-Vurukala/net-qualcomm-rmnet-Enable-Mapv5/20210223-010109
base: https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-n
On 2/22/21 11:09 AM, Michal Hocko wrote:
>>
>> I actually have tried adjusting the threshold but found that it doesn't work
>> well for
>> the case with unenven memory access frequency between cgroups. The soft
>> limit for the low memory event cgroup could creep up quite a lot, exceeding
>>
This allows devices without a high precission timer to speed up boot from
more than 100s to lest than 30s.
BCM2835 rngtest:
root@OpenWrt:/# cat /dev/hwrng | rngtest -c 1000
rngtest 6.10
Copyright (c) 2004 by Henrique de Moraes Holschuh
This is free software; see the source for copying conditions.
Hi!
> From: Stefano Garzarella
>
> commit cf1a3b35382c10ce315c32bd2b3d7789897fbe13 upstream.
>
> As preparation for the next patches, we store the MAC address,
> parsed during the vdpasim_create(), in a buffer that will be used
> to fill 'config' together with other configurations.
I'm not sur
config: powerpc64-randconfig-r014-20210222 (attached as .config)
compiler: clang version 12.0.0 (https://github.com/llvm/llvm-project
c9439ca36342fb6013187d0a69aef92736951476)
reproduce (this is a W=1 build):
wget
https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O
Hi John,
Le lundi 22 février 2021 à 17:39 +0100, Benjamin Gaignard a écrit :
>
> Le 22/02/2021 à 17:24, John Cox a écrit :
> > > The H.265 ITU specification (section 7.4) define the general
> > > slice segment header semantics.
> > > Modified/added fields are:
> > > - video_parameter_set_id: (7.4
bcm7038_wdt can be used on bmips (bcm63xx) devices too.
Signed-off-by: Álvaro Fernández Rojas
---
drivers/watchdog/bcm7038_wdt.c | 30 --
1 file changed, 24 insertions(+), 6 deletions(-)
diff --git a/drivers/watchdog/bcm7038_wdt.c b/drivers/watchdog/bcm7038_wdt.c
ind
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any
issue:
Reported-and-tested-by: syzbot+429d3f82d757c211b...@syzkaller.appspotmail.com
Tested on:
commit: 2b31ee47 nbd: handle device refs for DESTROY_ON_DISCONNECT..
git tree:
git://git.kernel.org/
>From QPIC version 2.0 onwards new register got added to read last
codeword. This change will add the READ_LOCATION_LAST_CW_n register.
For first three code word READ_LOCATION_n register will be
use.For last code word READ_LOCATION_LAST_CW_n register will be
use.
Signed-off-by: Md Sadre Alam
---
On Mon, 2021-02-22 at 17:28 +0100, Benjamin Gaignard wrote:
>
> Le 22/02/2021 à 17:16, John Cox a écrit :
> > > The HEVC HANTRO driver needs to know the number of bits to skip at
> > > the beginning of the slice header.
> > > That is a hardware specific requirement so create a dedicated control
>
Some BCM6358 devices start with Core #1 instead of Core #0.
Apart from that, SMP is restricted to 1 CPU since BCM6358 has a shared TLB,
which makes it impossible for the current SMP support to start both CPUs.
The problem is that smp_processor_id() returns 0 and then cpu_logical_map()
converts tha
Quoting Douglas Anderson (2021-02-18 14:55:09)
> At boot time the following happens:
> 1. Device core gets ready to probe our SPI driver.
> 2. Device core applies SPI controller's "default" pinctrl.
> 3. Device core calls the SPI driver's probe() function which will
>eventually setup the chip s
Le lundi 22 février 2021 à 17:28 +0100, Benjamin Gaignard a écrit :
>
> Le 22/02/2021 à 17:16, John Cox a écrit :
> > > The HEVC HANTRO driver needs to know the number of bits to skip at
> > > the beginning of the slice header.
> > > That is a hardware specific requirement so create a dedicated co
Hamming ECC doesn't cover the OOB data, so reading or writing OOB shall
always be done without ECC enabled.
This is a problem when adding JFFS2 cleanmarkers to erased blocks. If JFFS2
clenmarkers are added to the OOB with ECC enabled, OOB bytes will be changed
from ff ff ff to 00 00 00, reporting i
Quoting Matthias Kaehlcke (2021-02-19 18:10:59)
> Lazor rev3 and older are stuffed with a 47k NTC as thermistor for
> the charger temperature which currently isn't supported by the
> PM6150 ADC driver. Delete the charger thermal zone and ADC channel
> to avoid the use of bogus temperature values.
>
Hi,
On Fri, Jan 29, 2021 at 11:08 AM Sai Prakash Ranjan
wrote:
>
> @@ -1202,6 +1207,13 @@ void etm4_config_trace_mode(struct etmv4_config
> *config)
> /* excluding kernel AND user space doesn't make sense */
> WARN_ON_ONCE(mode == (ETM_MODE_EXCL_KERN | ETM_MODE_EXCL_USER));
>
> +
On Wed, Feb 03, 2021 at 09:26:43PM -0800, Atish Patra wrote:
> SBI v0.2 functions can return an error code from SBI implementation.
> We are already processing the SBI error code and coverts it to the Linux
> error code.
>
> Propagate to the error code to the caller as well. As of now, kvm is the
On Mon, Feb 22, 2021 at 10:52:09AM -0800, Linus Torvalds wrote:
> On Mon, Feb 22, 2021 at 9:35 AM Rob Herring wrote:
> >
> > Please pull DT updates for v5.12.
>
> Ugh.
>
> This causes "git status" to be unhappy, because there's a new
> generated file (scripts/dtc/fdtoverlay) without a gitignore
On 2/22/21 12:58 PM, Saulo Alessandre wrote:
From: Saulo Alessandre
* crypto/asymmetric_keys/x509_cert_parser.c
- prepare x509 parser to load nist_secp384r1
* crypto/ecc_curve_defs.h
- add nist_p384 params
* include/crypto/ecdh.h
- add ECC_CURVE_NIST_P384
* include/linux/oid_registr
On 2/22/2021 10:31 AM, Mickaël Salaün wrote:
> On 22/02/2021 17:51, Casey Schaufler wrote:
>> On 2/22/2021 7:06 AM, Mickaël Salaün wrote:
>>> From: Mickaël Salaün
>>>
>>> Add a new option CONFIG_LSM_AUTO to enable users to delegate default LSM
>>> stacking order to kernel developers. This enable
device_initcall() is too late for bcm63xx.
We need to call of_clk_init() earlier in order to properly boot.
Signed-off-by: Álvaro Fernández Rojas
---
arch/mips/bmips/setup.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/mips/bmips/setup.c b/arch/mips/bmips/setup.c
inde
On Mon, Feb 22, 2021 at 12:20:04PM -0800, Stephen Boyd wrote:
> Quoting Matthias Kaehlcke (2021-02-19 18:10:59)
> > Lazor rev3 and older are stuffed with a 47k NTC as thermistor for
> > the charger temperature which currently isn't supported by the
> > PM6150 ADC driver. Delete the charger thermal
Hi Mirela,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on linuxtv-media/master]
[also build test WARNING on robh/for-next linus/master v5.11 next-20210222]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we
Quoting Matthias Kaehlcke (2021-02-22 12:38:46)
> On Mon, Feb 22, 2021 at 12:20:04PM -0800, Stephen Boyd wrote:
> > Quoting Matthias Kaehlcke (2021-02-19 18:10:59)
> > > Lazor rev3 and older are stuffed with a 47k NTC as thermistor for
> > > the charger temperature which currently isn't supported b
On 2/15/21 9:10 AM, Johannes Berg wrote:
On Mon, 2021-02-15 at 17:04 +0100, Peter Zijlstra wrote:
On Mon, Feb 15, 2021 at 02:12:30PM +0100, Johannes Berg wrote:
On Mon, 2021-02-15 at 11:44 +0100, Peter Zijlstra wrote:
I think something like so will work, but please double check.
Yeah, that l
On Sun, Feb 21, 2021 at 6:45 PM Nathan Chancellor wrote:
>
> On Sun, Feb 21, 2021 at 03:07:17PM -0800, Linus Torvalds wrote:
> > On Thu, Feb 18, 2021 at 10:06 PM Dave Airlie wrote:
> > >
> > > Let me know if there are any issues,
> >
> > gcc was happy, and I obviously already pushed out my merge,
Le samedi 20 février 2021 à 15:23 -0800, Dmitry Torokhov a écrit :
> Hi Vincent,
Hi Dmitry, thank you for the review !
> On Wed, Feb 10, 2021 at 06:33:52PM +0100, Vincent Knecht wrote:
> > +
> > + for (i = 0; i < MAX_SUPPORTED_FINGER_NUM; i++) {
> > + p = &touch_event.pkt[i];
On Mon, Feb 22, 2021 at 9:28 PM Kevin Tang wrote:
>
> Adds drm support for the Unisoc's display subsystem.
>
> This is drm kms driver, this driver provides support for the
> application framework in Android, Yocto and more.
>
> Application framework can access Unisoc's display internel
> periphera
Randy Dunlap writes:
> Address Jon's feedback on the previous patch by adding info about
> field separators in the /proc/loadavg file.
>
> Signed-off-by: Randy Dunlap
> Cc: Jonathan Corbet
> Cc: linux-...@vger.kernel.org
> ---
> Documentation/filesystems/proc.rst |4
> 1 file changed,
Driver implementation for AMS/TAOS tsl2591 ambient light sensor.
This driver supports configuration via device tree and sysfs.
Supported channels for raw infrared light intensity,
raw combined light intensity and illuminance in lux.
The driver additionally supports iio events on lower and
upper th
Device tree binding for AMS/TAOS tsl2591 ambient light sensor.
This driver supports configuration via device tree and sysfs.
Supported channels for raw infrared light intensity,
raw combined light intensity and illuminance in lux.
The driver additionally supports iio events on lower and
upper thre
Masahiro Yamada writes:
> You should use KCFLAGS to pass additional compiler flags from the
> command line. Using EXTRA_CFLAGS is wrong.
>
> EXTRA_CFLAGS is supposed to specify flags applied only to the current
> Makefile (and now deprecated in favor of ccflags-y).
>
> It is still used in arch/mi
On 2/22/2021 12:13 PM, Álvaro Fernández Rojas wrote:
> Some BCM6358 devices start with Core #1 instead of Core #0.
> Apart from that, SMP is restricted to 1 CPU since BCM6358 has a shared TLB,
> which makes it impossible for the current SMP support to start both CPUs.
>
> The problem is that sm
Hi all,
In commit
179d16007236 ("block: remove superfluous param in blk_fill_rwbs()")
Fixes tag
Fixes: 1b9a9ab78b0 ("blktrace: use op accessors")
has these problem(s):
- SHA1 should be at least 12 digits long
Can be fixed by setting core.abbrev to 12 (or more) or (for git v2.11
Hi All,
Le lundi 02 novembre 2020 à 21:05 +0200, Adrian Ratiu a écrit :
> From: Boris Brezillon
>
> Add the VP9 stateless decoder controls plus the documentation that goes
> with it.
>
> Signed-off-by: Boris Brezillon
> Signed-off-by: Ezequiel Garcia
> Signed-off-by: Adrian Ratiu
> ---
> ..
Hi all,
In commit
99bbb6e0b436 ("xen/events: don't unmask an event channel when an eoi is
pending")
Fixes tag
Fixes: 54c9de89895e0a36047 ("xen/events: add a new late EOI evtchn framework")
has these problem(s):
- Subject does not match target commit subject
Just use
git log
The function blk_put_request() is just a wrapper to
blk_mq_free_request(), remove the unnecessary wrapper.
Any feedback is welcome on this RFC.
Signed-off-by: Chaitanya Kulkarni
---
block/blk-core.c | 6 --
block/blk-merge.c | 2 +-
block/bsg-lib.c
Would it be possible to teach checkpatch not to warn about
canonical references to earlier commits? E.g.
WARNING: Possible unwrapped commit description (prefer a maximum 75 chars per
line)
#7:
commit e80634a75aba ("EDAC, skx: Retrieve and print retry_rd_err_log registers")
Thanks
-Tony
On Mon, Feb 22, 2021 at 9:32 PM Casey Schaufler wrote:
>
> On 2/22/2021 10:31 AM, Mickaël Salaün wrote:
> > On 22/02/2021 17:51, Casey Schaufler wrote:
> >> On 2/22/2021 7:06 AM, Mickaël Salaün wrote:
> >>> From: Mickaël Salaün
> >>>
> >>> Add a new option CONFIG_LSM_AUTO to enable users to deleg
On 2/22/21 10:06 AM, Julian Braha wrote:
> When RTLLIB_CRYPTO_TKIP is enabled and CRYPTO is disabled,
> Kbuild gives the following warning:
>
> WARNING: unmet direct dependencies detected for CRYPTO_MICHAEL_MIC
> Depends on [n]: CRYPTO [=n]
> Selected by [m]:
> - RTLLIB_CRYPTO_TKIP [=m] && S
Hi Grygorii,
On Mon, 22 Feb 2021 12:35:10 +0200 Grygorii Strashko
wrote:
>
> Sorry for inconvenience, is there anything I can do to help resolve it?
> (Changes went through a different trees)
No, it is fine.
--
Cheers,
Stephen Rothwell
pgpKLoMTrD3Vl.pgp
Description: OpenPGP digital signatur
On 2/22/21 13:01, Stephen Rothwell wrote:
> Hi all,
>
> In commit
>
> 179d16007236 ("block: remove superfluous param in blk_fill_rwbs()")
>
> Fixes tag
>
> Fixes: 1b9a9ab78b0 ("blktrace: use op accessors")
>
> has these problem(s):
>
> - SHA1 should be at least 12 digits long
> Can be fix
> -Original Message-
> From: Kieran Bingham [mailto:kieran.bing...@ideasonboard.com]
> Sent: Tuesday, February 23, 2021 12:06 AM
> To: Song Bao Hua (Barry Song) ; cor...@lwn.net;
> linux-...@vger.kernel.org; jan.kis...@siemens.com
> Cc: linux-kernel@vger.kernel.org; linux...@openeuler.org
On 22/02/2021 18:12:42+0100, Sebastian Reichel wrote:
> Congatec's QMX6 system on module (SoM) uses a m41t62 as RTC. The
> modules SQW clock output defaults to 32768 Hz. This behaviour is
> used to provide the i.MX6 CKIL clock. Once the RTC driver is probed,
> the clock is disabled and all i.MX6 fu
Driver implementation for AMS/TAOS tsl2591 ambient light sensor.
This driver supports configuration via device tree and sysfs.
Supported channels for raw infrared light intensity,
raw combined light intensity and illuminance in lux.
The driver additionally supports iio events on lower and
upper th
Device tree binding for AMS/TAOS tsl2591 ambient light sensor.
This driver supports configuration via device tree and sysfs.
Supported channels for raw infrared light intensity,
raw combined light intensity and illuminance in lux.
The driver additionally supports iio events on lower and
upper thre
On 2/22/21 12:03 PM, Álvaro Fernández Rojas wrote:
> bcm7038_wdt can be used on bmips (bcm63xx) devices too.
>
It might make sense to actually enable it for BCM63XX.
> Signed-off-by: Álvaro Fernández Rojas
> ---
> drivers/watchdog/bcm7038_wdt.c | 30 --
> 1 file chan
This patch series adds support for the Kontron pITX-imx8m board:
https://www.kontron.com/products/boards-and-standard-form-factors/single-board-computer/pitx-imx8m.html
Heiko Thiery (2):
dt-bindings: arm: fsl: add Kontron pITX-imx8m board
arm64: dts: fsl: add support for Kontron pitx-imx8m bo
Add the Kontron pITX-imx8m board.
Signed-off-by: Heiko Thiery
Reviewed-by: Krzysztof Kozlowski
---
v2:
- bring in correct alphabetical order
v3:
- no change
Documentation/devicetree/bindings/arm/fsl.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/a
The Kontron pitx-imx8m board is based on an i.MX8MQ soc.
Signed-off-by: Heiko Thiery
Reviewed-by: Krzysztof Kozlowski
---
v2:
- bring root nodes in alphabetical order
- remove pinctrl_gpio_keys for pciewake
- remove pinctrl_sai2 and pinctrl_spdfif1 since it is not used yet
Thanks to Michael
On 22/02/2021 22:20:47+0100, Alexandre Belloni wrote:
> On 22/02/2021 18:12:42+0100, Sebastian Reichel wrote:
> > Congatec's QMX6 system on module (SoM) uses a m41t62 as RTC. The
> > modules SQW clock output defaults to 32768 Hz. This behaviour is
> > used to provide the i.MX6 CKIL clock. Once the
On Mon, Feb 22, 2021 at 01:35:26PM +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.14.222 release.
> There are 57 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 kno
On Mon, Feb 22, 2021 at 01:35:58PM +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.9.258 release.
> There are 49 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
On Mon, Feb 22, 2021 at 01:13:17PM +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.4.100 release.
> There are 13 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
On Mon, Feb 22, 2021 at 01:12:51PM +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.19.177 release.
> There are 50 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 kno
On Mon, Feb 22, 2021 at 01:35:56PM +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.4.258 release.
> There are 35 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
On Mon, Feb 22, 2021 at 01:12:54PM +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.10.18 release.
> There are 29 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
On Mon, Feb 22, 2021 at 01:12:52PM +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.11.1 release.
> There are 12 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.
On Mon, Feb 22, 2021 at 11:28:18AM +, Flavio Suligoi wrote:
[ ... ]
> > Having said that, I'd prefer to have a module parameter in the watchdog
> > core. We already have a number of similar module parameters in various
> > drivers, all named differently, and I'd rather not have more.
>
> Ok, I
"Dmitry V. Levin" writes:
> On sparc, fork and clone syscalls have an unusual semantics of
> returning the pid of the parent process to the child process.
>
> Apparently, the implementation did not honor pid namespaces at all,
> so the child used to get the pid of its parent in the init namespace
On Thu, 18 Feb 2021, Jens Axboe wrote:
> On 2/18/21 4:16 PM, Andrew Morton wrote:
> > On Thu, 18 Feb 2021 14:36:31 -0700 Jens Axboe wrote:
> >
> >> Currently we cap the batch count at max(32, 2*nr_online_cpus), which these
> >> days is kind of silly as systems have gotten much bigger than in 2009
On Mon, Feb 22, 2021 at 08:07:03PM +0100, Uladzislau Rezki wrote:
> On Mon, Feb 22, 2021 at 10:16:08AM -0800, Paul E. McKenney wrote:
> > On Mon, Feb 22, 2021 at 06:16:05PM +0100, Uladzislau Rezki wrote:
> > > On Mon, Feb 22, 2021 at 07:09:03AM -0800, Paul E. McKenney wrote:
> > > > On Mon, Feb 22,
Aditya Srivastava writes:
> Currently, kernel-doc causes an unexpected error when array element (i.e.,
> "type (*foo[bar])(args)") is present as pointer parameter in
> pointer-to-function parsing.
>
> For e.g., running kernel-doc -none on kernel/gcov/gcc_4_7.c causes this
> error:
> "Use of unini
On Mon, Feb 22, 2021 at 01:12:54PM +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.10.18 release.
> There are 29 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
The pull request you sent on Tue, 9 Feb 2021 11:43:27 +0200:
> https://git.kernel.org/pub/scm/linux/kernel/git/rppt/memblock
> tags/memblock-v5.12-rc1
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/7b7028edf939f6ab3bb7465937b33dd714020fa8
Thank you!
--
Deet-doot-do
The pull request you sent on Sun, 21 Feb 2021 22:31:56 +:
> git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git work.d_name
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/205f92d7f2106fb248d65d2abce943ed6002598f
Thank you!
--
Deet-doot-dot, I am a bot.
ht
On Fri, Feb 19, 2021 at 03:00:05PM +0800, Jin Yao wrote:
> Warning "dso not found" is reported when using "perf report -D".
>
> 66702781413407 0x32c0 [0x30]: PERF_RECORD_SAMPLE(IP, 0x2): 28177/28177:
> 0x55e493e00563 period: 106578 addr: 0
> ... thread: perf:28177
> .. dso:
>
> 667027
The pull request you sent on Sun, 21 Feb 2021 22:41:42 +:
> git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git work.audit
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/250a25e7a1d71da06213aa354ece44fb8faa73f7
Thank you!
--
Deet-doot-dot, I am a bot.
htt
On 2/22/21 4:03 PM, Stephen Rothwell wrote:
> Hi all,
>
> In commit
>
> 99bbb6e0b436 ("xen/events: don't unmask an event channel when an eoi is
> pending")
>
> Fixes tag
>
> Fixes: 54c9de89895e0a36047 ("xen/events: add a new late EOI evtchn
> framework")
>
> has these problem(s):
>
> - Su
On Mon, Feb 22, 2021 at 01:13:17PM +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.4.100 release.
> There are 13 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
The pull request you sent on Mon, 22 Feb 2021 16:32:32 +0900:
> git://git.kernel.org/pub/scm/linux/kernel/git/linkinjeon/exfat.git
> tags/exfat-for-5.12-rc1
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/c63dca9e23a3b6761d174b3c13ec365e41d4c0b0
Thank you!
--
Deet-d
The pull request you sent on Mon, 22 Feb 2021 15:21:07 +0100:
> https://github.com/ceph/ceph-client.git tags/ceph-for-5.12-rc1
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/20bf195e9391195925dac4a50e4c2c8165c1b9c5
Thank you!
--
Deet-doot-dot, I am a bot.
https://ko
Am 2021-02-22 22:26, schrieb Heiko Thiery:
The Kontron pitx-imx8m board is based on an i.MX8MQ soc.
Signed-off-by: Heiko Thiery
Reviewed-by: Krzysztof Kozlowski
Reviewed-by: Michael Walle
Applied. Thanks!
Alex
On Thu, Feb 18, 2021 at 6:12 PM Wang, Kevin(Yang) wrote:
>
> thanks,
>
> Reviewed-by: Kevin Wang
>
> Regards,
> Kevin
>
> > 在 2021年2月19日，06:49，Nathan Chancellor 写道：
> >
> > Clang warns:
> >
> > drivers/gpu/drm/amd/amdgpu/../pm/swsmu/smu_cmn.c:764:2: warning:
> > variabl
Applied. Thanks!
Alex
On Sun, Feb 21, 2021 at 10:15 PM Quan, Evan wrote:
>
> [AMD Official Use Only - Internal Distribution Only]
>
> Reviewed-by: Evan Quan
>
> -Original Message-
> From: amd-gfx On Behalf Of Jiapeng
> Chong
> Sent: Saturday, February 20, 2021 10:55 AM
> To: Deucher,
Aditya Srivastava writes:
> There are files in kernel, which use 'typedef struct' syntax for defining
> struct. For eg, include/linux/zstd.h, drivers/scsi/megaraid/mega_common.h,
> etc.
> However, kernel-doc still does not support it, causing a parsing error.
>
> For eg, running scripts/kernel-do
Applied. Thanks!
Alex
On Sat, Feb 20, 2021 at 2:16 AM Jiapeng Chong
wrote:
>
> Fix the following coccicheck warnings:
>
> ./drivers/gpu/drm/amd/display/dc/core/dc_link_ddc.c:544:34-39: WARNING:
> conversion to bool not needed here.
>
> Reported-by: Abaci Robot
> Signed-off-by: Jiapeng Chong
>
Applied. Thanks!
Alex
On Sat, Feb 20, 2021 at 3:35 AM Jiapeng Chong
wrote:
>
> Fix the following coccicheck warnings:
>
> ./drivers/gpu/drm/amd/amdgpu/sdma_v5_2.c:1621:40-45: WARNING: conversion
> to bool not needed here.
>
> ./drivers/gpu/drm/amd/amdgpu/sdma_v5_2.c:1619:40-45: WARNING: convers
Le lundi 22 février 2021 à 16:00 -0500, Nicolas Dufresne a écrit :
Hi All,
Le lundi 02 novembre 2020 à 21:05 +0200, Adrian Ratiu a écrit :
> From: Boris Brezillon
>
> Add the VP9 stateless decoder controls plus the documentation that goes
> with it.
>
> Signed-off-by: Boris Brezillon
> Signed-
When SND_SOC_DMIC is enabled and GPIOLIB is disabled,
Kbuild gives the following warning:
WARNING: unmet direct dependencies detected for SND_SOC_DMIC
Depends on [n]: SOUND [=y] && !UML && SND [=y] && SND_SOC [=y] && GPIOLIB [=n]
Selected by [y]:
- SND_SOC_AMD_RENOIR_MACH [=y] && SOUND [=y]
Add support for being able to set the learning attribute on port, and
make sure that the standalone ports start up with learning disabled.
We can remove the code in bcm_sf2 that configured the ports learning
attribute because we want the standalone ports to have learning disabled
by default and po
On Mon, Feb 22, 2021 at 01:12:51PM +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.19.177 release.
> There are 50 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 kno
Hi Guenter,
> El 22 feb 2021, a las 22:24, Guenter Roeck escribió:
>
> On 2/22/21 12:03 PM, Álvaro Fernández Rojas wrote:
>> bcm7038_wdt can be used on bmips (bcm63xx) devices too.
>>
> It might make sense to actually enable it for BCM63XX.
bcm63xx SoCs are supported in bcm63xx and bmips.
bcm
Please see my comments inlined below.
Thanks,
Jian
On Mon, Feb 22, 2021 at 3:58 AM Will Deacon wrote:
>
> On Fri, Feb 19, 2021 at 03:08:13PM -0800, Jian Cai wrote:
> > This patch adds CONFIG_HARDEN_SLS_ALL that can be used to turn on
> > -mharden-sls=all, which mitigates the straight-line specul
On 2/22/2021 1:46 PM, Florian Fainelli wrote:
> Add support for being able to set the learning attribute on port, and
> make sure that the standalone ports start up with learning disabled.
>
> We can remove the code in bcm_sf2 that configured the ports learning
> attribute because we want the s
Another bump for review. :-)
On Wed, Feb 10, 2021 at 3:25 PM Bill Wendling wrote:
>
> Bumping for review from Masahiro Yamada and Andrew Morton.
>
> -bw
>
> On Fri, Jan 22, 2021 at 2:12 AM Bill Wendling wrote:
> >
> > From: Sami Tolvanen
> >
> > Enable the use of clang's Profile-Guided Optimiz
On 2/22/21 2:31 PM, Hugh Dickins wrote:
> On Thu, 18 Feb 2021, Jens Axboe wrote:
>> On 2/18/21 4:16 PM, Andrew Morton wrote:
>>> On Thu, 18 Feb 2021 14:36:31 -0700 Jens Axboe wrote:
>>>
Currently we cap the batch count at max(32, 2*nr_online_cpus), which these
days is kind of silly as sy
When DRM_TOSHIBA_TC358762 is enabled and DRM_KMS_HELPER is disabled,
Kbuild gives the following warning:
WARNING: unmet direct dependencies detected for DRM_PANEL_BRIDGE
Depends on [n]: HAS_IOMEM [=y] && DRM_BRIDGE [=y] && DRM_KMS_HELPER [=n]
Selected by [y]:
- DRM_TOSHIBA_TC358762 [=y] && H
On Mon, Feb 22, 2021 at 01:42:56PM -0500, George Kennedy wrote:
>
> On 2/22/2021 11:13 AM, David Hildenbrand wrote:
> > On 22.02.21 16:13, George Kennedy wrote:
> > >
> > > On 2/22/2021 4:52 AM, David Hildenbrand wrote:
> > > >
> > > > Let me look into the code ... I have little experience with
On Wed, Feb 17, 2021 at 10:08 AM Kees Cook wrote:
>
> Ah yes, sorry for overlooking that. I can send a follow-up PR. AIUI,
> it's usually better for Linus's workflow for me to build on sent PRs
> instead of resending. (But given the merge window disruption, we'll see
> what happens!)
Since I'm on
1 - 100 of 1414 matches
Mail list logo
