Hi Laurent, all,
On 6/24/20 7:01 PM, Laurent Pinchart wrote:
Hi Jacopo,
On Wed, Jun 24, 2020 at 09:53:07AM +0200, Jacopo Mondi wrote:
On Tue, Jun 16, 2020 at 12:00:15PM +0200, Ramzi BEN MEFTAH wrote:
From: Steve Longerbeam
+Niklas, +Laurent
Niklas, Laurent, how does this play with CAP_IO
On 6/25/20 10:31 AM, Jason Gunthorpe wrote:
On Thu, Jun 25, 2020 at 10:25:38AM -0700, Ralph Campbell wrote:
Making sure to include linux-mm and Bharata B Rao for IBM's
use of migrate_vma*().
On 6/24/20 11:10 AM, Ralph Campbell wrote:
On 6/24/20 12:23 AM, Christoph Hellwig wrote:
On Mon, Ju
On 25/06/2020 16:29, Stefan Hajnoczi wrote:
On Wed, Jun 24, 2020 at 05:02:54PM +0300, Paraschiv, Andra-Irina wrote:
On 23/06/2020 11:56, Stefan Hajnoczi wrote:
On Mon, Jun 22, 2020 at 11:03:12PM +0300, Andra Paraschiv wrote:
+/* User memory region flags */
+
+/* Memory region for enclave ge
(Adding Jernej, seems I haven't Cced him!)
On Thu, 2020-06-25 at 10:53 -0400, Nicolas Dufresne wrote:
> Le mardi 23 juin 2020 à 15:28 -0300, Ezequiel Garcia a écrit :
> > Align v4l2_h264_reference to 32-bits, giving some room
> > for future extensions.
> >
> > Signed-off-by: Ezequiel Garcia
> >
On Thu, Jun 25, 2020 at 05:36:13PM +0100, Lee Jones wrote:
> Looks as though 9f75ce666199 ("regulator: da9063: fix suspend") failed
$ git show 9f75ce666199
fatal: ambiguous argument '9f75ce666199': unknown revision or path not in the
working tree.
You should probably CC this to the authors of th
On Thu, Jun 25, 2020 at 09:25:40AM -0700, Sean Christopherson wrote:
> On Thu, Jun 25, 2020 at 10:09:13AM +0200, Paolo Bonzini wrote:
> > On 25/06/20 08:15, Sean Christopherson wrote:
> > > IMO, kvm_cpuid() is simply buggy. If KVM attempts to access a
> > > non-existent
> > > MSR then it darn wel
On Thu, Jun 25, 2020 at 7:09 PM Saravana Kannan wrote:
>
> On Thu, Jun 25, 2020 at 10:03 AM Rafael J. Wysocki wrote:
> >
> > On Thu, Jun 25, 2020 at 7:01 PM Saravana Kannan
> > wrote:
> > >
> > > On Thu, Jun 25, 2020 at 9:58 AM Rafael J. Wysocki
> > > wrote:
> > > >
> > > > On Thu, Jun 25, 20
Le jeudi 25 juin 2020 à 14:42 -0300, Ezequiel Garcia a écrit :
> (Adding Jernej, seems I haven't Cced him!)
>
> On Thu, 2020-06-25 at 10:53 -0400, Nicolas Dufresne wrote:
> > Le mardi 23 juin 2020 à 15:28 -0300, Ezequiel Garcia a écrit :
> > > Align v4l2_h264_reference to 32-bits, giving some room
On Thu, Jun 25, 2020 at 10:47 AM Rafael J. Wysocki wrote:
>
> On Thu, Jun 25, 2020 at 7:09 PM Saravana Kannan wrote:
> >
> > On Thu, Jun 25, 2020 at 10:03 AM Rafael J. Wysocki
> > wrote:
> > >
> > > On Thu, Jun 25, 2020 at 7:01 PM Saravana Kannan
> > > wrote:
> > > >
> > > > On Thu, Jun 25, 2
On Thu, 2020-06-25 at 09:52 +0200, Hans Verkuil wrote:
> On 23/06/2020 20:28, Ezequiel Garcia wrote:
> > The H264 interface is now ready to be part of the official
> > public API.
> >
> > In addition, sanitize header includes.
> >
> > Signed-off-by: Ezequiel Garcia
> > ---
> > drivers/staging/m
- On Jun 25, 2020, at 9:44 AM, rostedt rost...@goodmis.org wrote:
> From: "Steven Rostedt (VMware)"
>
[...]
> Here's the design of this solution:
>
> All this is per cpu, and only needs to worry about nested events (not
> parallel events).
>
> The players:
>
> write_tail: The index in the
Hi Linus,
First rc pull request
Collected fixes from the last four weeks, fixing several regressions
in areas that had big changes this cycle.
Thanks,
Jason
The following changes since commit b3a9e3b9622ae10064826dccb4f7a52bd88c7407:
Linux 5.8-rc1 (2020-06-14 12:45:04 -0700)
are available i
On Thu, 25 Jun 2020 at 10:16, Marc Zyngier wrote:
>
> On 2020-06-25 06:03, kernel test robot wrote:
> > Hi David,
> >
> > Thank you for the patch! Perhaps something to improve:
> >
> > [auto build test WARNING on linus/master]
> > [also build test WARNING on v5.8-rc2 next-20200624]
> > [cannot app
Add the OST bindings for the X1 SoC from Ingenic.
Tested-by: 周正 (Zhou Zheng)
Signed-off-by: 周琰杰 (Zhou Yanjie)
---
Notes:
v1->v2:
No change.
.../devicetree/bindings/timer/ingenic,ost.yaml | 62 ++
include/dt-bindings/clock/ingenic,ost.h| 12 +
X1000 and SoCs after X1000 (such as X1500 and X1830) had a separate
OST, it no longer belongs to TCU. This driver will register both a
clocksource and a sched_clock to the system.
Tested-by: 周正 (Zhou Zheng)
Co-developed-by: 漆鹏振 (Qi Pengzhen)
Signed-off-by: 漆鹏振 (Qi Pengzhen)
Signed-off-by: 周琰杰 (
v1->v2:
Fix compile warnings.
周琰杰 (Zhou Yanjie) (2):
dt-bindings: timer: Add Ingenic X1000 OST bindings.
clocksource: Ingenic: Add support for the Ingenic X1000 OST.
.../devicetree/bindings/timer/ingenic,ost.yaml | 62 +++
drivers/clocksource/Kconfig| 19 +-
dri
On Thu, Jun 25, 2020 at 06:30:50PM +0100, Matthew Wilcox wrote:
> On Thu, Jun 25, 2020 at 07:14:16PM +0200, Borislav Petkov wrote:
> > On Thu, Jun 18, 2020 at 01:08:32AM +0300, Jarkko Sakkinen wrote:
> > > diff --git a/mm/mprotect.c b/mm/mprotect.c
> > > index ce8b8a5eacbb..f7731dc13ff0 100644
> >
After running my ring buffer benchmark on this update, it went from
55ns to 85ns per event. A 30ns increase! At first I freaked out, but
then noticed that I unnecessarily take the time stamp counter twice,
which is the most expensive operation.
Here's a diff to my patch (I'll send a v2 later) that
This pinout is common for every 8992-based device and
should therefore reside in the SoC device tree.
Also convert addresses into phandles.
Signed-off-by: Konrad Dybcio
---
.../boot/dts/qcom/msm8992-bullhead-rev-101.dts | 13 -
1 file changed, 4 insertions(+), 9 deletions(-)
d
This commit ensures the correct IRQ type is set
and disables the device by default.
The mmc-hs400-1_8v property is also moved to
Bullhead as it might not be present on all boards.
The node has been renamed to sdhci@ instead of mmc@
and the phandle was changed to sdhc_1 to comply with
the newer DTS
Following changes have been made:
- remove name, compatible and msm-id
- wrap clocks in clocks{}
- order nodes by name and by address
- clock_gcc -> gcc
- msmgpio -> tlmm
- retire msm8992-pins.dtsi
- add some of the missing pins
- make comments C-style
- make apcs a mailbox
Signed-off-by: Konrad
changes since v2:
- drop some superseeded patches
- reduce the amount of commits
- modernize the 8992 dts
- add libra and talkman DTSes
- do some housekeeping and fix minor issues
Tested on Libra and Talkman. Bullhead *shouldn't* break.
Depends on my 8994 patchset [1] (because of compatibles
and
Add support for I2C to enable support for peripherals
such as touchscreens or sensors. Also add BLSP_UART2 interface.
Please note that the naming scheme follows downstream and as
abominable as it is, that's what we get.
Signed-off-by: Konrad Dybcio
---
arch/arm64/boot/dts/qcom/msm8992.dtsi | 15
On Thu, 25 Jun 2020 09:42:34 -0700
Korben Rusek wrote:
> Great work! I'm not exactly qualified to review the code, but the
> logic seems correct. I'm curious how unlikely a zero delta is now and
> how you quantify it. Also does it negate the patch that I emailed out
Actually, in all my stress te
This commit adds cpu nodes for all 6 cores
present on this SoC and the cpu-map.
Signed-off-by: Konrad Dybcio
---
arch/arm64/boot/dts/qcom/msm8992.dtsi | 82 ---
1 file changed, 75 insertions(+), 7 deletions(-)
diff --git a/arch/arm64/boot/dts/qcom/msm8992.dtsi
b/arch/ar
This commit adds support for the Xiaomi Libra (Mi 4C)
smartphone. It's based on the Qualcomm msm8992 SoC.
It currently supports:
* Screen console from bootloader
* SDHCI
* Regulator configuration
* Serial console
* I2C
Signed-off-by: Konrad Dybcio
---
arch/arm64/boot/dts/qcom/Makefile
This SoC's firmware does not fully support the PSCI
spec, but it's good enough to bring the cores up.
Signed-off-by: Konrad Dybcio
---
arch/arm64/boot/dts/qcom/msm8992.dtsi | 5 +
1 file changed, 5 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/msm8992.dtsi
b/arch/arm64/boot/dts/qcom/
This lets us use clocks provided by RPM.
Signed-off-by: Konrad Dybcio
---
arch/arm64/boot/dts/qcom/msm8992.dtsi | 5 +
1 file changed, 5 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/msm8992.dtsi
b/arch/arm64/boot/dts/qcom/msm8992.dtsi
index bc3acc0cf9bf..188fff2095f1 100644
--- a/ar
Add device tree support for the Microsoft Lumia 950 smartphone.
It is based on msm8992 and supports booting Linux via a custom
EDK2 port.
Currently it supports:
* Screen console via EFIFB
* Booting via EFI_STUB
* SDHCI
* I2C
* PSCI core bringup
Please note that there is an implementation of EL2 s
Signed-off-by: Konrad Dybcio
---
arch/arm64/boot/dts/qcom/msm8992.dtsi | 6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/msm8992.dtsi
b/arch/arm64/boot/dts/qcom/msm8992.dtsi
index f780cd39ded6..aee33ed61858 100644
--- a/arch/arm64/boot/dts/qcom/msm8992.dtsi
+++ b
Add the property required for the bootloader to select
the correct device tree blob. It has been removed from
the SoC device tree as it should be set on a per-device
basis.
Signed-off-by: Konrad Dybcio
---
arch/arm64/boot/dts/qcom/msm8992-bullhead-rev-101.dts | 1 +
1 file changed, 1 insertion(+
Add the PMU so we can get proper perf event support on this SoC.
Signed-off-by: Konrad Dybcio
---
arch/arm64/boot/dts/qcom/msm8992.dtsi | 5 +
1 file changed, 5 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/msm8992.dtsi
b/arch/arm64/boot/dts/qcom/msm8992.dtsi
index e8b801813f14..c4c9
Add SPMI PMIC arbiter device to communicate with PMICs
attached to SPMI bus.
Signed-off-by: Konrad Dybcio
---
arch/arm64/boot/dts/qcom/msm8992.dtsi | 16
1 file changed, 16 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/msm8992.dtsi
b/arch/arm64/boot/dts/qcom/msm8992.dtsi
changes since v2:
- fix commit messages (sorry!)
changes since v1:
- drop some superseeded patches
- reduce the amount of commits
- modernize the 8992 dts
- add libra and talkman DTSes
- do some housekeeping and fix minor issues
Tested on Libra and Talkman. Bullhead *shouldn't* break.
Depends on
Add the property required for the bootloader to select
the correct device tree blob. It has been removed from
the SoC device tree as it should be set on a per-device
basis.
Signed-off-by: Konrad Dybcio
---
arch/arm64/boot/dts/qcom/msm8992-bullhead-rev-101.dts | 1 +
1 file changed, 1 insertion(+
Following changes have been made:
- remove name, compatible and msm-id
- wrap clocks in clocks{}
- order nodes by name and by address
- clock_gcc -> gcc
- msmgpio -> tlmm
- retire msm8992-pins.dtsi
- add some of the missing pins
- make comments C-style
- make apcs a mailbox
Signed-off-by: Konrad
Signed-off-by: Konrad Dybcio
---
arch/arm64/boot/dts/qcom/msm8992.dtsi | 6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/msm8992.dtsi
b/arch/arm64/boot/dts/qcom/msm8992.dtsi
index f780cd39ded6..aee33ed61858 100644
--- a/arch/arm64/boot/dts/qcom/msm8992.dtsi
+++ b
This lets us use clocks provided by RPM.
Signed-off-by: Konrad Dybcio
---
arch/arm64/boot/dts/qcom/msm8992.dtsi | 5 +
1 file changed, 5 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/msm8992.dtsi
b/arch/arm64/boot/dts/qcom/msm8992.dtsi
index bc3acc0cf9bf..188fff2095f1 100644
--- a/ar
This pinout is common for every 8992-based device and
should therefore reside in the SoC device tree.
Also convert addresses into phandles.
Signed-off-by: Konrad Dybcio
---
.../boot/dts/qcom/msm8992-bullhead-rev-101.dts | 13 -
1 file changed, 4 insertions(+), 9 deletions(-)
d
This commit adds support for the Xiaomi Libra (Mi 4C)
smartphone. It's based on the Qualcomm msm8992 SoC.
It currently supports:
* Screen console from bootloader
* SDHCI
* Regulator configuration
* Serial console
* I2C
Signed-off-by: Konrad Dybcio
---
arch/arm64/boot/dts/qcom/Makefile
Add support for I2C to enable support for peripherals
such as touchscreens or sensors. Also add BLSP_UART2 interface.
Please note that the naming scheme follows downstream and as
abominable as it is, that's what we get.
Signed-off-by: Konrad Dybcio
---
arch/arm64/boot/dts/qcom/msm8992.dtsi | 15
> Andres Beltran (3):
> Drivers: hv: vmbus: Add vmbus_requestor data structure for VMBus
> hardening
> scsi: storvsc: Use vmbus_requestor to generate transaction ids for
> VMBus hardening
> hv_netvsc: Use vmbus_requestor to generate transaction ids for VMBus
> hardening
For the s
Add SPMI PMIC arbiter device to communicate with PMICs
attached to SPMI bus.
Signed-off-by: Konrad Dybcio
---
arch/arm64/boot/dts/qcom/msm8992.dtsi | 16
1 file changed, 16 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/msm8992.dtsi
b/arch/arm64/boot/dts/qcom/msm8992.dtsi
Add device tree support for the Microsoft Lumia 950 smartphone.
It is based on msm8992 and supports booting Linux via a custom
EDK2 port.
Currently it supports:
* Screen console via EFIFB
* Booting via EFI_STUB
* SDHCI
* I2C
* PSCI core bringup
Please note that there is an implementation of EL2 s
Add the PMU so we can get proper perf event support on this SoC.
Signed-off-by: Konrad Dybcio
---
arch/arm64/boot/dts/qcom/msm8992.dtsi | 5 +
1 file changed, 5 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/msm8992.dtsi
b/arch/arm64/boot/dts/qcom/msm8992.dtsi
index e8b801813f14..c4c9
This commit adds cpu nodes for all 6 cores
present on this SoC and the cpu-map.
Signed-off-by: Konrad Dybcio
---
arch/arm64/boot/dts/qcom/msm8992.dtsi | 82 ---
1 file changed, 75 insertions(+), 7 deletions(-)
diff --git a/arch/arm64/boot/dts/qcom/msm8992.dtsi
b/arch/ar
This SoC's firmware does not fully support the PSCI
spec, but it's good enough to bring the cores up.
Signed-off-by: Konrad Dybcio
---
arch/arm64/boot/dts/qcom/msm8992.dtsi | 5 +
1 file changed, 5 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/msm8992.dtsi
b/arch/arm64/boot/dts/qcom/
Simplify meson8b_init_rgmii_tx_clk() by using struct clk_parent_data to
initialize the clock parents. No functional changes intended.
Signed-off-by: Martin Blumenstingl
---
.../ethernet/stmicro/stmmac/dwmac-meson8b.c | 49 +++
1 file changed, 17 insertions(+), 32 deletions(-)
This commit ensures the correct IRQ type is set
and disables the device by default.
The mmc-hs400-1_8v property is also moved to
Bullhead as it might not be present on all boards.
The node has been renamed to sdhci@ instead of mmc@
and the phandle was changed to sdhc_1 to comply with
the newer DTS
Hi Marc,
On 24/06/20 20:57, Marc Zyngier wrote:
> For as long as SMP ARM has existed, IPIs have been handled as
> something special. The arch code and the interrupt controller exchange
> a couple of hooks (one to generate an IPI, another to handle it).
>
> Although this is perfectly manageable, it
On 24/06/20 20:57, Marc Zyngier wrote:
> @@ -958,9 +958,76 @@ void handle_IPI(int ipinr, struct pt_regs *regs)
>
> if ((unsigned)ipinr < NR_IPI)
> trace_ipi_exit_rcuidle(ipi_types[ipinr]);
> +}
> +
> +/* Legacy version, should go away once all irqchips have been converted */
>
On 24/06/20 20:57, Marc Zyngier wrote:
> @@ -696,9 +696,76 @@ void handle_IPI(int ipinr, struct pt_regs *regs)
>
> if ((unsigned)ipinr < NR_IPI)
> trace_ipi_exit_rcuidle(ipi_types[ipinr]);
> +}
> +
> +/* Legacy version, should go away once all irqchips have been converted */
>
On 24/06/20 20:58, Marc Zyngier wrote:
> @@ -852,8 +841,7 @@ void arch_send_wakeup_ipi_mask(const struct cpumask *mask)
> #ifdef CONFIG_IRQ_WORK
> void arch_irq_work_raise(void)
> {
> - if (__smp_cross_call)
> - smp_cross_call(cpumask_of(smp_processor_id()), IPI_IRQ_WORK);
> +
On Thu, Jun 25, 2020 at 1:34 AM Will Deacon wrote:
>
> On Thu, Jun 25, 2020 at 09:16:03AM +0100, Marc Zyngier wrote:
> > On 2020-06-25 06:03, kernel test robot wrote:
> > > Hi David,
> > >
> > > Thank you for the patch! Perhaps something to improve:
> > >
> > > [auto build test WARNING on linus/ma
On 24/06/20 20:58, Marc Zyngier wrote:
> @@ -801,26 +802,15 @@ void show_ipi_list(struct seq_file *p, int prec)
> unsigned int cpu, i;
>
> for (i = 0; i < NR_IPI; i++) {
> + unsigned int irq = irq_desc_get_irq(ipi_desc[i]);
> seq_printf(p, "%*s%u:%s", prec -
On 24/06/20 20:58, Marc Zyngier wrote:
> Change the way we deal with GICv3 SGIs by turning them into proper
> IRQs, and calling into the arch code to register the interrupt range
> instead of a callback.
>
> Signed-off-by: Marc Zyngier
> ---
> drivers/irqchip/irq-gic-v3.c | 81 +
Hi Rishabh,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on linux/master]
[also build test WARNING on linus/master v5.8-rc2 next-20200625]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use as
On Thu, Jun 25, 2020 at 09:22:26AM -0700, Sami Tolvanen wrote:
> On Thu, Jun 25, 2020 at 09:47:16AM +0200, Peter Zijlstra wrote:
> > Right, then we need to make --no-vmlinux work properly when
> > !DEBUG_ENTRY, which I think might be buggered due to us overriding the
> > argument when the objname
On Thu, Jun 25, 2020 at 07:23:19PM +0200, Borislav Petkov wrote:
> Also, you had all patches until now split nice and logically doing one
> thing only.
>
> But this one is huge. Why?
>
> Why can't you split out the facilities which the driver uses: encl.[ch]
> into a patch, then ioctl.c into a se
On Thu, 25 Jun 2020 13:55:07 -0400 (EDT)
Mathieu Desnoyers wrote
> > Here's the design of this solution:
> >
> > All this is per cpu, and only needs to worry about nested events (not
> > parallel events).
> >
> > The players:
> >
> > write_tail: The index in the buffer where new events can be
On Tue, Jun 23, 2020 at 10:19:03AM +0200, Roger Pau Monné wrote:
> CAUTION: This email originated from outside of the organization. Do not click
> links or open attachments unless you can confirm the sender and know the
> content is safe.
>
>
>
> On Tue, Jun 23, 2020 at 12:43:14AM +, Ancha
Dear Friend
I sourced your email from a human resource profile database in the
chamber, my name is Mr.Ibrahim Zufar. Account officer to late Mr. Hussein
Mubarak from Kuwait who is a gold merchant Agent here in Ouagadougou
Burkina Faso, a well known Philanthropist before he died.
He made a Wi
On Thu, 25 Jun 2020, Mark Brown wrote:
> On Thu, Jun 25, 2020 at 05:36:06PM +0100, Lee Jones wrote:
>
> > /**
> > * devm_regulator_register - Resource managed regulator_register()
> > + * @dev: device for regulator "consumer"
> > * @regulator_desc: regulator to register
> > * @config: runt
On Thu, 25 Jun 2020, Mark Brown wrote:
> On Thu, Jun 25, 2020 at 05:36:07PM +0100, Lee Jones wrote:
> > Kerneldoc validation gets confused if syntax isn't "@.*: ".
> >
> > Adding the missing colons squashes the following W=1 warnings:
>
> > * of_check_coupling_data - Parse rdev's coupling prop
On Thu, 25 Jun 2020, Mark Brown wrote:
> On Thu, Jun 25, 2020 at 05:36:13PM +0100, Lee Jones wrote:
> > Looks as though 9f75ce666199 ("regulator: da9063: fix suspend") failed
>
> $ git show 9f75ce666199
> fatal: ambiguous argument '9f75ce666199': unknown revision or path not in the
> working tre
On 25.06.2020 20:13, Jiri Olsa wrote:
> On Thu, Jun 25, 2020 at 07:01:08PM +0300, Alexey Budankov wrote:
>
> SNIP
>
Well, ok.
I will rename process_interval() to __process_interval() and
then print_interval() to process_interval().
Regarding timeout let's have
On 25/06/20 18:25, Sean Christopherson wrote:
> I get the "what" of the change, and even the "why" to some extent, but I
> dislike the idea of supporting/encouraging blind reads/writes to MSRs.
> Blind writes are just asking for problems, and suppressing warnings on reads
> is almost guaranteed to
On Thu, Jun 25, 2020 at 11:34:48AM -0700, Sean Christopherson wrote:
> Hmm, I think the most reasonable way to break up this beast would be to
> incrementally introduce functionality. E.g. four or so patches, one for
> each ioctl() of ENCLAVE_CREATE, ENCLAVE_ADD_PAGES, ENCLAVE_INIT and
> ENCLAVE_S
On Thu, Jun 25, 2020 at 07:42:18PM +0100, Lee Jones wrote:
> On Thu, 25 Jun 2020, Mark Brown wrote:
> > On Thu, Jun 25, 2020 at 05:36:06PM +0100, Lee Jones wrote:
> > > + * @dev: device for regulator "consumer"
> > That's an odd style you're using in your "change" here - why the quotes?
> It's t
Hi,
On Wed, Jun 24, 2020 at 11:54 PM Stephen Boyd wrote:
>
> Quoting Doug Anderson (2020-06-24 20:35:16)
> > Hi,
> >
> > On Wed, Jun 24, 2020 at 6:25 PM Stephen Boyd wrote:
> > >
> > > Quoting Douglas Anderson (2020-06-24 17:08:04)
> > > > The geni SPI protocol appears to have been designed with
Basically, consider .text.{hot|unlikely|unknown}.* part of .text, too.
When compiling with profiling information (collected via PGO
instrumentations or AutoFDO sampling), Clang will separate code into
.text.hot, .text.unlikely, or .text.unknown sections based on profiling
information. After D79600
On Thu, Jun 25, 2020 at 12:31:16PM +0100, Matthew Wilcox (Oracle) wrote:
> I want a memalloc_nowait like we have memalloc_noio and memalloc_nofs
> for an upcoming patch series, and Jens also wants it for non-blocking
> io_uring. It turns out we already have dm-bufio which could benefit
> from mema
On Thu, Jun 18, 2020 at 01:08:33AM +0300, Jarkko Sakkinen wrote:
> Subject: Re: [PATCH v33 11/21] x86/sgx: Linux Enclave Driver
^
Add
> Intel Software Guard eXtensions (SGX) is a set of CPU instructions that
> can b
Hi Lee.
On Thu, Jun 25, 2020 at 09:03:37AM +0100, Lee Jones wrote:
> On Wed, 24 Jun 2020, Sam Ravnborg wrote:
>
> > Hi Lee.
> >
> > On Wed, Jun 24, 2020 at 04:43:21PM +0100, Lee Jones wrote:
> > > On Wed, 24 Jun 2020, Sam Ravnborg wrote:
> > >
> > > > Hi Lee.
> > > >
> > > > On Wed, Jun 24, 20
> -Original Message-
> From: Andres Beltran
> Sent: Thursday, June 25, 2020 11:37 AM
> To: KY Srinivasan ; Haiyang Zhang
> ; Stephen Hemminger ;
> wei@kernel.org
> Cc: linux-hyp...@vger.kernel.org; linux-kernel@vger.kernel.org; Michael
> Kelley ; parri.and...@gmail.com; Andres Beltr
Hi!
> [ Upstream commit 3ef9d5073b552d56bd6daf2af1e89b7e8d4df183 ]
>
> The microphone-jack state needs to be masked in a case of a 4-pin jack
> when microphone and ground pins are shorted. Presence of nvidia,headset
> tells that WM8903 CODEC driver should mask microphone's status if short
> circu
On Thu, Jun 25, 2020 at 10:11:07AM -0700, Divya Indi wrote:
> Hi Leon,
>
> Please find my comments inline -
>
> On 6/25/20 3:09 AM, Leon Romanovsky wrote:
> > On Tue, Jun 23, 2020 at 07:13:09PM -0700, Divya Indi wrote:
> >> Commit 3ebd2fd0d011 ("IB/sa: Put netlink request into the request list
> >
Hi!
> Currently mute LED and micmute LED share the same GPIO polarity.
>
> So split the polarity for mute and micmute, in case they have different
> polarities.
> +++ b/sound/pci/hda/patch_realtek.c
> @@ -94,6 +94,7 @@ struct alc_spec {
>
> /* mute LED for HP laptops, see alc269_fixup_mi
On Thu, 25 Jun 2020 13:55:07 -0400 (EDT)
Mathieu Desnoyers wrote:
> What worries me about this "optimization" is what happens in a multi-nesting
> scenario.
> If we just fallback to a full timestamp as soon as nesting is detected,
> things become
> really simple for multiple nesting. However u
On Thu, Jun 25, 2020 at 9:25 PM Enric Balletbo i Serra
wrote:
>
> Remove the ambiguity with GPL-2.0 and use an explicit GPL-2.0-only
> tag.
Is there any? Last time IIRC Greg told me that in the kernel the old
and new variants are okay.
...
> 28 files changed, 28 insertions(+), 28 deletions(-)
On Thu, 25 Jun 2020 13:55:07 -0400 (EDT)
Mathieu Desnoyers wrote:
> What are the types used for before_stamp and write_stamp ? If those
> are 64-bit integers, how does sharing them between nested contexts
> work on 32-bit architectures ?
BTW, I forgot to state in either of my two emails, THANK Y
On Wed, 24 Jun 2020 12:49:25 -0500, Dan Murphy wrote:
> This series fixes issues tih the shut-down gpio device tree allocation and a
> code format issue found.
>
> While working on a project slot programming for the tx and rx paths needed to
> be
> enabled. In addition the vsense slot programmin
On Wed, Jun 24, 2020 at 1:25 PM Lakshmi Ramasubramanian
wrote:
>
> On 6/23/20 12:58 PM, Mimi Zohar wrote:
>
> Hi Steve\Paul,
>
> >> Sample audit messages:
> >>
> >> [6.303048] audit: type=1804 audit(1592506281.627:2): pid=1 uid=0
> >> auid=4294967295 ses=4294967295 subj=kernel op=measuring_key
'lynx->pci_device' is allocated with a size of RCV_BUFFER_SIZE. This is to
say (16 * 1024).
Pass the same size when it is freed.
Fixes: 286468210d83 ("firewire: new driver: nosy - IEEE 1394 traffic sniffer")
Signed-off-by: Christophe JAILLET
---
v2: move the #define RCV_BUFFER_SIZE at the top of
Attempting to clean-up W=1 kernel builds, which are currently
overwhelmingly riddled with niggly little warnings.
Resent to include patch contributors/maintainers/MLs.
Lee Jones (10):
regulator: consumer: Supply missing prototypes for 3 core functions
regulator: devres: Fix issues with kernel
Kerneldoc expects function arguments to be in the format '@.*:'. If
this format is not followed the kerneldoc tooling/parsers/validators
get confused.
Fixes the following W=1 warning(s):
drivers/regulator/wm8350-regulator.c:1234: warning: Function parameter or
member 'wm8350' not described in
Nothing about this comment identifies it as a kerneldoc header.
They're missing all of their struct's property descriptions and
the correct 'struct *' header.
Fixes the following W=1 warning(s):
drivers/regulator/cpcap-regulator.c:99: warning: cannot understand function
prototype: 'struct cpcap
Provide descriptions for some missing function args and
rename others to match the names used.
Fixes the following W=1 warning(s):
drivers/regulator/devres.c:187: warning: Function parameter or member 'dev'
not described in 'devm_regulator_register'
drivers/regulator/devres.c:226: warning: Fun
Used primarily for the AB8540 which lost support in early 2018.
It is now deemed safe to remove this legacy data structure.
Also fixes W=1 issue:
drivers/regulator/ab8500.c:88: warning: Function parameter or member
'expand_register' not described in 'ab8500_regulator_info'
Cc: Linus Walleij
Nothing about this comment identifies it as a kerneldoc header.
It's missing all of it's function argument descriptions and the
correct function header.
Fixes the following W=1 warning(s):
drivers/regulator/max14577-regulator.c:166: warning: Function parameter or
member 'max14577' not described
It's okay to not check the return value that you're not conserned
about, however it is not okay to assign a variable and not check or
use the result.
Fixes W=1 warnings(s):
drivers/regulator/cpcap-regulator.c:172:13: warning: variable ‘ignore’ set but
not used [-Wunused-but-set-variable]
172 |
regulator_suspend_enable(), regulator_suspend_disable() and
regulator_set_suspend_voltage() are all exported members of the
API, but are all missing prototypes.
Fixes the following W=1 warning(s):
drivers/regulator/core.c:3805:5: warning: no previous prototype for
‘regulator_suspend_enable’ [-W
There isn't any code present within the current kernel to
override this 'weak' function. Besides returning '0', which
is never checked anyway, the whole function appears to be
superfluous.
Consequently fixes W=1 warning:
drivers/regulator/dbx500-prcmu.c:113:27: warning: no previous prototype fo
Looks as though 99f75ce666199 ("regulator: da9063: fix suspend") failed
to clean-up all of the existing .suspend variable initialisations.
This has led to some 'initilized field overwritten' issues now present
in W=1 builds.
This patch squashes the following build warnings:
In file included from
Kerneldoc validation gets confused if syntax isn't "@.*: ".
Adding the missing colons squashes the following W=1 warnings:
Cc: Rajendra Nayak
Signed-off-by: Lee Jones
---
drivers/regulator/of_regulator.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/regulator/of_r
Hi "Matthew,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on tip/sched/core]
[also build test ERROR on dm/for-next linus/master v5.8-rc2]
[cannot apply to xfs-linux/for-next next-20200625]
[If your patch is applied to the wrong git tree, kindly drop us a note
On 2020-06-25 21:30, Guenter Roeck wrote:
On Mon, Jun 22, 2020 at 11:50:52AM +0530, Sai Prakash Ranjan wrote:
On 2020-06-21 13:03, Bjorn Andersson wrote:
> On Tue 16 Jun 23:56 PDT 2020, Sai Prakash Ranjan wrote:
>
> > Hi Bjorn,
> >
>
> Hi Sai,
>
> > On 2020-02-12 03:54, Sai Prakash Ranjan wrote:
On Thu, 25 Jun 2020 16:01:23 +0530, Sai Prakash Ranjan wrote:
> QCOM KRYO{3,4}XX silver/LITTLE CPU cores are based on
> Cortex-A55 and are SSB safe, hence add them to SSB
> safelist -> arm64_ssb_cpus[].
Applied to arm64 (for-next/fixes), thanks!
[1/1] arm64: Add KRYO{3,4}XX silver CPU cores to SS
On 6/24/2020 5:21 AM, Vinod Koul wrote:
> Hi Wesley,
>
> On 21-05-20, 18:50, Wesley Cheng wrote:
>> Allow for the PHY to be put into a powered down state when possible.
>> Add the required suspend and resume callbacks, which will determine
>> what resources can be turned off depending on the ca
This series converts QCOM watchdog timer bindings to YAML. Also
it adds the missing SoC-specific compatible for QCS404, SC7180,
SDM845 and SM8150 SoCs.
v1:
https://lore.kernel.org/lkml/cover.1576211720.git.saiprakash.ran...@codeaurora.org/
v2:
https://lore.kernel.org/lkml/cover.1580570160.git.sa
601 - 700 of 1104 matches
Mail list logo
