Hi,
- convert DT binding to YAML
- add DT property to disable charger detection
(Errata i2075 for AM65 SR1.0)
Changelog:
v2
- Address Rob's comments on YAML schema.
cheers,
-roger
Bin Liu (1):
dts: am65: add ti,dis-chg-det-quirk flag to usb phy nodes
Roger Quadros (3):
dt-binding: phy:
On Tue, Jun 02, 2020 at 12:59:52PM +0800, Lianbo Jiang wrote:
> So, here, let's simplify the logic to improve code readability. If the
> KEXEC_SIG_FORCE enabled or kexec lockdown enabled, signature verification
> is mandated. Otherwise, we lift the bar for any kernel image.
>
> Signed-off-by:
On Tue, Jun 02, 2020 at 09:23:57PM +1000, Michael Ellerman wrote:
> Markus Elfring writes:
> Please just remove the message instead, it's a tiny allocation that's
> unlikely to ever fail, and the caller will print an error anyway.
> >>>
> >>> How do you think about to take another look
hi Avri
thanks review.
On Mon, 2020-06-01 at 06:25 +, Avri Altman wrote:
> Hi,
>
> > If param_offset is not 0, the memcpy length shouldn't be the
> > true descriptor length.
> >
> > Fixes: a4b0e8a4e92b ("scsi: ufs: Factor out
> > ufshcd_read_desc_param")
> > Signed-off-by: Bean Huo
> >
The following commit has been merged into the sched/core branch of tip:
Commit-ID: 25de110d148666752dc0e0da7a0b69de31cd7098
Gitweb:
https://git.kernel.org/tip/25de110d148666752dc0e0da7a0b69de31cd7098
Author:Ingo Molnar
AuthorDate:Tue, 02 Jun 2020 12:08:39 +02:00
The following commit has been merged into the perf/urgent branch of tip:
Commit-ID: 16accae3d97f97d7f61c4ee5d0002bccdef59088
Gitweb:
https://git.kernel.org/tip/16accae3d97f97d7f61c4ee5d0002bccdef59088
Author:Stephane Eranian
AuthorDate:Thu, 28 May 2020 13:16:14 -07:00
On 6/2/20 11:31 AM, Valentin Schneider wrote:
> Hi Benjamin,
>
> On 27/05/20 16:16, Benjamin Gaignard wrote:
>> Before start streaming set cpufreq minimum frequency requirement.
>> The cpufreq governor will adapt the frequencies and we will have
>> no latency for handling interrupts.
>>
> Few
On Mon, Jun 01, 2020 at 12:29:27PM -0700, Kees Cook wrote:
> On Sun, May 31, 2020 at 01:50:30PM +0200, Christian Brauner wrote:
> > We've been making heavy use of the seccomp notifier to intercept and
> > handle certain syscalls for containers. This patch allows a syscall
> > supervisor listening
On 2020-06-01 20:12, Paul Moore wrote:
> On Mon, Jun 1, 2020 at 6:58 PM Richard Guy Briggs wrote:
> > On 2020-06-01 12:10, Paul Moore wrote:
> > > On Thu, May 28, 2020 at 9:44 PM Richard Guy Briggs
> > > wrote:
>
> ...
>
> > > > diff --git a/net/netfilter/nf_tables_api.c
> > > >
Hello Piotr,
Quoting Piotr Stankiewicz (2020-06-02 11:20:19)
> Seeing as there is shorthand available to use when asking for any type
> of interrupt, or any type of message signalled interrupt, leverage it.
>
> Signed-off-by: Piotr Stankiewicz
> Reviewed-by: Andy Shevchenko
Reviewed-by:
On Tue, Jun 02, 2020 at 03:39:23PM +0530, Sumit Semwal wrote:
> +static int qcom_labibb_regulator_is_enabled(struct regulator_dev *rdev)
> +{
> + int ret;
> + unsigned int val;
> + struct labibb_regulator *reg = rdev_get_drvdata(rdev);
> +
> + ret = regmap_read(reg->regmap,
Hi Daniel,
On 6/1/20 10:44 PM, Daniel Lezcano wrote:
On 27/05/2020 11:58, Lukasz Luba wrote:
Add support for other devices than CPUs. The registration function
does not require a valid cpumask pointer and is ready to handle new
devices. Some of the internal structures has been reorganized in
Hello,
On 6/2/20 8:24 AM, Kieran Bingham wrote:
> Hi Helen, Dafna,
>
> On 02/06/2020 11:55, Helen Koike wrote:
>>
>> On 6/2/20 7:52 AM, Dafna Hirschfeld wrote:
>>>
>>> On 01.06.20 14:16, Kaaira Gupta wrote:
On Fri, May 29, 2020 at 05:43:57PM +0200, Dafna Hirschfeld wrote:
> Hi,
>
在 2020/6/2 下午12:05, Hugh Dickins 写道:
> Cc'ing Alex Shi, because I noticed this when trying his v11 per-memcg
> lru_lock series (which appears to be a big improvement over earlier
> versions, thanks in particular to Johannes's memcg swap simplifications);
> and Alex's 12/16 makes a change on top
On Tue, 12 May 2020 at 12:34, Emil Velikov wrote:
>
> Hi Rodrigo,
>
> On Mon, 11 May 2020 at 12:55, Rodrigo Siqueira
> wrote:
> >
> > From: Rodrigo Siqueira
> >
> > The compute_crc() function is responsible for calculating the
> > framebuffer CRC value; due to the XRGB format, this function
On 6/2/20 1:07 PM, John Paul Adrian Glaubitz wrote:
> Hi!
>
> On 6/2/20 1:04 PM, Geert Uytterhoeven wrote:
>>> What do you mean with the sentence "when arch/ppc/ was still king"?
>>
>> Ah, Bartl copied that from my email ;-)
>>
>> There used to be APUS support under arch/ppc/.
>> Later, 32-bit
Adjust pgoff also when moving a map's start address.
Example with v5.4.34 based kernel:
Before:
$ sudo tools/perf/perf record -a --kcore -e intel_pt//k sleep 1
[ perf record: Woken up 1 times to write data ]
[ perf record: Captured and wrote 1.958 MB perf.data ]
$ sudo
Following process triggers a memleak caused by forgetting to release the
initial anchor PEB (CONFIG_MTD_UBI_FASTMAP is disabled):
1. attach -> __erase_worker -> produce the initial anchor PEB
2. detach -> ubi_fastmap_close (Do nothing, it should have released the
initial anchor PEB)
Don't
On Tue, Jun 02, 2020 at 03:39:20PM +0530, Sumit Semwal wrote:
> +
> + if (time_remaining <= 0) {
> + rdev_err(rdev, "Enabled check failed.\n");
> + return -ETIMEDOUT;
s/failed/timed out/
> + * @poll_enabled_time: Maximum time (in uS) to poll
Hi Helen, Dafna,
On 02/06/2020 11:55, Helen Koike wrote:
>
> On 6/2/20 7:52 AM, Dafna Hirschfeld wrote:
>>
>> On 01.06.20 14:16, Kaaira Gupta wrote:
>>> On Fri, May 29, 2020 at 05:43:57PM +0200, Dafna Hirschfeld wrote:
Hi,
Thanks for the patch
I don't know how real devices
Markus Elfring writes:
Please just remove the message instead, it's a tiny allocation that's
unlikely to ever fail, and the caller will print an error anyway.
>>>
>>> How do you think about to take another look at a previous update suggestion
>>> like the following?
>>>
>>>
As the "else if" and "else" branch body are identical the
condition has no effect. So removing "else if" condition.
Signed-off-by: Aishwarya Ramakrishnan
---
drivers/net/ethernet/nvidia/forcedeth.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/drivers/net/ethernet/nvidia/forcedeth.c
Hi Rodrigo,
On Mon, 11 May 2020 at 12:55, Rodrigo Siqueira wrote:
> -static uint32_t _vkms_get_crc(struct vkms_composer *primary_composer,
> - struct vkms_composer *cursor_composer)
> +static int compose_planes(void **vaddr_out,
> + struct
Hello,
syzbot found the following crash on:
HEAD commit:0e21d462 Add linux-next specific files for 20200602
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=17fee51610
kernel config: https://syzkaller.appspot.com/x/.config?x=ecc1aef35f550ee3
dashboard
Hello,
syzbot found the following crash on:
HEAD commit:0e21d462 Add linux-next specific files for 20200602
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=127233ee10
kernel config: https://syzkaller.appspot.com/x/.config?x=ecc1aef35f550ee3
dashboard
Hello,
syzbot found the following crash on:
HEAD commit:0e21d462 Add linux-next specific files for 20200602
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=1597f2fe10
kernel config: https://syzkaller.appspot.com/x/.config?x=ecc1aef35f550ee3
dashboard
On 6/2/20 4:30 PM, Michael Ellerman wrote:
Christophe Leroy writes:
Le 02/06/2020 à 06:12, Ravi Bangoria a écrit :
kbuild test robot reported few build warnings with hw_breakpoint code
when compiled with clang[1]. Fix those.
[1]:
在 2020/6/2 17:23, Sascha Hauer 写道:
Hi,
On Mon, Jun 01, 2020 at 05:11:34PM +0800, Zhihao Cheng wrote:
Following process triggers a memleak caused by forgetting to release the
initial anchor PEB (CONFIG_MTD_UBI_FASTMAP is disabled):
1. attach -> __erase_worker -> produce the initial anchor PEB
> The original patch was basically fine.
I propose to reconsider the interpretation of the software situation once more.
* Should the allocated clock object be kept usable even after
a successful return from this function?
* How much do “destructor” calls matter here for (sub)devices?
>
On 2020/6/2 下午6:16, Jason Wang wrote:
On 2020/6/2 下午5:42, Dan Carpenter wrote:
Hi Zhu,
url:
https://github.com/0day-ci/linux/commits/Zhu-Lingshan/vdpa-bypass-waking-up-vhost_woker-for-vdpa-vq-kick/20200526-133819
base: https://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git
On Tue, 2 Jun 2020 16:24:15 +0800, Chunyan Zhang wrote:
> The watchdog counter consists of WDG_LOAD_LOW and WDG_LOAD_HIGH,
> which would be loaded to watchdog counter once writing WDG_LOAD_LOW.
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
Thanks!
[1/1]
Hi!
On 6/2/20 1:04 PM, Geert Uytterhoeven wrote:
>> What do you mean with the sentence "when arch/ppc/ was still king"?
>
> Ah, Bartl copied that from my email ;-)
>
> There used to be APUS support under arch/ppc/.
> Later, 32-bit arch/ppc/ and 64-bit arch/ppc64/ were merged in a new\
>
Hi,
> Instead of adding that kernel module which is x86-specific
> to a generic lib/ directory, it should be in, say,
> tools/testing/selftests/x86/test_fpu_module.c or so and instead of
The kernel module is not actually x86-specific, even though it is
currently only enabled for x86. amdgpu
Hi Adrian,
On Tue, Jun 2, 2020 at 12:41 PM John Paul Adrian Glaubitz
wrote:
> On 6/2/20 12:37 PM, Bartlomiej Zolnierkiewicz wrote:
> >> These #ifdefs are relics from APUS (Amiga Power-Up System), which
> >> added a PPC board. APUS support was killed off a long time ago,
> >> when arch/ppc/ was
Hi,
On Mon, Jun 01, 2020 at 03:58:26PM +0800, Jian-Hong Pan wrote:
> Maxime Ripard 於 2020年5月28日 週四 下午3:30寫道：
> >
> > Hi Daniel,
> >
> > On Wed, May 27, 2020 at 05:15:12PM +0800, Daniel Drake wrote:
> > > On Wed, May 27, 2020 at 5:13 PM Maxime Ripard wrote:
> > > > I'm about to send a v3 today
Christophe Leroy writes:
> Le 02/06/2020 à 06:12, Ravi Bangoria a écrit :
>> kbuild test robot reported few build warnings with hw_breakpoint code
>> when compiled with clang[1]. Fix those.
>>
>> [1]:
>> https://lore.kernel.org/linuxppc-dev/202005192233.oi9cjrta%25...@intel.com/
>>
This
Hi,
On Tue, Jun 02, 2020 at 01:29:51PM +0300, Petteri Aimonen wrote:
> The kernel module is not actually x86-specific, even though it is
> currently only enabled for x86. amdgpu driver already does kernel mode
> floating point operations on PPC64 also, and the same module could be
> used to
On 6/2/20 7:52 AM, Dafna Hirschfeld wrote:
>
>
> On 01.06.20 14:16, Kaaira Gupta wrote:
>> On Fri, May 29, 2020 at 05:43:57PM +0200, Dafna Hirschfeld wrote:
>>> Hi,
>>> Thanks for the patch
>>>
>>> I don't know how real devices handle ARGB formats,
>>> I wonder if it should be the part of the
On 01/06/2020 19:08, Doug Anderson wrote:
Am not 100% sure if "qcom,fuse-blow-frequency" is something integration
specific or SoC Specific, My idea was that this will give more
flexibility in future. As adding new SoC Support does not need driver
changes.
Having said that, Am okay either
In imx6sll.dtsi, the ssi node name is different with other
platforms (imx6qdl, imx6sl, imx6sx), but the
sound/soc/fsl/fsl-asoc-card.c machine driver needs to check
ssi node name for audmux configuration, then different ssi
node name causes issue on imx6sll platform.
So we change ssi node name to
On 01.06.20 14:16, Kaaira Gupta wrote:
On Fri, May 29, 2020 at 05:43:57PM +0200, Dafna Hirschfeld wrote:
Hi,
Thanks for the patch
I don't know how real devices handle ARGB formats,
I wonder if it should be the part of the debayer.
Hi! qcam tries to support BA24 as it is one of the formats
From: Vijay Viswanath
If vendor platform drivers are controlling whole logic of voltage
switching, then sdhci driver no need control vqmmc regulator.
So skip enabling/disable vqmmc from SDHC driver.
Signed-off-by: Vijay Viswanath
Signed-off-by: Veerabhadrarao Badiganti
Acked-by: Adrian Hunter
On qcom SD host controllers voltage switching be done after the HW
is ready for it. The HW informs its readiness through power irq.
The voltage switching should happen only then.
Use the internal voltage switching and then control the voltage
switching using power irq.
Set the regulator load as
On qcom SD host controllers voltage switching be done after the HW
is ready for it. The HW informs its readiness through power irq.
The voltage switching should happen only then.
So added support to register voltage regulators from the msm driver
and use them.
This patchset was posted long back
Supply the max load needed for driving the mmc supplies.
Signed-off-by: Veerabhadrarao Badiganti
---
Documentation/devicetree/bindings/mmc/mmc-controller.yaml | 6 ++
1 file changed, 6 insertions(+)
diff --git a/Documentation/devicetree/bindings/mmc/mmc-controller.yaml
On 6/2/2020 2:07 AM, Andrey Smirnov wrote:
> Add a small bit of plumbing necessary to use CAAM on VFxxx SoCs.
>
> Signed-off-by: Andrey Smirnov
> Cc: Chris Healy
> Cc: Horia Geantă
> Cc: Herbert Xu
> Cc: Fabio Estevam
> Cc: linux-...@nxp.com
> Cc: linux-cry...@vger.kernel.org
> Cc:
On 6/2/2020 1:06 AM, Stephen Boyd wrote:
Quoting Sivaprakash Murugesan (2020-06-01 05:41:15)
On 5/28/2020 7:29 AM, Stephen Boyd wrote:
Quoting Sivaprakash Murugesan (2020-05-27 05:24:51)
diff --git a/drivers/clk/qcom/apss-ipq6018.c b/drivers/clk/qcom/apss-ipq6018.c
new file mode 100644
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
x86/entry
branch HEAD: 4b1f63084d3ebd14c3ef2cd4e8732c25bcd8381d x86/xen: Unbreak
hypervisor callback on 32bit
i386-tinyconfig vmlinux size:
As the "else if" and "else" branch body are identical the
condition has no effect. So removing "else if" condition.
Signed-off-by: Aishwarya Ramakrishnan
---
drivers/net/ethernet/stmicro/stmmac/stmmac_platform.c | 2 --
1 file changed, 2 deletions(-)
diff --git
On 01/06/2020 16:59, Vishal Sagar wrote:
> Hi Hans,
>
> Thanks for reviewing!
>
>>> + case V4L2_CID_XILINX_SDIRX_TS_IS_INTERLACED:
>>> + if (!xsdirxss->vidlocked) {
>>> + dev_err(dev, "Can't get values when video not
>> locked!\n");
>>> + return
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 3d77e6a8804abcc0504c904bd6e5cdf3a5cf8162
commit: 3442a9ecb8e72a33c28a2b969b766c659830e410 perf/x86/intel/uncore: Factor
out __snr_uncore_mmio_init_box
date: 2 months ago
config:
you want tag next-20200602
or if you just want that trees that conflicted, then
block: git://git.kernel.dk/linux-block.git branch for-next
rdma: git://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma.git branch
for-next
--
Cheers,
Stephen Rothwell
pgpuJx8Q8mjVY.pgp
Description: OpenPGP digital signature
Hi Geert!
On 6/2/20 12:37 PM, Bartlomiej Zolnierkiewicz wrote:
>
> On 5/14/20 10:21 PM, Geert Uytterhoeven wrote:
>
>> These #ifdefs are relics from APUS (Amiga Power-Up System), which
>> added a PPC board. APUS support was killed off a long time ago,
>> when arch/ppc/ was still king, but
On Tue, Jun 02, 2020 at 04:14:38PM +0800, Neal Liu wrote:
> For security awareness SoCs on ARMv8 with TrustZone enabled,
> peripherals like entropy sources is not accessible from normal world
> (linux) and rather accessible from secure world (HYP/ATF/TEE) only.
> This driver aims to provide a
Since we lack the hardware (or proper emulator setup) for
testing needed changes add FIXMEs to document the issues
(so at least they are not forgotten).
Cc: Al Viro
Cc: Geert Uytterhoeven
Signed-off-by: Bartlomiej Zolnierkiewicz
---
drivers/video/fbdev/amifb.c |2 ++
1 file changed, 2
Hi all,
News: The merge window has opened, so please do *not* add v5.9 material
to your linux-next included branches until after v5.8-rc1 has been
released.
Changes since 20200529:
My fixes tree contains:
4cb4bfffe2c1 ("device_cgroup: Fix RCU list debugging warning")
The drm-intel-fixes
On 5/14/20 10:21 PM, Geert Uytterhoeven wrote:
> These #ifdefs are relics from APUS (Amiga Power-Up System), which
> added a PPC board. APUS support was killed off a long time ago,
> when arch/ppc/ was still king, but these #ifdefs were missed, because
> they didn't test for CONFIG_APUS.
On Tue, 02 Jun 2020, Matthias Brugger wrote:
>
>
> On 02/06/2020 10:28, Lee Jones wrote:
> > On Tue, 02 Jun 2020, Gene Chen wrote:
> >
> >> From: Gene Chen
> >>
> >> Add MFD driver for mt6360 pmic chip include Battery Charger/
> >> USB_PD/Flash, LED/RGB and LED/LDO/Buck
> >>
> >>
The original patch was basically fine. Just add a Fixes tag and resend.
regards,
dan carpenter
On 6/2/2020 3:48 PM, Stephen Rothwell wrote:
Hi Ayush,
On Tue, 2 Jun 2020 13:01:09 +0530 Ayush Sawal wrote:
On 6/2/2020 4:42 AM, Stephen Rothwell wrote:
In commit
055be6865dea ("Crypto/chcr: Fixes a coccinile check error")
Fixes tag
Fixes: 567be3a5d227 ("crypto:
has these
On 02/06/2020 12:18, Sergey Senozhatsky wrote:
> Hi Hans,
>
> On (20/06/02 11:51), Hans Verkuil wrote:
>> Hi Sergey,
>>
>> While doing final testing for this patch series (together with the v4l-utils
>> patch)
>> I found one remaining issue:
>
> Thanks for the report.
>
>>> +static void
Christophe Leroy writes:
> Le 28/05/2020 à 12:17, Christophe Leroy a écrit :
>> Mapping of early shadow area is implemented by using a single static
>> page table having all entries pointing to the same early shadow page.
>> The shadow area must therefore occupy full PGD entries.
>>
>> The
On Tue, Jun 02, 2020 at 09:07:15AM +, Chris Paterson wrote:
> Hello Sasha,
>
> > From: stable-ow...@vger.kernel.org On
> > Behalf Of Sasha Levin
> > Sent: 02 June 2020 03:07
> >
> > On Mon, Jun 01, 2020 at 10:14:20PM +, Chris Paterson wrote:
> > >Hi Greg,
> > >
> > >> From:
This is the start of the stable review cycle for the 5.6.16 release.
There are 174 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 should be made by Thu, 04 Jun 2020 10:16:52 +.
Anything
On Mon, 2020-06-01 at 19:35 -0700, Linus Torvalds wrote:
>
> On Mon, Jun 1, 2020 at 6:06 PM Balbir Singh wrote:
> >
> > I think apps can do this independently today as in do the flush
> > via software fallback in the app themselves.
>
> Sure, but they can't force the kernel to do crazy things
On Mon, May 18, 2020 at 01:50:59PM +0200, Alexander Gordeev wrote:
> On Mon, May 18, 2020 at 02:33:43PM +0300, Andy Shevchenko wrote:
> > On Mon, May 18, 2020 at 1:40 PM Alexander Gordeev
> > wrote:
> > >
> > > Commit 2d6261583be0 ("lib: rework bitmap_parse()") does
> > > not take into account
This is the start of the stable review cycle for the 5.4.44 release.
There are 139 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 should be made by Thu, 04 Jun 2020 10:16:52 +.
Anything
This is the start of the stable review cycle for the 4.19.126 release.
There are 92 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made by Thu, 04 Jun 2020 10:16:52 +.
Anything
> Call to pm_runtime_get_sync increments counter even in case of
> failure leading to incorrect ref count.
> Call pm_runtime_put_autosuspend if pm_runtime_get_sync fails.
How do you think about a wording variant like the following?
Change description:
The PM runtime reference counter is
This is the start of the stable review cycle for the 4.9.226 release.
There are 59 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 should be made by Thu, 04 Jun 2020 10:16:52 +.
Anything
This is the start of the stable review cycle for the 4.14.183 release.
There are 76 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 should be made by Thu, 04 Jun 2020 10:16:52 +.
Anything
Rich Felker schrieb:
>> There is a functional argument agains using get_user_32 twice, which I
>> overlooked in my private reply to Adrian. If any of the loads fail, we
>> do not only want err to be set to -EFAULT (which will happen), but we
>> also want a 64-bit zero as result. If one 32-bit read
Hi Hans,
On (20/06/02 11:51), Hans Verkuil wrote:
> Hi Sergey,
>
> While doing final testing for this patch series (together with the v4l-utils
> patch)
> I found one remaining issue:
Thanks for the report.
> > +static void set_buffer_cache_hints(struct vb2_queue *q,
> > +
Jin Yao reported the issue (and posted first versions of this change)
with groups being defined over events with different cpu mask.
This causes assert aborts in get_group_fd, like:
# perf stat -M "C2_Pkg_Residency" -a -- sleep 1
perf: util/evsel.c:1464: get_group_fd: Assertion `!(fd == -1)'
Hi Ayush,
On Tue, 2 Jun 2020 13:01:09 +0530 Ayush Sawal wrote:
>
> On 6/2/2020 4:42 AM, Stephen Rothwell wrote:
> >
> > In commit
> >
> >055be6865dea ("Crypto/chcr: Fixes a coccinile check error")
> >
> > Fixes tag
> >
> >Fixes: 567be3a5d227 ("crypto:
> >
> > has these problem(s):
> >
>
On 2020/6/2 下午5:42, Dan Carpenter wrote:
Hi Zhu,
url:
https://github.com/0day-ci/linux/commits/Zhu-Lingshan/vdpa-bypass-waking-up-vhost_woker-for-vdpa-vq-kick/20200526-133819
base: https://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git linux-next
config:
'seq_buf' provides a very useful abstraction for writing to a string
buffer without needing to worry about it over-flowing. However even
though the API has been stable for couple of years now its still not
exported to kernel loadable modules limiting its usage.
Hence this patch proposes update to
Introduce support for PAPR NVDIMM Specific Methods (PDSM) in papr_scm
module and add the command family NVDIMM_FAMILY_PAPR to the white list
of NVDIMM command sets. Also advertise support for ND_CMD_CALL for the
nvdimm command mask and implement necessary scaffolding in the module
to handle
This patch implements support for PDSM request 'PAPR_PDSM_HEALTH'
that returns a newly introduced 'struct nd_papr_pdsm_health' instance
containing dimm health information back to user space in response to
ND_CMD_CALL. This functionality is implemented in newly introduced
papr_pdsm_health() that
This is the start of the stable review cycle for the 4.4.226 release.
There are 47 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 should be made by Thu, 04 Jun 2020 09:57:12 +.
Anything
On 2020/6/2 下午4:45, Michael S. Tsirkin wrote:
So vhost needs to poke at userspace *a lot* in a quick succession. It
is thus benefitial to enable userspace access, do our thing, then
disable. Except access_ok has already been pre-validated with all the
relevant nospec checks, so we don't need
Implement support for fetching nvdimm health information via
H_SCM_HEALTH hcall as documented in Ref[1]. The hcall returns a pair
of 64-bit bitmap, bitwise-and of which is then stored in
'struct papr_scm_priv' and subsequently partially exposed to
user-space via newly introduced dimm specific
Changes since v9 [1]:
* Added acks from Aneesh and Steven Steven Rostedt.
Changes since v8 [2]:
* Updated proposed changes to remove usage of term 'SCM' due to
ambiguity with 'PMEM' and 'NVDIMM'. [ Dan Williams ]
* Replaced the usage of term 'SCM' with 'PMEM' in most contexts.
[ Aneesh ]
*
Add documentation to 'papr_hcalls.rst' describing the bitmap flags
that are returned from H_SCM_HEALTH hcall as per the PAPR-SCM
specification.
Cc: "Aneesh Kumar K . V"
Cc: Dan Williams
Cc: Michael Ellerman
Cc: Ira Weiny
Signed-off-by: Vaibhav Jain
---
Changelog:
Resend:
* None
v8..v9:
*
On Sat, May 30, 2020 at 10:49:55PM +0200, Christophe JAILLET wrote:
> 'pinctrl_unregister()' should not be called to undo
> 'devm_pinctrl_register_and_init()', it is already handled by the framework.
>
> This simplifies the error handling paths of the probe function.
> The 'imx_free_resources()'
On 23-May-20 11:00 PM, Vidya Sagar wrote:
On 22-May-20 7:36 PM, Thierry Reding wrote:
On Fri, May 22, 2020 at 02:32:49PM +0100, Lorenzo Pieralisi wrote:
On Fri, May 22, 2020 at 02:06:55PM +0200, Thierry Reding wrote:
On Wed, May 20, 2020 at 04:48:16PM -0600, Rob Herring wrote:
On Wed,
On 2020-06-02 11:09, Serge Semin wrote:
Add Thomas and myself as maintainers of the MIPS CPU and GIC IRQchip,
MIPS
GIC timer and MIPS CPS CPUidle drivers.
Signed-off-by: Serge Semin
---
Changelog v3:
- Keep the files list alphabetically ordered.
- Add Thomas as the co-maintainer of the
Switching to mail where patches are discussed.
> Subject: [PATCH] arch/x86: reset MXCSR to default in kernel_fpu_begin()
Fix formatting to:
Subject: [PATCH] x86/fpu: Reset MXCSR to default in kernel_fpu_begin()
> From: Petteri Aimonen
>
> Previously kernel floating point code would run with
From: Nisha Kumari
This patch adds devicetree nodes for LAB and IBB regulators.
Signed-off-by: Nisha Kumari
Signed-off-by: Sumit Semwal
[sumits: Updated for better compatible strings and names]
--
v2: sumits: updated for better compatible string and names
v3: sumits: updated interrupt-names
In this patch series,
Patch-1
adds required infrastructure to deal with prefetchable memory region
information coming from 'ranges' property of the respective device-tree node
separately from non-prefetchable memory region information.
Patch-2
Adds support to use ATU region-3 for establishing the
Some regulators might need to verify that they have indeed been enabled
after the enable() call is made and enable_time delay has passed.
This is implemented by repeatedly checking is_enabled() upto
poll_enabled_time, waiting for the already calculated enable delay in
each iteration.
From: Nisha Kumari
Add Short circuit interrupt handling and recovery for the lab and ibb
regulators on qcom platforms.
The client panel drivers need to register for REGULATOR_EVENT_OVER_CURRENT
notification which will be triggered on short circuit. They should
try to enable the regulator once,
Folks, the code and DT-related patches here have been mostly reviewed.
Please consider merge the series in or at least give me a feedback to
update the series, since merge window is getting opened and I would
really appreciate to see the leftover being merged in.
Regarding this patchset origin.
It's a Common Device Memory Map controller embedded into the MIPS IP
cores, which dts node is supposed to have compatible and reg properties.
Signed-off-by: Serge Semin
Reviewed-by: Rob Herring
---
Changelog prev:
- Lowercase the example hex'es.
---
.../bindings/bus/mti,mips-cdmm.yaml
Modern device tree bindings are supposed to be created as YAML-files
in accordance with DT schema. This commit replaces MIPS GIC legacy bare
text binding with YAML file. As before the binding file states that the
corresponding dts node is supposed to be compatible with MIPS Global
Interrupt
Add required structure members to struct pcie_port to handle prefetchable
memory aperture separately from non-prefetchable memory aperture so that
any dependency on the order of their appearance in the 'ranges' property
of the respective PCIe device tree node can be removed.
Signed-off-by: Vidya
It's a Cluster Power Controller embedded into the MIPS IP cores.
Currently the corresponding dts node is supposed to have compatible
and reg properties.
Signed-off-by: Serge Semin
Reviewed-by: Rob Herring
---
Changelog prev:
- Reword the changelog summary - use shorter version.
- Lowercase
Add Thomas and myself as maintainers of the MIPS CPU and GIC IRQchip, MIPS
GIC timer and MIPS CPS CPUidle drivers.
Signed-off-by: Serge Semin
---
Changelog v3:
- Keep the files list alphabetically ordered.
- Add Thomas as the co-maintainer of the designated drivers.
---
MAINTAINERS | 11
Use ATU region-3 to setup mapping for prefetchable memory region. It also
modifies the code to consume an ATU region for mapping non-prefetchable or
prefetchable memory regions only if the CPU address and PCIe bus addresses
are not equal as there is no need to use ATU mapping if there is a 1:1
From: Nisha Kumari
Qualcomm platforms have LAB(LCD AMOLED Boost)/IBB(Inverting Buck Boost)
regulators, labibb for short, which are used as power supply for
LCD Mode displays.
This patch adds labibb regulator driver for pmi8998 PMIC, found on
SDM845 platforms.
Signed-off-by: Nisha Kumari
901 - 1000 of 1198 matches
Mail list logo
