On 04/02/21 08:22, Yang Weijiang wrote:
Thanks Sean for catching this!
Hi, Paolo,
Do I need to send another version to include Sean's change?
No, it's okay.
Paolo
Hello!
On 04.02.2021 10:17, Xu Wang wrote:
Remove casting the values returned by dma_alloc_coherent.
I'm not seeing any casting, I'm seeing a trailing space removed.
Signed-off-by: Xu Wang
---
drivers/usb/host/ehci-mem.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
On Wed, Feb 03, 2021 at 09:46:55AM -0800, Ivan Babrou wrote:
> > Can you pretty please not line-wrap console output? It's unreadable.
>
> GMail doesn't make it easy, I'll send a link to a pastebin next time.
> Let me know if you'd like me to regenerate the decoded stack.
Not my problem that you
Hi Will,
On 2021-02-03 21:13, Will Deacon wrote:
Hi Marc,
On Mon, Feb 01, 2021 at 11:56:22AM +, Marc Zyngier wrote:
There isn't much that a VHE kernel needs on top of whatever has
been done for nVHE, so let's move the little we need to the
VHE stub (the SPE setup), and drop the
On 03.02.2021 20:20, Yang Shi wrote:
> Now nr_deferred is available on per memcg level for memcg aware shrinkers, so
> don't need
> allocate shrinker->nr_deferred for such shrinkers anymore.
>
> The prealloc_memcg_shrinker() would return -ENOSYS if !CONFIG_MEMCG or memcg
> is disabled
> by
Hi Boris,
Boris Brezillon wrote on Thu, 4 Feb
2021 10:27:38 +0100:
> On Thu, 4 Feb 2021 10:04:08 +0100
> Miquel Raynal wrote:
>
> > Hi Boris,
> >
> > Boris Brezillon wrote on Thu, 4 Feb
> > 2021 09:59:45 +0100:
> >
> > > On Thu, 4 Feb 2021 14:22:21 +0530
> > > Manivannan Sadhasivam
From: Colin Ian King
There is a spelling mistake in a netdev_warn message. Fix it.
Signed-off-by: Colin Ian King
---
drivers/net/ethernet/mellanox/mlx5/core/en_main.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/ethernet/mellanox/mlx5/core/en_main.c
On Thu, 4 Feb 2021 10:04:08 +0100
Miquel Raynal wrote:
> Hi Boris,
>
> Boris Brezillon wrote on Thu, 4 Feb
> 2021 09:59:45 +0100:
>
> > On Thu, 4 Feb 2021 14:22:21 +0530
> > Manivannan Sadhasivam wrote:
> >
> > > On Thu, Feb 04, 2021 at 09:13:36AM +0100, Miquel Raynal wrote:
> > > >
On 04/02/2021 08:28, Yang Li wrote:
> This patch removes unneeded return variables, using only
> '0' instead.
> It fixes the following warning detected by coccinelle:
> ./drivers/scsi/ipr.c:9508:5-7: Unneeded variable: "rc". Return "0" on
> line 9524
>
> Reported-by: Abaci Robot
> Signed-off-by:
On 04/02/2021 08:20, Yang Li wrote:
> This patch removes unneeded return variables, using only
> '0' instead.
> It fixes the following warning detected by coccinelle:
> ./drivers/scsi/qla4xxx/ql4_os.c:3642:5-7: Unneeded variable: "rc".
> Return "0" on line 3741
>
> Reported-by: Abaci Robot
>
On Thu, Feb 04, 2021 at 09:30:08AM +, Marc Zyngier wrote:
> Hi Will,
>
> On 2021-02-03 21:13, Will Deacon wrote:
> > Hi Marc,
> >
> > On Mon, Feb 01, 2021 at 11:56:22AM +, Marc Zyngier wrote:
> > > There isn't much that a VHE kernel needs on top of whatever has
> > > been done for nVHE,
On 2/3/21 12:10 PM, Bharata B Rao wrote:
> On Wed, Jan 27, 2021 at 12:04:01PM +0100, Vlastimil Babka wrote:
>> Yes, but it's tricky to do the retuning safely, e.g. if freelist
>> randomization
>> is enabled, see [1].
>>
>> But as a quick fix for the regression, the heuristic idea could work
>>
On Wed 2021-02-03 15:47:27, Steven Rostedt wrote:
> On Wed, 3 Feb 2021 12:35:07 -0800
> Kees Cook wrote:
>
> > > With a big notice that all pointers of unhashed, I don't think we need to
> > > print it failed when we expect it to fail.
> > >
> > > If anything, skip the test and state:
> > >
>
The global UID uniqueness attribute exposes whether the platform
guarantees that the user-defined per-device UID attribute values
(/sys/bus/pci/device//uid) are unique and can thus be used as
a global identifier for the associated PCI device. With this commit
it is exposed at
On 2021-02-04 09:34, Will Deacon wrote:
On Thu, Feb 04, 2021 at 09:30:08AM +, Marc Zyngier wrote:
[...]
I think the following patch addresses the above issue, which I'll
squash
with the original patch. Please shout if I missed anything.
Thanks,
M.
diff --git
From: Colin Ian King
There is a spelling mistake in the function name alloc_channles_and_rings.
Fix this by renaming it to alloc_channels_and_rings.
Signed-off-by: Colin Ian King
---
drivers/net/ethernet/synopsys/dwc-xlgmac-desc.c | 2 +-
drivers/net/ethernet/synopsys/dwc-xlgmac-net.c | 2 +-
Hello,
syzbot found the following issue on:
HEAD commit:6642d600 Merge tag '5.11-rc5-smb3' of git://git.samba.org/..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=14de59e8d0
kernel config: https://syzkaller.appspot.com/x/.config?x=f75d66d6d359ef2f
On 04/02/2021 06:01, diksh...@codeaurora.org wrote:
> On 2021-02-01 16:50, Hans Verkuil wrote:
>> On 25/01/2021 06:51, Dikshita Agarwal wrote:
>>> Long Term Reference (LTR) frames are the frames that are encoded
>>> sometime in the past and stored in the DPB buffer list to be used
>>> as reference
On Thu, Feb 04, 2021 at 10:07:58AM +0100, Ard Biesheuvel wrote:
> On Thu, 4 Feb 2021 at 09:43, Guillaume Tucker
> wrote:
> >
> > Hi Ard,
> >
> > Please see the bisection report below about a boot failure on
> > rk3288 with next-20210203. It was also bisected on
> > imx6q-var-dt6customboard with
With the advent of various new memory types, some machines will have
multiple types of memory, e.g. DRAM and PMEM (persistent memory). The
memory subsystem of these machines can be called memory tiering
system, because the performance of the different types of memory are
usually different.
After
With the advent of various new memory types, some machines will have
multiple types of memory, e.g. DRAM and PMEM (persistent memory). The
memory subsystem of these machines can be called memory tiering
system, because the performance of the different types of memory are
usually different.
In
To optimize page placement in a memory tiering system with NUMA
balancing, the hot pages in the slow memory node need to be
identified. Essentially, the original NUMA balancing implementation
selects the mostly recently accessed (MRU) pages as the hot pages.
But this isn't a very good algorithm
If the NUMA balancing isn't used to optimize the page placement among
sockets but only among memory types, the hot pages in the fast memory
node couldn't be migrated (promoted) to anywhere. So it's unnecessary
to scan the pages in the fast memory node via changing their PTE/PMD
mapping to be
To distinguish the number of the memory tiering promoted pages from
that of the originally inter-socket NUMA balancing migrated pages.
The counter is per-node (count in the target node). So this can be
used to identify promotion imbalance among the NUMA nodes.
Signed-off-by: "Huang, Ying"
Cc:
In NUMA balancing memory tiering mode, the hot slow memory pages could
be promoted to the fast memory node via NUMA balancing. But this
incurs some overhead too. So that sometimes the workload performance
may be hurt. To avoid too much disturbing to the workload in these
situations, we should
The following changes since commit 0d7389718c32ad6bb8bee7895c91e2418b6b26aa:
Merge tag 'nvme-5.21-2020-02-02' of git://git.infradead.org/nvme into
for-5.12/drivers (2021-02-02 07:11:47 -0700)
are available in the Git repository at:
https://github.com/evdenis/linux-floppy
The 02/03/2021 11:18, Mike Snitzer wrote:
> On Wed, Feb 03 2021 at 10:53am -0500,
> Sergei Shtepa wrote:
>
> > blk_interposer allows to intercept bio requests, remap bio to another
> > devices or add new bios.
> >
> > Signed-off-by: Sergei Shtepa
> > ---
> > block/bio.c | 2 +
On Thu, Feb 04, 2021 at 10:20:35AM +0100, Pawel Laszczak wrote:
> Patch removes some useless trace events that can
> be replaced by ftrace.
>
> Reported-by: Dan Carpenter
> Signed-off-by: Pawel Laszczak
> ---
> drivers/usb/cdns3/cdnsp-ep0.c| 5 -
> drivers/usb/cdns3/cdnsp-gadget.c |
On Thu, 4 Feb 2021 at 11:06, Russell King - ARM Linux admin
wrote:
>
> On Thu, Feb 04, 2021 at 10:07:58AM +0100, Ard Biesheuvel wrote:
> > On Thu, 4 Feb 2021 at 09:43, Guillaume Tucker
> > wrote:
> > >
> > > Hi Ard,
> > >
> > > Please see the bisection report below about a boot failure on
> > >
On Mon, Feb 01, 2021 at 07:40:45PM +0200, James Clark wrote:
>
> On 31/01/2021 14:01, Leo Yan wrote:
> > Option 1: by merging patches 07/08 and 08/08, we can firstly support PID
> > tracing for root namespace, and later we can extend to support PID
> > tracing in container (and in VMs).
> >
> >
Christoph Hellwig writes:
> The static inline get_cxl_module function is entirely unused since commit
> 8bf6b91a5125a ("Revert "powerpc/powernv: Add support for the cxl kernel
> api on the real phb"), so remove it.
>
> Signed-off-by: Christoph Hellwig
> Reviewed-by: Andrew Donnellan
> ---
>
On 04/02/21 01:01, Sean Christopherson wrote:
Add helpers to consolidate the GPA reserved bits checks that are scattered
all over KVM, and fix a few bugs in the process.
The original motivation was simply to get rid of all the different open
coded variations of the checks (there were a lot),
On Wed, 03 Feb 2021, Colin King wrote:
> From: Colin Ian King
>
> There is a spelling mistake in a drm_dbg message. Fix it.
>
> Signed-off-by: Colin Ian King
Thanks, pushed to drm-intel-next.
BR,
Jani.
> ---
> drivers/gpu/drm/i915/display/intel_dp.c | 2 +-
> 1 file changed, 1
On 02/03/21 18:35, Vincent Guittot wrote:
> > > raw_spin_unlock(_rq->lock);
> > > - /*
> > > - * This CPU is going to be idle and blocked load of idle CPUs
> > > - * need to be updated. Run the ilb locally as it is a good
> > > - * candidate for ilb instead of waking up
Hi Sam,
I replied to several of the patches: it looks like the drm code has changed
since
some of this patches were written, and I think it can be simplified quite a bit.
Regards,
Hans
On 04/02/2021 10:54, Sam McNally wrote:
> I can for this patch; I'm not really sure of the right
On 03/02/2021 16:15, Qais Yousef wrote:
> On 01/28/21 18:31, Valentin Schneider wrote:
[...]
>> @@ -10238,7 +10236,7 @@ static void nohz_balancer_kick(struct rq *rq)
>> * When ASYM_CPUCAPACITY; see if there's a higher capacity CPU
>> * to run the misfit task on.
>>
On 2/4/21 4:17 PM, Ravi Bangoria wrote:
Don't allow Uprobe on 2nd word of a prefixed instruction. As per
ISA 3.1, prefixed instruction should not cross 64-byte boundary.
So don't allow Uprobe on such prefixed instruction as well.
There are two ways probed instruction is changed in mapped
On Wed, Feb 03, 2021 at 09:29:18PM +0100, Ard Biesheuvel wrote:
> I think we have agreement on the approach but it is unclear who is
> going to write the patch.
How's that below?
And frankly, I'd even vote for removing those assertions altogether. If
somehow the EFI pgd lands somewhere else, the
On 2/4/21 3:47 AM, Leo Yan wrote:
On Tue, Feb 02, 2021 at 11:19:22PM +, Suzuki Kuruppassery Poulose wrote:
On 2/2/21 4:38 PM, Leo Yan wrote:
This patch adds helper function cs_etm__get_pid_fmt(), by passing
parameter "traceID", it returns the PID format.
Signed-off-by: Leo Yan
---
The rule of list walk has gone since:
commit a9d5adeeb4b2 ("mm/memcontrol: allow to uncharge page without using
page->lru field")
So remove the strange comment and replace the loop with a
list_for_each_entry().
Signed-off-by: Muchun Song
---
mm/memcontrol.c | 17 ++---
1 file
On 04-02-21, 16:14, Hsin-Yi Wang wrote:
> From: Saravana Kannan
>
> Add a function that allows looking up required OPPs given a source OPP
> table, destination OPP table and the source OPP.
>
> Signed-off-by: Saravana Kannan
> Signed-off-by: Hsin-Yi Wang
> ---
> drivers/opp/core.c | 59
On Sat, 23 Jan 2021, Hans de Goede wrote:
> Hi all,
>
> Here is v4 of my series to rework the arizona codec jack-detect support
> to use the snd_soc_jack helpers instead of direct extcon reporting.
>
> This is done by reworking the extcon driver into an arizona-jackdet
> library and then
On 04-02-21, 17:46, Chanwoo Choi wrote:
> > Signed-off-by: Saravana Kannan
> > Reviewed-by: Chanwoo Choi
> > Acked-by: MyungJoo Ham
> > Signed-off-by: Hsin-Yi Wang
>
> Acked-by: Chanwoo Choi
I am not sure if keeping both Acked-by and Reviewed-by make sense. I
am keeping Acked-by as it was
Fixes the following W=1 kernel build warning(s):
drivers/crypto/bcm/spu.c:464: warning: Excess function parameter 'Return'
description in 'spum_gcm_ccm_pad_len'
drivers/crypto/bcm/spu.c:524: warning: Function parameter or member 'iv_len'
not described in 'spum_aead_ivlen'
Fixes the following W=1 kernel build warning(s):
drivers/crypto/bcm/spu2.c:557: warning: Function parameter or member 'fmd' not
described in 'spu2_fmd_init'
drivers/crypto/bcm/spu2.c:557: warning: Function parameter or member
'spu2_type' not described in 'spu2_fmd_init'
Fixes the following W=1 kernel build warning(s):
drivers/crypto/ux500/cryp/cryp_irq.c:21: warning: Function parameter or member
'device_data' not described in 'cryp_enable_irq_src'
drivers/crypto/ux500/cryp/cryp_irq.c:21: warning: Function parameter or member
'irq_src' not described in
Fixes the following W=1 kernel build warning(s):
drivers/crypto/ux500/cryp/cryp.c:19: warning: Incorrect use of kernel-doc
format: * cryp_wait_until_done - wait until the device logic is not busy
drivers/crypto/ux500/cryp/cryp.c:22: warning: Function parameter or member
'device_data' not
Fixes the following W=1 kernel build warning(s):
drivers/crypto/keembay/ocs-hcu.c:107: warning: expecting prototype for struct
ocs_hcu_dma_list. Prototype was for struct ocs_hcu_dma_entry instead
drivers/crypto/keembay/ocs-hcu.c:127: warning: expecting prototype for struct
ocs_dma_list.
Fixes the following W=1 kernel build warning(s):
drivers/crypto/chelsio/chcr_core.c:2: warning: wrong kernel-doc identifier on
line:
Cc: Ayush Sawal
Cc: Vinay Kumar Yadav
Cc: Rohit Maheshwari
Cc: Herbert Xu
Cc: "David S. Miller"
Cc: Manoj Malviya
Cc: Atul Gupta
Cc: Jitendra Lulla
Cc: M
Shared mappings are allowed to be created without reservations since
commit c37f9fb11c97 ("hugetlb: allow huge page mappings to be created
without reservations"). Remove this obsolete comment which may cause
confusing.
Signed-off-by: Miaohe Lin
---
mm/hugetlb.c | 1 -
1 file changed, 1
Fixes the following W=1 kernel build warning(s):
drivers/crypto/nx/nx-aes-cbc.c:24: warning: Function parameter or member 'tfm'
not described in 'cbc_aes_nx_set_key'
drivers/crypto/nx/nx-aes-cbc.c:24: warning: Function parameter or member
'in_key' not described in 'cbc_aes_nx_set_key'
Fixes the following W=1 kernel build warning(s):
drivers/crypto/bcm/cipher.c:1048: warning: Function parameter or member 'req'
not described in 'spu_aead_rx_sg_create'
drivers/crypto/bcm/cipher.c:2966: warning: Function parameter or member
'cipher' not described in 'rfc4543_gcm_esp_setkey'
Fixes the following W=1 kernel build warning(s):
drivers/crypto/atmel-ecc.c:41: warning: cannot understand function prototype:
'struct atmel_ecdh_ctx '
Cc: Tudor Ambarus
Cc: Herbert Xu
Cc: "David S. Miller"
Cc: Nicolas Ferre
Cc: Alexandre Belloni
Cc: Ludovic Desroches
Cc:
There are many slightly different prototypes for this syscall,
but none of them is like the documented one.
Of all the different prototypes,
let's document the asm-generic one.
..
.../linux$ grep_syscall mmap2
arch/csky/kernel/syscall.c:17:
SYSCALL_DEFINE6(mmap2,
unsigned long, addr,
Firmware allocates memory regions for PFs and VFs in DRAM.
The PFs memory region is used for AF-PF and PF-VF mailbox.
This mbox facilitates communication between AF-PF and PF-VF.
On CN10K platform:
The DRAM region allocated to PF is enumerated as PF BAR4 memory.
PF BAR4 contains AF-PF mbox region
The current admin function (AF) driver and the netdev driver supports
OcteonTx2 silicon variants. The same OcteonTx2's
Resource Virtualization Unit (RVU) is carried forward to the next-gen
silicon ie OcteonTx3, with some changes and feature enhancements.
This patch set adds support for OcteonTx3
From: Subbaraya Sundeep
Firmware allocates memory regions for PFs and VFs in DRAM.
The PFs memory region is used for AF-PF and PF-VF mailbox.
This mbox facilitate communication between AF-PF and PF-VF.
On CN10K platform:
The DRAM region allocated to PF is enumerated as PF BAR4 memory.
PF BAR4
NIX hardware context structure got changed to accommodate new
features like bandwidth steering, L3/L4 outer/inner checksum
enable/disable etc., on CN10K platform.
This patch defines new mbox message NIX_CN10K_AQ_INST for new
NIX context initialization.
This patch also updates the NPA context
On CN10K platform NPA and NIX context structure bit fields
had changed to support new features like bandwidth steering etc.
This patch dumps approprate context for CN10K platform.
Signed-off-by: Geetha sowjanya
Signed-off-by: Sunil Goutham
---
.../ethernet/marvell/octeontx2/af/rvu_debugfs.c
We must free/disable all interrupts and cancel all pending works
before doing further cleanup.
Before this commit arizona_extcon_remove() was doing several
register writes to shut things down before disabling the IRQs
and it was cancelling only 1 of the 3 different works used.
Move all the
On CN10K platform NIX RQ and SQ context structure got changed.
This patch uses new mbox message "NIX_CN10K_AQ_ENQ" for NIX
context initialization on CN10K platform.
This patch also updates the nix_rx_parse_s and nix_sqe_sg_s
structures to add packet steering bit feilds.
Signed-off-by: Geetha
The initial value of the GPIO should match the info->micd_modes[0].gpio
value. arizona_extcon_probe() already stores the necessary flag in a
mode variable, but instead of passing mode as flags to the gpiod_get()
it was using a hardcoded GPIOD_OUT_LOW.
Reviewed-by: Andy Shevchenko
Acked-by:
We could use helper function range_in_vma() to check whether the vma is in
the desired range to simplify the code.
Signed-off-by: Miaohe Lin
---
mm/hugetlb.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/mm/hugetlb.c b/mm/hugetlb.c
index cf82629319ed..442705be052a 100644
From: Hariprasad Kelam
MAC on CN10K silicon support loopback for selftest or debug purposes.
This patch does necessary configuration to loopback packets upon receiving
request from LMAC mapped RVU PF's netdev via mailbox.
Also MAC (CGX) on OcteonTx2 silicon variants and MAC (RPM) on
OcteonTx3
.../linux$ grep_syscall ipc
ipc/syscall.c:110:
SYSCALL_DEFINE6(ipc, unsigned int, call, int, first, unsigned long, second,
unsigned long, third, void __user *, ptr, long, fifth)
ipc/syscall.c:205:
COMPAT_SYSCALL_DEFINE6(ipc, u32, call, int, first, int, second,
u32, third,
On Thu, Feb 04, 2021 at 09:10:11AM +0100, Dmitry Vyukov wrote:
> On Wed, Feb 3, 2021 at 2:37 PM Peter Zijlstra wrote:
> > Letting perf send a signal to the monitored task is intrusive.. let me
> > think on that.
>
> I was thinking of something very similar to that bpf_send_signal that
> delays
Hi Brian,
On Wed, 3 Feb 2021 19:52:08 -0800 Brian Vazquez wrote:
>
> Hi Stephen, thanks for the report. I'm having trouble trying to
> compile for ppc, but I believe this should fix the problem, could you
> test this patch, please? Thanks!
That fixed it, thanks (though the patch was badly
Hi Bjorn,
this is a follow-up to my previous RFC of exposing our s390 specific UID
Checking attribute at /sys/bus/pci/zpci/unique_uids. As suggested by Greg
(thanks!) this version changes things to use named attributes directly without
resorting to any raw kobject handling, as a result the code
On Thu, Feb 04, 2021 at 01:01:57AM +, Alexey Klimov wrote:
> @@ -1281,6 +1282,11 @@ static int cpu_up(unsigned int cpu, enum cpuhp_state
> target)
> err = _cpu_up(cpu, 0, target);
> out:
> cpu_maps_update_done();
> +
> + /* To avoid out of line uevent */
> + if (!err)
> +
Thank you, I'll fix it all.
--
Sergei Shtepa
Veeam Software developer.
From: Mingchuang Qiao
In bus scan flow, the "LTR Mechanism Enable" bit of DEVCTL2 register is
configured in pci_configure_ltr(). If device and bridge both support LTR
mechanism, the "LTR Mechanism Enable" bit of device and bridge will be
enabled in DEVCTL2 register. And pci_dev->ltr_path will be
On Thu, Feb 4, 2021 at 10:39 AM Peter Zijlstra wrote:
>
> On Thu, Feb 04, 2021 at 09:10:11AM +0100, Dmitry Vyukov wrote:
> > On Wed, Feb 3, 2021 at 2:37 PM Peter Zijlstra wrote:
>
> > > Letting perf send a signal to the monitored task is intrusive.. let me
> > > think on that.
> >
> > I was
It isn't easy for the administrator to determine the hot threshold.
So in this patch, a method to adjust the hot threshold automatically
is implemented. The basic idea is to control the number of the
candidate promotion pages to match the promotion rate limit. If the
hint page fault latency of a
On Jan 13 2021, Palmer Dabbelt wrote:
> On Tue, 10 Nov 2020 07:22:09 PST (-0800), sagar.ka...@sifive.com wrote:
>> HiFive Unleashed is having VSC8541-01 ethernet phy device and requires a
>> specific reset sequence of 0-1-0-1 in order to use it in unmanaged mode.
>> This series addresses a corner
On 2/4/21 12:24 PM, Jiri Kosina wrote:
> On Tue, 26 Jan 2021, Denis Efremov wrote:
>
>> Applied. I'll send it to Jens soon with a couple of cleanup patches.
>>
>> https://github.com/evdenis/linux-floppy/commit/e32f6163c47efbdbad06258560aa00d1c7e5b699
>
> Denis,
>
> I don't see this fix in
On Wed, Feb 3, 2021 at 5:14 PM Daniel Vetter wrote:
>
> On Tue, Jan 19, 2021 at 5:03 PM Daniel Vetter wrote:
> >
> > On Tue, Jan 19, 2021 at 4:20 PM Greg Kroah-Hartman
> > wrote:
> > >
> > > On Tue, Jan 19, 2021 at 03:34:47PM +0100, Daniel Vetter wrote:
> > > > On Tue, Jan 19, 2021 at 3:32 PM
On 03.02.2021 20:20, Yang Shi wrote:
> The number of deferred objects might get windup to an absurd number, and it
> results in clamp of slab objects. It is undesirable for sustaining
> workingset.
>
> So shrink deferred objects proportional to priority and cap nr_deferred to
> twice
> of
On Thu, Feb 04, 2021 at 05:06:25PM +0800, Ruifeng Zhang wrote:
> Greg KH 于2021年1月29日周五 下午4:53写道：
> >
> > On Fri, Jan 29, 2021 at 04:27:26PM +0800, Ruifeng Zhang wrote:
> > > From: Ruifeng Zhang
> > >
> > > Suspend type contains s2ram and s2idle, but syscore is only
> > > available for S2RAM.
> >
On Mon, 18 Jan 2021, Campion Kang wrote:
> This files defines the sud-device types and hwmon profiles support by
> Advantech embedded controller.
>
> Signed-off-by: Campion Kang
> ---
> include/dt-bindings/mfd/ahc1ec0-dt.h | 25 +
> 1 file changed, 25 insertions(+)
>
On 04/02/2021 10:27, Ard Biesheuvel wrote:
> On Thu, 4 Feb 2021 at 11:06, Russell King - ARM Linux admin
> wrote:
>>
>> On Thu, Feb 04, 2021 at 10:07:58AM +0100, Ard Biesheuvel wrote:
>>> On Thu, 4 Feb 2021 at 09:43, Guillaume Tucker
>>> wrote:
Hi Ard,
Please see the
On 04/02/21 03:19, Sean Christopherson wrote:
Ah, took me a few minutes, but I see what you're saying. LAM will introduce
bits that are repurposed for CR3, but not generic GPAs. And, the behavior is
based on CPU support, so it'd make sense to have a mask cached in vcpu->arch
as opposed to
Hi Nick,
On Fri, Jan 29, 2021 at 04:44:00PM -0800, Nick Desaulniers wrote:
> Modifies CONFIG_DEBUG_INFO_DWARF4 to be a member of a choice which is
> the default. Does so in a way that's forward compatible with existing
> configs, and makes adding future versions more straightforward.
>
> GCC
On 03/02/2021 17:23, Marc Zyngier wrote:
Before:
In free path, we have:
its_irq_domain_free(nvecs = 27)
bitmap_release_region(count order = 5 == 32bits)
Current:
In free path, we have:
its_irq_domain_free(nvecs = 1) for free each 27 vecs
bitmap_release_region(count
On Wednesday 03 Feb 2021 at 14:37:10 (+), Will Deacon wrote:
> On Fri, Jan 08, 2021 at 12:15:14PM +, Quentin Perret wrote:
> > +static inline unsigned long __hyp_pgtable_max_pages(unsigned long nr_pages)
> > +{
> > + unsigned long total = 0, i;
> > +
> > + /* Provision the worst case
On Thu, Feb 04, 2021 at 11:27:16AM +0100, Ard Biesheuvel wrote:
> Hi Russell,
>
> If Guillaume is willing to do the experiment, and it fixes the issue,
> it proves that rk3288 is relying on the flush before the MMU is
> disabled, and so in that case, the fix is trivial, and we can just
> apply
(cc Marc)
On Thu, 4 Feb 2021 at 11:48, Russell King - ARM Linux admin
wrote:
>
> On Thu, Feb 04, 2021 at 11:27:16AM +0100, Ard Biesheuvel wrote:
> > Hi Russell,
> >
> > If Guillaume is willing to do the experiment, and it fixes the issue,
> > it proves that rk3288 is relying on the flush before
On 2/4/21 4:00 AM, Leo Yan wrote:
On Tue, Feb 02, 2021 at 11:29:47PM +, Suzuki Kuruppassery Poulose wrote:
On 2/2/21 4:38 PM, Leo Yan wrote:
From: Suzuki K Poulose
The PID of the task could be traced as VMID when the kernel is running
at EL2. Teach the decoder to look for VMID when the
On Thu, 04 Feb 2021, Hans de Goede wrote:
> Hi all,
>
> On 1/20/21 10:49 PM, Hans de Goede wrote:
> > Hi All,
> >
> > Here is v4 of my series to add support for Intel Bay Trail based devices
> > which use a WM5102 codec for audio output/input.
> >
> > This was developed and tested on a Lenovo
On Thu, Feb 04, 2021 at 10:37:24AM +, Lee Jones wrote:
> On Fri, 29 Jan 2021, Dan Carpenter wrote:
>
> > The "req" struct is always added to the "wm831x->auxadc_pending" list,
> > but it's only removed from the list on the success path. If a failure
> > occurs then the "req" struct is freed
On Thu, 4 Feb 2021 at 11:52, Borislav Petkov wrote:
>
> On Wed, Feb 03, 2021 at 09:29:18PM +0100, Ard Biesheuvel wrote:
> > I think we have agreement on the approach but it is unclear who is
> > going to write the patch.
>
> How's that below?
>
> And frankly, I'd even vote for removing those
' as documented in
https://git-scm.com/docs/git-format-patch]
url:
https://github.com/0day-ci/linux/commits/alexandru-tachici-analog-com/iio-adc-ad7124-allow-16-channels/20210204-171550
base: https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git togreg
config: h8300-randconfig-r002-20210204
On Thu, Feb 4, 2021 at 4:18 PM Chunyan Zhang wrote:
>
> From: Magnum Shan
>
> According to the specification, bit[2] represents SPRD_OUTBOX_FIFO_FULL,
> not bit[0], so correct it.
>
> Fixes: ca27fc26cd22 ("mailbox: sprd: Add Spreadtrum mailbox driver")
> Signed-off-by: Magnum Shan
>
On 04. 02. 21, 9:51, Greg Kroah-Hartman wrote:
It might work somewhere, but there are a lot of (X * 65536 + Y * 256 + Z)
assumptions all around the world. So this doesn't look like a good idea.
Ok, so what happens if we "wrap"? What will break with that? At first
glance, I can't see anything
Hi,
On 2/4/21 12:05 PM, Lee Jones wrote:
> On Sat, 23 Jan 2021, Hans de Goede wrote:
>
>> Hi all,
>>
>> Here is v4 of my series to rework the arizona codec jack-detect support
>> to use the snd_soc_jack helpers instead of direct extcon reporting.
>>
>> This is done by reworking the extcon driver
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.
This is set 1 of 2 sets required to fully clean Crypto.
Lee Jones (20):
crypto: hisilicon: sec_drv: Supply missing description for
Fixes the following W=1 kernel build warning(s):
drivers/crypto/hisilicon/sec/sec_drv.c:843: warning: Function parameter or
member 'queue' not described in 'sec_queue_empty'
Cc: Herbert Xu
Cc: "David S. Miller"
Cc: Zaibo Xu
Cc: Jonathan Cameron
Cc: linux-cry...@vger.kernel.org
Hi Nicolin,
A regression was detected by kernelci.org in IGT's drm_read tests
on mainline, it was first seen on 17th December 2020. You can
find some details here:
https://kernelci.org/test/case/id/600b82dc1e3208f123d3dffc/
Then an automated bisection was run and it landed on this
patch
Fixes the following W=1 kernel build warning(s):
drivers/crypto/bcm/util.c:136: warning: Function parameter or member
'from_nents' not described in 'spu_msg_sg_add'
drivers/crypto/bcm/util.c:136: warning: Function parameter or member 'length'
not described in 'spu_msg_sg_add'
Cc: Herbert Xu
The ones remove here not only fail to conform to kernel-doc, but also
provide no value, so let's remove them completely in this case.
Fixes the following W=1 kernel build warning(s):
drivers/crypto/ux500/hash/hash_core.c:368: warning: Function parameter or
member 'ctx' not described in
On 02.02.21 11:17, Jiapeng Chong wrote:
Fix the following coccicheck warnings:
./drivers/net/xen-netfront.c:1816:52-54: WARNING !A || A && B is
equivalent to !A || B.
Reported-by: Abaci Robot
Signed-off-by: Jiapeng Chong
Reviewed-by: Juergen Gross
Juergen
1 - 100 of 1521 matches
Mail list logo
