Charge Current is more apropriately reflected by CURRENT_NOW property
(measured current) than CONSTANT_CURRENT_VOLTAGE (configured CC-phase
current limit). Fix the reference and make the sign reflect direction
of the current.
Signed-off-by: Michał Mirosław
---
On Tue, Mar 10, 2020 at 03:17:46PM -0700, Jesse Brandeburg wrote:
> Fix many sparse warnings when building with C=1. These are useless
> noise from the bitops.h file and getting rid of them helps devs
> make more use of the tools and possibly find real bugs.
>
> When the kernel is compiled with
Hi Nikita,
On 5/4/20 6:29 PM, nikitos...@gmail.com wrote:
From: Nikita Travkin
This commit adds support for AWINIC AW2013 3-channel LED driver.
The chip supports 3 PWM channels and is controlled with I2C.
Signed-off-by: Nikita Travkin
---
drivers/leds/Kconfig | 10 +
Hi Maxime,
On Mon, 4 May 2020 at 14:09, Maxime Ripard wrote:
>
> Hi Clement,
>
> On Thu, Apr 30, 2020 at 04:00:14PM +0200, Clément Péron wrote:
> > On Thu, 30 Apr 2020 at 10:46, Maxime Ripard wrote:
> > > On Wed, Apr 29, 2020 at 06:33:00PM +0200, Clément Péron wrote:
> > > > On Wed, 29 Apr 2020
On Mon, 2020-05-04 at 19:58 +0200, Greg Kroah-Hartman wrote:
> From: Lu Baolu
>
> commit ba61c3da00f4a5bf8805aeca1ba5ac3c9bd82e96 upstream.
>
> The CONFIG_ prefix should be added in the code.
>
> Fixes: 046182525db61 ("iommu/vt-d: Add Kconfig option to enable/disable
> scalable mode")
>
do_splice() is used by io_uring, as will be do_tee(). Move f_mode
checks from sys_{splice,tee}() to do_{splice,tee}(), so they're
enforced for io_uring as well.
Fixes: 7d67af2c0134 ("io_uring: add splice(2) support")
Reported-by: Jann Horn
Signed-off-by: Pavel Begunkov
---
fs/splice.c | 45
Signed-off-by: Konrad Dybcio
---
.../display/panel/asus,z00t-tm5p5-n35596.yaml | 56 +++
1 file changed, 56 insertions(+)
create mode 100644
Documentation/devicetree/bindings/display/panel/asus,z00t-tm5p5-n35596.yaml
diff --git
This adds support for TMP5P5 NT35596 1080x1920 video
mode panel that can be found on some Asus Zenfone 2
Laser (Z00T) devices.
This panel seems to only be found in this device
and we have no straightforward way of actually
getting the correct model number, as no schematics
are released publicly.
changes since v1:
- make `backlight_properties props` constant
- a couple of line breaks
- change name and compatible to reflect ASUS being the vendor
- remove a redundant TODO
Konrad Dybcio (2):
drivers: drm: panel: Add ASUS TM5P5 NT35596 panel driver
dt-bindings: display: Document ASUS Z00T
Hi Paul,
On Mon, May 4, 2020 at 3:01 PM Paul E. McKenney wrote:
>
> On Mon, May 04, 2020 at 02:08:05PM -0400, Joel Fernandes wrote:
> > On Mon, May 04, 2020 at 07:48:22PM +0200, Uladzislau Rezki wrote:
> > > On Mon, May 04, 2020 at 08:24:37AM -0700, Paul E. McKenney wrote:
> > [..]
> > > > > >
On Mon, 4 May 2020 15:44:36 -0300
Jason Gunthorpe wrote:
> On Mon, May 04, 2020 at 12:26:43PM -0600, Alex Williamson wrote:
> > On Fri, 1 May 2020 20:48:49 -0300
> > Jason Gunthorpe wrote:
> >
> > > On Fri, May 01, 2020 at 03:39:30PM -0600, Alex Williamson wrote:
> > >
> > > > static int
Hi Ondrej,
On Mon, 4 May 2020 at 14:27, Ondřej Jirman wrote:
>
> Hi Clément,
>
>
> So I guess ignoring the voltage and not disabling this OPP may or may not work
> based on SoC bin.
>
> On Orange Pi One, there's a regulator that supports two voltages (that can't
> support all the listed OPPs
Hi Jens,
Are you ok with this one? One of my later series depends on it, but so
far I've kept it separate because it's a bug fix.
Thanks,
Martijn
On Sat, Apr 18, 2020 at 5:46 PM Bart Van Assche wrote:
>
> On 2020-03-31 04:41, Martijn Coenen wrote:
> > loop_set_status() calls
On Mon, May 04, 2020 at 03:17:40PM -0400, Pavel Tatashin wrote:
> On Mon, May 4, 2020 at 3:12 PM Kees Cook wrote:
> >
> > On Mon, May 04, 2020 at 02:47:45PM -0400, Pavel Tatashin wrote:
> > > > > # reboot -f
> > > > >
> > > > > After VM is back:
> > > > >
> > > > > # mount -t pstore pstore /mnt
>
On Sat, May 02, 2020 at 10:35:55AM -0400, Pavel Tatashin wrote:
> Currently, it is possible to dump kmesges for panic, or oops.
> With dump_all it is possible to dump messages for kmesg_dump events,
> for example reboot, halt, shutdown, kexec.
Please just collapse this into patch #2.
Thanks!
On Sat, May 02, 2020 at 10:35:54AM -0400, Pavel Tatashin wrote:
> Currently, ramoops is capable to collect dmesg buffer only during
> panic and oops events. However, it is desirable to optionally allow
> collecting dmesg buffers during other events as well: reboot, kexec,
> emergency reboot etc.
>
Hi,
thanks for your review. There are some inline responses below. Where I'm not
responding it means that I'll be just fixing what you've pointed out.
On Wed, Apr 29, 2020 at 07:00:37AM +0100, Lee Jones wrote:
> On Sat, 25 Apr 2020, Lubomir Rintel wrote:
>
> > This driver provides access to the
On Mon, May 4, 2020 at 9:06 AM Michal Hocko wrote:
>
> On Mon 04-05-20 08:35:57, Shakeel Butt wrote:
> > On Mon, May 4, 2020 at 8:00 AM Michal Hocko wrote:
> > >
> > > On Mon 04-05-20 07:53:01, Shakeel Butt wrote:
> [...]
> > > > I am trying to see if "no eligible task" is really an issue and
This is building perf from kernel-5.6.10 on armv7hl and aarch64:
Compiler is gcc 10.1.0-RC
LD perf-in.o
ld: arch/perf-in.o: in function `.LANCHOR0':
/home/iurt/rpmbuild/BUILD/kernel-arm/linux-5.6/tools/perf/util/include/../../util/cs-etm.h:118:
multiple definition of `traceid_list';
Dan,
On 5/3/20 2:32 PM, Dan Murphy wrote:
Add DT bindings for the LEDs multicolor class framework.
Add multicolor ID to the color ID list for device tree bindings.
CC: Rob Herring
Acked-by: Pavel Machek
Acked-by: Jacek Anaszewski
Signed-off-by: Dan Murphy
---
On 04/05/20 20:55, Peter Xu wrote:
> On Mon, May 04, 2020 at 11:55:55AM -0400, Paolo Bonzini wrote:
>> The purpose of this series is to get rid of the get_dr6 accessor
>> and, on Intel, of set_dr6 as well. This is done mostly in patch 2,
>> since patch 3 is only the resulting cleanup. Patch 1 is
On Mon, May 4, 2020 at 3:12 PM Kees Cook wrote:
>
> On Mon, May 04, 2020 at 02:47:45PM -0400, Pavel Tatashin wrote:
> > > > # reboot -f
> > > >
> > > > After VM is back:
> > > >
> > > > # mount -t pstore pstore /mnt
> > > > # head /mnt/dmesg-ramoops-0
> > > > Restart#1 Part1
> > >
> > > Is there
On Sun, May 3, 2020 at 9:07 PM Masahiro Yamada wrote:
>
> Marek Behún reported a case where pkg-config fails to detect the
> libyaml-dev package, which is presumably a bug of the distro.
>
> Irrespective of that, I am not a big fan of pkg-config in the Makefile
> parse stage. The cost of
On Mon, 04 May 2020 14:38:23 -0400
Nicolas Dufresne wrote:
> Le lundi 04 mai 2020 à 14:01 -0400, Nicolas Dufresne a écrit :
> > Le samedi 02 mai 2020 à 19:55 -0300, Ezequiel Garcia a écrit :
> > > +Nicolas
> > >
> > > On Sat, 2020-05-02 at 20:37 +0200, Boris Brezillon wrote:
> > > > On Fri,
Hi Prasad,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on tip/timers/core]
[also build test ERROR on tip/auto-latest tip/timers/nohz v5.7-rc4
next-20200501]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we
On Mon, May 04, 2020 at 02:47:45PM -0400, Pavel Tatashin wrote:
> > > # reboot -f
> > >
> > > After VM is back:
> > >
> > > # mount -t pstore pstore /mnt
> > > # head /mnt/dmesg-ramoops-0
> > > Restart#1 Part1
> >
> > Is there a reason that using ramoops.console_size isn't sufficient for
> > this?
264889][ C118] softirqs last enabled at (0): []
copy_process+0x10ff/0x30a0
[18310.273908][ C118] softirqs last disabled at (0): [<>] 0x0
[18310.280958][ C118] CPU: 118 PID: 129976 Comm: trinity-c93 Tainted: G
O L5.7.0-rc4-next-20200504+ #1
[18310.291463][ C118] H
> From: Stanley Chu
> Sent: Monday, May 4, 2020 4:56 PM
> To: linux-s...@vger.kernel.org; martin.peter...@oracle.com;
> avri.alt...@wdc.com; alim.akh...@samsung.com; j...@linux.ibm.com;
> asuto...@codeaurora.org
> Cc: Bean Huo (beanhuo) ; c...@codeaurora.org;
> matthias@gmail.com;
On Mon, 4 May 2020 20:38:32 +0200
Joerg Roedel wrote:
> Fair point, but this just shows how problematic it is to call something
> like vmalloc_sync_mappings() from a lower-level kernel API function.
> The obvious fix for this would be to make pgd_lock irq-safe, but this is
> getting more and
Just as a precaution, make sure that proc handlers don't accidentally
grow "count" beyond the allocated kbuf size.
Signed-off-by: Kees Cook
---
This applies to hch's sysctl cleanup tree...
---
fs/proc/proc_sysctl.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/fs/proc/proc_sysctl.c
the outliers, there, everything else is
> > using /bin/bash, so I'll switch to that, ok Andreas?
>
> Sure, no problem. Thanks!
Just a gentle reminder that this can still be fixed in today's
linux-next tree (next-20200504).
Greetings!
Daniel Díaz
daniel.d...@linaro.org
On Mon, May 04, 2020 at 01:08:22PM -0500, Bjorn Helgaas wrote:
> On Sat, May 02, 2020 at 08:15:37AM +0200, Greg Kroah-Hartman wrote:
> > On Fri, May 01, 2020 at 05:40:41PM -0500, Bjorn Helgaas wrote:
> > > From: Bjorn Helgaas
> > >
> > > These interfaces return a negative error number or an IRQ:
On Mon, 04 May 2020 14:01:32 -0400
Nicolas Dufresne wrote:
> Le samedi 02 mai 2020 à 19:55 -0300, Ezequiel Garcia a écrit :
> > +Nicolas
> >
> > On Sat, 2020-05-02 at 20:37 +0200, Boris Brezillon wrote:
> > > On Fri, 01 May 2020 13:57:49 -0300
> > > Ezequiel Garcia wrote:
> > >
> > > > >
Hi Nicolas,
Am 04.05.20 um 10:59 schrieb Nicolas Saenz Julienne:
> Hi Stefan, thanks for the review!
>
> On Sat, 2020-05-02 at 11:05 +0200, Stefan Wahren wrote:
>>> + if (version)
>>> + goto exit;
>>> +
>>> + dev_addr = pdev->bus->number << 20 | PCI_SLOT(pdev->devfn) << 15 |
>>> +
From: Lu Baolu
commit ba61c3da00f4a5bf8805aeca1ba5ac3c9bd82e96 upstream.
The CONFIG_ prefix should be added in the code.
Fixes: 046182525db61 ("iommu/vt-d: Add Kconfig option to enable/disable
scalable mode")
Reported-and-tested-by: Kumar, Sanjay K
Signed-off-by: Lu Baolu
Cc: Ashok Raj
GCC 10.0.1 gives me this warning when building KVM:
warning: ‘nr_pages_avail’ may be used uninitialized in this function
[-Wmaybe-uninitialized]
2442 | for ( ; start_gfn <= end_gfn; start_gfn += nr_pages_avail) {
It should not happen, but silent it.
Signed-off-by: Peter Xu
---
From: wu000...@umn.edu
Date: Sat, 2 May 2020 17:42:59 -0500
> From: Qiushi Wu
>
> In function nfp_abm_vnic_set_mac, pointer nsp is allocated by nfp_nsp_open.
> But when nfp_nsp_has_hwinfo_lookup fail, the pointer is not released,
> which can lead to a memory leak bug. Fix this issue by adding
On Mon, 2020-05-04 at 19:55 +0200, Uwe Kleine-König wrote:
> Hi Sam,
>
> On Mon, May 04, 2020 at 07:45:22PM +0200, Sam Ravnborg wrote:
> > On Mon, May 04, 2020 at 11:30:20AM +0200, Mauro Carvalho Chehab wrote:
> > > There are some new broken doc links due to yaml renames
> > > at DT. Developers
On Sat, May 02, 2020 at 11:36:11PM -0700, syzbot wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:8999dc89 net/x25: Fix null-ptr-deref in x25_disconnect
> git tree: net
> console output: https://syzkaller.appspot.com/x/log.txt?x=1600444010
> kernel config:
Currently, when adding memory, we create entries in /sys/firmware/memmap/
as "System RAM". This will lead to kexec-tools to add that memory to the
fixed-up initial memmap for a kexec kernel (loaded via kexec_load()). The
memory will be considered initial System RAM by the kexec'd kernel and
can no
Memory flagged with IORESOURCE_MEM_DRIVER_MANAGED is special - it won't be
part of the initial memmap of the kexec kernel and not all memory might be
accessible. Don't place any kexec images onto it.
Cc: Andrew Morton
Cc: Michal Hocko
Cc: Pankaj Gupta
Cc: Wei Yang
Cc: Baoquan He
Cc: Dave
Some device drivers rely on memory they managed to not get added to the
initial (firmware) memmap as system RAM - so it's not used as initial
system RAM by the kernel and the driver is under control. While this is the
case during cold boot and after a reboot, kexec is not aware of that and
might
Third time is the charm? Let's see ... :)
This is the follow up of [1]:
[PATCH v1 0/3] mm/memory_hotplug: Make virtio-mem play nicely with
kexec-tools
and [2]:
[PATCH v2 0/3] mm/memory_hotplug: Allow to not create firmware memmap
entries
kexec (via kexec_load()) can currently not properly
From: Grygorii Strashko
Date: Fri, 1 May 2020 23:50:04 +0300
> This series introduced support for significantly upgraded TI A65x/J721E Common
> platform time sync (CPTS) modules which are part of AM65xx Time
> Synchronization
> Architecture [1].
...
Series applied, thank you.
On Mon, May 04, 2020 at 02:08:05PM -0400, Joel Fernandes wrote:
> On Mon, May 04, 2020 at 07:48:22PM +0200, Uladzislau Rezki wrote:
> > On Mon, May 04, 2020 at 08:24:37AM -0700, Paul E. McKenney wrote:
> [..]
> > > > > Presumably the list can also be accessed without holding this lock,
> > > > >
On Fri, Apr 24, 2020 at 08:43:38AM +0200, Christoph Hellwig wrote:
> Instead of having all the sysctl handlers deal with user pointers, which
> is rather hairy in terms of the BPF interaction, copy the input to and
> from userspace in common code. This also means that the strings are
> always
First 2 bytes are used in large-page nand.
Signed-off-by: Álvaro Fernández Rojas
---
v2: extend original comment
drivers/mtd/nand/raw/brcmnand/brcmnand.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/mtd/nand/raw/brcmnand/brcmnand.c
The current code generates 8 oob sections:
S1 1-5
ECC 6-8
S2 9-15
S3 16-21
ECC 22-24
S4 25-31
S5 32-37
ECC 38-40
S6 41-47
S7 48-53
ECC 54-56
S8 57-63
Change it by merging continuous sections:
S1 1-5
ECC 6-8
S2 9-21
ECC
From: Colin King
Date: Fri, 1 May 2020 15:10:16 +0100
> From: Colin Ian King
>
> The multiplication of cfg->ctr[1] by 10 is performed using a
> 32 bit multiplication (since cfg->ctr[1] is a u32) and this can lead
> to a potential overflow. Fix this by making the constant a ULL to
>
On Mon, May 04, 2020 at 11:55:55AM -0400, Paolo Bonzini wrote:
> The purpose of this series is to get rid of the get_dr6 accessor
> and, on Intel, of set_dr6 as well. This is done mostly in patch 2,
> since patch 3 is only the resulting cleanup. Patch 1 is a related
> bug fix that I found while
On Mon, May 4, 2020 at 12:59 PM Alex Elder wrote:
>
> The IPA accesses "IMEM" and main system memory through an SMMU, so
> its DT node requires an iommus property to define range of stream IDs
> it uses.
>
> Signed-off-by: Alex Elder
> ---
> Documentation/devicetree/bindings/net/qcom,ipa.yaml |
On Mon, 4 May 2020 18:09:16 +0200
Cornelia Huck wrote:
> On Fri, 01 May 2020 15:41:24 -0600
> Alex Williamson wrote:
>
> > There is no PCI spec defined capability with ID 0, therefore we don't
> > expect to find it in a capability chain and we use this index in an
> > internal array for
On Tue, Apr 28, 2020 at 04:15:11PM +0300, Denis V. Lunev wrote:
> Local variable netdev is not used in these calls.
>
> It should be noted, that this change is required to work in bonded mode.
> In the other case we would get the following assert:
> "RTNL: assertion failed at net/core/dev.c
Since the PWM framework is switching struct pwm_args.period's datatype
to u64, prepare for this transition by using DIV_ROUND_UP_ULL to handle
a 64-bit dividend.
Signed-off-by: Guru Das Srinagesh
Acked-by: Guenter Roeck
---
drivers/hwmon/pwm-fan.c | 2 +-
1 file changed, 1 insertion(+), 1
Since the PWM framework is switching struct pwm_args.period's datatype
to u64, prepare for this transition by using DIV64_U64_ROUND_CLOSEST to
handle a 64-bit divisor.
Signed-off-by: Guru Das Srinagesh
Acked-by: Palmer Dabbelt
---
drivers/pwm/pwm-sifive.c | 2 +-
1 file changed, 1
Since the PWM framework is switching struct pwm_state.period's datatype
to u64, prepare for this transition by using DIV64_U64_ROUND_CLOSEST to
handle a 64-bit divisor.
Signed-off-by: Guru Das Srinagesh
---
drivers/pwm/pwm-imx-tpm.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
Because period and duty cycle are defined as ints with units of
nanoseconds, the maximum time duration that can be set is limited to
~2.147 seconds. Change their definitions to u64 in the structs of the
PWM framework so that higher durations may be set.
Also use the right format specifiers in
Since the PWM framework is switching struct pwm_state.period's
datatype to u64, prepare for this transition by using
DIV_ROUND_UP_ULL to handle a 64-bit dividend, and div64_u64 to handle a
64-bit divisor.
Also handle a possible overflow in the calculation of period_cycles when
both clk_rate and
Since the PWM framework is switching struct pwm_args.period's datatype
to u64, prepare for this transition by using div64_u64() to handle a
64-bit divisor.
Also ensure that divide-by-zero (with fixed_rate as denominator) does
not happen with an explicit check with probe failure as a consequence.
Since the PWM framework is switching struct pwm_state.period's datatype
to u64, prepare for this transition by using DIV_ROUND_CLOSEST_ULL to
handle a 64-bit dividend.
Signed-off-by: Guru Das Srinagesh
Acked-by: Sean Young
---
drivers/media/rc/ir-rx51.c | 3 ++-
1 file changed, 2
Since the PWM framework is switching struct pwm_state.period's datatype
to u64, prepare for this transition by using nsecs_to_jiffies() which
does away with the need for a division operation.
Signed-off-by: Guru Das Srinagesh
Acked-by: Chen-Yu Tsai
---
drivers/pwm/pwm-sun4i.c | 2 +-
1 file
Since the PWM framework is switching struct pwm_state.period's datatype
to u64, prepare for this transition by using div_u64 to handle a 64-bit
dividend instead of a straight division operation.
Signed-off-by: Guru Das Srinagesh
Reviewed-by: Daniel Thompson
Acked-by: Lee Jones
---
Because period and duty cycle are defined in the PWM framework structs as ints
with units of nanoseconds, the maximum time duration that can be set is limited
to ~2.147 seconds. Consequently, applications desiring to set greater time
periods via the PWM framework are not be able to do so - like,
Since the PWM framework is switching struct pwm_state.duty_cycle's
datatype to u64, prepare for this transition by using DIV_ROUND_UP_ULL
to handle a 64-bit dividend.
Signed-off-by: Guru Das Srinagesh
Reviewed-by: Jani Nikula
Acked-by: Jani Nikula
---
Since the PWM framework is switching struct pwm_args.period's datatype
to u64, prepare for this transition by typecasting it to u32.
Also, since the dividend is still a 32-bit number, any divisor greater
than the numerator will cause the quotient to be zero, so return 0 in
that case to
> > # reboot -f
> >
> > After VM is back:
> >
> > # mount -t pstore pstore /mnt
> > # head /mnt/dmesg-ramoops-0
> > Restart#1 Part1
>
> Is there a reason that using ramoops.console_size isn't sufficient for
> this?
Unfortunately, the console option is not working for us (Microsoft),
we have an
From: Arnd Bergmann
Date: Thu, 30 Apr 2020 12:39:02 +0200
> gcc-10 warns about functions that return a pointer to a stack
> variable. In chcr_write_cpl_set_tcb_ulp(), this does not actually
> happen, but it's too hard to see for the compiler:
>
> drivers/crypto/chelsio/chcr_ktls.c: In function
On Mon, May 4, 2020 at 10:32 AM Kai-Heng Feng
wrote:
>
> igb device gets runtime suspended when there's no link partner. We can't
> get correct speed under that state:
> $ cat /sys/class/net/enp3s0/speed
> 1000
>
> In addition to that, an error can also be spotted in dmesg:
> [ 385.991957] igb
On Fri, Apr 24, 2020 at 08:43:37AM +0200, Christoph Hellwig wrote:
> Move the sysctl tables to the end of the file to avoid lots of pointless
> forward declarations.
>
> Signed-off-by: Christoph Hellwig
Reviewed-by: Kees Cook
-Kees
> ---
> kernel/sysctl.c | 3565
On Mon, May 04, 2020 at 12:26:43PM -0600, Alex Williamson wrote:
> On Fri, 1 May 2020 20:48:49 -0300
> Jason Gunthorpe wrote:
>
> > On Fri, May 01, 2020 at 03:39:30PM -0600, Alex Williamson wrote:
> >
> > > static int vfio_pci_add_vma(struct vfio_pci_device *vdev,
> > >
Hi GVRao,
Thanks for the patch. Sorry for late reply.
On Mon, 2020-04-20 at 14:20:56 -0700, Venkateshwar Rao Gannavarapu wrote:
> The Xilinx MIPI DSI Tx Subsystem soft IP is used to display video
> data from AXI-4 stream interface.
>
> It supports upto 4 lanes, optional register interface for
On Mon, 2020-05-04 at 16:20 +0800, Wang YanQing wrote:
> According to submitting-patches.rst, 'Fixes:' tag has a little
> stricter condition about the one line summary than normal git
> commit description:
> “...
> Do not split the tag across multiple lines, tags are exempt from
> the "wrap at 75
On Mon, 2020-05-04 at 16:37 +0800, Wang YanQing wrote:
> The current GIT_COMMIT_ID will report error when the commit description
> spans across three lines, for examples:
> "...
> To rehash a previous explanation given in commit 1c44ce560b4d ("net:
> mscc: ocelot: fix vlan_filtering when enslaving
On Fri, Apr 24, 2020 at 08:43:36AM +0200, Christoph Hellwig wrote:
> Extern declarations in .c files are a bad style and can lead to
> mismatches. Use existing definitions in headers where they exist,
> and otherwise move the external declarations to suitable header
> files.
>
> Signed-off-by:
On 04.05.20 18:47, Oleg Nesterov wrote:
> uprobe_write_opcode() must not cross page boundary; prepare_uprobe()
> relies on arch_uprobe_analyze_insn() which should validate "vaddr" but
> some architectures (csky, s390, and sparc) don't do this.
I think the idea was that the uprobe instruction
Thank Kees, I think it is a little cleaner this way.
Thank you,
Pasha
On Mon, May 4, 2020 at 2:12 PM Kees Cook wrote:
>
> On Mon, May 04, 2020 at 01:15:00PM -0400, Steven Rostedt wrote:
> > On Sat, 2 May 2020 10:35:53 -0400
> > Pavel Tatashin wrote:
> >
> > > kmsg_dump() allows to dump kmesg
On Fri, Apr 24, 2020 at 08:43:35AM +0200, Christoph Hellwig wrote:
> watermark_boost_factor_sysctl_handler is just a pointless wrapper for
> proc_dointvec_minmax, so remove it and use proc_dointvec_minmax
> directly.
>
> Signed-off-by: Christoph Hellwig
Reviewed-by: Kees Cook
-Kees
>
On Mon, May 04, 2020 at 02:13:42PM +1000, Balbir Singh wrote:
> Implement a mechanism to selectively flush the L1D cache. The goal is to
> allow tasks that are paranoid due to the recent snoop assisted data sampling
> vulnerabilites, to flush their L1D on being switched out. This protects
> their
The pull request you sent on Mon, 4 May 2020 12:44:49 -0500:
> git://git.kernel.org/pub/scm/linux/kernel/git/gustavoars/linux.git
> tags/flexible-array-member-5.7-rc5
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/67f852ef92274116c9487cb312e58105d0e8d3e7
Thank you!
On Mon, May 04, 2020 at 01:40:42PM -0400, Steven Rostedt wrote:
> Seems that your patch caused a lockdep splat on my box:
>
>
> WARNING: possible irq lock inversion dependency detected
> 5.7.0-rc3-test+ #249 Not tainted
>
The pull request you sent on Mon, 4 May 2020 10:46:49 -0700:
> https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git
> tags/gcc-plugins-v5.7-rc5
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/9851a0dee7c28514f149f7e4f60ec1b06286cc1b
Thank you!
--
The pull request you sent on Mon, 4 May 2020 08:15:40 -0400:
> https://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git tags/for_linus
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/a16a47e98a30ae6a424d30ce9f4f99e4d9384713
Thank you!
--
Deet-doot-dot, I am a
Le lundi 04 mai 2020 à 14:01 -0400, Nicolas Dufresne a écrit :
> Le samedi 02 mai 2020 à 19:55 -0300, Ezequiel Garcia a écrit :
> > +Nicolas
> >
> > On Sat, 2020-05-02 at 20:37 +0200, Boris Brezillon wrote:
> > > On Fri, 01 May 2020 13:57:49 -0300
> > > Ezequiel Garcia wrote:
> > >
> > > > > >
On Mon, May 04, 2020 at 01:16:10PM +0300, Shenhar, Talel wrote:
> > > + mci = edac_mc_alloc(0, ARRAY_SIZE(layers), layers,
> > > + sizeof(struct al_mc_edac));
> > You can let that line stick out.
>
> I rather avoid having this as a checkpatch warnning... (automation
> -Original Message-
> From: Hans de Goede
> Sent: Saturday, May 2, 2020 1:30 PM
> To: Darren Hart; Andy Shevchenko; Limonciello, Mario
> Cc: Hans de Goede; linux-a...@vger.kernel.org; platform-driver-
> x...@vger.kernel.org; linux-kernel@vger.kernel.org
> Subject: [PATCH 4/5]
On Sun, May 3, 2020 at 5:57 AM David Laight wrote:
>
> From: Linus Torvalds
> > Sent: 01 May 2020 19:29
> ...
> > And as DavidL pointed out - if you ever have "iomem" as a source or
> > destination, you need yet another case. Not because they can take
> > another kind of fault (although on some
On Mon 04 May 10:58 PDT 2020, Alex Elder wrote:
> The ipa_mem_data structure type was never actually used. Instead,
> the IPA memory regions were defined using the ipa_mem structure.
>
> Redefine struct ipa_mem_data so it encapsulates the array of IPA-local
> memory region descriptors along
The following commit has been merged into the x86/boot branch of tip:
Commit-ID: 34bb49229f19399a5b45c323afb5749f31f7876c
Gitweb:
https://git.kernel.org/tip/34bb49229f19399a5b45c323afb5749f31f7876c
Author:Joerg Roedel
AuthorDate:Tue, 28 Apr 2020 17:16:22 +02:00
Committer:
On Mon 04 May 10:58 PDT 2020, Alex Elder wrote:
> The IPA accesses "IMEM" and main system memory through an SMMU, so
> its DT node requires an iommus property to define range of stream IDs
> it uses.
>
> Signed-off-by: Alex Elder
> ---
> Documentation/devicetree/bindings/net/qcom,ipa.yaml | 10
On Sat, May 02, 2020 at 11:54:09PM +, Christoph Lameter wrote:
> On Thu, 30 Apr 2020, Roman Gushchin wrote:
>
> > Sorry, but what exactly do you mean?
>
> I think the right approach is to add a pointer to each slab object for
> memcg support.
>
As I understand, embedding the memcg pointer
Use a few more common kernel styles.
Trivially reduce efi_printk object size by using a dereference to
a temporary instead of multiple dereferences of the same object.
Use efi_printk(const char *str) and static or static const for its
internal variables.
Use the more common form of while
From: Alex Elder
Date: Mon, 4 May 2020 12:58:55 -0500
> This series adds the definition of two memory regions that must be
> mapped for IPA to access through an SMMU. It requires the SMMU to
> be defined in the IPA node in the SoC's Device Tree file.
>
> There is no change since version 1 to
On Mon 04 May 10:58 PDT 2020, Alex Elder wrote:
> Define a region of IMEM memory available for use by IPA in the
> platform configuration data. Initialize it from ipa_mem_init().
> The memory must be mapped for access through an SMMU.
>
Reviewed-by: Bjorn Andersson
Regards,
Bjorn
>
On Fri, 1 May 2020 20:48:49 -0300
Jason Gunthorpe wrote:
> On Fri, May 01, 2020 at 03:39:30PM -0600, Alex Williamson wrote:
>
> > static int vfio_pci_add_vma(struct vfio_pci_device *vdev,
> > struct vm_area_struct *vma)
> > {
> > @@ -1346,15 +1450,49 @@ static
A number of kthread-related functions indirectly take task_struct->pi_lock
while holding worker->lock in the call chain like this:
spin_lock(>lock)
kthread_insert_work
wake_up_process
try_to_wake_up
raw_spin_lock_irqsave(>pi_lock, flags)
This lock dependency exists whenever
On 5/1/20 4:45 PM, Alex Elder wrote:
The IPA accesses "IMEM" and main system memory through an SMMU, so
its DT node requires an iommus property to define range of stream IDs
it uses.
Signed-off-by: Alex Elder
Please ignore this patch. I have reposted it as the first
patch in a new series:
Hi,
Usually you need to send patches to a maintainer who could then
merge/apply them.
On 5/4/20 9:45 AM, Andrew Dunai wrote:
> ---
> drivers/platform/x86/touchscreen_dmi.c | 21 +
> 1 file changed, 21 insertions(+)
>
> diff --git a/drivers/platform/x86/touchscreen_dmi.c
>
From: Kai-Heng Feng
Date: Tue, 5 May 2020 01:32:18 +0800
> igb device gets runtime suspended when there's no link partner. We can't
> get correct speed under that state:
> $ cat /sys/class/net/enp3s0/speed
> 1000
>
> In addition to that, an error can also be spotted in dmesg:
> [ 385.991957]
On Mon, May 4, 2020 at 1:44 PM Paul E. McKenney wrote:
>
> On Mon, May 04, 2020 at 10:15:32AM -0700, Paul E. McKenney wrote:
> > On Mon, May 04, 2020 at 08:05:00AM -0400, Joel Fernandes (Google) wrote:
> > > These patches clean up the usage of dynticks nesting counters simplifying
> > > the
> >
Whenever thermal_zone_device_register() is called and zone is created
successfully, send a notification "THERMAL_ZONE_CREATE".
Similarly send "THERMAL_ZONE_DELETE" when thermal_zone_device_unregister
is called.
Signed-off-by: Srinivas Pandruvada
---
drivers/thermal/thermal_core.c | 4
1
401 - 500 of 1610 matches
Mail list logo
