On Thu, 15 Apr 2021 16:47:54 +0200, Greg Kroah-Hartman
wrote:
> This is the start of the stable review cycle for the 5.10.31 release.
> There are 25 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 Fri, Apr 16, 2021 at 10:35 AM Vivek Goyal wrote:
>
> I am seeing missed wakeups which ultimately lead to a deadlock when I am
> using virtiofs with DAX enabled and running "make -j". I had to mount
> virtiofs as rootfs and also reduce to dax window size to 32M to reproduce
> the problem
On 4/14/21 4:39 PM, Maciej W. Rozycki wrote:
> Existing `blogic_msg' invocations do not appear to overrun its internal
> buffer of a fixed length of 100, which would cause stack corruption, but
> it's easy to miss with possible further updates and a fix is cheap in
> performance terms, so limit
On Fri, Apr 16, 2021 at 02:12:36PM -0500, Gustavo A. R. Silva wrote:
> Fix the following out-of-bounds warning:
>
> net/sctp/sm_make_chunk.c:3150:4: warning: 'memcpy' offset [17, 28] from the
> object at 'addr' is out of the bounds of referenced subobject 'v4' with type
> 'struct sockaddr_in'
On 4/16/2021 12:45 PM, Peter Zijlstra wrote:
On Fri, Apr 16, 2021 at 03:01:48PM -, tip-bot2 for Kan Liang wrote:
@@ -2331,6 +2367,9 @@ static void x86_pmu_event_unmapped(struct perf_event
*event, struct mm_struct *m
if (!(event->hw.flags & PERF_X86_EVENT_RDPMC_ALLOWED))
Resumes the actual scsi device the unit descriptor of which
is being accessed instead of the hba alone.
Reviewed-by: Adrian Hunter
Reviewed-by: Can Guo
Signed-off-by: Asutosh Das
---
drivers/scsi/ufs/ufs-sysfs.c | 24
1 file changed, 12 insertions(+), 12 deletions(-)
During runtime-suspend of ufs host, the scsi devices are
already suspended and so are the queues associated with them.
But the ufs host sends SSU (START_STOP_UNIT) to wlun
during its runtime-suspend.
During the process blk_queue_enter checks if the queue is not in
suspended state. If so, it waits
The VirtIO TC has adopted a new feature in virtio-blk enabling
discovery of lifetime information.
This commit adds support for the VIRTIO_BLK_T_LIFETIME command
to the virtio_blk driver, and adds two new attributes to the
sysfs entry for virtio_blk:
* pre_eol_info
* life_time
which are defined
On Tue, Apr 13, 2021 at 10:52:13PM -0700, Andrei Vagin wrote:
> We already have process_vm_readv and process_vm_writev to read and write
> to a process memory faster than we can do this with ptrace. And now it
> is time for process_vm_exec that allows executing code in an address
> space of
On 17/04/21 12:39 am, Roman Gushchin wrote:
On Sat, Apr 17, 2021 at 12:11:37AM +0530, Pratik Sampat wrote:
On 17/04/21 12:04 am, Roman Gushchin wrote:
On Fri, Apr 16, 2021 at 11:57:03PM +0530, Pratik Sampat wrote:
On 16/04/21 10:43 pm, Roman Gushchin wrote:
On Fri, Apr 16, 2021 at
On Fri, Apr 16, 2021 at 12:24:13PM -0700, Eric Dumazet wrote:
> From: Eric Dumazet
>
> We have to loop only to copy u64 values.
> After this first loop, we copy at most one u32, one u16 and one byte.
Does it actually yield a better code?
FWIW, this
void bar(unsigned);
void foo(unsigned n)
{
'mod' is not used when !CONFIG_MODULES. Mark as __maybe_unused to
fix the following warning:
kernel/static_call.c: In function ‘__static_call_update’:
kernel/static_call.c:153:18: warning: unused variable ‘mod’ [-Wunused-variable]
153 | struct module *mod = site_mod->mod;
|
On 4/16/21 1:55 PM, Mark Brown wrote:
On Fri, Apr 16, 2021 at 11:47:01AM -0500, Pierre-Louis Bossart wrote:
On 4/16/21 11:31 AM, Mark Brown wrote:
Not really written down that I can think of. I think the next steps
that I can think of right now are unfortunately bigger and harder ones,
On 4/14/21 4:38 PM, Maciej W. Rozycki wrote:
> Hi,
>
> First of all, does anyone have a copy of: "MultiMaster UltraSCSI Host
> Adapters for PCI Systems: Technical Reference Manual" (pub. 3002493-E)?
> It used to live in the "Mylex Manuals and Documentation Archives" section
> of the Mylex
On Mon, Mar 01, 2021 at 12:51:45PM +0530, chakravarthikulkarni wrote:
> In this commit fixed coding style for braces and comments.
>
> Signed-off-by: chakravarthikulkarni
Applied to pci/hotplug for v5.13, thanks!
I dropped the comment change because it's really one comment that
should remain
On Fri, Apr 09, 2021 at 02:01:57PM +0300, Dan Carpenter wrote:
> We can't use kfree() to free device managed resources so the kfree(dev)
> is against the rules.
>
> It's easier to write this code if we open code the device_register() as
> a device_initialize() and device_add(). That way if
On 4/14/21 4:39 PM, Maciej W. Rozycki wrote:
> Update BusLogic driver's messaging system to use `pr_cont' for
> continuation lines, bringing messy output:
>
> pci :00:13.0: PCI->APIC IRQ transform: INT A -> IRQ 17
> scsi: * BusLogic SCSI Driver Version 2.1.17 of 12 September 2013 *
>
On 4/15/21 2:25 PM, Shuah Khan wrote:
On 4/15/21 8:07 AM, Igor Matheus Andrade Torrente wrote:
Fixes a race condition - for lack of a more precise term - between
em28xx_v4l2_open and em28xx_v4l2_init, by detaching the v4l2_dev,
media_pad and vdev structs from the em28xx_v4l2, and managing
Fix the following out-of-bounds warning:
net/core/flow_dissector.c:835:3: warning: 'memcpy' offset [33, 48] from the
object at 'flow_keys' is out of the bounds of referenced subobject 'ipv6_src'
with type '__u32[4]' {aka 'unsigned int[4]'} at offset 16 [-Warray-bounds]
The problem is that the
- On Apr 16, 2021, at 3:02 PM, paulmck paul...@kernel.org wrote:
[...]
>
> If it can be done reasonably, I suggest also having some way for the
> person building userspace RCU to say "I know what I am doing, so do
> it with volatile rather than memory_order_consume."
Like so ?
#define
Hi Rob,
Am 2021-04-16 20:44, schrieb Rob Herring:
On Fri, Apr 16, 2021 at 01:49:23PM +0200, Michael Walle wrote:
The goal is to fetch a (base) MAC address from the OTP region of a SPI
NOR
flash.
This is the first part, where I try to add the nvmem provider support
to
the MTD core.
I'm not
From: Eric Dumazet
We have to loop only to copy u64 values.
After this first loop, we copy at most one u32, one u16 and one byte.
Signed-off-by: Eric Dumazet
---
arch/x86/include/asm/uaccess.h | 14 +++---
1 file changed, 11 insertions(+), 3 deletions(-)
diff --git
On Tue, Apr 13, 2021 at 10:53:05AM +0100, Lorenzo Pieralisi wrote:
> On Wed, Mar 24, 2021 at 10:09:42AM +0100, Pali Rohár wrote:
> > On Wednesday 24 March 2021 11:05:05 Jianjun Wang wrote:
> > > This interface will be used by PCI host drivers for PIO translation,
> > > export it to support
On Sun, Apr 11, 2021 at 11:27 PM Michal Suchánek wrote:
>
> Yes, I do have the rust support.
I applied your patch in rust-next and it is in the latest linux-next,
let me know if that helped.
Masahiro, if you want to apply it on your side, just let me know!
Cheers,
Miguel
On Wed, Mar 24, 2021 at 11:05:03AM +0800, Jianjun Wang wrote:
> These series patches add pcie-mediatek-gen3.c and dt-bindings file to
> support new generation PCIe controller.
Incidental: b4 doesn't work on this thread, I suspect because the
usual subject line format is:
[PATCH v9 9/7]
Hi,
On 16/04/2021 12:20:30-0500, Rob Herring wrote:
> On Wed, Apr 14, 2021 at 3:38 AM Lee Jones wrote:
> >
> > On Fri, 09 Apr 2021, satya priya wrote:
> >
> > > Convert pm8xxx bindings from .txt to .yaml format. Also,
> > > split this binding into two: parent binding(qcom-pm8xxx.yaml)
> > > and
On Thu, 15 Apr 2021 19:59:53 -0500, Nishanth Menon wrote:
> Convert the ti,secure-proxy to yaml for better checks and documentation.
> Differences being mostly in the examples:
> - Dropped the example usage of mailbox client, it is better done in
> tisci node definition.
> - Switched reg usage
Fix the following out-of-bounds warning:
net/sctp/sm_make_chunk.c:3150:4: warning: 'memcpy' offset [17, 28] from the
object at 'addr' is out of the bounds of referenced subobject 'v4' with type
'struct sockaddr_in' at offset 0 [-Warray-bounds]
This helps with the ongoing efforts to globally
On Fri, Apr 16, 2021 at 03:35:36PM +0200, Thomas Bogendoerfer wrote:
> On Fri, Apr 16, 2021 at 12:29:46PM +0300, Sergei Shtylyov wrote:
> > On 16.04.2021 11:52, Thomas Bogendoerfer wrote:
> >
> > > Add device tree bindings for ethernet controller integrated into
> > > IDT 79RC3243x SoCs.
> > >
>
On Sat, Apr 17, 2021 at 12:11:37AM +0530, Pratik Sampat wrote:
>
>
> On 17/04/21 12:04 am, Roman Gushchin wrote:
> > On Fri, Apr 16, 2021 at 11:57:03PM +0530, Pratik Sampat wrote:
> > >
> > > On 16/04/21 10:43 pm, Roman Gushchin wrote:
> > > > On Fri, Apr 16, 2021 at 08:58:33PM +0530, Pratik
On Fri, Apr 16, 2021 at 10:52:06AM +0200, Thomas Bogendoerfer wrote:
> Add device tree bindings for ethernet controller integrated into
> IDT 79RC3243x SoCs.
>
> Signed-off-by: Thomas Bogendoerfer
> ---
> .../bindings/net/idt,3243x-emac.yaml | 74 +++
> 1 file changed,
On Fri, 16 Apr 2021 at 20:16, Jian Cai wrote:
>
> LLVM's integrated assembler does not support using commas separating
> the name and arguments in .macro. However, only spaces are used in the
> manual page. This replaces commas between macro names and the subsequent
> arguments with space in
The following commit has been merged into the timers/core branch of tip:
Commit-ID: 9c336c9935cff267470bb3aaa85c66fac194b650
Gitweb:
https://git.kernel.org/tip/9c336c9935cff267470bb3aaa85c66fac194b650
Author:Jindong Yue
AuthorDate:Wed, 31 Mar 2021 16:33:18 +08:00
The following commit has been merged into the timers/core branch of tip:
Commit-ID: d7840aaadd6e84915866a8f0dab586f6107dadf1
Gitweb:
https://git.kernel.org/tip/d7840aaadd6e84915866a8f0dab586f6107dadf1
Author:Wang Wensheng
AuthorDate:Fri, 26 Mar 2021 02:23:28
Committer:
The following commit has been merged into the timers/core branch of tip:
Commit-ID: 07ff4aed015c564d03fd518d2fb54e5e6948903c
Gitweb:
https://git.kernel.org/tip/07ff4aed015c564d03fd518d2fb54e5e6948903c
Author:Marc Kleine-Budde
AuthorDate:Wed, 03 Mar 2021 11:35:44 +01:00
On Thu, 15 Apr 2021 21:45:00 +0300, Eugen Hristev wrote:
> Add bindings for the Microchip eXtended Image Sensor Controller.
> Based on the atmel,isc.yaml binding.
>
> Signed-off-by: Eugen Hristev
> ---
> Changes in v5:
> - fixed license clause to add BSD-2
> Changes in v4:
> - added '|' at
On Fri, Apr 16, 2021 at 07:15:37PM +0530, Vidya Sagar wrote:
> The PCIe controller in Tegra194 SoC is not completely ECAM-compliant.
> With the current hardware design limitations in place, ECAM can be enabled
> only for one controller (C5 controller to be precise) with bus numbers
> starting from
On Fri, Apr 16, 2021 at 10:03:40AM +0200, Johan Jonker wrote:
> From: Enric Balletbo i Serra
>
> Convert the soc/rockchip/power_domain.txt binding document to
> json-schema and move to the power bindings directory.
>
> Signed-off-by: Enric Balletbo i Serra
> Signed-off-by: Elaine Zhang
>
On Fri, Apr 16, 2021 at 02:40:08PM -0400, Mathieu Desnoyers wrote:
> - On Apr 16, 2021, at 12:01 PM, paulmck paul...@kernel.org wrote:
>
> > On Fri, Apr 16, 2021 at 05:17:11PM +0200, Peter Zijlstra wrote:
> >> On Fri, Apr 16, 2021 at 10:52:16AM -0400, Mathieu Desnoyers wrote:
> >> > Hi Paul,
On Fri, Apr 16, 2021 at 8:10 PM Al Viro wrote:
>
> How well would ? operator fit that pattern? _If_ it's just a syntax sugar
> along the lines of "if argument matches Err(_), return Err(_)", the types
> shouldn't be an issue, but that might need some fun with releasing resources,
> etc. If it's
On 4/15/21 1:39 AM, Muchun Song wrote:
> For HugeTLB page, there are more metadata to save in the struct page.
> But the head struct page cannot meet our needs, so we have to abuse
> other tail struct page to store the metadata. In order to avoid
> conflicts caused by subsequent use of more tail
On Fri, Apr 16, 2021 at 11:47:01AM -0500, Pierre-Louis Bossart wrote:
> On 4/16/21 11:31 AM, Mark Brown wrote:
> > Not really written down that I can think of. I think the next steps
> > that I can think of right now are unfortunately bigger and harder ones,
> > mainly working out a way to
On Fri, 16 Apr 2021 10:03:38 +0200, Johan Jonker wrote:
> Current dts files with 'pmu' nodes are manually verified.
> In order to automate this process pmu.txt
> has to be converted to yaml.
>
> Signed-off-by: Johan Jonker
> ---
> .../devicetree/bindings/arm/rockchip/pmu.txt | 16 ---
On Fri, 16 Apr 2021 10:03:39 +0200, Johan Jonker wrote:
> The compatible strings below are already in use in the Rockchip
> dtsi files, but were somehow never added to a document, so add
>
> "rockchip,px30-pmu", "syscon", "simple-mfd"
> "rockchip,rk3288-pmu", "syscon", "simple-mfd"
>
On 4/16/21 4:36 AM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20210415:
>
I noticed this build error message (on an i386 build):
../certs/Makefile:52: *** Could not determine digest type to use from kernel
config. Stop.
and when I was checking on why it happened, I noticed that
#
On Fri, 16 Apr 2021 10:03:41 +0200, Johan Jonker wrote:
> From: Elaine Zhang
>
> Add the compatible string for RK3568 SoC.
>
> Signed-off-by: Elaine Zhang
> Signed-off-by: Johan Jonker
> ---
> A note for rob+dt and others:
> A review and ack tag was not added, because in this version
>
B range
> and just take care of leaving enough space for BPF.
>
> In addition, by moving the kernel to the end of the address space, both
> sv39 and sv48 kernels will be exactly the same without needing to be
> relocated at runtime.
>
> Suggested-by: Arnd Bergmann
>
Hi Faiyaz,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on linus/master]
[also build test WARNING on v5.12-rc7]
[cannot apply to hnaz-linux-mm/master next-20210416]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting
Set the BHI and BHIe pointers to NULL as part of clean-up. This
makes sure that stale pointers are not accessed after powering
MHI down.
Suggested-by: Hemant Kumar
Signed-off-by: Bhaumik Bhatt
---
drivers/bus/mhi/core/init.c | 3 +++
1 file changed, 3 insertions(+)
diff --git
MHI driver requires register space length to add range checks and
prevent memory region accesses outside of that for MMIO space.
Set it before registering the MHI controller.
Signed-off-by: Bhaumik Bhatt
---
drivers/net/wireless/ath/ath11k/mhi.c | 1 +
1 file changed, 1 insertion(+)
diff --git
MHI driver requires register space length to add range checks and
prevent memory region accesses outside of that for MMIO space.
Set it from the PCI generic controller driver before registering
the MHI controller.
Signed-off-by: Bhaumik Bhatt
---
drivers/bus/mhi/pci_generic.c | 1 +
1 file
When obtaining the BHI or BHIe offsets during the power up
preparation phase, range checks are missing. These can help
controller drivers avoid accessing any address outside of the
MMIO region. Ensure that mhi_cntrl->reg_len is set before MHI
registration as it is a required field and range checks
Set the BHI and/or BHIe offsets in mhi_prepare_for_power_up(),
rearrange the function, and remove the equivalent from
mhi_async_power_up(). This helps consolidate multiple checks
in different parts of the driver and can help MHI fail early on
before power up begins if the offsets are not read
Make controller driver specify the MMIO register region length
for range checking of BHI or BHIe space. This can help validate
that offsets are in acceptable memory region or not and avoid any
boot-up issues due to BHI or BHIe memory accesses.
Signed-off-by: Bhaumik Bhatt
---
This patch series improves the power up behavior by allowing MHI host driver to
set BHI and/or BHIe offsets early on in the preparation phase and fail pre-power
up if offsets are not found or not within a limited MMIO region. This also
allows MHI host to clean up the offsets in the unprepare after
On Thu, Apr 15, 2021 at 11:04:37PM -0700, Nick Desaulniers wrote:
> On Thu, Apr 15, 2021 at 9:27 PM Boqun Feng wrote:
> >
> > [Copy LKMM people, Josh, Nick and Wedson]
> >
> > On Thu, Apr 15, 2021 at 08:58:16PM +0200, Peter Zijlstra wrote:
> > > On Wed, Apr 14, 2021 at 08:45:51PM +0200,
On 4/1/21 5:13 PM, Tyrel Datwyler wrote:
> Currently, neither the vio_bus or vio_driver structures provide support
> for a shutdown() routine.
>
> Add support for shutdown() by allowing drivers to provide a
> implementation via function pointer in their vio_driver struct and
> provide a proper
On Fri, Apr 16, 2021 at 01:30:01PM -0500, Rob Herring wrote:
> On Fri, 16 Apr 2021 13:49:26 +0200, Michael Walle wrote:
> > Flash devices can have one-time-programmable regions. Add a nvmem
> > binding so they can be used as a nvmem provider.
> >
> > Signed-off-by: Michael Walle
> > ---
> >
> From: Stephen Hemminger
> Sent: Friday, April 16, 2021 11:09 AM
> ...
> On Fri, 16 Apr 2021 17:58:45 +
> Dexuan Cui wrote:
>
> > > >
> > > > This probably should be a separate patch.
> > > > I think it is trying to address the case of VF discovery in
> > > > Hyper-V/Azure
> where
> > >
On Fri, Apr 16, 2021 at 01:49:23PM +0200, Michael Walle wrote:
> The goal is to fetch a (base) MAC address from the OTP region of a SPI NOR
> flash.
>
> This is the first part, where I try to add the nvmem provider support to
> the MTD core.
>
> I'm not sure about the device tree bindings.
On 17/04/21 12:04 am, Roman Gushchin wrote:
On Fri, Apr 16, 2021 at 11:57:03PM +0530, Pratik Sampat wrote:
On 16/04/21 10:43 pm, Roman Gushchin wrote:
On Fri, Apr 16, 2021 at 08:58:33PM +0530, Pratik Sampat wrote:
Hello Dennis,
I apologize for the clutter of logs before, I'm pasting the
- On Apr 16, 2021, at 12:01 PM, paulmck paul...@kernel.org wrote:
> On Fri, Apr 16, 2021 at 05:17:11PM +0200, Peter Zijlstra wrote:
>> On Fri, Apr 16, 2021 at 10:52:16AM -0400, Mathieu Desnoyers wrote:
>> > Hi Paul, Will, Peter,
>> >
>> > I noticed in this discussion
On Fri, Apr 16, 2021 at 11:57:03PM +0530, Pratik Sampat wrote:
>
>
> On 16/04/21 10:43 pm, Roman Gushchin wrote:
> > On Fri, Apr 16, 2021 at 08:58:33PM +0530, Pratik Sampat wrote:
> > > Hello Dennis,
> > >
> > > I apologize for the clutter of logs before, I'm pasting the logs of
> > > before
Hi Tudor,
Tudor Ambarus wrote on Sat, 3 Apr 2021
09:09:31 +0300:
> The write buffer comes from user and should be const.
> Constify write buffer in mtd core and across all _write_user_prot_reg()
> users. cfi_cmdset_{0001, 0002} and onenand_base will pay the cost of an
> explicit cast to discard
On Fri, Apr 16, 2021 at 2:53 PM Takashi Iwai wrote:
>
> Currently the DRM fbcon helper for console blank,
> drm_fb_helper_blank(), simply calls drm_fb_helper_dpms() and always
> returns zero, supposing the driver dealing with DPMS or atomic
> crtc->active flip to handle blanking the screen. It
On Fri, 16 Apr 2021 13:49:27 +0200, Michael Walle wrote:
> SPI-NOR flashes may have OTP regions and have a nvmem binding. This
> binding is described in mtd.yaml.
>
> Signed-off-by: Michael Walle
> ---
> Changes since RFC:
> - new patch
>
>
On Fri, 16 Apr 2021 13:49:26 +0200, Michael Walle wrote:
> Flash devices can have one-time-programmable regions. Add a nvmem
> binding so they can be used as a nvmem provider.
>
> Signed-off-by: Michael Walle
> ---
> Changes since RFC:
> - added missing "$"
> - dropped first example
> - use
The Chrome Embedded Controller (EC) generates a hard reset type C event
when a USB Power Delivery (PD) hard reset is encountered. Handle this
event by unregistering the partner and cable on the associated port and
clearing the event flag.
Cc: Benson Leung
Signed-off-by: Prashant Malani
---
On Wed, Apr 14, 2021 at 4:45 PM Srinivas Neeli wrote:
>
> HI baratosz and Andy,
>
It's Bartosz. You literally just need to copy & paste the name from my email...
> > -Original Message-
> > From: Bartosz Golaszewski
> > Sent: Tuesday, April 13, 2021 4:14 PM
> > To: Andy Shevchenko
> >
On 16/04/21 10:43 pm, Roman Gushchin wrote:
On Fri, Apr 16, 2021 at 08:58:33PM +0530, Pratik Sampat wrote:
Hello Dennis,
I apologize for the clutter of logs before, I'm pasting the logs of before and
after the percpu test in the case of the patchset being applied on 5.12-rc6 and
the vanilla
Update the EC command header to include the new event bit. This bit
is included in the latest version of the Chrome EC headers[1].
[1]
https://chromium.googlesource.com/chromiumos/platform/ec/+/refs/heads/main/include/ec_commands.h
Change-Id: I52a36e725d945665814d4e59ddd1e76a3692db9f
---
v2 is
On Thu, Apr 15, 2021 at 10:07:32PM -0700, Guenter Roeck wrote:
> On 4/15/21 7:13 PM, rentao.b...@gmail.com wrote:
> > From: Tao Ren
> >
> > Fix the time comparison (timeout vs. max_hw_heartbeat_ms) in set_timeout
> > handler to avoid potential integer overflow when the supplied timeout is
> >
I should've mentioned this patch is for 4.19 only as the code has been
rewritten in later versions, but requires a large amount of backports
(https://github.com/ClangBuiltLinux/linux/issues/1349). This is the
only blocker for 4.19 migration to LLVM's integrated assembler on CrOS
that I am aware
On 4/15/2021 4:11 PM, Bart Van Assche wrote:
On 4/14/21 11:58 AM, Asutosh Das wrote:
[ ... ]
Hi Bart,
Thanks for the comments. I will fix the comments in the next version.
The following code is executed before ufshcd_async_scan() is called:
dev = hba->dev;
[ ... ]
On 4/16/21 11:31 AM, Mark Brown wrote:
On Fri, Apr 16, 2021 at 04:03:05PM +, codrin.ciubota...@microchip.com wrote:
Thank you for the links! So basically the machine driver disappears and
all the components will be visible in user-space.
Not entirely - you still need something to say
Hi Shengjiu,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on asoc/for-next]
[also build test ERROR on v5.12-rc7 next-20210416]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented
On Fri, 2021-04-16 at 18:53 +0100, Marc Zyngier wrote:
> On Fri, 16 Apr 2021 17:05:49 +0100,
> Robert Hancock wrote:
> > On Fri, 2021-04-16 at 14:41 +0100, Marc Zyngier wrote:
> > > On Fri, 16 Apr 2021 00:32:50 +0100,
> > > Robert Hancock wrote:
> > > > Previously the XILINX_INTC config option
LLVM's integrated assembler does not support using commas separating
the name and arguments in .macro. However, only spaces are used in the
manual page. This replaces commas between macro names and the subsequent
arguments with space in calls to clock_gettime_return to make it
compatible with IAS.
On Fri, Apr 16, 2021 at 07:18:48PM +0200, Peter Zijlstra wrote:
> On Fri, Apr 16, 2021 at 07:10:17PM +0200, Miguel Ojeda wrote:
>
> > Of course, UB is only a subset of errors, but it is a major one, and
> > particularly critical for privileged code.
>
> I've seen relatively few UBSAN warnings
On Tue, Apr 13, 2021 at 5:33 PM Daniel Latypov wrote:
>
> On Mon, Apr 12, 2021 at 11:41 PM David Gow wrote:
> >
> > On Tue, Apr 13, 2021 at 3:07 AM Daniel Latypov wrote:
> > >
> > > Add basic test coverage for files that don't require any config options:
> > > * part of math.h (what seem to be
On Fri, Apr 16, 2021 at 07:47:32PM +0200, Miguel Ojeda wrote:
> On Fri, Apr 16, 2021 at 7:05 PM Linus Torvalds
> wrote:
> >
> > Typical Rust error handling should match the regular kernel
> > IS_ERR/ERR_PTR/PTR_ERR model fairly well, although the syntax is
> > fairly different (and it's not
On Fri, 16 Apr 2021 17:58:45 +
Dexuan Cui wrote:
> > >
> > > This probably should be a separate patch.
> > > I think it is trying to address the case of VF discovery in Hyper-V/Azure
> > > where
> > > the reported
> > > VF from Hypervisor is bogus or confused.
> >
> > This is for the
Hi Takashi,
I love your patch! Yet something to improve:
[auto build test ERROR on drm-intel/for-linux-next]
[also build test ERROR on drm-tip/drm-tip drm-exynos/exynos-drm-next
tegra-drm/drm/tegra/for-next linus/master v5.12-rc7 next-20210416]
[cannot apply to drm/drm-next]
[If your patch
Hi Takashi,
I love your patch! Yet something to improve:
[auto build test ERROR on drm-intel/for-linux-next]
[also build test ERROR on drm-tip/drm-tip drm-exynos/exynos-drm-next
tegra-drm/drm/tegra/for-next linus/master v5.12-rc7 next-20210416]
[cannot apply to drm/drm-next]
[If your patch
On Fri, Apr 16, 2021 at 10:34 AM Andy Shevchenko
wrote:
>
> On Fri, Apr 16, 2021 at 09:15:34AM -0700, Dan Williams wrote:
> > On Fri, Apr 16, 2021 at 1:58 AM Andy Shevchenko
> > wrote:
> > > On Fri, Apr 16, 2021 at 8:28 AM Dan Williams
> > > wrote:
> > > > On Thu, Apr 15, 2021 at 6:59 AM Andy
On Fri, 2021-04-16 at 19:57 +0200, Christophe JAILLET wrote:
> The devm_ variant of 'kcalloc()' and 'kmalloc_array()' are not tested
> Add the corresponding check.
>
> Signed-off-by: Christophe JAILLET
> ---
> v2: use a cleaner regex as proposed by Joe Perches
Acked-by: Joe Perches
> ---
>
Add basic test coverage for files that don't require any config options:
* part of math.h (what seem to be the most commonly used macros)
* gcd.c
* lcm.c
* int_sqrt.c
* reciprocal_div.c
(Ignored int_pow.c since it's a simple textbook algorithm.)
These tests aren't particularly interesting, but
Le 16/04/2021 à 19:03, Joe Perches a écrit :
On Fri, 2021-04-16 at 18:51 +0200, Christophe JAILLET wrote:
Le 16/04/2021 à 18:11, Joe Perches a écrit :
On Fri, 2021-04-16 at 17:58 +0200, Christophe JAILLET wrote:
The devm_ variant of 'kcalloc()' and 'kmalloc_array()' are not tested
Add the
> -Original Message-
> From: Niklas Schnelle
> Sent: Thursday, April 15, 2021 12:55 PM
> To: Bjorn Helgaas
> Cc: K, Narendra; Viktor Mihajlovski; Stefan Raspl; Peter Oberparleiter; linux-
> net...@vger.kernel.org; linux-...@vger.kernel.org; linux-
> ker...@vger.kernel.org;
On Thu, Apr 15, 2021 at 09:27:33PM +0800, peng@oss.nxp.com wrote:
> From: Peng Fan
>
> V4:
> Typo fix
> patch 4: take state as a check condition
> patch 5: move regmap lookup/attach to imx_rproc_detect_mode
> patch 6: add imx_rproc_clk_enable for optional clk
> patch 8: use switch/case
> From: Haiyang Zhang
> Sent: Friday, April 16, 2021 10:11 AM
> > From: Stephen Hemminger
> > > ...
> > > @@ -2319,8 +2320,17 @@ static struct net_device
> > *get_netvsc_byslot(const struct net_device *vf_netdev)
> > > if (!ndev_ctx->vf_alloc)
> > > continue;
> > >
>
The devm_ variant of 'kcalloc()' and 'kmalloc_array()' are not tested
Add the corresponding check.
Signed-off-by: Christophe JAILLET
---
v2: use a cleaner regex as proposed by Joe Perches
---
scripts/checkpatch.pl | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
On Fri, Apr 16, 2021 at 10:23:32AM -0700, Jacob Pan wrote:
> Perhaps similar to cgroup v1 vs v2, it took a long time and with known
> limitations in v1.
cgroup v2 is still having transition problems, if anything it is a
cautionary tale to think really hard about uAPI because transitioning
can be
On Fri, 16 Apr 2021 17:05:49 +0100,
Robert Hancock wrote:
>
> On Fri, 2021-04-16 at 14:41 +0100, Marc Zyngier wrote:
> > On Fri, 16 Apr 2021 00:32:50 +0100,
> > Robert Hancock wrote:
> > > Previously the XILINX_INTC config option was hidden and only
> > > auto-selected on the MicroBlaze
On 4/16/21 4:36 AM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20210415:
on x86_64, objtool is not liking retpoline.o:
$ gcc --version
gcc (SUSE Linux) 7.5.0
Is there already a patch for these?
= build-r8840.out =
arch/x86/lib/retpoline.o: warning: objtool:
Quoting Ulf Hansson (2021-04-16 00:17:10)
> On Thu, 15 Apr 2021 at 21:29, Stephen Boyd wrote:
> >
> >
> > Don't think so. The device (with the kobject inside) is removed, and
> > thus the mmc1 device will be removed, but the kobject's release function
> > is delayed due to the config. This means
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
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
On Fri, Apr 16, 2021 at 7:05 PM Linus Torvalds
wrote:
>
> Typical Rust error handling should match the regular kernel
> IS_ERR/ERR_PTR/PTR_ERR model fairly well, although the syntax is
> fairly different (and it's not limited to pointers).
Yeah, exactly. We already have a `KernelResult` type
On Thu, Apr 15, 2021 at 09:27:40PM +0800, peng@oss.nxp.com wrote:
> From: Peng Fan
>
> i.MX7ULP A7 core runs under control of M4 core, M4 core starts by ROM
> and powers most serivces used by A7 core, so A7 core has no power to
s/serivces/services
> start and stop M4 core. And the M4
301 - 400 of 1309 matches
Mail list logo
