On 7/25/19 2:47 AM, Richard Tresidder wrote:
If the of_node name of the supply is available from the devicetree binding
then include it under the var POWER_SUPPLY_OF_NODE_NAME.
This helps where a consistent name is known via the device tree binding
but it is hard to identify based on the usual
Hi,
On 25/07/19 15:56, Ingo Molnar wrote:
>
> * Ingo Molnar wrote:
>
> >
> > * Juri Lelli wrote:
> >
> > > When the topology of root domains is modified by CPUset or CPUhotplug
> > > operations information about the current deadline bandwidth held in the
> > > root domain is lost.
> > >
>
Hi Dafna,
On Wed, Jul 24, 2019 at 2:51 PM Dafna Hirschfeld
wrote:
>
> From: dafna
>
> Add basic dts support for i.MX8MQ NITROGEN8M.
>
> Signed-off-by: Gary Bisson
> Signed-off-by: Dafna Hirschfeld
Your From and Signed-off-by tags do not match.
> ---
> arch/arm64/boot/dts/freescale/Makefile
Paolo,
On Thu, 25 Jul 2019 at 19:17, Paolo Bonzini wrote:
>
> On 25/07/19 13:34, Greg Kroah-Hartman wrote:
> > Any chance you can run 'git bisect' to find the offending patch? Or
> > just try reverting a few, you can ignore the ppc ones, so that only
> > leaves you 7 different commits.
> >
> >
Hi Rafael,
at 17:51, Rafael J. Wysocki wrote:
Hi Keith,
Unfortunately,
commit d916b1be94b6dc8d293abed2451f3062f6af7551
Author: Keith Busch
Date: Thu May 23 09:27:35 2019 -0600
nvme-pci: use host managed power state for suspend
doesn't universally improve things. In fact, in some
On Thu, 25 Jul 2019 13:17:07 +
wrote:
> Hi, Boris,
>
> On 07/25/2019 03:37 PM, Boris Brezillon wrote:
> > External E-Mail
> >
> >
> > On Thu, 25 Jul 2019 11:19:06 +
> > wrote:
> >
> >>> + */
> >>> +static int spi_nor_exec_op(struct spi_nor *nor, struct spi_mem_op *op,
> >>> +
On Thu 25-07-19 15:05:02, David Hildenbrand wrote:
> On 25.07.19 14:56, Michal Hocko wrote:
> > On Wed 24-07-19 16:30:17, David Hildenbrand wrote:
> >> We end up calling __add_memory() without the device hotplug lock held.
> >> (I used a local patch to assert in __add_memory() that the
> >>
* Ingo Molnar wrote:
>
> * Juri Lelli wrote:
>
> > When the topology of root domains is modified by CPUset or CPUhotplug
> > operations information about the current deadline bandwidth held in the
> > root domain is lost.
> >
> > This patch addresses the issue by recalculating the lost
* Juri Lelli wrote:
> When the topology of root domains is modified by CPUset or CPUhotplug
> operations information about the current deadline bandwidth held in the
> root domain is lost.
>
> This patch addresses the issue by recalculating the lost deadline
> bandwidth information by
The thermal trip points have unit name but no reg property, so we can
remove them
arch/arm64/boot/dts/qcom/qcs404.dtsi:1080.31-1084.7: Warning
(unit_address_vs_reg): /thermal-zones/aoss-thermal/trips/trip-point@0: node has
a unit name, but no reg property
On Fri 24 May 2019 at 11:15, Alexandre Mergnat wrote:
> Replace hihi by hifi in the mali parent_names of the g12a SoC family.
>
> Fixes: 085a4ea93d54 ("clk: meson: g12a: add peripheral clock controller")
> Cc: Jerome Brunet
> Signed-off-by: Alexandre Mergnat
Missed that one in the last cycle,
The adc nodes have reg property but were missing the unit name, so add
that to fix these warnings:
arch/arm64/boot/dts/qcom/pms405.dtsi:91.12-94.6: Warning (unit_address_vs_reg):
/soc@0/spmi@200f000/pms405@0/adc@3100/ref_gnd: node has a reg or ranges
property, but no unit name
pms405@1 nodes specified unnecessary #address-cells/#size-cells but the
subnodes dont have "ranges" or "reg" so remove it
arch/arm64/boot/dts/qcom/pms405.dtsi:141.21-150.4: Warning
(avoid_unnecessary_addr_size): /soc@0/spmi@200f000/pms405@1: unnecessary
#address-cells/#size-cells without
So this is second installment of my work to fix warns on qcom DTS, this time
the traget is qcs404 platform.
Vinod Koul (3):
arm64: dts: qcom: pms405: add unit name adc nodes
arm64: dts: qcom: pms405: remove reduandant properties
arm64: dts: qcom: qcs404: remove unit name for thermal trip
On Wed, Jul 24, 2019 at 12:28:50PM +0530, Anshuman Khandual wrote:
> On 07/23/2019 04:26 PM, Mark Rutland wrote:
> > On Mon, Jul 15, 2019 at 11:47:47AM +0530, Anshuman Khandual wrote:
> >> This series enables memory hot remove on arm64 after fixing a memblock
> >> removal ordering problem in
On Wed, Jul 24, 2019 at 11:09 PM Haishuang Yan
wrote:
>
> We need the same checks introduced by commit cb9f1b783850
> ("ip: validate header length on virtual device xmit") for
> ipip tunnel.
Fixes: cb9f1b783850b ("ip: validate header length on virtual device xmit")
> Signed-off-by: Haishuang
On Thu, Jul 25, 2019 at 01:27:58PM +, Parshuram Raju Thombare wrote:
> Hi Andrew,
>
> >One thing which was never clear is how you are testing the features you are
> >adding. Please could you describe your test setup and how each new feature
> >is tested using that hardware. I'm particularly
On 25/07/19 13:34, Greg Kroah-Hartman wrote:
> Any chance you can run 'git bisect' to find the offending patch? Or
> just try reverting a few, you can ignore the ppc ones, so that only
> leaves you 7 different commits.
>
> Does this same test pass in 5.3-rc1?
Anders, are you running the same
On Thu, 2019-07-25 at 14:19 +0100, Mark Brown wrote:
> The patch
>
>ASoC: Intel: Fix some acpi vs apci typo in somme comments
[]
> diff --git a/sound/soc/intel/common/soc-acpi-intel-bxt-match.c
> b/sound/soc/intel/common/soc-acpi-intel-bxt-match.c
[]
> @@ -1,6 +1,6 @@
> //
On Sat, Jul 20, 2019 at 07:38:57AM +0300, Dmitry Torokhov wrote:
> On Fri, Jul 19, 2019 at 08:52:20PM +0900, Greg Kroah-Hartman wrote:
> > On Sat, Jul 06, 2019 at 10:39:38AM -0700, Dmitry Torokhov wrote:
> > > On Sat, Jul 6, 2019 at 10:19 AM Greg Kroah-Hartman
> > > wrote:
> > > >
> > > > On Sat,
25.07.2019 13:26, Vinod Koul пишет:
> On 05-07-19, 18:05, Dmitry Osipenko wrote:
>> Tegra's APB DMA engine updates words counter after each transferred burst
>> of data, hence it can report transfer's residual with more fidelity which
>> may be required in cases like audio playback. In particular
25.07.2019 12:40, Peter De Schrijver пишет:
> On Tue, Jul 23, 2019 at 04:28:35AM +0300, Dmitry Osipenko wrote:
>> 08.07.2019 2:03, Dmitry Osipenko пишет:
>>> Hello,
>>>
>>> This small series addresses two suspend-resume bugs: one affects Tegra30+
>>> due to a typo in the code, other fixes CPU hang
On Thu, Jul 25, 2019 at 01:05:54PM +0100, Lee Jones wrote:
> On Tue, 09 Jul 2019, Andy Shevchenko wrote:
>
> > On Fri, Jul 05, 2019 at 12:55:03PM +0800, Kai-Heng Feng wrote:
> > > Goodix touchpad may drop its first couple input events when
> > > i2c-designware-platdrv and intel-lpss it connects
On Fri, Jul 05, 2019 at 12:55:03PM +0800, Kai-Heng Feng wrote:
> Goodix touchpad may drop its first couple input events when
> i2c-designware-platdrv and intel-lpss it connects to took too long to
> runtime resume from runtime suspended state.
>
> This issue happens becuase the touchpad has a
On Tue, Jul 23, 2019 at 05:10:53PM -0700, Saravana Kannan wrote:
> Add device-links to track functional dependencies between devices
> after they are created (but before they are probed) by looking at
> their common DT bindings like clocks, interconnects, etc.
>
> Having functional dependencies
On Wed, Jul 24, 2019 at 11:47:02AM +0800, Chen-Yu Tsai wrote:
> From: Chen-Yu Tsai
>
> With the recent addition of commit 75dad2520fc3 ("net: dsa: b53: Disable
> all ports on setup"), users of b53 (BCM53125 on Lamobo R1 in my case)
> are forced to use the dsa subsystem to enable the switch,
On Thu, Jul 25, 2019 at 11:52:24AM +0530, Prateek Sood wrote:
> On 7/24/19 9:30 PM, Muchun Song wrote:
> > There is a race condition between removing glue directory and adding a new
> > device under the glue directory. It can be reproduced in following test:
> >
> > path 1: Add the child device
Commit-ID: d92e35b76cfcafc31987a2aa186a8e8b4ee84f52
Gitweb: https://git.kernel.org/tip/d92e35b76cfcafc31987a2aa186a8e8b4ee84f52
Author: Grzegorz Halat
AuthorDate: Fri, 28 Jun 2019 14:28:13 +0200
Committer: Thomas Gleixner
CommitDate: Thu, 25 Jul 2019 15:35:08 +0200
x86/reboot: Always
On Thu, Jul 25, 2019 at 1:25 AM Richard Tresidder
wrote:
>
> When a battery or batteries in a system are in parallel then one or more
> may not be providing any current to the system.
> This fixes an incorrect
> status indication of FULL for the battery simply because it wasn't
> discharging at
On Thu, 2019-07-25 at 14:59 +0200, Hans Verkuil wrote:
> On 7/24/19 7:16 PM, Ezequiel Garcia wrote:
> > This series adds VP8 decoding support on RK3399 SoC.
> >
> > I'm including a set of commits from Boris' recent H264 series [1].
> > These commits add some helpers that are also useful for
On Thu, Apr 25, 2019 at 02:24:18PM +0800, junxiao.ch...@intel.com wrote:
> From: Junxiao Chang
>
> When platform device is deleted or there is error in adding
> device, platform device resources should be released. Currently
> API release_resource is used to release platform device resources.
>
On 2019/7/25 21:08, Andrew Lunn wrote:
>> You are discussing about the DT configuration, is Matthias Kaehlcke's work
>> also provide a generic way to configure PHY LEDS using ACPI?
>
> In general, you should be able to use the same properties in ACPI as
> DT. If the device_property_read_X()
On Tue, Jul 23, 2019 at 11:44:06AM +0530, Viresh Kumar wrote:
> CPUFREQ_NOTIFY is going to get removed soon, lets use
> CPUFREQ_CREATE_POLICY instead of that here. CPUFREQ_CREATE_POLICY is
> called only once (which is exactly what we want here) for each cpufreq
> policy when it is first created.
>
On Thu, Jul 25, 2019 at 2:59 AM Masahiro Yamada
wrote:
>
> UAPI headers licensed under GPL are supposed to have exception
> "WITH Linux-syscall-note" so that they can be included into non-GPL
> user space application code.
>
> The exception note is missing in some UAPI headers.
>
> Some of them
On Thu, Jul 25, 2019 at 01:27:58PM +, Parshuram Raju Thombare wrote:
> Hi Andrew,
>
> >One thing which was never clear is how you are testing the features you are
> >adding. Please could you describe your test setup and how each new feature
> >is tested using that hardware. I'm particularly
On 07/25/2019 04:17 PM, Tudor Ambarus wrote:
+static ssize_t spi_nor_spimem_xfer_data(struct spi_nor *nor,
+ struct spi_mem_op *op,
+ enum spi_nor_protocol proto)
+{
+ bool usebouncebuf = false;
>>>
Hi Chanwoo,
On 25.07.2019 12:17, Chanwoo Choi wrote:
> Hi Kamil,
>
> Looks good to me. But, I have some comment. Please check them.
Thank you for review, please see answers below.
> After this patch, exynos_bus_target is perfectly same with
> exynos_bus_passive_target. The
Hi Lee
On 07/25/2019 11:51 AM, Lee Jones wrote:
On Fri, 14 Jun 2019, Suzuki K Poulose wrote:
Add a wrapper to driver_find_device() to search for a device
by the of_node pointer, reusing the generic match function.
Also convert the existing users to make use of the new helper.
Cc: Lee Jones
On Thu, 25 Jul 2019 15:24:37 +0900
Masami Hiramatsu wrote:
> Allow kprobes which do not modify regs->ip, coexist with livepatch
> by dropping FTRACE_OPS_FL_IPMODIFY from ftrace_ops.
>
> User who wants to modify regs->ip (e.g. function fault injection)
> must set a dummy post_handler to its
On Tue, 23 Jul 2019 at 10:23, Manish Narani wrote:
>
> Hi Rob,
>
> Thanks a lot for the review!
>
>
> > -Original Message-
> > From: Rob Herring
> > Sent: Tuesday, July 23, 2019 3:24 AM
> > To: Manish Narani
> > Cc: ulf.hans...@linaro.org; mark.rutl...@arm.com; he...@sntech.de; Michal
>
On 19/06/2019 14.15, Boris Brezillon wrote:
> From: Hertz Wong
>
> Add helpers and patch hantro_{drv,v4l2}.c to prepare addition of H264
> decoding support.
>
> Signed-off-by: Hertz Wong
> Signed-off-by: Boris Brezillon
> ---
> +
> + /*
> + * Short term pics in descending pic num
On Thu, Jul 25, 2019 at 3:48 PM Jia-Ju Bai wrote:
>
> In ovl_fill_super(), there is an if statement on line 1607 to check
> whether ofs->upper_mnt is NULL:
> if (!ofs->upper_mnt)
>
> When ofs->upper_mnt is NULL and d_make_root() on line 1654 fails,
> ovl_free_fs() on line 1683 is executed.
>
On Mon, 22 Jul 2019 at 21:41, Douglas Anderson wrote:
>
> As talked about in the thread at:
>
> http://lkml.kernel.org/r/CAD=FV=X7P2F1k_zwHc0mbtfk55-rucTz_GoDH=pl6zwqkyc...@mail.gmail.com
>
> ...when the Marvell WiFi card tries to reset itself it kills
> Bluetooth. It was observed that we could
On 14-07-19, 17:55, Paul Cercueil wrote:
> The current driver works perfectly fine on every generation of the
> JZ47xx SoCs, except on the JZ4740.
>
> There, when hardware descriptors are chained together (with the LINK
> bit set), the next descriptor isn't automatically fetched as it should -
>
Hi Andrew,
>One thing which was never clear is how you are testing the features you are
>adding. Please could you describe your test setup and how each new feature
>is tested using that hardware. I'm particularly interested in what C45 device
>are you using? But i expect Russell would like to
On Thu, Jul 25, 2019 at 09:21:22PM +0800, Jason Wang wrote:
>
> On 2019/7/25 下午4:28, Michael S. Tsirkin wrote:
> > On Thu, Jul 25, 2019 at 03:43:41PM +0800, Jason Wang wrote:
> > > On 2019/7/25 下午1:52, Michael S. Tsirkin wrote:
> > > > On Tue, Jul 23, 2019 at 09:31:35PM +0800, Jason Wang wrote:
>
From: Jon Hunter
Date: Jul/25/2019, 14:20:07 (UTC+00:00)
>
> On 03/07/2019 11:37, Jose Abreu wrote:
> > Mapping and unmapping DMA region is an high bottleneck in stmmac driver,
> > specially in the RX path.
> >
> > This commit introduces support for Page Pool API and uses it in all RX
> >
> > Regressions (compared to build v5.2.2)
> >
> >
> > x86:
> > kvm-unit-tests:
> > * vmx
> >
> >
> > TESTNAME=vmx TIMEOUT=90s ACCEL= ./x86/run x86/vmx.flat -smp 1 -cpu
> > host,+vmx -append \"-exit_monitor_from_l2_test
Hi!
> tst_test.c:1161: INFO: Testing on vfat
> tst_mkfs.c:90: INFO: Formatting /dev/loop0 with vfat opts='' extra opts=''
> mkfs.vfat: unable to open /dev/loop0: Device or resource busy
> tst_mkfs.c:101: BROK: mkfs.vfat:1: tst_test.c failed with 741
This looks like mkfs.vfat got EBUSY after the
On Thu 25 Jul 2019 at 13:55, Mark Brown wrote:
> On Wed, Jul 24, 2019 at 06:24:02PM +0200, Jerome Brunet wrote:
>
>> Also, params does not need to be dynamically allocated as it does not
>> need to survive the event.
>
> It's dynamically allocated because it's a pretty large structure and so
>
On Thu, 25 Jul 2019 at 09:28, Jisheng Zhang wrote:
>
> devm_platform_ioremap_resource() wraps platform_get_resource() and
> devm_ioremap_resource() in a single helper, let's use that helper to
> simplify the code.
>
> Signed-off-by: Jisheng Zhang
Applied for next, thanks!
Kind regards
Uffe
>
On Tue, Jul 23, 2019 at 09:21:53AM +1000, Michael Ellerman wrote:
> Segher Boessenkool writes:
> >> can use both RA and RB to compute the address, rather than us forcing RA
> >> to 0.
> >>
> >> But at least with my compiler here (GCC 8 vintage) I don't actually see
> >> GCC ever using both GPRs
From: Arnd Bergmann
The driver builds fine without these.
Signed-off-by: Arnd Bergmann
Signed-off-by: Bartosz Golaszewski
---
drivers/media/platform/davinci/vpbe_display.c | 4
drivers/media/platform/davinci/vpbe_osd.c | 5 -
drivers/media/platform/davinci/vpbe_venc.c| 5
On 19-07-24 20:22:35, Chuhong Yuan wrote:
> Instead of using to_pci_dev + pci_get_drvdata,
> use dev_get_drvdata to make code simpler.
>
> Signed-off-by: Chuhong Yuan
This looks good to me.
Reviewed-by: Minwoo Im
On Thu 25 Jul 2019 at 14:00, Mark Brown wrote:
> On Wed, Jul 24, 2019 at 06:24:00PM +0200, Jerome Brunet wrote:
>> When handling dai_link events on codec to codec links, run all .startup()
>> callbacks on sinks and sources before running any .hw_params(). Same goes
>> for hw_free() and
On 12/07/19 6:32 AM, Andrew Jeffery wrote:
> Add a minimal driver for ASPEED's SD controller, which exposes two
> SDHCIs.
>
> The ASPEED design implements a common register set for the SDHCIs, and
> moves some of the standard configuration elements out to this common
> area (e.g. 8-bit mode, and
On 2019/7/25 下午4:28, Michael S. Tsirkin wrote:
On Thu, Jul 25, 2019 at 03:43:41PM +0800, Jason Wang wrote:
On 2019/7/25 下午1:52, Michael S. Tsirkin wrote:
On Tue, Jul 23, 2019 at 09:31:35PM +0800, Jason Wang wrote:
On 2019/7/23 下午5:26, Michael S. Tsirkin wrote:
On Tue, Jul 23, 2019 at
From: Arnd Bergmann
This fixes the following build error in davinci_vpfe.
/git/arm-soc/drivers/staging/media/davinci_vpfe/dm365_isif.c: In function
'vpfe_isif_init':
/git/arm-soc/drivers/staging/media/davinci_vpfe/dm365_isif.c:2031:2: error:
implicit declaration of function 'davinci_cfg_reg';
From: Arnd Bergmann
When building a multiplatform kernel that includes armv4 support,
the default target CPU does not support the blx instruction,
which leads to a build failure:
arch/arm/mach-davinci/sleep.S: Assembler messages:
arch/arm/mach-davinci/sleep.S:56: Error: selected processor does
From: Bartosz Golaszewski
This series makes DaVinci part of the multiplatform build for ARM v5.
First three patches fix build errors spotted and fixed by Arnd with v1.
The fourth patch adds necessary bits and pieces for davinci to support
multiplatform build and the last one actually adds all
From: Bartosz Golaszewski
Add modifications necessary to make davinci part of the ARM v5
multiplatform build.
Move the arch-specific configuration out of arch/arm/Kconfig and
into mach-davinci/Kconfig. Remove the sub-menu for DaVinci
implementations (they'll be visible directly under the system
On 03/07/2019 11:37, Jose Abreu wrote:
> Mapping and unmapping DMA region is an high bottleneck in stmmac driver,
> specially in the RX path.
>
> This commit introduces support for Page Pool API and uses it in all RX
> queues. With this change, we get more stable troughput and some increase
>
The patch
ASoC: Intel: Fix some acpi vs apci typo in somme comments
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-5.3
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next
From: Bartosz Golaszewski
Add all DaVinci boards to multi_v5_defconfig.
Signed-off-by: Bartosz Golaszewski
---
arch/arm/configs/multi_v5_defconfig | 12
1 file changed, 12 insertions(+)
diff --git a/arch/arm/configs/multi_v5_defconfig
b/arch/arm/configs/multi_v5_defconfig
index
On Mon, Jul 22, 2019 at 08:47:05PM +0200, Thomas Gleixner wrote:
> This is merily a refresh of V2.
>
> Changes vs. V2
> (https://lkml.kernel.org/r/20190704155145.617706...@linutronix.de)
>
> - Fix the NMI_VECTOR/VECTOR_NMI typo in kgdb
>
> - Remove the misleading vector 0-31 wording
>
Hi, Boris,
On 07/25/2019 03:37 PM, Boris Brezillon wrote:
> External E-Mail
>
>
> On Thu, 25 Jul 2019 11:19:06 +
> wrote:
>
>>> + */
>>> +static int spi_nor_exec_op(struct spi_nor *nor, struct spi_mem_op *op,
>>> + u64 *addr, void *buf, size_t len)
>>> +{
>>> + int
use rb_entry_safe() to make it clean
Signed-off-by: Weitao Hou
---
fs/ext4/extents_status.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/fs/ext4/extents_status.c b/fs/ext4/extents_status.c
index 7521de2dcf3a..08ce5ded3538 100644
--- a/fs/ext4/extents_status.c
+++
From: Numfor Mbiziwo-Tiapo
> Sent: 24 July 2019 19:45
>
> Perf does not build with the ubsan (undefined behavior sanitizer)
> and there is an error that says:
>
> tests/backward-ring-buffer.c:23:45: error: ‘%d’ directive output
> may be truncated writing between 1 and 10 bytes into a region of
>
> You are discussing about the DT configuration, is Matthias Kaehlcke's work
> also provide a generic way to configure PHY LEDS using ACPI?
In general, you should be able to use the same properties in ACPI as
DT. If the device_property_read_X() API is used, it will try both ACPI
and OF to get the
On 7/25/19 12:35 AM, Christophe JAILLET wrote:
Fix some typo to have the filaname given in a comment match the real name
of the file.
Some 'acpi' have erroneously been written 'apci'
Signed-off-by: Christophe JAILLET
yes, thanks for the corrections.
Acked-by: Pierre-Louis Bossart
---
From: Numfor Mbiziwo-Tiapo
> Sent: 24 July 2019 19:45
>
> The ubsan (undefined behavior sanitizer) version of perf throws an
> error on the 'x86 instruction decoder - new instructions' function
> of perf test.
>
> To reproduce this run:
> make -C tools/perf USE_CLANG=1
On 25.07.19 14:56, Michal Hocko wrote:
> On Wed 24-07-19 16:30:17, David Hildenbrand wrote:
>> We end up calling __add_memory() without the device hotplug lock held.
>> (I used a local patch to assert in __add_memory() that the
>> device_hotplug_lock is held - I might upstream that as well soon)
Hi Dmitry,
>> syzbot found the following crash on:
>>
>> HEAD commit:6d21a41b Add linux-next specific files for 20190718
>> git tree: linux-next
>> console output: https://syzkaller.appspot.com/x/log.txt?x=1377958fa0
>> kernel config:
>>
On 09-07-19, 16:32, YueHaibing wrote:
> If CONFIG_PM is not set, build warnings:
>
> drivers/dma/tegra210-adma.c:747:12: warning: tegra_adma_runtime_resume
> defined but not used [-Wunused-function]
> static int tegra_adma_runtime_resume(struct device *dev)
> drivers/dma/tegra210-adma.c:715:12:
On 7/18/19 10:57 AM, Mel Gorman wrote:
> "howaboutsynergy" reported via kernel buzilla number 204165 that
> compact_zone_order was consuming 100% CPU during a stress test for
> prolonged periods of time. Specifically the following command, which
> should exit in 10 seconds, was taking an excessive
On Wed, Jul 24, 2019 at 06:24:00PM +0200, Jerome Brunet wrote:
> When handling dai_link events on codec to codec links, run all .startup()
> callbacks on sinks and sources before running any .hw_params(). Same goes
> for hw_free() and shutdown(). This is closer to the behavior of regular
> dai
Hi Vladis,
> Certain ttys operations (pty_unix98_ops) lack tiocmget() and tiocmset()
> functions which are called by the certain HCI UART protocols (hci_ath,
> hci_bcm, hci_intel, hci_mrvl, hci_qca) via hci_uart_set_flow_control()
> or directly. This leads to an execution at NULL and can be
On 7/24/19 7:16 PM, Ezequiel Garcia wrote:
> This series adds VP8 decoding support on RK3399 SoC.
>
> I'm including a set of commits from Boris' recent H264 series [1].
> These commits add some helpers that are also useful for RK3399 VP8,
> and at the same time cleanup the driver nicely.
>
>
On 25. 07. 19 10:57, Dmitry Torokhov wrote:
Hi Michal,
On Tue, May 21, 2019 at 08:51:17AM +0200, Michal Vokáč wrote:
On 21. 05. 19 7:37, Dmitry Torokhov wrote:
Hi Michal,
On Fri, May 17, 2019 at 03:12:49PM +0200, Michal Vokáč wrote:
Hi,
I have to deal with a situation where we have a
On Wed 24-07-19 16:30:17, David Hildenbrand wrote:
> We end up calling __add_memory() without the device hotplug lock held.
> (I used a local patch to assert in __add_memory() that the
> device_hotplug_lock is held - I might upstream that as well soon)
>
> [ 26.771684]
On Wed, Jul 24, 2019 at 06:24:02PM +0200, Jerome Brunet wrote:
> Also, params does not need to be dynamically allocated as it does not
> need to survive the event.
It's dynamically allocated because it's a pretty large structure and so
the limited stack sizes the kernel has make it a bit
Hi Hans and thanks for the review!
On Mon 22 Jul 19, 16:40, Hans Verkuil wrote:
> On 6/14/19 4:38 PM, Paul Kocialkowski wrote:
> > This introduces the required definitions for HEVC decoding support with
> > stateless VPUs. The controls associated to the HEVC slice format provide
> > the required
Linus Torvalds writes:
> On Wed, Jul 24, 2019 at 7:47 AM Christian Brauner
> wrote:
>>
>> The code here uses a struct waitid_info to catch basic information about
>> process exit including the pid, uid, status, and signal that caused the
>> process to exit. This information is then stuffed
Hi Thor,
On 12/07/2019 19:28, thor.tha...@linux.intel.com wrote:
> From: Thor Thayer
>
> ARM32 SoCFPGAs had separate IRQs for SDRAM. ARM64 SoCFPGAs
> send all DBEs to SError so filtering by source is necessary.
>
> The Stratix10 SDRAM ECC is a better match with the generic
> Altera peripheral
On Sat, Jul 20, 2019 at 03:25:44PM -0500, Navid Emamdoost wrote:
> Allocation for priv->pFirmware may fail, so a null check is necessary.
> priv->pFirmware is accessed at line 2743. I added the check and made
> appropriate changes to propagate the errno to the caller.
>
> Signed-off-by: Navid
For pages that were retained via get_user_pages*(), release those pages
via the new put_user_page*() routines, instead of via put_page().
This is part a tree-wide conversion, as described in commit fc1d8e7cca2d
("mm: introduce put_user_page*(), placeholder versions").
Cc: Ira Weiny
Cc: John
On Mon, 22 Jul 2019, Arnd Bergmann wrote:
> When building davinci as multiplatform, we get a build error
> in this file:
>
> drivers/mfd/davinci_voicecodec.c:22:10: fatal error: 'mach/hardware.h' file
> not found
>
> The header is only used to access the io_v2p() macro, but the
> result is
Hi,
On 12/07/2019 03:20, Xiaofei Tan wrote:
> AER info of PCIe fatal error is not printed in the current driver.
> Because APEI driver will panic directly for fatal error, and can't
> run to the place of printing AER info.
>
> An example log is as following:
> [ 3157.655028] {763}[Hardware
On 25/07/2019 13:37, walter harms wrote:
>
>
> Am 25.07.2019 13:25, schrieb Colin King:
>> From: Colin Ian King
>>
>> The check to see if trigger is less than zero is always false, trigger
>> is always in the range 0..255. Hence the check is redundant and can
>> be removed.
>>
>>
On Mon, Jul 22, 2019 at 10:45:34AM -0500, David Lechner wrote:
> This series adds device tree bindings and a new counter driver for the Texas
> Instruments Enhanced Quadrature Encoder Pulse (eQEP).
>
> As mentioned in one of the commit messages, to start with, the driver only
> supports reading
This adds Qualcomm Venus video codec DT node for the video
codec hardware found in MSM8996 platforms.
Signed-off-by: Stanimir Varbanov
---
arch/arm64/boot/dts/qcom/msm8996.dtsi | 68 +++
1 file changed, 68 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/msm8996.dtsi
Hi Andrew,
On Wed, 19 Jun 2019 14:15:32 +0200
Boris Brezillon wrote:
> From: Rasmus Villemoes
>
> Our list_sort() utility has always supported a context argument that
> is passed through to the comparison routine. Now there's a use case
> for the similar thing for sort().
>
> This implements
On 24/07/2019 23:47, David Miller wrote:
> From: Wolfram Sang
> Date: Mon, 22 Jul 2019 19:26:35 +0200
>
>> Move from i2c_new_dummy() to i2c_new_dummy_device(). So, we now get an
>> ERRPTR which we use in error handling.
>>
>> Signed-off-by: Wolfram Sang
Subject & description are incomplete,
On Thu, 25 Jul 2019 11:19:06 +
wrote:
> > + */
> > +static int spi_nor_exec_op(struct spi_nor *nor, struct spi_mem_op *op,
> > + u64 *addr, void *buf, size_t len)
> > +{
> > + int ret;
> > + bool usebouncebuf = false;
>
> I don't think we need a bounce buffer for
Am 25.07.2019 13:25, schrieb Colin King:
> From: Colin Ian King
>
> The check to see if trigger is less than zero is always false, trigger
> is always in the range 0..255. Hence the check is redundant and can
> be removed.
>
> Addresses-Coverity: ("Logically dead code")
> Signed-off-by:
On Thu, 18 Jul 2019, Lukasz Majewski wrote:
> From: Sascha Hauer
>
> The mc34708 has an improved adc. The older variants will always convert
> a fixed order of channels. The mc34708 can do up to eight conversions
> in arbitrary channel order. Currently this extended feature is not
> supported.
On Mon, 22 Jul 2019, Nadav Amit wrote:
> > On Jul 22, 2019, at 11:51 AM, Thomas Gleixner wrote:
> > void on_each_cpu(void (*func) (void *info), void *info, int wait)
> > {
> >unsigned long flags;
> >
> >preempt_disable();
> > smp_call_function(func, info, wait);
> >
> >
On Thu, Jul 11, 2019 at 09:32:38PM +0800, Kefeng Wang wrote:
> ../drivers/char/hpet.c:159:17: warning: variable ‘m’ set but not used
> [-Wunused-but-set-variable]
>unsigned long m, t, mc, base, k;
> ^
> Signed-off-by: Kefeng Wang
> ---
> drivers/char/hpet.c | 3 +--
> 1 file
On 2019/7/25 3:12, Saeed Mahameed wrote:
> On Wed, 2019-07-24 at 11:18 +0800, Huazhong Tan wrote:
>> From: Yonglong Liu
>>
>> Some times just see the eth interface have been down/up via
>> dmesg, but can not know why the eth down. So adds some debug
>> messages to identify the cause for this.
On Thu, Jul 25, 2019 at 01:43:59PM +0200, Oleg Nesterov wrote:
> Or. We can change wait_consider_task() to not clear ->notask_error if
> WXXX and the child is PF_WAIT_PID.
>
> This way you can "safely" use wait() without WNOHANG, it won't block if
> all the children which can report an even are
701 - 800 of 1107 matches
Mail list logo
