On 7/23/20 4:15 PM, Arvind Sankar wrote:
> This #define is not used anywhere, and has the wrong value on x86_64.
Yeah, it certainly is unused.
> I tried digging into the history a bit, but it seems to have been unused
> even in the initial merge of sparsemem in v2.6.13, when it was first
>
On Fri, Jul 24, 2020 at 04:59:00PM +0200, Greg KH wrote:
> On Fri, Jul 24, 2020 at 09:48:54AM -0400, Jason Baron wrote:
> >
> >
> > On 7/19/20 7:10 PM, Jim Cromie wrote:
> > > this is v5, changes from previous:
> > > - moved a chunk from patch 13 to 12, per Jason
> > > - shorten logging prefix
On 07/23/20 at 11:21am, Mike Kravetz wrote:
> On 7/23/20 2:11 AM, Baoquan He wrote:
> > On 07/23/20 at 11:46am, Anshuman Khandual wrote:
> >>
> >>
> >> On 07/23/2020 08:52 AM, Baoquan He wrote:
> >>> A customer complained that no message is logged when the number of
> >>> persistent huge
On Fri, Jul 24, 2020 at 07:46:32AM -0700, Andi Kleen wrote:
> > Something that seems to 'work' is:
> > '{cycles,cpu/instructions,period=5/}', so maybe you can make the
> > group modifier :S use any sampling event if there is one, and otherwise
> > designate the leader.
> >
> > Then you can
Add support to read "renesas-vin-ycbcr-8b-g" DT property and select
the data pins accordingly for YCbCr422-8bit input
Signed-off-by: Lad Prabhakar
Reviewed-by: Biju Das
---
drivers/media/platform/rcar-vin/rcar-core.c | 4 +++-
drivers/media/platform/rcar-vin/rcar-dma.c | 7 +++
Hi All,
This patch series adds support to enable selecting data
lines via DT.
Cheers,
Prabhakar
Lad Prabhakar (2):
dt-bindings: media: renesas,vin: Document renesas-vin-ycbcr-8b-g
property
media: rcar-vin: Add support to read renesas-vin-ycbcr-8b-g property
Add a DT property "renesas-vin-ycbcr-8b-g" to select YCbCr422 8-bit data
input pins.
Signed-off-by: Lad Prabhakar
Reviewed-by: Biju Das
---
Documentation/devicetree/bindings/media/renesas,vin.yaml | 13 +
1 file changed, 13 insertions(+)
diff --git
On Fri, Jul 24, 2020 at 09:48:54AM -0400, Jason Baron wrote:
>
>
> On 7/19/20 7:10 PM, Jim Cromie wrote:
> > this is v5, changes from previous:
> > - moved a chunk from patch 13 to 12, per Jason
> > - shorten logging prefix to "dyndbg", drop __func__
> > - now with more commit-log advocacy
>
Fri, Jul 24, 2020 at 04:19:51PM CEST, vadym.koc...@plvision.eu wrote:
>Marvell Prestera 98DX326x integrates up to 24 ports of 1GbE with 8
>ports of 10GbE uplinks or 2 ports of 40Gbps stacking for a largely
>wireless SMB deployment.
>
>Prestera Switchdev is a firmware based driver that operates via
On Fri, Jul 24, 2020 at 08:57:47AM +0200, Greg KH wrote:
> On Fri, Jul 24, 2020 at 10:18:07AM +0530, Madhuparna Bhowmik wrote:
> > On Thu, Jul 23, 2020 at 03:11:58PM -0700, David Miller wrote:
> > > From: madhuparnabhowmi...@gmail.com
> > > Date: Wed, 22 Jul 2020 22:53:29 +0530
> > >
> > > >
On Fri, 24 Jul 2020 13:27:48 +0300
Mike Rapoport wrote:
> On Fri, Jul 24, 2020 at 08:05:52AM +0300, Jarkko Sakkinen wrote:
> > Use text_alloc() and text_free() instead of module_alloc() and
> > module_memfree() when an arch provides them.
> >
> > Cc: linux...@kvack.org
> > Cc: Andi Kleen
> >
On Fri, Jul 24, 2020 at 12:38:40PM +0200, Luka Kovacic wrote:
> An entry is added for MikroTik CRS3xx 98DX3236 based switches.
>
> Signed-off-by: Luka Kovacic
> Cc: Luka Perkov
> Cc: Jakov Petrina
Reviewed-by: Andrew Lunn
Andrew
On Fri, Jul 24, 2020 at 12:38:39PM +0200, Luka Kovacic wrote:
> MikroTik CRS328-4C-20S-4S board has a switch chip with an integrated
> Marvell Prestera 98DX3236 CPU.
>
> This commit includes two board variants, namely the factory
> default one and a Bit variant. The Bit variant has a
> bigger
Hi Linus,
Thanks for the review
> -Original Message-
> From: Linus Walleij
> Sent: Friday, July 24, 2020 2:52 PM
> To: kernel test robot
> Cc: Srinivas Neeli ; Bartosz Golaszewski
> ; Michal Simek ;
> Shubhrajyoti Datta ; Srinivas Goud
> ; kbuild-...@lists.01.org; open list:GPIO
On 7/23/20 2:26 PM, Rajendra Nayak wrote:
> Post a successful pm_ops->core_get, an error in probe
> should exit by doing a pm_ops->core_put which seems
> to be missing. So fix it.
>
> Signed-off-by: Rajendra Nayak
> ---
> drivers/media/platform/qcom/venus/core.c | 15 ++-
> 1
Hi,
This is a subset of my bigger work for memory controller drivers [1].
Patch #1 (memory): I can take it through my tree because of dependant
work around compile testing.
Patch #2: Independent, please pick it up if it looks good.
[1]
On Fri, Jul 24, 2020 at 12:38:38PM +0200, Luka Kovacic wrote:
> MikroTik CRS305-1G-4S board has a switch chip with an integrated
> Marvell Prestera 98DX3236 CPU.
>
> This commit includes two board variants, namely the factory
> default one and a Bit variant. The Bit variant has a
> bigger
Enabling the JZ4780_NEMC driver makes sense only for specific hardware -
the Ingenic SoC architecture. Set it's dependency to MACH_INGENIC so it
will not appear on unrelated architectures (easier job for
downstream/distro kernel engineers).
When compile testing, do not enable the driver on other
On Fri, Jul 24, 2020 at 10:31:23AM -0400, qianjun.ker...@gmail.com wrote:
> From: jun qian
>
> When get the pending softirqs, it need to process all the pending
> softirqs in the while loop. If the processing time of each pending
> softirq is need more than 2 msec in this loop, or one of the
Enabling the MTD_NAND_JZ4780 driver makes sense only for specific
hardware - the Ingenic SoC architecture. Set it's dependency to
MACH_INGENIC so it will not appear on unrelated architectures (easier
job for downstream/distro kernel engineers).
Signed-off-by: Krzysztof Kozlowski
---
Changes
On Fri, Jul 24, 2020 at 12:38:37PM +0200, Luka Kovacic wrote:
> MikroTik CRS326-24G-2S board has a switch chip with an integrated
> Marvell Prestera 98DX3236 CPU.
>
> This commit includes two board variants, namely the factory
> default one and a Bit variant. The Bit variant has a
> bigger
On Fri, Jul 24, 2020 at 11:21:19AM +1200, Chris Packham wrote:
> This series connects up the mv88e6xxx switches to the dsa infrastructure for
> configuring the port MTU. The first patch is also a bug fix which might be a
> candiatate for stable.
>
> I've rebased this series on top of
Hello,
From the book "Linux device drivers" (3rd edition), I find an
interesting rule for streaming DMA mapping:
Once a buffer has been mapped, it belongs to the device, not the
processor. Until
the buffer has been unmapped, the driver should not touch its contents
in any
way. Only after
Document device tree bindings of Seeed SoM and carrier board.
Signed-off-by: Marcin Sloniewski
---
Documentation/devicetree/bindings/arm/stm32/stm32.yaml | 6 ++
1 file changed, 6 insertions(+)
diff --git a/Documentation/devicetree/bindings/arm/stm32/stm32.yaml
On Thu, Jul 23, 2020 at 03:37:29PM -0700, Ashok Raj wrote:
> PASID and PRI capabilities are only enumerated in PF devices. VF devices
> do not enumerate these capabilites. IOMMU drivers also need to enumerate
> them before enabling features in the IOMMU. Extending the same support as
> PASID
Add the "seeed" vendor prefix for Seeed Technology Co., Ltd
Website: https://www.seeedstudio.com/
Signed-off-by: Marcin Sloniewski
Acked-by: Rob Herring
---
Documentation/devicetree/bindings/vendor-prefixes.yaml | 2 ++
1 file changed, 2 insertions(+)
diff --git
On Fri, Jul 24, 2020 at 07:39:08AM -0700, Andi Kleen wrote:
> > The consequence is that SLOTS must be the leader, is that really a
> > problem? You keep providing the {cycles, slots, metric-things} example,
>
> Yes that's a problem. One (major) use case for topdown is to
> sample on lots of
Add support for Seeed Studio's stm32mp157c odyssey board.
Board consists of SoM with stm32mp157c with 4GB eMMC and 512 MB DDR3 RAM
and carrier board with USB and ETH interfaces, SD card connector,
wifi and BT chip AP6236.
In this patch only basic kernel boot is supported and interfacing
SD card
On Fri, Jul 24, 2020 at 03:28:02PM +0200, Ingo Molnar wrote:
> Given that you are perf stress-testing the box, some recent perf
> commit would be the primary suspect - before doing a full bisect you
> might want to try current perf/core (2ac5413e5edc) and its upstream
> base: v5.8-rc3, to
On Fri, Jul 24, 2020 at 11:21:22AM +1200, Chris Packham wrote:
> Some of the chips in the mv88e6xxx family don't support jumbo
> configuration per port. But they do have a chip-wide max frame size that
> can be used. Use this to approximate the behaviour of configuring a port
> based MTU.
>
>
Hi Hans,
Could you suggest how to proceed with this :
- wait Samsung mainteners for ack.
- make a pull request with your ack for samsung mfc driver changes.
- make a pull request for constant quality only.
- postpone the whole patchset for 5.10 merge window.
On 7/21/20 10:45 AM, Stanimir
The following commit has been merged into the x86/build branch of tip:
Commit-ID: 587af649bcc04eb016822f209a975005c0092151
Gitweb:
https://git.kernel.org/tip/587af649bcc04eb016822f209a975005c0092151
Author:Arvind Sankar
AuthorDate:Wed, 22 Jul 2020 14:43:34 -04:00
On Fri, Jul 24, 2020 at 4:30 PM Arvind Sankar wrote:
>
> On Fri, Jul 24, 2020 at 02:50:34AM +0200, Sedat Dilek wrote:
> > On Thu, Jul 23, 2020 at 9:30 PM Nick Terrell wrote:
> > >
> > > From: Nick Terrell
> > >
> > > * Add support for zstd compressed kernel
> > > * Define __DISABLE_EXPORTS in
On Fri, 24 Jul 2020 08:05:48 +0300
Jarkko Sakkinen wrote:
> Add lock_modules() and unlock_modules() wrappers for acquiring module_mutex
> in order to remove the compile time dependency to it.
This subject is a bit confusing. This is just wrapping modules_mutex in
kpprobes. We still have compile
> Something that seems to 'work' is:
> '{cycles,cpu/instructions,period=5/}', so maybe you can make the
> group modifier :S use any sampling event if there is one, and otherwise
> designate the leader.
>
> Then you can write things like:
>
> '{slots, metric1, metric2,
On 07/23, Linus Torvalds wrote:
>
> IOW, I think we should do something like this (this is on top of my
> patch, since it has that wake_page_function() change in it, but notice
> how we have the exact same issue in our traditional
> autoremove_wake_function() usage).
...
> +static inline void
On Sun, Jul 19, 2020 at 06:19:20PM +0200, Alexander A. Klimov wrote:
> Rationale:
> Reduces attack surface on kernel devs opening the links for MITM
> as HTTPS traffic is much harder to manipulate.
>
> Deterministic algorithm:
> For each file:
> If not .svg:
> For each line:
> If
On Fri, Jul 24, 2020 at 7:28 AM Michael S. Tsirkin wrote:
>
> On Wed, Apr 22, 2020 at 05:26:31PM -0700, Daniel Colascione wrote:
> > userfaultfd handles page faults from both user and kernel code. Add a
> > new UFFD_USER_MODE_ONLY flag for userfaultfd(2) that makes the
> > resulting userfaultfd
On Fri, Jul 24, 2020 at 12:19:59AM -0700, Ian Rogers wrote:
> for_each_set_bit, or similar functions like for_each_cpu, may be hot
> within the kernel. If many bits were set then one could imagine on
> Intel a "bt" instruction with every bit may be faster than the function
> call and word length
On 7/24/20 7:39 AM, Guenter Roeck wrote:
> On 7/24/20 3:11 AM, Wang ShaoBo wrote:
>> Drop trailing whitespace.
>>
>> Signed-off-by: Wang ShaoBo
>> ---
>> drivers/hwmon/pmbus/max20730.c | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/hwmon/pmbus/max20730.c
On Fri, Jul 24, 2020 at 7:01 AM Michael S. Tsirkin wrote:
>
> On Wed, Apr 22, 2020 at 05:26:30PM -0700, Daniel Colascione wrote:
> > This small patch series adds a new flag to userfaultfd(2) that allows
> > callers to give up the ability to handle user-mode faults with the
> > resulting UFFD file
On Fri, Jul 24, 2020 at 03:30:39PM +0200, Christian Brauner wrote:
> On Thu, Jul 23, 2020 at 10:41:40AM -0700, Andrei Vagin wrote:
> > On Wed, Jul 22, 2020 at 07:15:06PM +0100, Catalin Marinas wrote:
> > > On Mon, Jul 13, 2020 at 06:57:43PM -0700, Andrei Vagin wrote:
> > > > On Sat, Jul 04, 2020
> The consequence is that SLOTS must be the leader, is that really a
> problem? You keep providing the {cycles, slots, metric-things} example,
Yes that's a problem. One (major) use case for topdown is to
sample on lots of different events, but always create groups that
also measure topdown
On 7/24/20 3:11 AM, Wang ShaoBo wrote:
> Drop trailing whitespace.
>
> Signed-off-by: Wang ShaoBo
> ---
> drivers/hwmon/pmbus/max20730.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/hwmon/pmbus/max20730.c b/drivers/hwmon/pmbus/max20730.c
> index
On 7/24/20 10:13 AM, Sibi Sankar wrote:
Hey Jonathan,
Thanks for the patch! Please use the
suggested register space definitions
instead.
Thanks for the suggestions, I was unsure what to use for the sizes. The
reg field is unused by the upstream driver so it is hard to figure out.
However,
On Thu, 23 Jul 2020 16:20:20 +0200, Jerome Brunet wrote:
> With commit e2329eeba45f ("ASoC: soc-component: add soc_component_err()")
> every error different for ENOTSUPP or EPROBE_DEFER will log an error.
>
> However, as explained in snd_soc_get_dai_name(), this callback may error
> to indicate
On Fri, Jul 10, 2020 at 11:46 AM Daniel Palmer wrote:
>
> This patch set adds initial support for MStar/Sigmastar's
> Armv7 based SoCs. There is just enough here to get to a shell
> with an initramfs but support for a lot of the hardware is
> in progress and will follow.
>
> MStar also shipped
On Fri, 24 Jul 2020 03:50:13 +0300, Vladimir Zapolskiy wrote:
> The change corrects registration and deregistration on error path
> of a regulator, the problem was manifested by a reported memory
> leak on deferred probe:
>
> as3722-regulator as3722-regulator: regulator 13 register failed
On Fri, Jul 24, 2020 at 12:57:51PM +0300, Mika Westerberg wrote:
> On Thu, Jul 23, 2020 at 10:30:58PM +0200, Karol Herbst wrote:
> > On Wed, Jul 22, 2020 at 11:25 AM Mika Westerberg
> > wrote:
> > >
> > > On Tue, Jul 21, 2020 at 01:37:12PM -0500, Patrick Volkerding wrote:
> > > > On 7/21/20 10:27
CCing Dan
On 24.07.20 14:42, Roger Pau Monne wrote:
> To be used in order to create foreign mappings. This is based on the
> ZONE_DEVICE facility which is used by persistent memory devices in
> order to create struct pages and kernel virtual mappings for the IOMEM
> areas of such devices. Note
On 7/24/20 12:15 AM, Joel Stanley wrote:
> From: Joachim Fenkes
>
> On BMCs with lower timer resolution than 1ms, msleep(1) will take
> way longer than 1ms, so looping 10k times won't wait for 10s but
> significantly longer.
>
> Fix this by using jiffies like the rest of the code.
>
> Fixes:
On 24.07.20 14:42, Roger Pau Monne wrote:
To be used in order to create foreign mappings. This is based on the
ZONE_DEVICE facility which is used by persistent memory devices in
order to create struct pages and kernel virtual mappings for the IOMEM
areas of such devices. Note that on kernels
On Fri, Jul 24, 2020 at 10:19:25AM -0400, Liang, Kan wrote:
> There will be a problem for the current perf tool, which assumes that the
> leader event is the sampling event.
>
> I will check how can we specially handle it in the perf tool.
Ah, okay. I've long lost track of how the tool works :/
On Wed, Jul 22, 2020 at 11:45:49AM +0200, David Hildenbrand wrote:
> This series is based on the latest s390/features branch [1]. It
> consolidates vmem_add_range(), vmem_remove_range(), and vmemmap_populate()
> into a single, recursive page table walker. It then implements
> vmemmap_free() and
On 7/23/20 9:50 PM, Chris Packham wrote:
> There's not much feedback when the ds1388 watchdog fires. Generally it
> yanks on the reset line and the board reboots. To provide some feedback
> indicate that the watchdog has fired in the past. This should help
> distinguish a watchdog triggered reset
Hi Robert,
> On Jul 22, 2020, at 07:55, Robert Hancock wrote:
>
> On Fri, Jul 10, 2020 at 6:28 PM Robert Hancock wrote:
>>
>> On Fri, Jul 10, 2020 at 6:23 PM Robert Hancock wrote:
>>>
>>> Noticed a problem on my desktop with an Asus PRIME H270-PRO
>>> motherboard after Fedora 32 upgraded to
From: jun qian
When get the pending softirqs, it need to process all the pending
softirqs in the while loop. If the processing time of each pending
softirq is need more than 2 msec in this loop, or one of the softirq
will running a long time, according to the original code logic, it
will process
On Fri, Jul 24, 2020 at 02:50:34AM +0200, Sedat Dilek wrote:
> On Thu, Jul 23, 2020 at 9:30 PM Nick Terrell wrote:
> >
> > From: Nick Terrell
> >
> > * Add support for zstd compressed kernel
> > * Define __DISABLE_EXPORTS in misc.c
> > * Bump the heap size for zstd.
> > * Update the
Hey Jonathan,
Thanks for the patch!
On 2020-07-13 21:11, Jonathan Marek wrote:
Add driver for the Qualcomm interconnect buses found in SM8250 based
platforms. The topology consists of several NoCs that are controlled by
a remote processor that collects the aggregated bandwidth for each
Hey Jonathan,
Thanks for the patch!
On 2020-07-13 21:11, Jonathan Marek wrote:
Add driver for the Qualcomm interconnect buses found in SM8150 based
platforms. The topology consists of several NoCs that are controlled by
a remote processor that collects the aggregated bandwidth for each
On Wed, Apr 22, 2020 at 05:26:31PM -0700, Daniel Colascione wrote:
> userfaultfd handles page faults from both user and kernel code. Add a
> new UFFD_USER_MODE_ONLY flag for userfaultfd(2) that makes the
> resulting userfaultfd object refuse to handle faults from kernel mode,
> treating these
* Thomas Gleixner wrote:
> From: Thomas Gleixner
>
> Replace the x86 code with the generic variant. Use temporary defines for
> idtentry_* which will be cleaned up in the next step.
>
> Signed-off-by: Thomas Gleixner
There was a comment that still referenced the old x86-specific API
On Fri 24-07-20 21:56:29, Muchun Song wrote:
> On Fri, Jul 24, 2020 at 7:34 PM Michal Hocko wrote:
[...]
> > I believe you can simplify this and use a similar pattern as the page
> > allocator. Something like
> >
> > for_each_node_mask(node, mpol_allowed) {
> > if
* Thomas Gleixner wrote:
> From: Thomas Gleixner
>
> Use the generic infrastructure to check for and handle pending work before
> transitioning into guest mode.
>
> This now handles TIF_NOTIFY_RESUME as well which was ignored so
> far. Handling it is important as this covers task work and
On 24/07/20, Sumit Garg wrote:
> On Thu, 23 Jul 2020 at 14:16, Jorge Ramirez-Ortiz wrote:
> >
> > The current code waits for data to be available before attempting a
> > second read. However the second read would not be executed as the
> > while loop exits.
> >
> > This fix does not wait if all
The ethtool API provides support for the configuration of the following
features: speed and duplex, auto-negotiation, MDI-x, forward error
correction, port media type. The API also provides information about the
port status, hardware and software statistic. The following limitation
exists:
-
The following features are supported:
- VLAN-aware bridge offloading
- VLAN-unaware bridge offloading
- FDB offloading (learning, ageing)
- Switchport configuration
Currently there are some limitations like:
- Only 1 VLAN-aware bridge instance supported
- FDB ageing
Marvell Prestera 98DX326x integrates up to 24 ports of 1GbE with 8
ports of 10GbE uplinks or 2 ports of 40Gbps stacking for a largely
wireless SMB deployment.
The current implementation supports only boards designed for the Marvell
Switchdev solution and requires special firmware.
The core
Add PCI interface driver for Prestera Switch ASICs family devices, which
provides:
- Firmware loading mechanism
- Requests & events handling to/from the firmware
- Access to the firmware on the bus level
The firmware has to be loaded each time device is reset. The driver is
loading
Add brief description how to configure base mac address binding in
device-tree.
Describe requirement for the PCI port which is connected to the ASIC, to
allow access to the firmware related registers.
Signed-off-by: Vadym Kochan
---
.../bindings/net/marvell,prestera.txt | 34
Add very basic support for devlink interface:
- driver name
- fw version
- devlink ports
Signed-off-by: Vadym Kochan
---
drivers/net/ethernet/marvell/prestera/Kconfig | 1 +
.../net/ethernet/marvell/prestera/Makefile| 2 +-
.../net/ethernet/marvell/prestera/prestera.h |
Marvell Prestera 98DX326x integrates up to 24 ports of 1GbE with 8
ports of 10GbE uplinks or 2 ports of 40Gbps stacking for a largely
wireless SMB deployment.
Prestera Switchdev is a firmware based driver that operates via PCI bus. The
current implementation supports only boards designed for the
On 7/24/2020 9:54 AM, Peter Zijlstra wrote:
On Fri, Jul 24, 2020 at 09:43:44AM -0400, Liang, Kan wrote:
On 7/24/2020 7:46 AM, pet...@infradead.org wrote:
On Fri, Jul 24, 2020 at 12:55:43PM +0200, pet...@infradead.org wrote:
+ event_sched_out(event, cpuctx, ctx);
+
Hi Evgeny,
Thank you for the patch.
On Thu, Jul 23, 2020 at 6:04 PM Evgeny Novikov wrote:
>
> In case of errors vpif_probe_complete() releases memory for vpif_obj.sd
> and unregisters the V4L2 device. But then this is done again by
> vpif_probe() itself. The patch removes the cleaning from
>
On Fri, Jul 24, 2020 at 09:40:31AM +0200, Krzysztof Kozlowski wrote:
> Fix minor whitespace and comment issues. No functional changes.
>
> Signed-off-by: Krzysztof Kozlowski
>
> ---
Applied (and part of pull request to arm-soc).
For the other omap-gpmc testing is welcomed.
Best regards,
In some platforms, VCC regulator may not be declared in device tree
to keep itself "always-on". In this case, hba->vreg_info.vcc is NULL
and shall not be operated during any flow.
Prevent possible NULL hba->vreg_info.vcc access in LPM mode by checking
if it is valid first.
Signed-off-by: Stanley
On Fri, Jul 24, 2020 at 09:40:32AM +0200, Krzysztof Kozlowski wrote:
> Add GPLv2 license header and remove GPL boiler plate text.
>
> Signed-off-by: Krzysztof Kozlowski
> ---
> drivers/memory/pl172.c | 5 +
> 1 file changed, 1 insertion(+), 4 deletions(-)
Applied (and part of pull request
On Fri, Jul 24, 2020 at 09:40:36AM +0200, Krzysztof Kozlowski wrote:
> The variable 'node' is not used. Remove it to silence compile warning:
>
> drivers/memory/da8xx-ddrctl.c: In function 'da8xx_ddrctl_probe':
> drivers/memory/da8xx-ddrctl.c:105:22: warning: variable 'node' set but
>
On Fri, Jul 24, 2020 at 09:40:35AM +0200, Krzysztof Kozlowski wrote:
> Fix minor whitespace and comment issues. Do not break message strings.
> No functional changes.
>
> Signed-off-by: Krzysztof Kozlowski
>
> ---
>
> Changes since v1:
> 1. New patch
> ---
> drivers/memory/fsl_ifc.c | 30
On Fri, Jul 24, 2020 at 09:40:28AM +0200, Krzysztof Kozlowski wrote:
> Fix checkpatch warning:
> WARNING: function definition argument 'struct device *' should also have
> an identifier name
>
> Signed-off-by: Krzysztof Kozlowski
> ---
> drivers/memory/mtk-smi.c | 2 +-
> 1 file changed, 1
On Fri, Jul 24, 2020 at 09:40:27AM +0200, Krzysztof Kozlowski wrote:
> Single statement blocks don't need braces. Fixes checkpatch warning:
>
> WARNING: braces {} are not necessary for single statement blocks
>
> Signed-off-by: Krzysztof Kozlowski
> Acked-by: Florian Fainelli
> Acked-by:
Hey Jonathan,
Thanks for the patch! Please use the
suggested register space definitions
instead.
On 2020-07-13 21:11, Jonathan Marek wrote:
Add the interconnect dts nodes for sm8150.
Signed-off-by: Jonathan Marek
---
arch/arm64/boot/dts/qcom/sm8150.dtsi | 82
1
Hey Jonathan,
Thanks for the patch! Please use the
suggested register space definitions
instead.
On 2020-07-13 21:11, Jonathan Marek wrote:
Add the interconnect dts nodes for sm8250.
Signed-off-by: Jonathan Marek
---
arch/arm64/boot/dts/qcom/sm8250.dtsi | 82
1
On Fri, Jul 24, 2020 at 09:40:26AM +0200, Krzysztof Kozlowski wrote:
> The string itself can be made const for safety.
>
> Signed-off-by: Krzysztof Kozlowski
> Acked-by: Florian Fainelli
> Acked-by: Markus Mayer
> ---
> drivers/memory/brcmstb_dpfe.c | 2 +-
> 1 file changed, 1 insertion(+), 1
On Fri, Jul 24, 2020 at 09:40:24AM +0200, Krzysztof Kozlowski wrote:
> Cast pointer to iomem memory properly to fix sparse warning:
>
> drivers/memory/ti-emif-pm.c:251:38: warning: incorrect type in argument 1
> (different address spaces)
> drivers/memory/ti-emif-pm.c:251:38:expected
On Fri, Jul 24, 2020 at 09:40:23AM +0200, Krzysztof Kozlowski wrote:
> The platform_get_irq() already prints error message so there is no need
> to do it again in the driver.
>
> Signed-off-by: Krzysztof Kozlowski
> ---
> drivers/memory/emif.c | 5 +
> 1 file changed, 1 insertion(+), 4
On Fri, Jul 24, 2020 at 09:40:22AM +0200, Krzysztof Kozlowski wrote:
> Make the code and printed messages slightly more readable. Fixes
> checkpatch warnings:
>
> WARNING: quoted string split across lines
> ERROR: space prohibited before that ',' (ctx:WxW)
>
> Signed-off-by: Krzysztof
On Fri, Jul 24, 2020 at 09:40:13AM +0200, Krzysztof Kozlowski wrote:
> SS conflicts with compile test build on i386:
>
> drivers/memory/ti-aemif.c:40:0: warning: "SS" redefined
> In file included from arch/x86/include/uapi/asm/ptrace.h:6:0,
> from
On Fri, Jul 24, 2020 at 09:40:21AM +0200, Krzysztof Kozlowski wrote:
> Fixes checkpatch warning:
>
> WARNING: Comparisons should place the constant on the right side of the
> test
>
> Signed-off-by: Krzysztof Kozlowski
> ---
> drivers/memory/emif.c | 2 +-
> 1 file changed, 1
Hi,
On 7/23/20 9:06 PM, Stanimir Varbanov wrote:
> Hi Rajendra,
>
> After applying 2,3 and 4/5 patches on linaro-integration v5.8-rc2 I see
> below messages on db845:
>
> qcom-venus aa0.video-codec: dev_pm_opp_set_rate: failed to find
> current OPP for freq 53397 (-34)
>
> ^^^ This one
On Fri, Jul 24, 2020 at 09:40:20AM +0200, Krzysztof Kozlowski wrote:
> Add GPLv2 license header and remove GPL boiler plate text.
>
> Signed-off-by: Krzysztof Kozlowski
>
> ---
>
> Changes since v1:
> 1. Use "GPL-2.0" instead of "GPL-2.0-only". It's shorter.
> ---
>
Hi,
pt., 24 lip 2020 o 11:17 Ahmad Fatoum napisał(a):
>
> Hi,
>
> On 7/23/20 9:43 PM, Marcin Słoniewski wrote:
> > Hello Ahmad,
> >
> > First of all thank you very much for your feedback, it was very helpful!
> >
> > śr., 22 lip 2020 o 08:40 Ahmad Fatoum napisał(a):
> >>
> >> On 7/21/20 8:53
On 7/24/20 5:17 AM, Ingo Molnar wrote:
>
> * Randy Dunlap wrote:
>
>> On 7/23/20 12:27 PM, Nick Terrell wrote:
>>> +config KERNEL_ZSTD
>>> + bool "ZSTD"
>>> + depends on HAVE_KERNEL_ZSTD
>>> + help
>>> + ZSTD is a compression algorithm targeting intermediate compression
>>> + with
On Fri, Jul 24, 2020 at 09:40:12AM +0200, Krzysztof Kozlowski wrote:
> The driver uses SZ_16M which is defined in include/linux/sizes.h. On
> ARM it was pulled by other headers but its inclusion is necessary for
> compile testing on other architectures.
>
> This fixes build error when compile
On 24/07/20 5:36 am, Thiago Jung Bauermann wrote:
>
> Hari Bathini writes:
>
>> Kdump kernel, used for capturing the kernel core image, is supposed
>> to use only specific memory regions to avoid corrupting the image to
>> be captured. The regions are crashkernel range - the memory reserved
On Fri, Jul 24, 2020 at 02:26:40PM +0200, Ingo Molnar wrote:
> > -#ifdef CONFIG_KERNEL_BZIP2
> > +#if defined(CONFIG_KERNEL_BZIP2)
> > # define BOOT_HEAP_SIZE0x40
> > -#else /* !CONFIG_KERNEL_BZIP2 */
> > +#elif defined(CONFIG_KERNEL_ZSTD)
> > +# define BOOT_HEAP_SIZE
The following commit has been merged into the perf/urgent branch of tip:
Commit-ID: fe5ed7ab99c656bd2f5b79b49df0e9ebf2cead8a
Gitweb:
https://git.kernel.org/tip/fe5ed7ab99c656bd2f5b79b49df0e9ebf2cead8a
Author:Oleg Nesterov
AuthorDate:Thu, 23 Jul 2020 17:44:20 +02:00
On Fri, Jul 24, 2020 at 03:51:04PM +0200, Arnd Bergmann wrote:
> On Fri, Jul 24, 2020 at 9:41 AM Krzysztof Kozlowski wrote:
> >
> > Dear All,
> >
> > Changes since v1:
> > 1. Few new patches,
> > 2. Please see individual logs (per patch).
> >
> >
> > The drivers/memory directory contains generic
If somehow no interrupt notification is raised for a completed request
and its doorbell bit is cleared by host, UFS driver needs to cleanup
its outstanding bit in ufshcd_abort(). Otherwise, system may behave
abnormally by below flow:
After ufshcd_abort() returns, this request will be requeued by
Currently I/O request could be still submitted to UFS device while
UFS is working on shutdown flow. This may lead to racing as below
scenarios and finally system may crash due to unclocked register
accesses.
To fix this kind of issues, specifically quiesce all SCSI devices
before UFS shutdown to
701 - 800 of 1419 matches
Mail list logo
