stable-rc/linux-4.9.y boot: 99 boots: 0 failed, 86 passed with 13 offline
(v4.9.194-130-gc1fc11455620)
Full Boot Summary:
https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.9.y/kernel/v4.9.194-130-gc1fc11455620/
Full Build Summary:
https://kernelci.org/build/stable-rc/branch/linux-4.9.y
On Thu, Oct 03, 2019 at 11:17:45PM -0700, Stephen Boyd wrote:
> Quoting Bjorn Andersson (2019-10-03 22:50:57)
> > On Thu 03 Oct 22:38 PDT 2019, Stephen Boyd wrote:
> >
> > > Quoting Murali Nalajala (2019-10-03 16:51:50)
> > > > @@ -151,14 +156,16 @@ struct soc_device *soc_device_register(struct
>
On 03/10/19 23:23, Rick Edgecombe wrote:
> Since software would have previously received a #PF with the RSVD error code
> set, when the HW encountered any set bits in the region 51 to M, there was
> some
> internal discussion on whether this should have a virtual MSR for the OS to
> turn
> it on
On 03/10/19 23:23, Rick Edgecombe wrote:
> Add a KVM capability for the KVM_MEM_EXECONLY memslot type. This memslot
> type is supported if the HW supports execute-only TDP.
>
> Signed-off-by: Rick Edgecombe
> ---
> arch/x86/include/asm/kvm_host.h | 1 +
> arch/x86/kvm/svm.c | 6
On 03/10/19 23:23, Rick Edgecombe wrote:
> Add XO memslot type to create execute-only guest physical memory based on
> the RO memslot. Like the RO memslot, disallow changing the memslot type
> to/from XO.
>
> In the EPT case ACC_USER_MASK represents the readable bit, so add the
> ability for set_s
* Christian Brauner:
> On Thu, Oct 03, 2019 at 08:56:19AM +0200, Florian Weimer wrote:
>> Is anyone else getting a very incomplete set of messages in this
>> thread?
>>
>> These changes likely matter to glibc, and I've yet to see the actual
>> patch. Would someone please forward it to me?
>>
>>
On Thu, 5 Sep 2019 at 14:22, Ludovic Barre wrote:
>
> From: Ludovic Barre
>
> This patch adds a specific busy_complete callback for sdmmc variant.
>
> sdmmc has 2 status flags:
> -busyd0: This is a hardware status flag (inverted value of d0 line).
> it does not generate an interrupt.
> -busyd0end
On 03/10/19 23:23, Rick Edgecombe wrote:
> +/* KVM based not-readable: only valid after cpuid check */
> +#define _PAGE_BIT_NR (__pgtable_kvmxo_bit)
> +#else /* defined(CONFIG_KVM_XO) && !defined(__ASSEMBLY__) */
> +#define _PAGE_BIT_NR 0
> +#endif /* defined(CONFIG_KVM_XO) && !defi
On 03/10/19 23:23, Rick Edgecombe wrote:
> +
> + protection_map[4] = PAGE_EXECONLY;
> + protection_map[12] = PAGE_EXECONLY;
Can you add #defines for the bits in protection_map? Also perhaps you
can replace the p_xo/p_xr/s_xo/s_xr checks with just with "if
(pgtable_kvmxo_enabled()".
Paolo
On 03/10/2019 16:52, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.4.195 release.
> There are 99 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 sh
On 03/10/2019 16:52, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.9.195 release.
> There are 129 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 s
On 03/10/2019 16:51, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.14.147 release.
> There are 185 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
On 03/10/2019 16:51, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.19.77 release.
> There are 211 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 s
Index of rvring is computed using pointer arithmetic. However, since
rvring->rvdev->vring is the base of the vring array, computation
of rvring idx should be reversed. It previously lead to writing at negative
indices in the resource table.
Signed-off-by: Clement Leger
---
drivers/remoteproc/rem
Hi Miguel,
On Thu, Oct 3, 2019 at 10:21 PM Miguel Ojeda
wrote:
> On Thu, Oct 3, 2019 at 7:29 PM Linus Torvalds
> wrote:
> > On Thu, Oct 3, 2019 at 10:24 AM Masahiro Yamada
> > wrote:
> > >
> > > I just want to annotate __always_inline for the case
> > > "2. code that if not inlined is somehow n
In __set_page_owner_handle(), we should loop over page
[0...(1 << order) - 1] and setup their page_owner structures.
Currently, __set_page_owner_handle() update page_ext at the end of
the loop, sets the page_owner of (page + 0) twice and
misses the page_owner of (page + (1 << order) - 1).
Fix it
On 03/10/2019 16:49, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.3.4 release.
> There are 344 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 sho
On 03/10/2019 16:49, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.2.19 release.
> There are 313 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 sh
On 03/10/19 23:23, Rick Edgecombe wrote:
> + if (!vcpu->arch.gva_available)
> + return 0;
Please return RET_PF_* constants, RET_PF_EMULATE here.
> + if (error_code & PFERR_WRITE_MASK)
> + fault_error_code |= X86_PF_WRITE;
> +
> + fault.vector = PF_VECTOR;
> +
On 02.10.19 23:37, Qian Cai wrote:
> On Tue, 2019-09-24 at 16:36 +0200, David Hildenbrand wrote:
>> Since commit 3f906ba23689 ("mm/memory-hotplug: switch locking to a percpu
>> rwsem") we do a cpus_read_lock() in mem_hotplug_begin(). This was
>> introduced to fix a potential deadlock between get_on
On Thu, Oct 03, 2019 at 02:41:11PM +, mario.limoncie...@dell.com wrote:
> > -Original Message-
> > From: Mika Westerberg
> > Sent: Thursday, October 3, 2019 3:00 AM
> > To: Limonciello, Mario
> > Cc: yehezkel...@gmail.com; linux-...@vger.kernel.org;
> > andreas.noe...@gmail.com; michae
On Thu, Oct 03, 2019 at 04:51:34PM -0700, Kevin Hilman wrote:
> "kernelci.org bot" writes:
>
> > stable-rc/linux-5.2.y boot: 136 boots: 1 failed, 126 passed with 9 offline
> > (v5.2.18-314-g2c8369f13ff8)
> >
> > Full Boot Summary:
> > https://kernelci.org/boot/all/job/stable-rc/branch/linux-5.2
On Fri, Oct 04, 2019 at 08:38:48AM +0100, Jon Hunter wrote:
>
> On 03/10/2019 16:49, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 5.3.4 release.
> > There are 344 patches in this series, all will be posted as a response
> > to this one. If anyone has any issu
On 10/4/19 9:37 AM, Miles Chen wrote:
> In __set_page_owner_handle(), we should loop over page
> [0...(1 << order) - 1] and setup their page_owner structures.
>
> Currently, __set_page_owner_handle() update page_ext at the end of
> the loop, sets the page_owner of (page + 0) twice and
> misses the
On Fri, 2019-10-04 at 09:57 +0200, Vlastimil Babka wrote:
> On 10/4/19 9:37 AM, Miles Chen wrote:
> > In __set_page_owner_handle(), we should loop over page
> > [0...(1 << order) - 1] and setup their page_owner structures.
> >
> > Currently, __set_page_owner_handle() update page_ext at the end of
Hi all,
We are developing a v4l2 subdevice driver to be able to support the imx378
sensor and upstream it. But we would like to have a continuous frame
interval and the
current VIDIOC_SUBDEV_ENUM_FRAME_INTERVAL ioctl implementation doesn't
support it.
How can we proceed here? Can we maybe add the
On Thu, Oct 03, 2019 at 12:48:39PM -0700, Eric Biggers wrote:
> On Thu, Oct 03, 2019 at 05:54:35PM +0200, Greg Kroah-Hartman wrote:
> >
> > static void queue_interrupt(struct fuse_iqueue *fiq, struct fuse_req *req)
> > {
> > - spin_lock(&fiq->waitq.lock);
> > + spin_lock(&fiq->lock);
> >
On Thu, Oct 03, 2019 at 10:56:24PM +0200, Hans de Goede wrote:
> Hi,
>
> On 03-10-2019 22:45, John Stultz wrote:
> > On Thu, Oct 3, 2019 at 4:26 AM Greg Kroah-Hartman
> > wrote:
> > >
> > > On Wed, Oct 02, 2019 at 11:16:16PM +, John Stultz wrote:
> > > > From: Yu Chen
> > > >
> > > > This
On Fri, 2019-10-04 at 12:42 +0800, Walter Wu wrote:
> On Thu, 2019-10-03 at 16:53 +0200, Dmitry Vyukov wrote:
> > On Thu, Oct 3, 2019 at 3:51 PM Walter Wu wrote:>
> > >
> > > static void print_error_description(struct kasan_access_info *info)
> > > {
> > > - pr_err("BUG: KASAN: %s in %pS\n
On Thu, Oct 03, 2019 at 09:50:33AM -0700, Tejun Heo wrote:
> Hello, Mika.
>
> On Wed, Oct 02, 2019 at 03:21:36PM +0300, Mika Westerberg wrote:
> > but from that discussion I don't see more generic solution to be
> > implemented.
> >
> > Any ideas we should fix this properly?
>
> Yeah, the only f
--git a/scripts/jobserver-count b/scripts/jobserver-count
> new file mode 100755
> index ..0b482d6884d2
> --- /dev/null
> +++ b/scripts/jobserver-count
> @@ -0,0 +1,58 @@
> +#!/usr/bin/env python
This breaks our daily linux-next build for an fedora 30 rpm on s3
On Fri, Oct 4, 2019 at 10:54 AM Mika Westerberg
wrote:
>
> On Thu, Oct 03, 2019 at 02:41:11PM +, mario.limoncie...@dell.com wrote:
> > > -Original Message-
> > > From: Mika Westerberg
> > > Sent: Thursday, October 3, 2019 3:00 AM
> > > To: Limonciello, Mario
> > > Cc: yehezkel...@gmai
On Fri, Oct 4, 2019 at 5:31 AM Srinivas Pandruvada
wrote:
>
> On Thu, 2019-10-03 at 20:05 +0200, Rafael J. Wysocki wrote:
> > On Wednesday, October 2, 2019 2:29:26 PM CEST Giovanni Gherdovich
> > wrote:
> > > From: Srinivas Pandruvada
> > >
> > > intel_pstate has two operating modes: active and p
On 02. 10. 19 23:58, Dmitry Torokhov wrote:
Some drivers need to be able to know the current polling interval for
devices working in polling mode, let's allow them fetching it.
Signed-off-by: Dmitry Torokhov
Just tested to use this function from a mpr121_touchkey driver.
Works as expected. Wh
On Fri, Oct 04, 2019 at 12:19:25PM +0800, Kefeng Wang wrote:
> The riscv has csr_read/write macro, see arch/riscv/include/asm/csr.h,
> the same function naming will cause build error, using such generic names
> in a driver is bad, rename csr_[read,write][l,] to mobiveil_csr_read/write
> to fix it.
On 04/10/2019 00:10, Steven Rostedt wrote:
> On Wed, 2 Oct 2019 20:21:06 +0200
> Peter Zijlstra wrote:
>
>> On Wed, Oct 02, 2019 at 06:35:26PM +0200, Daniel Bristot de Oliveira wrote:
>>
>>> ftrace was already batching the updates, for instance, causing 3 IPIs to
>>> enable
>>> all functions. Th
On Thu, Oct 03, 2019 at 10:51:38PM +0200, Hans de Goede wrote:
> Hi,
>
> On 03-10-2019 22:37, John Stultz wrote:
> > On Thu, Oct 3, 2019 at 2:25 AM Hans de Goede wrote:
> > > On 03-10-2019 01:16, John Stultz wrote:
> > > > From: Yu Chen
> > > >
> > > > This patch adds notifier for drivers want
From: Colin Ian King
There is a spelling mistake in in an error message, fix it.
Signed-off-by: Colin Ian King
---
tools/testing/selftests/kvm/lib/sparsebit.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/testing/selftests/kvm/lib/sparsebit.c
b/tools/testing/selfte
On Thu 03-10-19 15:44:29, Qian Cai wrote:
> Long time ago, there fixed a similar deadlock in show_slab_objects()
> [1]. However, it is apparently due to the commits like 01fb58bcba63
> ("slab: remove synchronous synchronize_sched() from memcg cache
> deactivation path") and 03afc0e25f7f ("slab: get
On Fri 04-10-19 01:41:38, Yang Shi wrote:
> Since lumpy reclaim was removed in v3.5 scan_control is not used by
> may_write_to_{queue|inode} and pageout() anymore, remove the unused
> parameter.
I haven't really checked whether it was the lumpy reclaim removal but it
is clearly not used these days
Hi,
This series introduces support for Tegra194 XUSB host and pad
controller. Tegra194 XUSB host and pad controller are highly
similar to the controllers found on Tegra186. Therefore, it's
possible to resue xhci-tegra.c and xusb-tegra186.c for Tegra194.
JC Kuo (7):
xhci: tegra: Parameterize mai
On Fri, Sep 27, 2019 at 07:11:54PM +0900, Benjamin Poirier wrote:
> qlge refills rx buffers from napi context. In case of allocation failure,
> allocation will be retried the next time napi runs. If a receive queue runs
> out of free buffers (possibly after subsequent allocation failures), it
> dro
Adds the XUSB pad and XUSB controllers on Tegra194.
Signed-off-by: JC Kuo
---
Changes in v2:
- renamed xhci@361 with usb@361
- moved padctl@352 and usb@361 inside /cbb
- cleaned up "clocks" property of usb@361 node
- added blanks lines to visually separate blocks
arch/ar
On Fri, Oct 04, 2019 at 11:07:34AM +0300, Yehezkel Bernat wrote:
> > Also if you can get the hw_vendor_id and hw_product_id from the kernel
> > does that mean you don't need to do the two reads or you still need
> > those?
>
> Are those the chip vendor or the OEM, in case they are different?
Thos
Tegra194 XUSB host controller has rearranged mailbox registers. This
commit makes mailbox registers address a part of "soc" data so that
xhci-tegra driver can be used for Tegra194.
Signed-off-by: JC Kuo
---
drivers/usb/host/xhci-tegra.c | 58 +--
1 file changed,
Add support for the XUSB pad controller found on Tegra194 SoCs. It is
mostly similar to the same IP found on Tegra186, but the number of
pads exposed differs, as do the programming sequences. Because most of
the Tegra194 XUSB PADCTL registers definition and programming sequence
are the same as Tegr
This commit adds Tegra194 XUSB host mode controller support. This is
very similar to the existing Tegra124/Tegra210/Tegra186 XHCI, except
1. the number of ports and PHYs differs
2. the IPFS wrapper being removed
3. mailbox registers address changes
Signed-off-by: JC Kuo
---
drivers/usb/hos
Extend the bindings to cover the set of features found in Tegra194.
Note that, technically, there are four more supplies connected to the
XUSB pad controller (DVDD_PEX, DVDD_PEX_PLL, HVDD_PEX and HVDD_PEX_PLL)
, but the power sequencing requirements of Tegra194 require these to be
under the control
As xusb-tegra186.c will be reused for Tegra194, it would be good to
protect Tegra186 soc data with CONFIG_ARCH_TEGRA_186_SOC. This commit
also reshuffles Tegra186 soc data single CONFIG_ARCH_TEGRA_186_SOC
will be sufficient.
Signed-off-by: JC Kuo
---
Changes in v2:
- new patch to protect Tegra186
This commit enables XUSB host and pad controller in Tegra194
P2972- board.
Signed-off-by: JC Kuo
---
Changes in v2:
- use capitalization of regulator names
- fix gpio property of VDD_5V_SATA regulator
.../arm64/boot/dts/nvidia/tegra194-p2888.dtsi | 36 ++-
.../boot/dts/nvidia/tegra1
On Thu, Sep 19, 2019 at 02:25:36PM +, Jerome Pouiller wrote:
> From: Jérôme Pouiller
>
> Instantiate build infrastructure WFx driver. This driver provides support
> for Wifi chipset Silicon Labs WF200 and further:
>
>https://www.silabs.com/documents/public/data-sheets/wf200-datasheet.pdf
>> How do you think about to avoid the addition of the SmPL variable
>> “virtual report” to the script “add_namespace.cocci” if you would dare
>> to integrate my change proposal for an adjusted directory hierarchy?
>
> Perhaps I'm lazy, but i seems simpler to add 20 characters than to move
> all of
On Thu, 2019-10-03 at 20:31 -0700, Srinivas Pandruvada wrote:
> On Thu, 2019-10-03 at 20:05 +0200, Rafael J. Wysocki wrote:
> > On Wednesday, October 2, 2019 2:29:26 PM CEST Giovanni Gherdovich
> > wrote:
> > > From: Srinivas Pandruvada
> > >
> > > intel_pstate has two operating modes: active and
On 03.10.19 14:14, Qian Cai wrote:
>
>
>> On Oct 3, 2019, at 8:01 AM, Anshuman Khandual
>> wrote:
>>
>> Will something like this be better ?
>
> Not really. dump_page() will dump PageCompound information anyway, so it is
> trivial to figure out if went in that path.
>
I agree, I use the dum
I just tried to compile kernel 5.4-rc1 on my ThinkPad, which runs Devuan
Beowulf. Got the following:
$ make bindeb-pkg
UPD include/config/kernel.release
sh ./scripts/package/mkdebian
dpkg-buildpackage -r"fakeroot -u" -a$(cat debian/arch) -b -nc -uc
dpkg-buildpackage: info: source package li
On Fri, 4 Oct 2019 at 10:24, Giovanni Gherdovich wrote:
>
> On Thu, 2019-10-03 at 20:31 -0700, Srinivas Pandruvada wrote:
> > On Thu, 2019-10-03 at 20:05 +0200, Rafael J. Wysocki wrote:
> > > On Wednesday, October 2, 2019 2:29:26 PM CEST Giovanni Gherdovich
> > > wrote:
> > > > From: Srinivas Pand
Ping ?
- On 13 Sep, 2019, at 12:58, Clément Leger cle...@kalray.eu wrote:
> Ping ?
>
> - On 19 Aug, 2019, at 13:45, Clément Leger cle...@kalray.eu wrote:
>
>> From: Clément Leger
>>
>> elf32 and elf64 mainly differ by their types. In order to avoid
>> copy/pasting the whole loader cod
On Fri, Oct 4, 2019 at 10:24 AM Giovanni Gherdovich wrote:
>
> On Thu, 2019-10-03 at 20:31 -0700, Srinivas Pandruvada wrote:
> > On Thu, 2019-10-03 at 20:05 +0200, Rafael J. Wysocki wrote:
> > > On Wednesday, October 2, 2019 2:29:26 PM CEST Giovanni Gherdovich
> > > wrote:
> > > > From: Srinivas P
Currently, the play_idle function does not allow to tell which idle
state we want to go. Improve this by passing the idle state as
parameter to the function.
Export cpuidle_find_deepest_state() symbol as it is used from the
intel_powerclamp driver as a module.
There is no functional changes, the
The play_idle function has two users, the intel powerclamp and the
idle_injection.
The idle injection cooling device uses the function via the
idle_injection powercap's APIs. Unfortunately, play_idle is currently
limited by the idle state depth: by default the deepest idle state is
selected. On th
Currently the idle injection framework only allows to inject the
deepest idle state available on the system.
Give the opportunity to specify which idle state we want to inject by
adding a new function helper to set the state and use it when calling
play_idle().
There is no functional changes, the
Hi
Here are patches to add a new 'perf record' option '--kcore' which will put
a copy of /proc/kcore, kallsyms and modules into a perf.data directory.
Note, that without the --kcore option, output goes to a file as previously.
The tools' -o and -i options work with either a file name or directory
Support directory output that contains a regular perf.data file, named
"data". By default the directory is named perf.data i.e.
perf.data
└── data
Most of the infrastucture to support a directory is already there. This
patch makes the changes needed to support the format above.
Pr
perf_dir_version belongs to struct perf_data which is declared in data.h.
To allow its use in inline perf_data functions, move perf_dir_version to
data.h
Signed-off-by: Adrian Hunter
---
tools/perf/util/data.h | 4
tools/perf/util/header.h | 4
2 files changed, 4 insertions(+), 4 del
Add a new 'perf record' option '--kcore' which will put a copy of
/proc/kcore, kallsyms and modules into a perf.data directory. Note, that
without the --kcore option, output goes to a file as previously.
The tools' -o and -i options work with either a file name or directory
name.
Example:
$ sudo
In order to rename the "header" file to "data" without conflicting,
correctly identify the non-header files as starting with "data."
Signed-off-by: Adrian Hunter
---
tools/perf/util/data.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/perf/util/data.c b/tools/perf/uti
In preparation to support a single file directory format, rename "header"
to "data" because "header" is a mis-leading name when there is only 1 file.
Note, in the multi-file case, the "header" file also contains data.
Signed-off-by: Adrian Hunter
---
tools/perf/util/data.c | 2 +-
tools/perf/uti
On 3/10/19 4:43 PM, Arnaldo Carvalho de Melo wrote:
> Em Thu, Oct 03, 2019 at 10:25:31AM -0300, Arnaldo Carvalho de Melo escreveu:
>> Em Thu, Oct 03, 2019 at 02:01:16PM +0300, Adrian Hunter escreveu:
>>> On 6/09/19 11:57 AM, Adrian Hunter wrote:
On 21/08/19 11:32 AM, Adrian Hunter wrote:
>
On Fri, Oct 4, 2019 at 10:28 AM Vincent Guittot
wrote:
>
> On Fri, 4 Oct 2019 at 10:24, Giovanni Gherdovich wrote:
> >
> > On Thu, 2019-10-03 at 20:31 -0700, Srinivas Pandruvada wrote:
> > > On Thu, 2019-10-03 at 20:05 +0200, Rafael J. Wysocki wrote:
> > > > On Wednesday, October 2, 2019 2:29:26
Dear All,
this series adds MSDIF/RWDT/PCIEC support to the HiHope RZ/G2N.
This series depends on the following series and patches:
* https://patchwork.kernel.org/cover/11166155/
* https://patchwork.kernel.org/cover/11157129/
* https://patchwork.kernel.org/cover/11158259/
* https://patchwork.kerne
Add PCIe support for the RZ/G2N (a.k.a. R8A774B1).
Signed-off-by: Fabrizio Castro
---
Documentation/devicetree/bindings/pci/rcar-pci.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/pci/rcar-pci.txt
b/Documentation/devicetree/bindings/pci/rcar-pci.txt
in
Document RZ/G2N (R8A774B1) SoC bindings.
Signed-off-by: Fabrizio Castro
---
This patch depends on https://patchwork.kernel.org/patch/11162283/
---
Documentation/devicetree/bindings/spi/renesas,sh-msiof.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/s
RZ/G2N (a.k.a. R8A774B1) watchdog implementation is compatible
with R-Car Gen3, therefore add the relevant documentation.
Signed-off-by: Fabrizio Castro
---
Documentation/devicetree/bindings/watchdog/renesas,wdt.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bin
On Thu, 2019-10-03 at 16:47 -0700, Florian Fainelli wrote:
> On 10/3/19 12:39 PM, Nicolas Saenz Julienne wrote:
> > On Thu, 2019-10-03 at 11:08 -0700, Florian Fainelli wrote:
> > > On 10/2/19 4:45 AM, Nicolas Saenz Julienne wrote:
> > > > Currently, in arm_dt_init_cpu_maps(), the hwid of the boot C
On Fri, 2019-10-04 at 10:29 +0200, Rafael J. Wysocki wrote:
> On Fri, Oct 4, 2019 at 10:24 AM Giovanni Gherdovich
> wrote:
> >
> > On Thu, 2019-10-03 at 20:31 -0700, Srinivas Pandruvada wrote:
> > > On Thu, 2019-10-03 at 20:05 +0200, Rafael J. Wysocki wrote:
> > > > On Wednesday, October 2, 2019
On 03.10.19 18:48, Aneesh Kumar K.V wrote:
> On 10/1/19 8:33 PM, David Hildenbrand wrote:
>> On 01.10.19 16:57, David Hildenbrand wrote:
>>> On 01.10.19 16:40, David Hildenbrand wrote:
From: "Aneesh Kumar K.V"
With altmap, all the resource pfns are not initialized. While initializin
On 03/10/2019 13:19, Andrew Jones wrote:
> On Wed, Oct 02, 2019 at 03:50:28PM +0100, Steven Price wrote:
>> Introduce a paravirtualization interface for KVM/arm64 based on the
>> "Arm Paravirtualized Time for Arm-Base Systems" specification DEN 0057A.
>>
>> This only adds the details about "Stolen
On 03.10.19 23:36, Qian Cai wrote:
> Convert two functions to static inline to get ride of W=1 GCC warnings
> like,
>
> mm/gup.c: In function 'gup_pte_range':
> mm/gup.c:1816:16: warning: variable 'ptem' set but not used
> [-Wunused-but-set-variable]
> pte_t *ptep, *ptem;
> ^~
Add minimal thermal zone for two temperature sensor
One is located close to the DDR and the other one is
located close to the PLLs (between the CPU and GPU)
Acked-by: Martin Blumenstingl
Reviewed-by: Neil Armstrong
Tested-by: Christian Hewitt
Tested-by: Kevin Hilman
Signed-off-by: Guillaume La
Adding the devicetree binding documentation for the Amlogic temperature
sensor found in the Amlogic Meson G12A and G12B SoCs.
Reviewed-by: Rob Herring
Reviewed-by: Amit Kucheria
Tested-by: Christian Hewitt
Tested-by: Kevin Hilman
Signed-off-by: Guillaume La Roque
---
.../bindings/thermal/aml
Add cpu and ddr temperature sensors for G12 Socs
Reviewed-by: Martin Blumenstingl
Reviewed-by: Neil Armstrong
Reviewed-by: Amit Kucheria
Tested-by: Christian Hewitt
Tested-by: Kevin Hilman
Signed-off-by: Guillaume La Roque
---
.../boot/dts/amlogic/meson-g12-common.dtsi| 20 +
Add myself as maintainer for Amlogic Thermal driver.
Reviewed-by: Neil Armstrong
Signed-off-by: Guillaume La Roque
---
MAINTAINERS | 9 +
1 file changed, 9 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 390c3194ee93..bdc30d740342 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@
Amlogic G12A and G12B SoCs integrate two thermal sensors
with the same design. One is located close to the DDR controller
and the other one is located close to the PLLs (between the CPU and GPU).
The calibration data for each of the thermal sensors instance is stored
in a different location within
This patchs series add support of New Amlogic temperature sensor and minimal
thermal zone for SEI510 and ODROID-N2 boards.
First implementation was doing on IIO[1] but after comments i move on thermal
framework.
Formulas and calibration values come from amlogic.
Changes since v6:
- add missing
Add missing #colling-cells field for G12A SoC
Add cooling-map for passive and hot trip point
Tested-by: Christian Hewitt
Tested-by: Kevin Hilman
Reviewed-by: Neil Armstrong
Signed-off-by: Guillaume La Roque
---
arch/arm64/boot/dts/amlogic/meson-g12a.dtsi | 24 +
1 file cha
Add missing #colling-cells field for G12B SoC
Add cooling-map for passive and hot trip point
Tested-by: Christian Hewitt
Tested-by: Kevin Hilman
Reviewed-by: Neil Armstrong
Signed-off-by: Guillaume La Roque
---
arch/arm64/boot/dts/amlogic/meson-g12b.dtsi | 29 +
1 file cha
On 04.10.19 11:00, David Hildenbrand wrote:
> On 03.10.19 18:48, Aneesh Kumar K.V wrote:
>> On 10/1/19 8:33 PM, David Hildenbrand wrote:
>>> On 01.10.19 16:57, David Hildenbrand wrote:
On 01.10.19 16:40, David Hildenbrand wrote:
> From: "Aneesh Kumar K.V"
>
> With altmap, all the
On 10/4/19 8:23 AM, Uwe Kleine-König wrote:
> Hello,
>
> On Thu, Oct 03, 2019 at 09:46:49PM -0700, Yizhuo wrote:
>> Inside function stm32_pwm_config(), variable "psc" and " arr"
>> could be uninitialized if regmap_read() returns -EINVALs.
>> However, they are used later in the if statement to deci
On Thu 2019-10-03 21:56:34, Will Deacon wrote:
> Hi Kees,
>
> On Wed, Oct 02, 2019 at 01:58:46PM -0700, Kees Cook wrote:
> > On Wed, Oct 02, 2019 at 01:35:38PM +0100, Will Deacon wrote:
> > > Calling 'panic()' on a kernel with CONFIG_PREEMPT=y can leave the
> > > calling CPU in an infinite loop, b
On Thu, Oct 03, 2019 at 07:46:06AM -0700, Chris Healy wrote:
> >
> > The iMX6 does not have MMUv2 hardware, it has MMUv1. With MMUv1
> > hardware requires command buffers within the first 2GiB of physical
> > RAM.
> >
> I thought that the i.MX6q has the MMUv1 and GC2000 GPU while the
> i.MX6qp has
On 2019/10/04 10:19, Greg Kroah-Hartman wrote:
> On Fri, Sep 27, 2019 at 07:11:54PM +0900, Benjamin Poirier wrote:
[...]
>
> As this code got moved to staging with the goal to drop it from the
> tree, why are you working on fixing it up? Do you want it moved back
> out of staging into the "real"
On Fri, Oct 04, 2019 at 12:04:46AM +, Dexuan Cui wrote:
> > From: Stefano Garzarella
> > Sent: Friday, September 27, 2019 4:27 AM
> > ...
> > Patch 9 changes the hvs_remote_addr_init(). setting the
> > VMADDR_CID_HOST as remote CID instead of VMADDR_CID_ANY to make
> > the choice of transport
On Fri, Oct 4, 2019 at 10:52 AM Giovanni Gherdovich wrote:
>
> On Fri, 2019-10-04 at 10:29 +0200, Rafael J. Wysocki wrote:
> > On Fri, Oct 4, 2019 at 10:24 AM Giovanni Gherdovich
> > wrote:
> > >
> > > On Thu, 2019-10-03 at 20:31 -0700, Srinivas Pandruvada wrote:
> > > > On Thu, 2019-10-03 at 20
On Fri, Oct 4, 2019 at 10:02 AM Walter Wu wrote:
>
> On Fri, 2019-10-04 at 12:42 +0800, Walter Wu wrote:
> > On Thu, 2019-10-03 at 16:53 +0200, Dmitry Vyukov wrote:
> > > On Thu, Oct 3, 2019 at 3:51 PM Walter Wu
> > > wrote:>
> > > >
> > > > static void print_error_description(struct kasan_acce
On Fri, Oct 04, 2019 at 03:01:51AM +, Michael Kelley wrote:
> From: Roman Kagan Sent: Thursday, October 3, 2019 5:53
> AM
> > >
> > > AFAIU you're trying to mirror native_x2apic_icr_write() here but this is
> > > different from what hv_apic_icr_write() does
> > > (SET_APIC_DEST_FIELD(id)).
>
On 2019-10-03 16:36:08 [-0400], Waiman Long wrote:
> The check_preemption_disabled() function uses cpumask_equal() to see
> if the task is bounded to the current CPU only. cpumask_equal() calls
> memcmp() to do the comparison. As x86 doesn't have __HAVE_ARCH_MEMCMP,
> the slow memcmp() function in
On 9/29/19 10:00 PM, Jernej Skrabec wrote:
> These helpers are used by stateless codecs when they support multiple
> slices per frame and hold capture buffer flag is set. It's expected that
> all such codecs will use this code.
>
> Signed-off-by: Jernej Skrabec
> ---
> drivers/media/v4l2-core/v4
Hi Manivannan,
On Thu, Oct 03, 2019 at 03:25:03PM +0530, Manivannan Sadhasivam wrote:
> Add driver for Sony IMX290 CMOS image sensor driver. The driver only
> supports I2C interface for programming and MIPI CSI-2 for sensor output.
>
> Signed-off-by: Manivannan Sadhasivam
Could you remove the u
write_seqcountbeqin => write_seqcount_begin
Signed-off-by: Mukesh Ojha
---
include/linux/seqlock.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/linux/seqlock.h b/include/linux/seqlock.h
index bcf4cf2..370ef8f 100644
--- a/include/linux/seqlock.h
+++ b/include/linux
On Thu, Oct 03, 2019 at 02:30:10PM +0300, Mike Rapoport wrote:
> On Thu, Oct 03, 2019 at 09:49:14AM +0100, Russell King - ARM Linux admin
> wrote:
> > On Thu, Oct 03, 2019 at 08:34:52AM +0300, Mike Rapoport wrote:
> > > (trimmed the CC)
> > >
> > > On Wed, Oct 02, 2019 at 06:14:11AM -0500, Adam F
1 - 100 of 841 matches
Mail list logo
