Stephen Rothwell wrote:
> After merging the fscache tree, today's linux-next build (x86_64
> allmodconfig) produced this warning:
>
> fs/afs/file.c: In function 'afs_req_issue_op':
> fs/afs/file.c:291:6: warning: unused variable 'ret' [-Wunused-variable]
> 291 | int ret;
> | ^~~
>
Uwe Kleine-König writes:
> Hello,
>
> On 3/2/21 3:09 AM, Michael Ellerman wrote:
>> Stephen Rothwell writes:
>>> Hi all,
>>>
>>> After merging the powerpc-fixes tree, today's linux-next build (powerpc
>>> allyesconfig) failed like this:
>>>
>>> drivers/net/ethernet/ibm/ibmvnic.c:5399:13: error: c
Hi all!
On 02/03/2021 18:42, Joe Perches wrote:
[...]
> - For instance: (head -10 of the git grep for file statics)
>
> drivers/accessibility/speakup/keyhelp.c:18:static u_short masks[] = { 32, 16,
> 8, 4, 2, 1 };
> drivers/accessibility/speakup/keyhelp.c:26:static u_char funcvals[]
gt;
> > Mh, I'm on latest linux-next (next-20210302) and I've applied patch 3/3
> > and
> > reverted commit 7007b745a508 ("PCI: layerscape: Convert to
> > builtin_platform_driver()"). I'd assumed that PCIe shouldn't be working,
> > right? B
Add a name of the menu and fill control type.
Signed-off-by: Stanimir Varbanov
---
drivers/media/v4l2-core/v4l2-ctrls.c | 8
1 file changed, 8 insertions(+)
diff --git a/drivers/media/v4l2-core/v4l2-ctrls.c
b/drivers/media/v4l2-core/v4l2-ctrls.c
index 016cf6204cbb..5d99e2294335 100644
Some controllers can choose to skip preparation for power up.
In that case, device context is initialized based on the pre_init
flag not being set during mhi_prepare_for_power_up(). There is no
reason MHI host driver should maintain and provide controllers
with two separate paths for preparing MHI.
On Tue, Mar 2, 2021 at 2:24 PM Michael Walle wrote:
>
> Am 2021-03-02 22:11, schrieb Saravana Kannan:
> > I think Patch 1 should fix [4] without [5]. Can you test the series
> > please?
>
> Mh, I'm on latest linux-next (next-20210302) and I've applied
On Tue, Mar 2, 2021 at 2:09 PM Nick Desaulniers wrote:
>
> On Tue, Mar 2, 2021 at 2:02 PM Fangrui Song wrote:
> >
> > On 2021-03-02, Nathan Chancellor wrote:
> > >When building with LLVM_IAS=1, there is no point to specifying
> > >'--prefix=' because that flag is only used to find the cross assem
On Tue, Mar 2, 2021 at 7:14 PM Álvaro Fernández Rojas wrote:
> I'm trying to add support for bcm63xx pin controllers, and Linus
> suggested that I could use gpio regmap instead of adding duplicated code.
> However, I need to access gpio_chip inside gpio_regmap to call
> pinctrl_add_gpio_range() w
As per documentation, fields marked as (required) in an MHI
controller structure need to be populated by the controller driver
before calling mhi_register_controller(). Ensure all required
fields are present in the controller before proceeding with the
registration.
Signed-off-by: Bhaumik Bhatt
-
Fix hyphenation, typos, capitalization, and a referenced file name
(.txt -> .rst).
Signed-off-by: Randy Dunlap
Cc: Dmitry Torokhov
Cc: linux-in...@vger.kernel.org
Cc: Jonathan Corbet
Cc: linux-...@vger.kernel.org
---
Documentation/input/event-codes.rst | 10 +-
1 file changed, 5 inse
Fix grammar, punctuation, and spelling.
Signed-off-by: Randy Dunlap
Cc: Dmitry Torokhov
Cc: linux-in...@vger.kernel.org
Cc: Jonathan Corbet
Cc: linux-...@vger.kernel.org
---
Documentation/input/input.rst |8
1 file changed, 4 insertions(+), 4 deletions(-)
--- linux-next-20210202.
Change other related documentation file names from .txt to .rst
and be more explicit about their paths/locations.
Signed-off-by: Randy Dunlap
Cc: Dmitry Torokhov
Cc: linux-in...@vger.kernel.org
Cc: Jonathan Corbet
Cc: linux-...@vger.kernel.org
Cc: Johann Deneux
Cc: Anssi Hannula
---
where is
Fix a typo (supportinf -> supporting).
Signed-off-by: Randy Dunlap
Cc: Dmitry Torokhov
Cc: linux-in...@vger.kernel.org
Cc: Jonathan Corbet
Cc: linux-...@vger.kernel.org
---
Documentation/input/uinput.rst |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- linux-next-20210202.orig/Doc
Update several Documentation/input/ files for wording, punctutation,
struct info, and file names.
Cc: Dmitry Torokhov
Cc: linux-in...@vger.kernel.org
Cc: Jonathan Corbet
Cc: linux-...@vger.kernel.org
[PATCH 1/8] input: Documentation: corrections for input.rst
[PATCH 2/8] input: Documentation:
On 3/2/21 11:27 AM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.9.259 release.
> There are 134 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 shou
Drop a repeated word.
Fix punctuation of "eg." to "e.g."
Fix punctuation of "ie" to "i.e."
Add hyphentation to non-zero.
Capitalize PM (for Power Management).
Capitalize ID (for Identifier).
Change "," in a run-on sentence to ";".
Signed-off-by: Randy Dunlap
Cc: Dmitry Torokhov
Cc: linux-in...@v
Add 'ledstate' to the keyboard_notifier_param struct info and tell
which header file contains that struct.
Signed-off-by: Randy Dunlap
Cc: Dmitry Torokhov
Cc: linux-in...@vger.kernel.org
Cc: Jonathan Corbet
Cc: linux-...@vger.kernel.org
---
Documentation/input/notifier.rst |3 ++-
1 file c
Use "E.g." instead of "Eg.".
Use correct index for buttons[] array.
Update all of struct gameport's descriptions.
Signed-off-by: Randy Dunlap
Cc: Dmitry Torokhov
Cc: linux-in...@vger.kernel.org
Cc: Jonathan Corbet
Cc: linux-...@vger.kernel.org
---
Documentation/input/gameport-programming.rst |
Correct hyphenation, spelling, and capitalization.
Signed-off-by: Randy Dunlap
Cc: Dmitry Torokhov
Cc: linux-in...@vger.kernel.org
Cc: Jonathan Corbet
Cc: linux-...@vger.kernel.org
Cc: Henrik Rydberg
---
Documentation/input/multi-touch-protocol.rst |8
1 file changed, 4 insertion
On Tue, Mar 2, 2021 at 1:07 PM Nathan Chancellor wrote:
>
> This is not necessary anymore now that we specify '--prefix=', which
> tells clang exactly where to find the GNU cross tools. This has been
> verified with self compiled LLVM 10.0.1 and LLVM 13.0.0 as well as a
> distribution version of L
On Tue, 2 Mar 2021 17:30:58 -0500
Steven Rostedt wrote:
> I just realized that I received this patch twice, and thought it was the
> same patch! Chen was three days ahead of you, so he get's the credit ;-)
>
> https://lore.kernel.org/r/20210222135840.56250-1-chenjun...@huawei.com
I'm applying
Hi Sergei!
On 3/2/21 11:26 PM, Sergei Trofimovich wrote:
> Gave v5.12-rc1 a try today and got a similar boot failure around
> hpsa queue initialization, but my failure is later:
> https://dev.gentoo.org/~slyfox/configs/guppy-dmesg-5.12-rc1
> Maybe I get different error because I flipped on mos
On 3/2/21 3:13 PM, Alex Xu (Hello71) wrote:
> I tried 29be7fc03d ("io_uring: ensure that threads freeze on suspend")
> and it seems to work OK. The system suspends fine and no errors are
> printed to the kernel log.
>
> I am using Gentoo on the machine in question.
>
> I didn't test the other p
On 3/2/21 3:07 PM, Sergei Trofimovich wrote:
> On Tue, 23 Feb 2021 08:08:30 +
> Sergei Trofimovich wrote:
>
>> On Mon, 22 Feb 2021 17:43:58 -0700
>> Jens Axboe wrote:
>>
>>> On 2/22/21 5:41 PM, Jens Axboe wrote:
On 2/22/21 5:34 PM, Jens Axboe wrote:
> On 2/22/21 4:53 PM, Serge
As per documentation, fields marked as (required) in an MHI
controller structure need to be populated by the controller driver
before calling mhi_register_controller(). Ensure all required
fields are present in the controller before proceeding with the
registration.
Signed-off-by: Bhaumik Bhatt
-
On Thu, 25 Feb 2021 16:01:17 +
Will Deacon wrote:
> On Thu, Feb 25, 2021 at 09:44:26AM -0500, Steven Rostedt wrote:
> > This requires an acked-by from one of the ARM64 maintainers.
> >
> > -- Steve
> >
> >
> > On Thu, 25 Feb 2021 22:07:47 +0800
> > Li Huafei wrote:
> >
> > > When cross
onfig
i386defconfig
mips allyesconfig
mips allmodconfig
powerpc allyesconfig
powerpc allmodconfig
powerpc allnoconfig
x86_64 randconfig-a00
On 3/2/21 11:28 AM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.4.102 release.
> There are 337 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 shou
On Thu, 18 Feb 2021 08:42:15 +0300
Arseny Krasnov wrote:
Not sure if this was pulled in yet, but I do have a small issue with this
patch.
> @@ -69,14 +82,19 @@ TRACE_EVENT(virtio_transport_alloc_pkt,
> __entry->type = type;
> __entry->op = op;
> __entry-
Am 2021-03-02 22:11, schrieb Saravana Kannan:
I think Patch 1 should fix [4] without [5]. Can you test the series
please?
Mh, I'm on latest linux-next (next-20210302) and I've applied patch 3/3
and
reverted commit 7007b745a508 ("PCI: layerscape: Convert to
builtin_platform_
Hi all,
After merging the f2fs tree, today's linux-next build (x86_64
allmodconfig) produced this warning:
fs/f2fs/sysfs.c:576:25: warning: 'f2fs_attr_ovp_segments' defined but not used
[-Wunused-variable]
576 | static struct f2fs_attr f2fs_attr_##name = __ATTR(name, 0444,
name##_show, NULL)
On 2/9/21 10:53 PM, Miaohe Lin wrote:
> We could use pages_per_huge_page to get the number of pages per hugepage,
> use get_hstate_idx to calculate hstate index, and use hstate_is_gigantic
> to check if a hstate is gigantic to make code more succinct.
>
> Signed-off-by: Miaohe Lin
These are all
If LLD was built with -DLLD_VENDOR="xyz", ld.lld --version output
will prefix LLD_VENDOR. Since LLD_VENDOR can contain spaces, the
LLD identifier isn't guaranteed to be $2 either.
Adjust the version checker to handle such versions of lld.
Signed-off-by: Bernhard Rosenkränzer
---
scripts/ld-vers
On 02/03/2021 22:38, Michael Kelley wrote:
> STIMER0 interrupts are most naturally modeled as per-cpu IRQs. But
> because x86/x64 doesn't have per-cpu IRQs, the core STIMER0 interrupt
> handling machinery is done in code under arch/x86 and Linux IRQs are
> not used. Adding support for ARM64 means a
Hi all,
After merging the fscache tree, today's linux-next build (x86_64
allmodconfig) produced this warning:
fs/afs/file.c: In function 'afs_req_issue_op':
fs/afs/file.c:291:6: warning: unused variable 'ret' [-Wunused-variable]
291 | int ret;
| ^~~
Introduced by commit
799fbdf9
On 02/03/2021 22:38, Michael Kelley wrote:
> While the driver for the Hyper-V Reference TSC and STIMERs is architecture
> neutral, vDSO is implemented for x86/x64, but not for ARM64. Current code
> calls into utility functions under arch/x86 (and coming, under arch/arm64)
> to handle the differenc
On 02/03/2021 22:38, Michael Kelley wrote:
> While the Hyper-V Reference TSC code is architecture neutral, the
> pv_ops.time.sched_clock() function is implemented for x86/x64, but not
> for ARM64. Current code calls a utility function under arch/x86 (and
> coming, under arch/arm64) to handle the di
I tried 29be7fc03d ("io_uring: ensure that threads freeze on suspend")
and it seems to work OK. The system suspends fine and no errors are
printed to the kernel log.
I am using Gentoo on the machine in question.
I didn't test the other patches you supplied. Let me know if there's
anything you
On Fri, Dec 25, 2020 at 01:25:27AM -0800, Nadav Amit wrote:
> From: Nadav Amit
>
> This patch-set went from v1 to RFCv2, as there is still an ongoing
> discussion regarding the way of solving the recently found races due to
> deferred TLB flushes. These patches are only sent for reference for now
> On Mar 2, 2021, at 2:13 PM, Peter Xu wrote:
>
> On Fri, Dec 25, 2020 at 01:25:27AM -0800, Nadav Amit wrote:
>> From: Nadav Amit
>>
>> This patch-set went from v1 to RFCv2, as there is still an ongoing
>> discussion regarding the way of solving the recently found races due to
>> deferred TLB
On 26 Feb 2021, at 2:18, Alistair Popple wrote:
> Migration is currently implemented as a mode of operation for
> try_to_unmap_one() generally specified by passing the TTU_MIGRATION flag
> or in the case of splitting a huge anonymous page TTU_SPLIT_FREEZE.
>
> However it does not have much in comm
On 3/2/21 11:28 AM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.10.20 release.
> There are 657 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 shou
On Tue, Mar 2, 2021 at 2:02 PM Fangrui Song wrote:
>
> On 2021-03-02, Nathan Chancellor wrote:
> >When building with LLVM_IAS=1, there is no point to specifying
> >'--prefix=' because that flag is only used to find the cross assembler,
> >which is clang itself when building with LLVM_IAS=1. All of
On Tue, 23 Feb 2021 08:08:30 +
Sergei Trofimovich wrote:
> On Mon, 22 Feb 2021 17:43:58 -0700
> Jens Axboe wrote:
>
> > On 2/22/21 5:41 PM, Jens Axboe wrote:
> > > On 2/22/21 5:34 PM, Jens Axboe wrote:
> > >> On 2/22/21 4:53 PM, Sergei Trofimovich wrote:
> > >>> On Mon, 22 Feb 202
As pointed by commit c0a9f4d396c9 ("can: c_can: Reduce register access")
the "driver casts the 16 message objects in stone, which is completely
braindead as contemporary hardware has up to 128 message objects".
The patch prepares the module to extend the number of message objects
beyond the 32 cur
After reading the commit 640916db2bf7 ("can: c_can: Make it SMP safe")
it may sound strange to see the IF_RX interface used by the
can_inval_tx_object function. A comment was added to avoid any
misunderstanding.
Signed-off-by: Dario Binacchi
---
Changes in v4:
- Restore IF_RX interface.
- Add a
The arbitration register is already set up with 32-bit writes in the
other parts of the code except for this point.
Signed-off-by: Dario Binacchi
---
(no changes since v1)
drivers/net/can/c_can/c_can.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/net/can/c_can/
On 2021-03-02, Nathan Chancellor wrote:
When building with LLVM_IAS=1, there is no point to specifying
'--prefix=' because that flag is only used to find the cross assembler,
which is clang itself when building with LLVM_IAS=1. All of the other
tools are invoked directly from PATH or a full path
Commit 9d23a9818cb1 ("can: c_can: Remove unused inline function") left
behind C_CAN_MSG_OBJ_TX_LAST constant.
Commit fa39b54ccf28 ("can: c_can: Get rid of pointless interrupts") left
behind C_CAN_MSG_RX_LOW_LAST and C_CAN_MSG_OBJ_RX_SPLIT constants.
The removed code also made a comment useless an
Commit 524369e2391f ("can: c_can: remove obsolete STRICT_FRAME_ORDERING Kconfig
option")
left behind wrong indentation, fix it.
Signed-off-by: Dario Binacchi
---
(no changes since v1)
drivers/net/can/c_can/c_can.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net
The D_CAN controller supports up to 128 messages. Until now the driver
only managed 32 messages although Sitara processors and DRA7 SOC can
handle 64.
The series was tested on a beaglebone board.
Note:
I have not changed the type of tx_field (belonging to the c_can_priv
structure) to atomic64_t
D_CAN controller supports 16, 32, 64 or 128 message objects, comparing
to 32 on C_CAN.
AM335x/AM437x Sitara processors and DRA7 SOC all instantiate a D_CAN
controller with 64 message objects, as described in the "DCAN features"
subsection of the CAN chapter of their technical reference manuals.
Th
On 3/1/21 2:47 AM, Miaohe Lin wrote:
> vma_resv_map(vma) checks if a reserve map is associated with the vma. The
> routine vma_needs_reservation() will check vma_resv_map(vma) and return 1
> if no reserv map is present. map_chg is set to the return value of
> vma_needs_reservation(). Therefore,
As recommended by Stephen Boyd, convert the Agilex/Stratix10/n5x clock
driver to use the clk_hw registration method.
Suggested-by: Stephen Boyd
Signed-off-by: Dinh Nguyen
---
drivers/clk/socfpga/clk-agilex.c | 114 ++-
drivers/clk/socfpga/clk-gate-s10.c | 15 ++--
Reviewed-by: Fangrui Song
Thanks for the clean-up!
--gcc-toolchain= is an obsscure way searching for GCC installation prefixes
(--prefix).
The logic is complex and different for different distributions/architectures.
If we specify --prefix= (-B) explicitly, --gcc-toolchain is not needed.
On 2
The definition of enum hv_message_type includes arch neutral and
x86/x64-specific values. Ideally there would be a way to put the
arch neutral values in an arch neutral module, and the arch
specific values in an arch specific module. But C doesn't provide
a way to extend enum types. As a compromise
Current code defines a separate get and set macro for each Hyper-V
synthetic MSR used by the VMbus driver. Furthermore, the get macro
can't be converted to a standard function because the second argument
is modified in place, which is somewhat bad form.
Redo this by providing a single get and a si
While the Hyper-V Reference TSC code is architecture neutral, the
pv_ops.time.sched_clock() function is implemented for x86/x64, but not
for ARM64. Current code calls a utility function under arch/x86 (and
coming, under arch/arm64) to handle the difference.
Change this approach to handle the diffe
On Tue, 2 Mar 2021, Joe Perches wrote:
> Here is a possible opportunity to reduce data usage in the kernel.
Does it actually reduce data usage?
julia
>
> $ git grep -P -n '^static\s+(?!const|struct)(?:\w+\s+){1,3}\w+\s*\[\s*\]'
> drivers/ | \
> grep -v __initdata | \
> wc -l
> 3250
>
>
As recommended by Stephen Boyd, convert the cyclone5/arria5 clock driver
to use the clk_hw registration method.
Suggested-by: Stephen Boyd
Signed-off-by: Dinh Nguyen
---
drivers/clk/socfpga/clk-gate.c | 11 +++
drivers/clk/socfpga/clk-periph.c | 8
drivers/clk/socfpga/clk-pl
As recommended by Stephen Boyd, convert the Arria10 clock driver to use
the clk_hw registration method.
Suggested-by: Stephen Boyd
Signed-off-by: Dinh Nguyen
---
drivers/clk/socfpga/clk-gate-a10.c | 8
drivers/clk/socfpga/clk-periph-a10.c | 11 ++-
drivers/clk/socfpga/clk-pl
On x86/x64, the TSC clocksource is available in a Hyper-V VM only if
Hyper-V provides the TSC_INVARIANT flag. The rating on the Hyper-V
Reference TSC page clocksource is currently set so that it will not
override the TSC clocksource in this case. Alternatively, if the TSC
clocksource is not availa
STIMER0 interrupts are most naturally modeled as per-cpu IRQs. But
because x86/x64 doesn't have per-cpu IRQs, the core STIMER0 interrupt
handling machinery is done in code under arch/x86 and Linux IRQs are
not used. Adding support for ARM64 means adding equivalent code
using per-cpu IRQs under arch
With the new Hyper-V MSR set function, hyperv_report_panic_msg() can be
architecture neutral, so move it out from under arch/x86 and merge into
hv_kmsg_dump(). This move also avoids needing a separate implementation
under arch/arm64.
No functional change.
Signed-off-by: Michael Kelley
Reviewed-b
The Hyper-V page allocator functions are implemented in an architecture
neutral way. Move them into the architecture neutral VMbus module so
a separate implementation for ARM64 is not needed.
No functional change.
Signed-off-by: Michael Kelley
Reviewed-by: Boqun Feng
---
arch/x86/hyperv/hv_in
While the driver for the Hyper-V Reference TSC and STIMERs is architecture
neutral, vDSO is implemented for x86/x64, but not for ARM64. Current code
calls into utility functions under arch/x86 (and coming, under arch/arm64)
to handle the difference.
Change this approach to handle the difference i
On x86/x64, Hyper-V provides a flag to indicate auto EOI functionality,
but it doesn't on ARM64. Handle this quirk inline instead of calling
into code under arch/x86 (and coming, under arch/arm64).
No functional change.
Signed-off-by: Michael Kelley
Reviewed-by: Boqun Feng
---
arch/x86/include
VMbus interrupts are most naturally modelled as per-cpu IRQs. But
because x86/x64 doesn't have per-cpu IRQs, the core VMbus interrupt
handling machinery is done in code under arch/x86 and Linux IRQs are
not used. Adding support for ARM64 means adding equivalent code
using per-cpu IRQs under arch/
To support Linux guests on Hyper-V on multiple architectures, the original
approach factored out all differences between Hyper-V on x86/x64 and
Hyper-V on ARM64 into functions or #defines under arch/x86 and
arch/arm64. Some of these differences are truly related to the
architecture, but others are
Hi!
> This is the start of the stable review cycle for the 5.10.20 release.
> There are 657 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.
CIP testing did not find any problems here (failures are ca
Hi!
> This is the start of the stable review cycle for the 4.4.259 release.
> There are 92 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.
CIP testing did not find any problems here:
https://gitlab.
Hi!
> This is the start of the stable review cycle for the 4.19.178 release.
> There are 246 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.
CIP testing did not find any problems here:
https://gitla
On Mar 02 Dan Carpenter wrote:
> In TCODE_STREAM_DATA mode, on 32bit systems, the "sizeof(*e) +
> request->length" operation can overflow leading to memory corruption.
>
> Fixes: 18e9b10fcdc0 ("firewire: cdev: add closure to async stream ioctl")
> Signed-off-by: Dan Carpenter
> ---
> drivers/fir
On 3/2/21 6:29 AM, Michal Hocko wrote:
> On Tue 02-03-21 06:11:51, Shakeel Butt wrote:
>> On Tue, Mar 2, 2021 at 1:44 AM Michal Hocko wrote:
>>>
>>> On Mon 01-03-21 17:16:29, Mike Kravetz wrote:
On 3/1/21 9:23 AM, Michal Hocko wrote:
> On Mon 01-03-21 08:39:22, Shakeel Butt wrote:
>>
Device link status was not getting updated correctly when
device_bind_driver() is called on a device. This causes a warning[1].
Fix this by updating device links that can be updated and dropping
device links that can't be updated to a sensible state.
[1] -
https://lore.kernel.org/lkml/56f7d032-ba
There's no point in adding a device to the deferred probe list if we
know for sure that it doesn't have a matching driver. So, check if a
device can match with a driver before adding it to the deferred probe
list.
Signed-off-by: Saravana Kannan
---
drivers/base/dd.c | 6 ++
include/linu
This reverts commit 3e4c982f1ce75faf5314477b8da296d2d00919df.
Since all reported issues due to fw_devlink=on should be addressed by
this series, revert the revert. fw_devlink=on Take II.
Signed-off-by: Saravana Kannan
---
drivers/base/core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
On Tue, Mar 02, 2021 at 07:46:27PM +0100, Björn Töpel wrote:
> Hi!
>
> Firstly; The long Cc-list is to reach the LKMM-folks.
>
> Some background; the XDP sockets use a ring-buffer to communicate
> between the kernel and userland. It's a
> single-consumer/single-producer ring, and described in
> n
LRU pagevec holds refcount of pages until the pagevec are drained.
It could prevent migration since the refcount of the page is greater
than the expection in migration logic. To mitigate the issue,
callers of migrate_pages drains LRU pagevec via migrate_prep or
lru_add_drain_all before migrate_page
The only usage of lm3533_attribute_group is to pass its address to
sysfs_create_group() and sysfs_remove_group(), both which takes pointers
to const attribute_group structs. Make it const to allow the compiler to
put it in read-only memory.
Done with the help of coccinelle.
Signed-off-by: Rikard
The only usage of pcf_attr_group is to pass its address to
sysfs_create_group() and sysfs_remove_group(), both which takes pointers
to const attribute_group structs. Make it const to allow the compiler to
put it in read-only memory.
Done with the help of coccinelle.
Signed-off-by: Rikard Falkebor
Seems the first submission somehow didn't make it to LKML, here's a
resend.
The only usage of the structs is to pass their address to
sysfs_create_group() and sysfs_remove_group(), both which takes pointers
to const attribute_group structs. Make them const to allow the compiler
to put them in read
This series fixes the last few remaining issues reported when fw_devlink=on
by default.
Patch 1 is just [6] pulled in without changes into this series. It reduces
some unnecessary probe reordering caused by a combination of fw_devlink and
existing device link code. This fixes some issue caused by
Pages containing buffer_heads that are in one of the per-CPU
buffer_head LRU caches will be pinned and thus cannot be migrated.
This can prevent CMA allocations from succeeding, which are often used
on platforms with co-processors (such as a DSP) that can only use
physically contiguous memory. It c
randconfig-a006-20210302
x86_64 randconfig-a001-20210302
x86_64 randconfig-a004-20210302
x86_64 randconfig-a002-20210302
x86_64 randconfig-a005-20210302
x86_64 randconfig-a003-20210302
i386 randconfig
> On Mar 2, 2021, at 12:24 PM, Alexei Starovoitov
> wrote:
>
> On Tue, Mar 2, 2021 at 10:38 AM Andy Lutomirski wrote:
>>
>> Is there something like a uprobe test suite? How maintained /
>> actively used is uprobe?
>
> uprobe+bpf is heavily used in production.
> selftests/bpf has only one
The only usage of attr_group is to pass its address to
sysfs_create_group() and sysfs_remove_group(), both which takes pointers
to const attribute_group structs. Make it const to allow the compiler to
put it in read-only memory.
Done with the help of coccinelle.
Signed-off-by: Rikard Falkeborn
-
This is not necessary anymore now that we specify '--prefix=', which
tells clang exactly where to find the GNU cross tools. This has been
verified with self compiled LLVM 10.0.1 and LLVM 13.0.0 as well as a
distribution version of LLVM 11.1.0 without binutils in the LLVM
toolchain locations.
Signe
When building with LLVM_IAS=1, there is no point to specifying
'--prefix=' because that flag is only used to find the cross assembler,
which is clang itself when building with LLVM_IAS=1. All of the other
tools are invoked directly from PATH or a full path specified via the
command line, which does
From: Clement Courbet
A significant portion of __calc_delta time is spent in the loop
shifting a u64 by 32 bits. Use `fls` instead of iterating.
This is ~7x faster on benchmarks.
The generic `fls` implementation (`generic_fls`) is still ~4x faster
than the loop.
Architectures that have a better
On Tue, Mar 02, 2021 at 03:56:16PM +0200, Andy Shevchenko wrote:
> The structures are used as place holders, so they are modified at run-time.
> Obviously they may not be constants.
>
> BUG: unable to handle page fault for address: d0643220
> ...
> CPU: 0 PID: 110 Comm: modprobe Not tainted
Michal Suchanek [msucha...@suse.de] wrote:
> GCC 7.5 reports:
> ../drivers/net/ethernet/ibm/ibmvnic.c: In function 'ibmvnic_reset_init':
> ../drivers/net/ethernet/ibm/ibmvnic.c:5373:51: warning: 'old_num_tx_queues'
> may be used uninitialized in this function [-Wmaybe-uninitialized]
> ../drivers/n
On Fri, Feb 26, 2021 at 1:03 PM Peter Zijlstra wrote:
>
> On Fri, Feb 26, 2021 at 11:52:39AM -0800, Josh Don wrote:
> > From: Clement Courbet
> >
> > A significant portion of __calc_delta time is spent in the loop
> > shifting a u64 by 32 bits. Use a __builtin_clz instead of iterating.
> >
> > Th
Simply print the type of the control.
Signed-off-by: Ezequiel Garcia
---
drivers/media/v4l2-core/v4l2-ctrls.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/media/v4l2-core/v4l2-ctrls.c
b/drivers/media/v4l2-core/v4l2-ctrls.c
index 1a683f4fa978..0fc7180a47e9 100644
--- a/drivers/
Hi!
> This driver adds initial support for several devices from Siemens. It is
> based on a platform driver introduced in an earlier commit.
Ok.
> diff --git a/drivers/leds/Makefile b/drivers/leds/Makefile
> index 2a698df9da57..c15e1e3c5958 100644
> --- a/drivers/leds/Makefile
> +++ b/drivers/le
Until now, the VP8 V4L2 API was not exported as a public API,
and only defined in a private media header (media/vp8-ctrls.h).
The reason for this was a concern about the API not complete
and ready to support VP8 decoding hardware accelerators.
After reviewing the VP8 specification in detail, and
In preparation for making the interface public,
document all the structures.
Signed-off-by: Ezequiel Garcia
---
include/media/vp8-ctrls.h | 99 +++
1 file changed, 99 insertions(+)
diff --git a/include/media/vp8-ctrls.h b/include/media/vp8-ctrls.h
index f2011
Rename to struct v4l2_vp8_loop_filter, which is closer to the
VP8 syntax. This change is only cosmetics, but since this API
is exposed to userspace, it's worth the trouble to get it consistent.
Signed-off-by: Ezequiel Garcia
---
.../userspace-api/media/v4l/ext-ctrls-codec.rst | 12 ++---
Move the VP8 stateless control types out of staging,
and re-number it to avoid any confusion.
Signed-off-by: Ezequiel Garcia
---
include/media/vp8-ctrls.h | 1 -
include/uapi/linux/videodev2.h | 2 ++
2 files changed, 2 insertions(+), 1 deletion(-)
diff --git a/include/media/vp8-ctrls.h b/
1 - 100 of 1506 matches
Mail list logo
