On (20/10/05 20:35), Guenter Roeck wrote:
> On a side note, I don't see the problem presumably fixed with this
> patch in any of my tests.
Hmm. This is rather interesting. Empty console= certainly oops-es my laptop,
but not the cros board I just tested this on. Do we carry around any chromeos
patc
On Mon, 05 Oct 2020, Rob Herring wrote:
> In cases where we don't reference another schema, 'additionalProperties'
> can be used instead. This is preferred for now as 'unevaluatedProperties'
> support isn't implemented yet.
>
> In a few cases, this means adding some missing property definitions o
On Fri, 02 Oct 2020, Rob Herring wrote:
> Another round of wack-a-mole. The json-schema default is additional
> unknown properties are allowed, but for DT all properties should be
> defined.
Acked-by: Lee Jones
--
Lee Jones [李琼斯]
Senior Technical Lead - Developer Services
Linaro.org │ Open sou
Hi Geert,
On Fri, Sep 25, 2020 at 3:16 PM Geert Uytterhoeven wrote:
>
> Hi Mateusz,
>
> On Wed, Sep 23, 2020 at 12:10 PM Mateusz Holenko
> wrote:
> > From: Filip Kokosinski
> >
> > Add documentation for LiteUART devicetree bindings.
> >
> > Signed-off-by: Filip Kokosinski
> > Signed-off-by: M
On Mon, Oct 05, 2020 at 02:07:23PM +0200, Wilken Gottwalt wrote:
> On Mon, 5 Oct 2020 18:36:36 +0700 Lars Melin wrote:
> > On 10/5/2020 18:06, Johan Hovold wrote:
> > > Do you remember the interface layout and why you blacklisted interface
> > > 1?
> > It is very likely that Cellient has replace
On Thu, 1 Oct 2020 21:07:51 -0700
Guenter Roeck wrote:
> On 10/1/20 3:22 PM, Andreas Kemnade wrote:
> > On Wed, 30 Sep 2020 22:00:09 +0200
> > Arnd Bergmann wrote:
> >
> >> On Wed, Sep 30, 2020 at 6:44 PM Guenter Roeck wrote:
> >>>
> >>> On Wed, Sep 30, 2020 at 10:54:42AM +0200, Andreas Ke
On 05/10/2020 21:47:01-0400, Peter Geis wrote:
> On Mon, Oct 5, 2020 at 6:29 PM Alexandre Belloni
> wrote:
> >
> > On 05/10/2020 09:13:08-0400, Peter Geis wrote:
> > > Good Morning,
> > >
> > > While testing suspend to ram on the Ouya, I encountered an interesting
> > > issue with the rtc-tps65910
On 24-09-20, 13:30, Ionela Voinescu wrote:
> Compared to other arch_* functions, arch_set_freq_scale() has an atypical
> weak definition that can be replaced by a strong architecture specific
> implementation.
>
> The more typical support for architectural functions involves defining
> an empty st
Hi Mateusz,
On Tue, Oct 6, 2020 at 9:01 AM Mateusz Holenko wrote:
> On Fri, Sep 25, 2020 at 3:16 PM Geert Uytterhoeven
> wrote:
> > On Wed, Sep 23, 2020 at 12:10 PM Mateusz Holenko
> > wrote:
> > > From: Filip Kokosinski
> > >
> > > Add documentation for LiteUART devicetree bindings.
> > >
>
Hi Alain
On 8/30/20 9:57 PM, Alain Volmat wrote:
> Update the sti platform LL_UART support to rely on
> CONFIG_DEBUG_UART_PHYS and CONFIG_DEBUG_UART_VIRT from Kconfig
>
> Signed-off-by: Alain Volmat
> ---
> arch/arm/Kconfig.debug | 23 ---
> arch/arm/include/debug/sti.S
On Mon, Sep 28, 2020 at 03:17:34PM -0700, David Miller wrote:
> From: Christoph Hellwig
> Date: Sat, 26 Sep 2020 09:00:49 +0200
>
> > ->sendpage is only called from generic_splice_sendpage. The only user of
> > generic_splice_sendpage is socket_file_ops, which is also the only
> > instance that
On Tue, 6 Oct 2020 at 06:12, wrote:
>
> The order in which 'users' counter is decremented vs calling drivers'
> close() method is implementation specific, and we should not rely on
> it. Let's introduce driver private flag and use it to signal ISR
> to exit when device is being closed.
>
> This ha
Hi Alain
On 8/30/20 9:57 PM, Alain Volmat wrote:
> Add the entry for the STiH418 SBC UART0 low level uart.
>
> Signed-off-by: Alain Volmat
> ---
> arch/arm/Kconfig.debug | 19 +--
> 1 file changed, 17 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm/Kconfig.debug b/arch/ar
Lee Jones writes:
> On Tue, 06 Oct 2020, Kalle Valo wrote:
>
>> Lee Jones writes:
>>
>> > On Thu, 10 Sep 2020, Lee Jones wrote:
>> >
>> >> This is a rebased/re-worked set of patches which have been
>> >> previously posted to the mailing list(s).
>> >>
>> >> This set is part of a larger effort
On 24-09-20, 13:30, Ionela Voinescu wrote:
> big.LITTLE switching complicates the setting of a correct cpufreq-based
> frequency invariance scale factor due to (as observed in
> drivers/cpufreq/vexpress-spc-cpufreq.c):
> - Incorrect current and maximum frequencies as a result of the
>exposure
Towards removing the mode specific @dax_kmem_res attribute from the
generic 'struct dev_dax', and preparing for multi-range support, move
resource tracking to driver data. The memory for the resource name
needs to have its own lifetime separate from the device bind lifetime
for cases where the dri
Make the device-dax 'size' attribute writable to allow capacity to be
split between multiple instances in a region. The intended consumers of
this capability are users that want to split a scarce memory resource
between device-dax and System-RAM access, or users that want to have
multiple security
Use sysfs_streq() in device_find_child_by_name() to allow it to use a
sysfs input string that might contain a trailing newline.
The other "device by name" interfaces,
{bus,driver,class}_find_device_by_name(), already account for sysfs
strings.
Link:
https://lkml.kernel.org/r/159643102106.4062302
In preparation for introducing seed devices the dax-bus core needs to be
able to intercept ->probe() and ->remove() operations. Towards that end
arrange for the bus and drivers to switch from raw 'struct device'
driver operations to 'struct dev_dax' typed operations.
Cc: Jason Yan
Cc: Vishal Verm
The 'struct resource' in 'struct dev_pagemap' is only used for holding
resource span information. The other fields, 'name', 'flags', 'desc',
'parent', 'sibling', and 'child' are all unused wasted space.
This is in preparation for introducing a multi-range extension of
devm_memremap_pages().
The
Towards removing the mode specific @dax_kmem_res attribute from the
generic 'struct dev_dax', and preparing for multi-range support, teach
the driver to calculate the hotplug range from the device range. The
hotplug range is the trivially calculated memory-block-size aligned
version of the device r
Changes since v5 [1]:
- (David) Introduce range_len() to include/linux/range.h immediately in
"device-dax: make pgmap optional for instance creation" rather than
wait until "mm/memremap_pages: convert to 'struct range'" to move it.
- (David) David points out that release_mem_region() can not b
;In preparation for a facility that enables dax regions to be sub-divided,
introduce infrastructure to track and allocate region capacity.
The new dax_region/available_size attribute is only enabled for volatile
hmem devices, not pmem devices that are defined by nvdimm namespace
boundaries. This
Add a seed device concept for dynamic dax regions to be able to split the
region amongst multiple sub-instances. The seed device, similar to
libnvdimm seed devices, is a device that starts with zero capacity
allocated and unbound to a driver. In contrast to libnvdimm seed devices
explicit 'create
The passed in dev_pagemap is only required in the pmem case as the
libnvdimm core may have reserved a vmem_altmap for dev_memremap_pages() to
place the memmap in pmem directly. In the hmem case there is no agent
reserving an altmap so it can all be handled by a core internal default.
Pass the res
Break the requirement that device-dax instances are physically contiguous.
With this constraint removed it allows fragmented available capacity to
be fully allocated.
This capability is useful to mitigate the "noisy neighbor" problem with
memory-side-cache management for virtual machines, or any o
In support of device-dax growing the ability to front physically
dis-contiguous ranges of memory, update devm_memremap_pages() to track
multiple ranges with a single reference counter and devm instance.
Convert all [devm_]memremap_pages() users to specify the number of
ranges they are mapping in t
On Tue, 6 Oct 2020 at 06:27, Yong Wu wrote:
>
> On Fri, 2020-10-02 at 13:08 +0200, Krzysztof Kozlowski wrote:
> > On Wed, Sep 30, 2020 at 03:06:25PM +0800, Yong Wu wrote:
> > > Convert MediaTek SMI to DT schema.
> > >
> > > Signed-off-by: Yong Wu
> > > ---
> > > .../mediatek,smi-common.txt
On Wed, Sep 30, 2020 at 03:06:41PM +0800, Yong Wu wrote:
> After extending v7s, our pagetable already support iova reach
> 16GB(34bit). the master got the iova via dma_alloc_attrs may reach
> 34bits, but its HW register still is 32bit. then how to set the
> bit32/bit33 iova? this depend on a SMI la
On Tue, 6 Oct 2020 07:45:10 +0200
Heiner Kallweit wrote:
>
> On 05.10.2020 18:00, Florian Fainelli wrote:
> >
> >
> > On 10/5/2020 8:54 AM, Heiner Kallweit wrote:
> >> On 05.10.2020 17:41, Florian Fainelli wrote:
> >>>
> >>>
> >>> On 10/5/2020 1:53 AM, Jisheng Zhang wrote:
> On Wed,
On Tue, Oct 06, 2020 at 12:26:45PM +0800, Yong Wu wrote:
> Hi Krzysztof,
>
> On Fri, 2020-10-02 at 13:10 +0200, Krzysztof Kozlowski wrote:
> > On Wed, Sep 30, 2020 at 03:06:29PM +0800, Yong Wu wrote:
> > > This patch adds decriptions for mt8192 IOMMU and SMI.
> > >
> > > mt8192 also is MTK IOMMU
Hi Geert,
On Fri, Sep 25, 2020 at 3:41 PM Geert Uytterhoeven wrote:
>
> Hi Mateusz,
>
> On Wed, Sep 23, 2020 at 12:12 PM Mateusz Holenko
> wrote:
> > From: Filip Kokosinski
> >
> > This commit adds driver for the FPGA-based LiteUART serial controller
> > from LiteX SoC builder.
> >
> > The cur
On Mon, Oct 05, 2020 at 11:19:02PM +, Harley A.W. Lorenzo wrote:
> On Monday, October 5, 2020 5:31 PM, Sudip Mukherjee
> wrote:
>
> > find_tt() can return NULL or the error value in ERR_PTR() and
> > dereferencing the return value without checking for the error can
> > lead to a possible der
On 24-09-20, 10:53, Nicola Mazzucato wrote:
> I am seeking some feedback/comments on the following approach.
>
> Intro:
> Info of performance depency for cpus will be beneficial for systems
> where f/w description of the CPU performance control domain is different
> from the clock domain, e.g. per
This patch is against to mkp's 5.10/scsi-staging.
1. fix warning: right shift count >= width of type.
---
On Mon, Oct 05, 2020 at 10:35:43AM -0400, Jonathan Marek wrote:
> The cache synchronization doesn't have anything to do with IOMMU (for
> example: cache synchronization would be useful in cases where drm/msm
> doesn't use IOMMU).
It has to do with doing DMA. And we have two frameworks for doing D
note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url:
https://github.com/0day-ci/linux/commits/Jeremy-Linton/arm64-bti-fix-BTI-to-handle-local-indirect-branches/20201006-021958
base: https://git.kernel.org/pub
On Mon, Oct 05, 2020 at 04:57:20PM +0200, Peter Zijlstra wrote:
> +static inline void balance_switch(struct rq *rq)
> +{
> + if (unlikely(rq->balance_flags)) {
> + /*
> + * Run the balance_callbacks, except on hotplug
> + * when we need to push the current
Alex Dewar writes:
> ath11k_peer_create() is called without its return value being checked,
> meaning errors will be unhandled. Add missing check and, as the mutex is
> unconditionally unlocked on leaving this function, simplify the exit
> path.
>
> Addresses-Coverity-ID: 1497531 ("Code maintaina
From: ching Huang
Fix warning: right shift count >= width of type.
Reported-by: kernel test robot
Signed-off-by: ching Huang
---
diff --git a/drivers/scsi/arcmsr/arcmsr_hba.c b/drivers/scsi/arcmsr/arcmsr_hba.c
index be6fb72..d13d672 100644
--- a/drivers/scsi/arcmsr/arcmsr_hba.c
+++ b/drivers/
On 10/4/2020 3:56 AM, Kuogee Hsieh wrote:
Set link rate by using OPP set rate api so that CX level will be set
accordingly based on the link rate.
Changes in v2:
-- remove dev from dp_ctrl_put() parameters
-- address review comments
This needs to go below '---' and should not be part of the
By the way I just realized that the DT binding in this driver seems
incorrect to me.
The controller logically supports 3 LED strings, each having
configurable control bank.
But the DT binding supports 2 DT nodes, one for each control bank
(identified by the `reg` property) and then `led-sources`
On Tue, 2020-10-06 at 08:42 +0200, Mauro Carvalho Chehab wrote:
> Em Mon, 5 Oct 2020 10:17:36 -0600
> Jonathan Corbet escreveu:
[]
> Sure. It should be easy to make the third argument optional, although
> the regex will be a little more harder to understand.
>
> Something like this should do the
Hi all,
Today's linux-next merge of the char-misc tree got a conflict in:
drivers/misc/ocxl/Kconfig
between commit:
dde6f18a8779 ("ocxl: Don't return trigger page when allocating an interrupt")
from the powerpc tree and commit:
4b53a3c72116 ("ocxl: fix kconfig dependency warning for OCX
Hi Rob,
On Mon, Oct 5, 2020 at 8:39 PM Rob Herring wrote:
> This doesn't yet do anything in the tools, but make it explicit so we can
> check either 'unevaluatedProperties' or 'additionalProperties' is present
> in schemas.
>
> 'unevaluatedProperties' is appropriate when including another schema
Hi Marc,
On Tue, Aug 25, 2020 at 3:21 AM Rob Herring wrote:
>
> On Sun, 16 Aug 2020 20:07:31 +0100, Lad Prabhakar wrote:
> > Document RZ/G1H (r8a7742) SoC specific bindings. The R8A7742 CAN module
> > is identical to R-Car Gen2 family.
> >
> > No driver change is needed due to the fallback compat
On Mon, Oct 05, 2020 at 05:57:36PM -0700, Ricardo Neri wrote:
> On Sat, Oct 03, 2020 at 10:53:45AM +0200, Greg Kroah-Hartman wrote:
> > On Fri, Oct 02, 2020 at 06:17:42PM -0700, Ricardo Neri wrote:
> > > Hybrid CPU topologies combine CPUs of different microarchitectures in the
> > > same die. Thus,
On Thu, Oct 01, 2020 at 11:48:40PM +0800, Ming Lei wrote:
> Hi,
>
> The 1st patch removes memory footprint of percpu_ref in fast path
> from 7 words to 2 words, since it is often used in fast path and
> embedded in user struct.
>
> The 2nd patch moves .q_usage_counter to 1st cacheline of
> 'reque
On Mon, Oct 5, 2020 at 8:39 PM Rob Herring wrote:
> In order to add meta-schema checks for additional/unevaluatedProperties
> being present, all schema need to make this explicit. As the top-level
> board/SoC schemas always have additional properties, add
> 'additionalProperties: true'.
>
> Signed
On Mon, Oct 5, 2020 at 8:39 PM Rob Herring wrote:
> In order to add meta-schema checks for additional/unevaluatedProperties
> being present, all schema need to make this explicit. As common/shared
> schema are included by other schemas, they should always allow for
> additionalProperties.
>
> Sign
+ Jes
On 10/5/2020 4:12 PM, Kalle Valo wrote:
Greg Kroah-Hartman writes:
On Fri, Oct 02, 2020 at 01:53:58PM +0200, Sebastian Andrzej Siewior wrote:
On 2020-10-02 13:37:25 [+0200], Greg Kroah-Hartman wrote:
Is it possible to end up here in softirq context or is this a relic?
I think it's a
Sean Christopherson writes:
> On Mon, Oct 05, 2020 at 05:29:47PM +0200, Vitaly Kuznetsov wrote:
>> Tianjia Zhang writes:
>>
>> > Original KVM_SET_CPUID has removed NX on non-NX hosts as it did
>> > before. but KVM_SET_CPUID2 does not. The two should be consistent.
>> >
>> > Signed-off-by: Tianj
On Tue 06-10-20 08:26:35, Anshuman Khandual wrote:
>
>
> On 10/05/2020 11:35 AM, Michal Hocko wrote:
> > On Mon 05-10-20 07:59:12, Anshuman Khandual wrote:
> >>
> >>
> >> On 10/02/2020 05:34 PM, Michal Hocko wrote:
> >>> On Wed 30-09-20 11:30:49, Anshuman Khandual wrote:
> Add following new
Use dma_alloc_coherent() for bounce buffer instead of kmalloc() to
make sure the bounce buffer to be allocated within its DMAable range.
Signed-off-by: Ikjoon Jang
---
drivers/spi/spi-mtk-nor.c | 94 ++-
1 file changed, 52 insertions(+), 42 deletions(-)
diff
Dear Rafael,
On 10/1/20 12:56 AM, Rafael J. Wysocki wrote:
> On Tue, Sep 29, 2020 at 10:56 AM Chanwoo Choi wrote:
>>
>> Dear Rafael,
>>
>> This is devfreq-next pull request for v5.10-rc1. I add detailed description
>> of
>> this pull request on the following tag. Please pull devfreq with followi
The ASUS D700SA desktop's audio (1043:2390) with ALC887 cannot detect
the headset microphone and another headphone jack until
ALC887_FIXUP_ASUS_HMIC and ALC887_FIXUP_ASUS_AUDIO quirks are applied.
The NID 0x15 maps as the headset microphone and NID 0x19 maps as another
headphone jack. Also need the
Add MT8192 spi-nor controller support.
Signed-off-by: Ikjoon Jang
Acked-by: Rob Herring
---
Documentation/devicetree/bindings/spi/mediatek,spi-mtk-nor.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/spi/mediatek,spi-mtk-nor.yaml
b/Documentation/devic
umented in
https://git-scm.com/docs/git-format-patch]
url:
https://github.com/0day-ci/linux/commits/Konrad-Dybcio/pm8994-msm8992-4-DT-updates/20201006-003302
base: https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git for-next
config: arm64-allyesconfig (attached as .config)
compile
Hi all,
Today's linux-next merge of the staging tree got a conflict in:
Documentation/devicetree/bindings/iio/adc/samsung,exynos-adc.yaml
between commit:
41fb845621ea ("dt-bindings: Another round of adding missing
'additionalProperties'")
from the devicetree tree and commit:
3b17dd2204
On Mon, Oct 05, 2020 at 04:57:32PM +0200, Peter Zijlstra wrote:
> +static inline struct task_struct *get_push_task(struct rq *rq)
> +{
> + struct task_struct *p = rq->curr;
> +
> + lockdep_assert_held(&rq->lock);
> +
> + if (rq->push_busy)
> + return NULL;
> +
> + if (p-
This patch adds dev_pm_ops to mtk-nor to support suspend/resume,
auto suspend delay is set to -1 by default.
Accessing registers are only permitted after its clock is enabled
to deal with unknown state of operating clk at probe time.
Signed-off-by: Ikjoon Jang
---
drivers/spi/spi-mtk-nor.c | 98
This patchset adds 36bit dma address and power management
supports for mt8192-nor.
Changes in v5:
- Rebase from merge conflict
Changes in v4:
- Drop two patches from a list, addressed by an another series
- Fix 0-day ci 'shift-count-overflow' warning
Changes in v3:
- Fix a bugfix of v2 in checki
This patch enables 36bit dma address support to spi-mtk-nor.
Currently this is enabled only for mt8192-nor.
Signed-off-by: Ikjoon Jang
---
drivers/spi/spi-mtk-nor.c | 21 -
1 file changed, 20 insertions(+), 1 deletion(-)
diff --git a/drivers/spi/spi-mtk-nor.c b/drivers/spi/s
Hi Geert,
On Fri, Sep 25, 2020 at 3:16 PM Geert Uytterhoeven wrote:
>
> Hi Mateusz,
>
> On Wed, Sep 23, 2020 at 12:10 PM Mateusz Holenko
> wrote:
> > From: Pawel Czarnecki
> >
> > This commit adds driver for the FPGA-based LiteX SoC
> > Controller from LiteX SoC builder.
> >
> > Co-developed-b
Hello PHY experts,
Short version:
what is the proper way to handle the PHY reset before identifying PHY?
Long version:
I stumbled over following issue:
If PHY reset is registered within PHY node. Then, sometimes, we will not be
able to identify it (read PHY ID), because PHY is under reset.
mdio
Hello,
syzbot found the following issue on:
HEAD commit:c2568c8c Merge branch 'net-Constify-struct-genl_small_ops'
git tree: net-next
console output: https://syzkaller.appspot.com/x/log.txt?x=14051a2b90
kernel config: https://syzkaller.appspot.com/x/.config?x=1e6c5266df853ae
dashbo
Hello,
syzbot found the following issue on:
HEAD commit:549738f1 Linux 5.9-rc8
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=15b97ba390
kernel config: https://syzkaller.appspot.com/x/.config?x=c06bcf3cc963d91c
dashboard link: https://syzkaller.appspot
Hello,
syzbot found the following issue on:
HEAD commit:c2568c8c Merge branch 'net-Constify-struct-genl_small_ops'
git tree: net-next
console output: https://syzkaller.appspot.com/x/log.txt?x=16e2fb4d90
kernel config: https://syzkaller.appspot.com/x/.config?x=1e6c5266df853ae
dashbo
On 10/5/20 6:31 PM, Pratyush Yadav wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the
> content is safe
>
> Since this flash doesn't have a Profile 1.0 table, the Octal DTR
> capabilities are enabled in the post SFDP fixup, along with the 8D-8D-8D
> fast read sett
On Tue, Oct 06, 2020 at 10:26:28AM +0300, Kalle Valo wrote:
> Alex Dewar writes:
>
> > ath11k_peer_create() is called without its return value being checked,
> > meaning errors will be unhandled. Add missing check and, as the mutex is
> > unconditionally unlocked on leaving this function, simplif
On 06.10.20 08:55, Dan Williams wrote:
> Towards removing the mode specific @dax_kmem_res attribute from the
> generic 'struct dev_dax', and preparing for multi-range support, move
> resource tracking to driver data. The memory for the resource name
> needs to have its own lifetime separate from t
Nishanth,
On 02/10/20 10:32 pm, Nishanth Menon wrote:
> On 22:15-20201002, Faiz Abbas wrote:
>> The following patches enable configs in the arm64 defconfig to support
>> GPIO and I2C support on TI's J721e platform.
>>
>> Faiz Abbas (2):
>> arm64: defconfig: Enable OMAP I2C driver
>> arm64: def
On Tue, Oct 06, 2020 at 01:08:23AM -0700, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit:549738f1 Linux 5.9-rc8
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=15b97ba390
> kernel config: https://syzkaller.appspot.co
This patch fixes the checkpatch.pl warning :
WARNING: else is not generally useful after a break or return
Expressions under 'else' branch in function 'gc0310_s_power' are
executed whenever the exppression in 'if' is False. Otherwise, return
from function occurs. Therefore, there is no need in 'e
Hello,
syzbot found the following issue on:
HEAD commit:22fbc037 Merge tag 'for-linus' of git://git.kernel.org/pub..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=133731eb90
kernel config: https://syzkaller.appspot.com/x/.config?x=4e672827d2ffab1f
das
Hello,
syzbot found the following issue on:
HEAD commit:d3d45f82 Merge tag 'pinctrl-v5.9-2' of git://git.kernel.or..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=14c3b3db90
kernel config: https://syzkaller.appspot.com/x/.config?x=89ab6a0c48f30b49
das
Hello,
syzbot found the following issue on:
HEAD commit:d3d45f82 Merge tag 'pinctrl-v5.9-2' of git://git.kernel.or..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1318aab790
kernel config: https://syzkaller.appspot.com/x/.config?x=89ab6a0c48f30b49
das
Hi All,
This patches are part of series [1], where patch 1/2 was missed to be applied
before YAML conversation and patch 2/2 was never applied.
I have restored the Acks for patch 1/2 and patch 2/2 is unchanged.
[1] https://patchwork.kernel.org/project/linux-renesas-soc/list/?series=329853
Cheer
Document r8a7742 specific compatible strings. No driver change is
needed as the fallback compatible string "renesas,tpu" activates the
right code in the driver.
Signed-off-by: Lad Prabhakar
Reviewed-by: Marian-Cristian Rotariu
Reviewed-by: Geert Uytterhoeven
Acked-by: Rob Herring
---
Document
Document RZ/G1H (R8A7742) SoC bindings.
Signed-off-by: Lad Prabhakar
Reviewed-by: Marian-Cristian Rotariu
Acked-by: Uwe Kleine-König
Reviewed-by: Geert Uytterhoeven
Reviewed-by: Yoshihiro Shimoda
Acked-by: Rob Herring
---
Documentation/devicetree/bindings/pwm/renesas,pwm-rcar.yaml | 1 +
1
On 05/10/2020 19:38, Rob Herring wrote:
In order to add meta-schema checks for additional/unevaluatedProperties
being present, all schema need to make this explicit. As common/shared
schema are included by other schemas, they should always allow for
additionalProperties.
Signed-off-by: Rob He
tree/branch:
https://git.kernel.org/pub/scm/linux/kernel/git/gustavoars/linux.git
testing/drm/amd/pm/phm
branch HEAD: c43a9eea7b3f51236a4dccc448f636500e3704d9 drm/amd/pm: Replace
one-element array with flexible-array member
elapsed time: 725m
configs tested: 97
configs skipped: 2
The follow
Em Mon, 5 Oct 2020 12:08:23 -0700
Eric Biggers escreveu:
> On Mon, Oct 05, 2020 at 02:06:22PM +0200, Mauro Carvalho Chehab wrote:
> > The latest version at:
> >
> >
> > https://git.linuxtv.org/mchehab/experimental.git/log/?h=sphinx3-fixes-v4
>
> Doesn't work either.
>
> $ git remote add
> @@ -1352,19 +1340,13 @@ static int exfat_rename(struct inode *old_dir, struct
> dentry *old_dentry,
> new_dir->i_ctime = new_dir->i_mtime = new_dir->i_atime =
> EXFAT_I(new_dir)->i_crtime = current_time(new_dir);
> exfat_truncate_atime(&new_dir->i_atime);
> - if (IS
On Tue, 6 Oct 2020 at 11:24, Naresh Kamboju wrote:
>
> On Mon, 5 Oct 2020 at 20:59, Greg Kroah-Hartman
> wrote:
> >
> > This is the start of the stable review cycle for the 5.4.70 release.
> > There are 57 patches in this series, all will be posted as a response
> > to this one. If anyone has an
On 05.10.20 21:11, Roman Gushchin wrote:
> On Mon, Oct 05, 2020 at 08:33:44PM +0200, David Hildenbrand wrote:
>> On 05.10.20 20:25, Roman Gushchin wrote:
>>> On Mon, Oct 05, 2020 at 07:27:47PM +0200, David Hildenbrand wrote:
On 05.10.20 19:16, Roman Gushchin wrote:
> On Mon, Oct 05, 2020 a
On 05/10/2020 19:38, Rob Herring wrote:
The default behavior for json-schema is any unknown property is allowed.
T
hat is generally not the behavior we want for DT. In order to disallow
extra properties, schemas need to define 'additionalProperties: false'
typically. Ideally, we'd just add th
On Mon, Oct 05, 2020 at 12:30:03PM -0700, Andy Lutomirski wrote:
> @@ -441,6 +441,9 @@ struct fixed_percpu_data {
>* GCC hardcodes the stack canary as %gs:40. Since the
>* irq_stack is the object at %gs:0, we reserve the bottom
>* 48 bytes of the irq stack for the canary.
>
The Dell WMI Systems Management Driver provides a sysfs
interface for systems management to enable BIOS configuration
capability on certain Dell Systems.
This driver allows user to configure Dell systems with a
uniform common interface. To facilitate this, the patch
introduces a generic way for dr
On Mon, Oct 05, 2020 at 07:10:39PM -0400, Brian Gerst wrote:
> On Mon, Oct 5, 2020 at 3:30 PM Andy Lutomirski wrote:
> >
> > x86_32 stackprotector is a maintenance nightmare. Clean it up. This
> > disables stackprotector on x86_32 on GCC 8.1 and on all clang
> > versions -- I'll file a bug for t
On Tue, Oct 6, 2020 at 7:04 AM Alain Volmat wrote:
> Hi Russell,
>
> Could you have a look a those two patches for the STi platform ?
I don't think there is much to say about those patches they are
straight-forward.
I would just put them into Russell's patch tracker. I think the
SoC tree also t
On Mon, Oct 05, 2020 at 10:48:54PM -0500, Jeremy Linton wrote:
> The AES code uses a 'br x7' as part of a function called by
> a macro. That branch needs a bti_j as a target. This results
> in a panic as seen below. Instead of trying to replace the branch
> target with a bti_jc, lets replace the in
On Mon, 5 Oct 2020, Kees Cook wrote:
> > TYPESAFE_BY_RCU, but if forcing that on by default would enhance security
> > by a measurable amount, it wouldn't be a terribly hard sell ...
>
> Isn't the "easy" version of this already controlled by slab_merge? (i.e.
> do not share same-sized/flagged km
On Mon, Oct 05, 2020 at 12:30:04PM -0700, Andy Lutomirski wrote:
> .macro SAVE_ALL pt_regs_ax=%eax switch_stacks=0 skip_gs=0 unwind_espfix=0
> cld
> .if \skip_gs == 0
> - PUSH_GS
> + pushl $0
> .endif
> pushl %fs
>
Is there a good reason not to just push gs into it? It
On Tue 22-09-20 16:37:12, Vlastimil Babka wrote:
> Page isolation can race with process freeing pages to pcplists in a way that
> a page from isolated pageblock can end up on pcplist. This can be fixed by
> repeated draining of pcplists, as done by patch "mm/memory_hotplug: drain
> per-cpu pages ag
Hi Rafael,
Numerous workload regressions have bisected repeatedly to the commit
6d4f08a6776 ("intel_idle: Use ACPI _CST on server systems") but only on
a set of haswell machines that all have the same CPU.
CPU(s): 48
On-line CPU(s) list: 0-47
Thread(s) per core: 2
Core(s) per socket
On Tue, 2020-10-06 at 06:47 +, Dexuan Cui wrote:
> Hi all,
> I'm running a single-CPU Linux VM on Hyper-V. The Linux kernel is v5.9-rc7
> and I have CONFIG_NR_CPUS=256.
>
> The Hyper-V Host (Version 17763-10.0-1-0.1457) provides a guest firmware,
> which always reports 128 Local APIC entries i
It was <2020-10-02 pią 21:45>, when Andrew Lunn wrote:
> On Fri, Oct 02, 2020 at 09:22:06PM +0200, Łukasz Stelmach wrote:
>> This is a driver for AX88796C Ethernet Adapter connected in SPI mode as
>> found on ARTIK5 evaluation board. The driver has been ported from a
>> v3.10.9 vendor kernel for AR
On Mon, Oct 05, 2020 at 05:30:59PM +0200, Miguel Ojeda wrote:
> Hi Lars,
>
> On Mon, Oct 5, 2020 at 2:27 PM wrote:
> >
> > This tries to make charlcd device independent.
>
> Thanks a lot for the work!
>
> I see you have written the differences between versions in each patch,
> but given there a
Hi Mateusz,
On Tue, Oct 6, 2020 at 10:02 AM Mateusz Holenko wrote:
> On Fri, Sep 25, 2020 at 3:16 PM Geert Uytterhoeven
> wrote:
> > On Wed, Sep 23, 2020 at 12:10 PM Mateusz Holenko
> > wrote:
> > > From: Pawel Czarnecki
> > >
> > > This commit adds driver for the FPGA-based LiteX SoC
> > >
1 - 100 of 1080 matches
Mail list logo
