Ünnepi üdvözlet. A nevem Karim Alassani, jogász és a Late személyes ügyvédje.
Mr. Jovan, ügyfelem, aki autóbalesetben halt meg családjával és egyetlen
lányával. A bank megkereste velem a legközelebbi rokont, hogy az általa
otthagyott alapot (4,211 000 millió dollár) elkobozzák.
De néhai
On 2020/12/29 18:51, Russell King - ARM Linux admin wrote:
> On Tue, Dec 29, 2020 at 02:30:56PM +0800, Leizhen (ThunderTown) wrote:
>>
>>
>> On 2020/12/26 20:13, Russell King - ARM Linux admin wrote:
>>> On Fri, Dec 25, 2020 at 07:44:58PM +0800, Zhen Lei wrote:
The outercache of some
The following commit has been merged into the x86/cleanups branch of tip:
Commit-ID: 3052636aa9aa2492ccac973449be63cae5b93a67
Gitweb:
https://git.kernel.org/tip/3052636aa9aa2492ccac973449be63cae5b93a67
Author:Zheng Yongjun
AuthorDate:Wed, 16 Dec 2020 21:11:59 +08:00
On Wed, Dec 16, 2020 at 09:18:46PM +0800, Zheng Yongjun wrote:
> Replace a comma between expression statements by a semicolon.
>
> Signed-off-by: Zheng Yongjun
> ---
> drivers/edac/ppc4xx_edac.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/edac/ppc4xx_edac.c
From: "freddy.hsin"
Before user space daemon start to access the watchdog device,
there is a time interval that watchdog is disabled in the
original flow. If the system freezing at this interval, it
cannot be rebooted by watchdog hardware automatically.
In order to solve this problem, the
Use kzalloc rather than kcalloc(1,...)
The semantic patch that makes this change is as follows:
(http://coccinelle.lip6.fr/)
//
@@
@@
- kcalloc(1,
+ kzalloc(
...)
//
Signed-off-by: Zheng Yongjun
---
drivers/scsi/qedf/qedf_main.c | 2 +-
1 file changed, 1 insertion(+), 1
Use kzalloc rather than kcalloc(1,...)
The semantic patch that makes this change is as follows:
(http://coccinelle.lip6.fr/)
//
@@
@@
- kcalloc(1,
+ kzalloc(
...)
//
Signed-off-by: Zheng Yongjun
---
drivers/net/ethernet/mellanox/mlxfw/mlxfw_mfa2.c | 2 +-
1 file changed, 1
The HW_REF_CPU_CYCLES event on the fixed counter 2 is pseudo-encoded as
0x0300 in the intel_perfmon_event_map[]. Correct its usage.
Fixes: 62079d8a4312 ("KVM: PMU: add proper support for fixed counter 2")
Signed-off-by: Like Xu
---
arch/x86/kvm/vmx/pmu_intel.c | 2 +-
1 file changed, 1
On 2020/12/30 15:01, YANG LI wrote:
> Goto statement jumping will cause lock to be executed again without
> executing unlock, placing the lock statement in front of goto
> label to fix this problem.
>
> Signed-off-by: YANG LI
> Reported-by: Abaci
> ---
> fs/dcache.c | 2 +-
> 1 file changed, 1
v1 --> v2:
Discard the middle-tier functions and do silent narrowing cast in the outcache
hook functions. For example:
-static void l2c220_inv_range(unsigned long start, unsigned long end)
+static void l2c220_inv_range(phys_addr_t pa_start, phys_addr_t pa_end)
{
+ unsigned long start =
The outercache of some Hisilicon SOCs support physical addresses wider
than 32-bits. The unsigned long datatype is not sufficient for mapping
physical addresses >= 4GB. The commit ad6b9c9d78b9 ("ARM: 6671/1: LPAE:
use phys_addr_t instead of unsigned long in outercache functions") has
already
The following commit has been merged into the x86/platform branch of tip:
Commit-ID: bdb154f074a6d73d520b1fdee6b4143e2e311dfb
Gitweb:
https://git.kernel.org/tip/bdb154f074a6d73d520b1fdee6b4143e2e311dfb
Author:Zheng Yongjun
AuthorDate:Wed, 16 Dec 2020 21:11:07 +08:00
On Wed, Dec 30, 2020 at 02:38:06PM +0800, YANG LI wrote:
> Use WARN_ON instead of if condition followed by BUG in
> gnttab_batch_map() and gnttab_batch_copy().
But those are not equivalent as far as I'm aware. BUG will stop
execution, while WARN_ON will print a splat and continue executing.
If
On Mon, 2020-12-28 at 04:04 -0800, Can Guo wrote:
> Users can initiate resets to specific SCSI device/target/host through
> IOCTL. When this happens, the SCSI cmd passed to eh_device/target/host
> _reset_handler() callbacks is initialized with a request whose tag is -1.
> So, in this case, it is
Trival cleanups:
- relocate set_summary() before its use
- relocate "allocate block address" to correct place
- remove unneeded f2fs_wait_on_page_writeback()
Signed-off-by: Chao Yu
---
fs/f2fs/gc.c | 8 +++-
1 file changed, 3 insertions(+), 5 deletions(-)
diff --git a/fs/f2fs/gc.c
At least for 4430, trying to use the single conversion mode eventually
hangs the thermal sensor. This can be quite easily seen with errors:
thermal thermal_zone0: failed to read out thermal zone (-5)
Also, trying to read the temperature shows a stuck value with:
$ while true; do cat
When we set bit 10 high we use continuous mode and not single
mode. Let's correct this to avoid confusion. No functional
changes here, the code does the right thing with bit 10.
Cc: Adam Ford
Cc: Carl Philipp Klemm
Cc: Eduardo Valentin
Cc: Merlijn Wajer
Cc: Pavel Machek
Cc: Peter Ujfalusi
We can use iopoll for checking the EOCZ (end of conversion) bit.
Cc: Adam Ford
Cc: Carl Philipp Klemm
Cc: Eduardo Valentin
Cc: Merlijn Wajer
Cc: Pavel Machek
Cc: Peter Ujfalusi
Cc: Sebastian Reichel
Signed-off-by: Tony Lindgren
---
drivers/thermal/ti-soc-thermal/ti-bandgap.c | 30
Allow user to set metric on default route learned via Router Advertisement.
Not: RFC 4191 does not say anything for metric for IPv6 default route.
Fix:
For IPv4, default route is learned via DHCPv4 and user is allowed to change
metric using config etc/network/interfaces. But for IPv6, default
On Mon, Dec 28, 2020 at 04:21:17PM -0800, Tim Harvey wrote:
> The Gateworks Venice GW71xx-0x/GW72xx-0x/GW73xx-0x are development
> kits comprised of a GW700x SoM and a Baseboard. Future SoM's such
> as the GW701x will create additional combinations.
>
> The GW700x SoM contains:
> - i.MX 8M Mini
* H. Nikolaus Schaller [201223 12:33]:
> With the arrival of
>
> commit 2fee9583198eb9 ("spi: dt-bindings: clarify CS behavior for spi-cs-high
> and gpio descriptors")
>
> it was clarified what the proper state for cs-gpios should be, even if the
> flag is ignored. The driver code is doing the
Fix:
For IPv4, default route is learned via DHCPv4 and user is allowed to change
metric using config etc/network/interfaces. But for IPv6, default route can
be learned via RA, for which, currently a fixed metric value 1024 is used.
Ideally, user should be able to configure metric on default route
Allow user to set metric on default route learned via Router Advertisement.
Not: RFC 4191 does not say anything for metric for IPv6 default route.
Fix:
For IPv4, default route is learned via DHCPv4 and user is allowed to change
metric using config etc/network/interfaces. But for IPv6, default
On Mon, Dec 28, 2020 at 11:36:02AM +, Timon Baetz wrote:
> Register for extcon notification and set charging current depending on
> the detected cable type. Current values are taken from vendor kernel,
> where most charger types end up setting 650mA [0].
>
> Also enable and disable the
On Mon, Dec 28, 2020 at 11:35:38AM +, Timon Baetz wrote:
> This allows the MAX8997 charger to set the current limit depending on
> the detected extcon charger type.
>
> Signed-off-by: Timon Baetz
> ---
> drivers/extcon/extcon-max8997.c | 4
> 1 file changed, 4 insertions(+)
It's
On Tue, 29 Dec 2020 21:06:54 +0100
Borislav Petkov wrote:
> On Mon, Dec 28, 2020 at 10:15:10AM +0900, Masami Hiramatsu wrote:
> > BTW, insn_decode() can return -EINVAL if !insn_complete(), is that OK?
>
> It does with this change. Or are you asking whether it returning -EINVAL
> in that case is
From: Ricky Wu
Make sure voltage below 0.5V before power on
when do power cycle
Signed-off-by: Ricky Wu
---
drivers/mmc/host/rtsx_pci_sdmmc.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/mmc/host/rtsx_pci_sdmmc.c
b/drivers/mmc/host/rtsx_pci_sdmmc.c
index
From: Ricky Wu
Added flag MMC_CAP2_NO_SDIO to mmc->caps2
Card Reader not support SDIO
Signed-off-by: Ricky Wu
---
drivers/mmc/host/rtsx_pci_sdmmc.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/mmc/host/rtsx_pci_sdmmc.c
b/drivers/mmc/host/rtsx_pci_sdmmc.c
On Tue, Dec 29, 2020 at 11:28:35PM +, Qais Yousef wrote:
> Hi Jiri
>
> On 12/29/20 18:34, Jiri Olsa wrote:
> > On Tue, Dec 29, 2020 at 03:13:52PM +, Qais Yousef wrote:
> > > Hi
> > >
> > > When I enable CONFIG_DEBUG_INFO_BTF I get the following error in the
> > > BTFIDS
> > > stage
> >
On 12/29/20 11:55 PM, Randy Dunlap wrote:
No, this is wrong. 'size' in this case is the size of the read.
And it's zero. Is this fixed by commit
3644e2d2dda78e21edd8f5415b6d7ab03f5f54f3
Toralf, can you test with 5.11-rc1 (or later)?
thanks.
My plan was to apply that commit on top of the
Hi Heiner,
Thanks for your reply.
On Wed, Dec 30, 2020 at 3:39 PM Heiner Kallweit wrote:
> I don't think that's the best option.
I'm well aware of that.
> You may want to add a PHY driver for your chip. Supposedly it
> supports at least PHY suspend/resume. You can use the RTL8366RB
> PHY
On 30.12.2020 10:07, DENG Qingfang wrote:
> Hi Heiner,
> Thanks for your reply.
>
> On Wed, Dec 30, 2020 at 3:39 PM Heiner Kallweit wrote:
>> I don't think that's the best option.
>
> I'm well aware of that.
>
>> You may want to add a PHY driver for your chip. Supposedly it
>> supports at
The function sockfd_lookup uses fget on the value that is stored in
the file field of the returned structure, so fput should ultimately be
applied to this value. This can be done directly, but it seems better
to use the specific macro sockfd_put, which does the same thing.
Perform a source code
On Tue, Dec 29, 2020 at 06:58:19PM +0100, Pavel Machek wrote:
> Hi!
>
> > From: Arnd Bergmann
> >
> > [ Upstream commit dbb60031dd0c2b85f10ce4c12ae604c28d3aaca4 ]
> >
> > gcc -Wextra warns about a function taking an enum argument
> > being called with a bool:
> >
> >
On Tue, Dec 29, 2020 at 08:42:50PM +0100, Bas Nieuwenhuizen wrote:
> Hi Greg,
>
> Someone bisected a non-booting computer with 5.10.4-rc1 to this
> commit. Would it be possible to back out of backporting this commit
> (was backported to 5.4 and 5.10)? I suspect we may need
>
On 12/21/2020 6:08 PM, Roja Rani Yarubandi wrote:
Store DMA mapping data in geni_i2c_dev struct to enhance DMA mapping
data scope. For example during shutdown callback to unmap DMA mapping,
this stored DMA mapping data can be used to call geni_se_tx_dma_unprep
and geni_se_rx_dma_unprep
On 12/21/2020 6:08 PM, Roja Rani Yarubandi wrote:
If the hardware is still accessing memory after SMMU translation
is disabled (as part of smmu shutdown callback), then the
IOVAs (I/O virtual address) which it was using will go on the bus
as the physical addresses which will result in unknown
On Tue, Dec 29, 2020 at 12:01:44PM -0700, Nathan Chancellor wrote:
> On Mon, Dec 28, 2020 at 01:43:30PM +0100, Greg Kroah-Hartman wrote:
> > From: Vadim Pasternak
> >
> > [ Upstream commit 912b341585e302ee44fc5a2733f7bcf505e2c86f ]
> >
> > Remove PSU EEPROM configuration for systems class
On Wed, Dec 30, 2020 at 06:00:52PM +0900, Masami Hiramatsu wrote:
> Maybe I need to replace it with dummy lines but it is possible.
Dummy lines like "IGNORE DURING CHECK" or something like that?
> But in [17/19], your patch seems not using INSN_MODE_KERN there.
I replaced it only locally just
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 139711f033f636cc78b6aaf7363252241b9698ef
commit: cb3659268a12602a2ad1e8e8d34ce155bb43ae6e soc: qcom: rpmh: Allow RPMH
driver to be loaded as a module
date: 9 weeks ago
config:
Hi!
> This is the start of the stable review cycle for the 4.4.249 release.
> There are 132 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.
>
> Responses should be made by Wed, 30 Dec 2020 12:48:23
On 12/30/2020 8:28 AM, YANG LI wrote:
There is a regular need in the kernel to provide a way to declare
having a dynamically sized set of trailing elements in a structure.
Kernel code should always use "flexible array members"[1] for these
cases. The older style of one-element or zero-length
Hi!
> This is the start of the stable review cycle for the 4.19.164 release.
> There are 346 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.
>
> Responses should be made by Wed, 30 Dec 2020 12:48:23
On Tue, Dec 29, 2020 at 11:42 PM Dylan Van Assche
wrote:
>
> All revisions of the PinePhone share most of the hardware.
> This patch makes it easier to detect PinePhone hardware without
> having to check for each possible revision.
Sounds good.
> Signed-off-by: Dylan Van Assche
> ---
>
Hi Qingfang,
On 2020-12-30 04:22, DENG Qingfang wrote:
Hi,
I added MT7530 IRQ support and registered its internal PHYs to IRQ.
It works but my patch used two hacks.
1. Removed phy_drv_supports_irq check, because config_intr and
handle_interrupt are not set for Generic PHY.
2. Allocated
On Wed, Dec 30, 2020 at 12:04:30PM +0800, Jason Wang wrote:
>
> On 2020/12/29 下午3:28, Eli Cohen wrote:
> > > @@ -43,6 +43,8 @@ struct vdpa_vq_state {
> > >* @index: device index
> > >* @features_valid: were features initialized? for legacy guests
> > >* @nvqs: the number of virtqueues
After full/fast commit, entries in staging queue are promoted to main
queue. In ext4_fs_cleanup function, it splice to staging queue to
staging queue.
Signed-off-by: Daejun Park
---
fs/ext4/fast_commit.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/ext4/fast_commit.c
When running this xfrm_policy.sh test script, even with some cases
marked as FAIL, the overall test result will still be PASS:
$ sudo ./xfrm_policy.sh
PASS: policy before exception matches
FAIL: expected ping to .254 to fail (exceptions)
PASS: direct policy matches (exceptions)
PASS: policy
On Wed, Dec 30, 2020 at 04:28:05PM +0800, Zhen Lei wrote:
> The outercache of some Hisilicon SOCs support physical addresses wider
> than 32-bits. The unsigned long datatype is not sufficient for mapping
> physical addresses >= 4GB. The commit ad6b9c9d78b9 ("ARM: 6671/1: LPAE:
> use phys_addr_t
On Wed, Dec 30, 2020 at 12:33:02PM +1000, Nicholas Piggin wrote:
> Excerpts from Russell King - ARM Linux admin's message of December 29, 2020
> 8:44 pm:
> > On Tue, Dec 29, 2020 at 01:09:12PM +1000, Nicholas Piggin wrote:
> >> I think it should certainly be documented in terms of what guarantees
On 2020-12-29 17:04, Russell King - ARM Linux admin wrote:
On Tue, Dec 29, 2020 at 04:00:59PM +, David Brazdil wrote:
The KVM/arm64 PSCI relay assumes that SYSTEM_OFF and SYSTEM_RESET
should
not return, as dictated by the PSCI spec. However, there is firmware
out
there which breaks this
On Wed, Dec 16, 2020 at 02:48:09PM +0800, Jason Wang wrote:
> Follows the vDPA support for multiple address spaces, this patch
> introduce uAPI for the userspace to know the number of virtqueue
> groups supported by the vDPA device.
>
> Signed-off-by: Jason Wang
> ---
> drivers/vhost/vdpa.c
Hi Yongjun,
many thanks for your patch.
On Wed, Dec 30, 2020 at 09:37:06AM +0800, Zheng Yongjun wrote:
> Use kzalloc rather than kcalloc(1,...)
>
> The semantic patch that makes this change is as follows:
> (http://coccinelle.lip6.fr/)
>
> //
> @@
> @@
>
> - kcalloc(1,
> + kzalloc(
>
Hi Markus
Thank you very much, very good suggestion, do I need to re-send a patch to fix
this problem, or modify the previous patch and send it again?
Thanks
Xiaolei
…
> +++ b/drivers/base/regmap/regmap-debugfs.c
> @@ -582,18 +582,25 @@ void regmap_debugfs_init(struct regmap *map)
…
> +
Currently, CMA and crashkernel are reserved in ZONE_DMA32, which
is OK for majority of devices. But the ones that need them in ZONE_DMA
need to configure it explicitly.
Since patchset "arm64: Default to 32-bit wide ZONE_DMA", ZONE_DMA's
size is fine-tuned. So we could directly reserve CMA and
Like crashkernel, CMA might also reserve memory located in ZONE_DMA,
so move dma_contiguous_reserve() to bootmem_init() to make sure that
arm64_dma_phys_limit is populated.
Just place dma_contiguous_reserve() after reserve_crashkernel() as
before.
Signed-off-by: Chen Zhou
Suggested-by: Nicolas
Currently, CMA and crashkernel are reserved in ZONE_DMA32, which
is OK for majority of devices. But the ones that need them in ZONE_DMA
need to configure it explicitly.
Since patchset "arm64: Default to 32-bit wide ZONE_DMA", ZONE_DMA's
size is fine-tuned. So we could directly reserve CMA and
Since patchset "arm64: Default to 32-bit wide ZONE_DMA", ZONE_DMA's
size is fine-tuned. In the absence of addressing limited masters,
ZONE_DMA will span the whole 32-bit address space, otherwise, in
the case of the Raspberry Pi 4, it'll only span the 30-bit address
space. Update the comments.
On deferred probe, we will get the following splat:
cpcap-usb-phy cpcap-usb-phy.0: could not initialize VBUS or ID IIO: -517
WARNING: CPU: 0 PID: 21 at drivers/regulator/core.c:2123 regulator_put+0x68/0x78
...
(regulator_put) from [] (release_nodes+0x1b4/0x1fc)
(release_nodes) from []
On Wed, Dec 30, 2020 at 10:38:40AM +0100, Pavel Machek wrote:
> Hi!
>
> > This is the start of the stable review cycle for the 4.19.164 release.
> > There are 346 patches in this series, all will be posted as a response
> > to this one. If anyone has any issues with these being applied, please
>
A new flag MACB_CAPS_CLK_HW_CHG was added and all callers of
macb_set_tx_clk were gated on the presence of this flag.
- if (!clk)
+ if (!bp->tx_clk || !(bp->caps & MACB_CAPS_CLK_HW_CHG))
However the flag was not added to anything other than the new
sama7g5_gem, turning that function call into
This series adds bindings and device-tree for the Beelink (AZW) GS-King-X,
which like GT-King and GT-King Pro is based on the W400 reference design.
Changes since v1:
- move audio from TDM_B to TDM_A
- drop S/PDIF content
- add Rob's bindings ack
Christian Hewitt (2):
dt-bindings: arm:
The Shenzen AZW (Beelink) GS-King-X is based on the Amlogic W400 reference
board with an S922X-H chip.
- 4GB LPDDR4 RAM
- 64GB eMMC storage
- 10/100/1000 Base-T Ethernet
- AP6356S Wireless (802.11 a/b/g/n/ac, BT 4.1)
- HDMI 2.1 video
- S/PDIF optical output
- 2x ESS9018 audio DACs
- 4x Ricor
The Shenzen AZW (Beelink) GS-King-X is based on the Amlogic W400 reference
board with an S922X-H chip.
Signed-off-by: Christian Hewitt
Acked-by: Rob Herring
---
Documentation/devicetree/bindings/arm/amlogic.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git
Hi,
Good point!
I will send a new version of the patch soon.
Kind regards,
Dylan Van Assche
On Wed, 2020-12-30 at 17:38 +0800, Chen-Yu Tsai wrote:
> On Tue, Dec 29, 2020 at 11:42 PM Dylan Van Assche <
> m...@dylanvanassche.be> wrote:
> > All revisions of the PinePhone share most of the
All revisions of the PinePhone share most of the hardware.
This patch makes it easier to detect PinePhone hardware without
having to check for each possible revision.
Signed-off-by: Dylan Van Assche
---
v2 updates the devicetree documentation as well.
On Wed, Dec 30, 2020 at 04:18:35PM +0800, Zheng Yongjun wrote:
> Use kzalloc rather than kcalloc(1,...)
>
> The semantic patch that makes this change is as follows:
> (http://coccinelle.lip6.fr/)
>
> //
> @@
> @@
>
> - kcalloc(1,
> + kzalloc(
> ...)
> //
>
> Signed-off-by: Zheng
On Tue, Dec 29, 2020 at 07:25:25AM -0800, Guenter Roeck wrote:
> On Tue, Dec 29, 2020 at 11:52:58AM +0100, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 5.10.4 release.
> > There are 716 patches in this series, all will be posted as a response
> > to this one.
On Tue, Dec 29, 2020 at 02:15:32PM -0600, Daniel Díaz wrote:
> Hello!
>
> On 12/29/20 4:52 AM, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 5.10.4 release.
> > There are 716 patches in this series, all will be posted as a response
> > to this one. If anyone
On Wed, Dec 30, 2020 at 10:00:28AM +, Russell King - ARM Linux admin wrote:
> On Wed, Dec 30, 2020 at 12:33:02PM +1000, Nicholas Piggin wrote:
> > Excerpts from Russell King - ARM Linux admin's message of December 29, 2020
> > 8:44 pm:
> > > On Tue, Dec 29, 2020 at 01:09:12PM +1000, Nicholas
On Tue, Dec 29, 2020 at 05:16:41PM +, Marc Zyngier wrote:
> Hi David,
>
> On 2020-12-29 16:00, David Brazdil wrote:
> > The KVM/arm64 PSCI relay assumes that SYSTEM_OFF and SYSTEM_RESET should
> > not return, as dictated by the PSCI spec. However, there is firmware out
> > there which breaks
Hi,
On 12/29/20 5:51 PM, Richard Fitzgerald wrote:
>
>
> On 29/12/2020 15:40, Hans de Goede wrote:
>> Hi,
>>
>> On 12/29/20 4:15 PM, Mark Brown wrote:
>>> On Tue, Dec 29, 2020 at 03:06:35PM +, Charles Keepax wrote:
>>>
There is maybe more argument for porting the Arizona code across
Currently we allow pipe input/output only through '-' string
being passed to '-o' or '-i' options, like:
# mkfifo perf.pipe
# perf record --no-buffering -e 'sched:sched_switch' -o - > perf.pipe &
[1] 354406
# cat perf.pipe | ./perf --no-pager script -i - | head -3
perf 354406
On 2020/12/30 17:54, Russell King - ARM Linux admin wrote:
> On Wed, Dec 30, 2020 at 04:28:05PM +0800, Zhen Lei wrote:
>> The outercache of some Hisilicon SOCs support physical addresses wider
>> than 32-bits. The unsigned long datatype is not sufficient for mapping
>> physical addresses >=
On Wed, Dec 30, 2020 at 7:36 AM Hillf Danton wrote:
>
> On Tue, 29 Dec 2020 22:57:13 +
> >
> > Fixes: 39d42fa96ba1 ("dm crypt: add flags to optionally bypass kcryptd
> > workqueues")
>
> Looks like a seperate fix to this commit is needed if what can be found
> at (Subject: [patch 00/12] UBS:
On 30/12/2020 11:04, Hans de Goede wrote:
Hi,
On 12/29/20 5:51 PM, Richard Fitzgerald wrote:
On 29/12/2020 15:40, Hans de Goede wrote:
Hi,
On 12/29/20 4:15 PM, Mark Brown wrote:
On Tue, Dec 29, 2020 at 03:06:35PM +, Charles Keepax wrote:
There is maybe more argument for porting the
In contexts like suspend, shutdown and error handling, we need to suspend
devfreq to make sure these contexts won't be disturbed by clock scaling.
However, suspending devfreq is not enough since users can still trigger a
clock scaling by manipulating the devfreq sysfs nodes like min/max_freq and
ufshcd_hba_exit() is always called after ufshcd_exit_clk_scaling() and
ufshcd_exit_clk_gating(), so move ufshcd_exit_clk_scaling/gating() to
ufshcd_hba_exit(). Meanwhile, add dedicated funcs to init and remove
sysfs nodes of clock scaling/gating to make the code more readable.
Overall
Commit 73cc291c27024 ("Make sure clk scaling happens only when HBA is
runtime ACTIVE") is no longer needed since commit f7a42540928a8 ("scsi:
ufs: Protect some contexts from unexpected clock scaling") is a more
mature fix to protect UFS LLD stability from clock scaling invoked through
sysfs nodes
I'm announcing the release of the 4.19.164 kernel.
All users of the 4.19 kernel series must upgrade.
The updated 4.19.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.19.y
and can be browsed at the normal kernel.org git web
I'm announcing the release of the 5.4.86 kernel.
All users of the 5.4 kernel series must upgrade.
The updated 5.4.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-5.4.y
and can be browsed at the normal kernel.org git web browser:
I'm announcing the release of the 5.10.4 kernel.
All users of the 5.10 kernel series must upgrade.
The updated 5.10.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-5.10.y
and can be browsed at the normal kernel.org git web browser:
This patch series does the following:
- converts the qcom,spmi-pmic bindings from .txt to .yaml format
- Sorted the compatible strings
- Adds PM6150 and PM6150L subtypes.
Changes from V1:
- Sorted the compatible strings as per Stephen Boyd's comments.
- Added a patch to convert the
Excerpts from Russell King - ARM Linux admin's message of December 30, 2020
8:58 pm:
> On Wed, Dec 30, 2020 at 10:00:28AM +, Russell King - ARM Linux admin
> wrote:
>> On Wed, Dec 30, 2020 at 12:33:02PM +1000, Nicholas Piggin wrote:
>> > Excerpts from Russell King - ARM Linux admin's message
Add the compatibles and PMIC ids for pm6150 and pm6150l PMICs
found on SC7180 based platforms.
Signed-off-by: Kiran Gunda
Acked-for-MFD-by: Lee Jones
Reviewed-by: Stephen Boyd
---
Documentation/devicetree/bindings/mfd/qcom,spmi-pmic.yaml | 2 ++
drivers/mfd/qcom-spmi-pmic.c
Convert the bindings from .txt to .yaml format.
Signed-off-by: Kiran Gunda
---
.../devicetree/bindings/mfd/qcom,spmi-pmic.txt | 80 --
.../devicetree/bindings/mfd/qcom,spmi-pmic.yaml| 117 +
2 files changed, 117 insertions(+), 80 deletions(-)
delete
local variable node_order do not need the static here.
Signed-off-by: Hui Su
---
mm/page_alloc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/mm/page_alloc.c b/mm/page_alloc.c
index bdbec4c98173..45e049ccf117 100644
--- a/mm/page_alloc.c
+++ b/mm/page_alloc.c
@@ -5864,7
From: Zqiang
Due to freeary function is called with spinlock be held,
the synchronize_rcu function may be called in kfree_rcu
function, the schedule may be happen in spinlock critical
region, need to replace kfree_rcu() with call_rcu().
Fixes: 693a8b6eecce ("ipc,rcu: Convert call_rcu(free_un)
Hi,
On 12/30/20 12:23 PM, Richard Fitzgerald wrote:
> On 30/12/2020 11:04, Hans de Goede wrote:
>> Hi,
>>
>> On 12/29/20 5:51 PM, Richard Fitzgerald wrote:
>>>
>>>
>>> On 29/12/2020 15:40, Hans de Goede wrote:
Hi,
On 12/29/20 4:15 PM, Mark Brown wrote:
> On Tue, Dec 29, 2020 at
On Tue, 15 Dec 2020 13:44:43 +0800
Ye Xiang wrote:
> The Hinge sensor is a common custom sensor on laptops. It calculates
> the angle between the lid (screen) and the base (keyboard). In addition,
> it also exposes screen and the keyboard angles with respect to the
> ground. Applications can
On Tue, 15 Dec 2020 13:44:41 +0800
Ye Xiang wrote:
> Here we register one iio device with three channels which present angle for
> hinge, keyboard and screen.
>
> This driver works on devices with Intel integrated sensor hub, where
> hinge sensor is presented using a custom sensor usage id.
>
Cadence controller will not initiate autonomous speed change if strapped
as Gen2. The Retrain Link bit is set as quirk to enable this speed change.
Signed-off-by: Nadeem Athani
---
drivers/pci/controller/cadence/pci-j721e.c | 3 ++
drivers/pci/controller/cadence/pcie-cadence-host.c |
Move the function cdns_pcie_host_wait_for_link() further up in the file,
as it's going to be used by upcoming additional code in the driver.
Signed-off-by: Nadeem Athani
---
drivers/pci/controller/cadence/pcie-cadence-host.c | 33 +++---
1 file changed, 16 insertions(+), 17
Cadence controller will not initiate autonomous speed change if strapped
as Gen2. The Retrain Link bit is set as quirk to enable this speed change.
Adding a quirk flag for defective IP. In future IP revisions this will not
be applicable.
Version history:
Changes in v7:
- Changing the commit title
On Wed, 2020-12-30 at 15:14 +0800, Peng Wang wrote:
> Some max_length wants to hold as large room as possible to
> ensure enough size to tackle with the biggest NR_CPUS.
> An example below:
>
> kernel/cgroup/cpuset.c:
> static struct cftype legacy_files[] = {
> {
> .name =
Latest (but not only latest) linux-next panics with divide
error on my QEMU setup.
The patch at the bottom of this message fixes the problem.
xor: measuring software checksum speed
divide error: [#1] PREEMPT SMP KASAN
PREEMPT SMP KASAN
CPU: 3 PID: 1 Comm: swapper/0 Not tainted
From: Borislav Petkov
No functional changes.
Signed-off-by: Borislav Petkov
---
arch/x86/include/asm/microcode.h | 2 --
arch/x86/kernel/cpu/microcode/core.c | 2 +-
2 files changed, 1 insertion(+), 3 deletions(-)
diff --git a/arch/x86/include/asm/microcode.h
Hi!
> commit a86cf9b29e8b12811cf53c4970eefe0c1d290476 upstream.
>
> Validate media bus code, width and height when setting the subdev format.
>
> This effectively reworks how setting subdev format is implemented in the
> driver.
Something is wrong here:
> + fmt->format.code =
From: Jangwoong Kim <6812sk...@gmail.com>
Get rid of gotos that do not contain any cleanup.
According to coding style documentation: "If there is no
cleanup needed then just return directly"
Signed-off-by: Jangwoong Kim <6812sk...@gmail.com>
---
kernel/futex.c | 7 +++
1 file changed, 3
Some max_length wants to hold as large room as possible to
ensure enough size to tackle with the biggest NR_CPUS.
An example below:
kernel/cgroup/cpuset.c:
static struct cftype legacy_files[] = {
{
.name = "cpus",
.seq_show = cpuset_common_seq_show,
1 - 100 of 485 matches
Mail list logo
