Add the reset to the TDM formatters of the g12a. This helps
with channel mapping when a playback/capture uses more than 1 lane.
Reviewed-by: Neil Armstrong
Signed-off-by: Jerome Brunet
---
arch/arm64/boot/dts/amlogic/meson-g12-common.dtsi | 8
1 file changed, 8 insertions(+)
diff
On 23/08/2019 16:44, Pierre-Louis Bossart wrote:
On 8/22/19 6:37 PM, Srinivas Kandagatla wrote:
This patch adds support to parsing device tree based
SoundWire slave devices.
Signed-off-by: Srinivas Kandagatla
---
drivers/soundwire/bus.c | 2 ++
drivers/soundwire/bus.h | 1 +
On 19/08/2019 11:21, Mars Cheng wrote:
> Add documentation for mt6779 uart dt-bindings
>
> Signed-off-by: Mars Cheng
Pushed to v5.3-next/dts64
Thanks!
> ---
> .../devicetree/bindings/serial/mtk-uart.txt|1 +
> 1 file changed, 1 insertion(+)
>
> diff --git
On 8/23/19 10:32 AM, Benjamin Tissoires wrote:
On Fri, Aug 23, 2019 at 4:22 PM Pedro Vanzella wrote:
Hi Benjamin,
On 8/23/19 4:25 AM, Benjamin Tissoires wrote:
Hi Pedro,
On Thu, Aug 22, 2019 at 10:19 PM Pedro Vanzella wrote:
Resumitting this after having rebased it against the latest
On Thu, Aug 22, 2019 at 04:30:37PM -0700, Scott Branden wrote:
> On 2019-08-22 2:12 p.m., Luis Chamberlain wrote:
> > On Thu, Aug 22, 2019 at 01:07:41PM -0700, Scott Branden wrote:
> > > On 2019-08-22 12:47 p.m., Luis Chamberlain wrote:
> > > > This implies you having to change the other callers,
On 19/08/2019 11:21, Mars Cheng wrote:
> Update binding document for mt6779 reference board
>
> Signed-off-by: Mars Cheng
> Reviewed-by: Rob Herring
Applied thanks!
> ---
> .../devicetree/bindings/arm/mediatek.yaml |4
> 1 file changed, 4 insertions(+)
>
> diff --git
Newer Logitech mice report their battery voltage through feature 0x1001
instead of the battery levels through feature 0x1000.
When the device is brought up and we try to query the battery, figure
out if it supports the old or the new feature. If it supports the new
feature, record the feature
Hi Linus,
On 23/08/2019 10:51, Linus Walleij wrote:
> On Mon, Aug 19, 2019 at 11:22 AM Mars Cheng wrote:
>
>> Add binding documentation of mediatek,sysirq for mt6779 SoC.
>>
>> Signed-off-by: Mars Cheng
>
> I'm relying on Sean to review this and ACK when he's pleased
> with the result.
>
I
On Fri, 23 Aug 2019 14:53:06 +
Parav Pandit wrote:
> > -Original Message-
> > From: Alex Williamson
> > Sent: Friday, August 23, 2019 7:58 PM
> > To: Parav Pandit
> > Cc: Jiri Pirko ; Jiri Pirko ; David S
> > . Miller
> > ; Kirti Wankhede ; Cornelia
> > Huck ;
From: Tudor Ambarus
This series is a prerequisite for the effort of moving the
manufacturer specific code out of the SPI NOR core.
The scope is to move all [FLASH-SPECIFIC] parameters and settings
from 'struct spi_nor' to 'struct spi_nor_flash_parameter'. We will
have a clear separation between
On 19/08/2019 11:21, Mars Cheng wrote:
> Add devicetree bindings for Mediatek mt6779 SoC Pin Controller.
>
> Signed-off-by: Mars Cheng
> Signed-off-by: Andy Teng
> ---
> include/dt-bindings/pinctrl/mt6779-pinfunc.h | 1242
> ++
This is just the header file, but the
From: Tudor Ambarus
The Flash parameters and settings are now stored in 'struct spi_nor'.
Use this instead of the stack allocated params.
Few functions stop passing pointer to params, as they can get it from
'struct spi_nor'. spi_nor_parse_sfdp() and children will keep passing
pointer to params
From: Tudor Ambarus
All flash parameters and settings should reside inside
'struct spi_nor_flash_parameter'. Move clear_sr_bp() from
'struct spi_nor' to 'struct spi_nor_flash_parameter'.
Rename clear_sr_bp()/disable_block_protection() to better indicate
what the function does.
Signed-off-by:
From: Tudor Ambarus
The scope is to move all [FLASH-SPECIFIC] parameters and settings
from 'struct spi_nor' to 'struct spi_nor_flash_parameter'.
'struct spi_nor_flash_parameter' describes the hardware capabilities
and associated settings of the SPI NOR flash memory. It includes
legacy flash
From: Tudor Ambarus
All flash parameters and settings should reside inside
'struct spi_nor_flash_parameter'. Drop the local copy of
quad_enable() and use the one from 'struct spi_nor_flash_parameter'.
Signed-off-by: Tudor Ambarus
---
drivers/mtd/spi-nor/spi-nor.c | 38
Seems chip-id in 5.3 is read here
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/mfd/mt6397-core.c?h=v5.3-rc5#n282
It is before platform_get_irq which may call irq-init changed in the
problematic commit.
I will add a dev_info here in next-code to see value of
From: Tudor Ambarus
All flash parameters and settings should reside inside
'struct spi_nor_flash_parameter'. Move the SMPT parsed erase map
from 'struct spi_nor' to 'struct spi_nor_flash_parameter'.
Please note that there is a roll-back mechanism for the flash
parameter and settings, for cases
+void intel_shutdown(struct snd_pcm_substream *substream,
+ struct snd_soc_dai *dai)
+{
+ struct sdw_cdns_dma_data *dma;
+
+ dma = snd_soc_dai_get_dma_data(dai, substream);
+ if (!dma)
+ return;
+
+ snd_soc_dai_set_dma_data(dai, substream, NULL);
+ kfree(dma);
On 23/08/2019 16:41, Pierre-Louis Bossart wrote:
On 8/22/19 6:37 PM, Srinivas Kandagatla wrote:
This patch adds bindings for Soundwire Slave devices that includes how
SoundWire enumeration address and Link ID are used to represented in
SoundWire slave device tree nodes.
Signed-off-by:
Hi Andrew
The 08/23/2019 15:25, Andrew Lunn wrote:
> External E-Mail
>
>
> > > > Why do the devices have to be from the same driver ?
> > After seeing yours and Andrews comments I realize that I try to do two
> > things, but I have only explained one of them.
> >
> > Here is what I was trying
From: Tudor Ambarus
To avoid inadvertent writes during power-up, some flashes are
write-protected by default after a power-on reset cycle.
A Global Block-Protection Unlock command offers a single
command cycle that unlocks the entire memory array. This is
identical with what other nor flashes
Naresh Kamboju writes:
> On Fri, 23 Aug 2019 at 04:10, Kevin Hilman wrote:
>>
>> "kernelci.org bot" writes:
>>
>> > stable-rc/linux-4.4.y boot: 101 boots: 2 failed, 84 passed with 12
>> > offline, 2 untried/unknown, 1 conflict (v4.4.189-79-gf18b2d12bf91)
>>
>> TL;DR; All is well.
>>
>> >
From: Tudor Ambarus
To avoid inadvertent writes during power-up, sst26vf064b is
write-protected by default after a power-on reset cycle.
Unlock the serial flash memory by using the Global Block Protection
Unlock command - it offers a single command cycle that unlocks
the entire memory array.
From: Tudor Ambarus
This is similar with what other nor flashes are doing by clearing the
block protection bits from the status register: disable the write
protection after a power-on reset cycle.
The Global Block-Protection Unlock command offers a single command cycle
that unlocks the entire
This has nothing to do with the move manufacturer out of the spi-nor core
pursue, but depends on:
https://patchwork.ozlabs.org/project/linux-mtd/list/?series=127030
On 08/23/2019 07:05 PM, Tudor Ambarus - M18064 wrote:
> From: Tudor Ambarus
>
> This is similar with what other nor flashes are
On Fri, Aug 23, 2019 at 04:41:59PM +0100, Will Deacon wrote:
>
> Given that these aren't functional changes, I've kept Ted's ack from v9
> and I'll queue these via arm64 assuming they pass testing.
>
> Ted -- please shout if you're not happy about that, and I'll drop the
> series.
That's fine,
On 2019-08-23 7:08 a.m., Christophe JAILLET wrote:
Hi,
in this patch, there is one piece that looked better before. (see below)
Removing the 'if (skb)' is fine, but concatening everything in one
statement just to save 2 variables and a few LOC is of no use, IMHO,
and the code is less
On Thu 22 Aug 2019 at 16:24, Neil Armstrong wrote:
> Following DVFS support for the Amlogic G12A and G12B SoCs, this serie
> enables DVFS on the SM1 SoC for the SEI610 board.
>
> The SM1 Clock structure is slightly different because of the Cortex-A55
> core used, having the capability for each
On 19/08/2019 11:21, Mars Cheng wrote:
> this adds initial MT6779 dts settings fo board support,
...for basic board support, including clocks pinctrl and uart.
By the way, while talking about basic support. Do you have any detailed plans to
upstream this SoC? We already have mt6755 and mt6795
> -Original Message-
> From: Alex Williamson
> Sent: Friday, August 23, 2019 9:22 PM
> To: Parav Pandit
> Cc: Jiri Pirko ; Jiri Pirko ; David S .
> Miller
> ; Kirti Wankhede ; Cornelia
> Huck ; k...@vger.kernel.org; linux-
> ker...@vger.kernel.org; cjia ; net...@vger.kernel.org
>
Hi Pedro,
On Fri, Aug 23, 2019 at 5:51 PM Pedro Vanzella wrote:
>
> Newer Logitech mice report their battery voltage through feature 0x1001
> instead of the battery levels through feature 0x1000.
>
> When the device is brought up and we try to query the battery, figure
> out if it supports the
On 2019-08-22 22:23:23 [-0500], Scott Wood wrote:
> On Thu, 2019-08-22 at 09:39 -0400, Joel Fernandes wrote:
> > On Wed, Aug 21, 2019 at 04:33:58PM -0700, Paul E. McKenney wrote:
> > > On Wed, Aug 21, 2019 at 06:19:04PM -0500, Scott Wood wrote:
> > > > Signed-off-by: Scott Wood
> > > > ---
> > >
On 2019-08-21 18:19:05 [-0500], Scott Wood wrote:
> Without this, rcu_note_context_switch() will complain if an RCU read
> lock is held when migrate_enable() calls stop_one_cpu().
>
> Signed-off-by: Scott Wood
> ---
> v2: Added comment.
>
> If my migrate disable changes aren't taken, then
Several blocks of code are guarded by #ifdef TO_DO_LIST. If this is
defined, compilation fails. No machinery exists to define this, and no
documenation on the in-progress feature exists. Since this code is dead,
let's delete it.
Signed-off-by: Stephen Brennan
---
Sorry, I know you're giving a
I am considering moving the IPMI watchdog over to the standard
watchdog framework. This will require the removal of the feature
that provides a byte of read data when the pretimeout occurs,
since that is not available in the standard framework.
Before I remove this, I thought I would ask: Is
On Fri, Aug 23, 2019 at 12:06:12PM -0400, Theodore Y. Ts'o wrote:
> On Fri, Aug 23, 2019 at 04:41:59PM +0100, Will Deacon wrote:
> >
> > Given that these aren't functional changes, I've kept Ted's ack from v9
> > and I'll queue these via arm64 assuming they pass testing.
> >
> > Ted -- please
After commit baeababb5b85d5c4e6c917efe2a1504179438d3b
("tun: return NET_XMIT_DROP for dropped packets"),
when tun_net_xmit drop packets, it will free skb and return NET_XMIT_DROP,
netpoll_send_skb_on_dev will run into two use after free cases:
1. retry netpoll_start_xmit with freed skb;
2. queue
On 2019-08-21 16:40:18 [-0700], Paul E. McKenney wrote:
> Save a couple of lines?
>
> static bool use_softirq = !IS_ENABLED(CONFIG_PREEMPT_RT_FULL);
>
> And if I understand your point above, the module_param() might be
> able to be the same either way given the new RCU. But if not,
> at least
Hi Linus,
Here are a few more bug fixes that trickled in since the last pull.
They've survived the usual xfstests runs and merge cleanly with this
morning's master. Please let me know if anything strange happens.
I expect there to be one more pull request tomorrow for the fix to that
quota
Hi Raphaël,
The title should probably go straight to the point, this provides
support for arm64 switch tables. The use of alternatives is just an
implementation detail (it is good to have it explained in the commit
message, but in the title it would be more helpful to see that this
actually
On Fri, 23 Aug 2019 17:21:33 +0800
zhangfei wrote:
> Hi, Jonathan
Hi zhangfei,
>
> Thanks for your careful review and good suggestion.
> Sorry for late response, I am checking one detail.
I have reviews on patches from years ago that I still haven't replied to ;)
>
> On 2019/8/16 上午12:54,
On Fri, Aug 23, 2019 at 2:16 AM Ingo Molnar wrote:
>
> > + */
> > + if (fatal_signal_pending(current)) {
> > + if (!(error_code & X86_PF_USER))
> > + no_context(regs, error_code, address, 0, 0);
>
> Since the 'signal' parameter to no_context() is 0, will
On Fri, 23 Aug 2019 17:21:33 +0800
zhangfei wrote:
> Hi, Jonathan
>
> Thanks for your careful review and good suggestion.
> Sorry for late response, I am checking one detail.
>
> On 2019/8/16 上午12:54, Jonathan Cameron wrote:
> > On Wed, 14 Aug 2019 17:34:25 +0800
> > Zhangfei Gao wrote:
> >
From: Branden Bonaby Sent: Thursday, August 22,
2019 8:39 PM
> > > diff --git a/drivers/hv/connection.c b/drivers/hv/connection.c
> > > index 09829e15d4a0..c9c63a4033cd 100644
> > > --- a/drivers/hv/connection.c
> > > +++ b/drivers/hv/connection.c
> > > @@ -357,6 +357,9 @@ void
On 8/23/19 10:57 AM, Srinivas Kandagatla wrote:
On 23/08/2019 16:41, Pierre-Louis Bossart wrote:
On 8/22/19 6:37 PM, Srinivas Kandagatla wrote:
This patch adds bindings for Soundwire Slave devices that includes how
SoundWire enumeration address and Link ID are used to represented in
The pull request you sent on Fri, 23 Aug 2019 14:27:26 +0200:
> https://github.com/ceph/ceph-client.git tags/ceph-for-5.3-rc6
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/4e5639449069d12e95edc10b63acf170843e1706
Thank you!
--
Deet-doot-dot, I am a bot.
The pull request you sent on Fri, 23 Aug 2019 17:12:13 +0200:
> ssh://g...@gitolite.kernel.org/pub/scm/linux/kernel/git/jeyu/linux.git
> tags/modules-for-v5.3-rc6
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/e3fb13b7e47cd18b2bd067ea8a491020b4644baf
Thank you!
--
The pull request you sent on Fri, 23 Aug 2019 12:07:12 +1000:
> git://anongit.freedesktop.org/drm/drm tags/drm-fixes-2019-08-23
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/1374a22e0641783a5fa25a18f23d9d7a91c38add
Thank you!
--
Deet-doot-dot, I am a bot.
On Fri, Aug 23, 2019 at 1:17 AM Tetsuo Handa
wrote:
>
> On 2019/08/23 8:59, Dmitry Vyukov wrote:
> >> Can't we introduce a kernel config which selectively blocks specific
> >> actions?
> >> If we don't need to worry about bypassing blacklist checks, we will be
> >> able to
> >> enable
On Fri, Aug 23, 2019 at 8:33 AM shuah wrote:
>
> Hi Brendan,
>
> On 8/20/19 5:20 PM, Brendan Higgins wrote:
> > Add core facilities for defining unit tests; this provides a common way
> > to define test cases, functions that execute code which is under test
> > and determine whether the code
On Fri, 2019-08-23 at 17:57 +0800, Biwen Li wrote:
> The patch supports flextimer for lx2160a
>
> Signed-off-by: Biwen Li
> ---
> drivers/rtc/rtc-fsl-ftm-alarm.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/rtc/rtc-fsl-ftm-alarm.c b/drivers/rtc/rtc-fsl-
> ftm-alarm.c
>
On Fri, Aug 23, 2019 at 8:36 AM shuah wrote:
>
> Hi Brendan,
>
> On 8/20/19 5:20 PM, Brendan Higgins wrote:
> > Add support for aborting/bailing out of test cases, which is needed for
> > implementing assertions.
> >
> > An assertion is like an expectation, but bails out of the test case
> >
On 8/23/19 10:48 AM, Brendan Higgins wrote:
On Fri, Aug 23, 2019 at 8:33 AM shuah wrote:
Hi Brendan,
On 8/20/19 5:20 PM, Brendan Higgins wrote:
Add core facilities for defining unit tests; this provides a common way
to define test cases, functions that execute code which is under test
and
On 8/23/19 10:56 AM, Brendan Higgins wrote:
On Fri, Aug 23, 2019 at 8:36 AM shuah wrote:
Hi Brendan,
On 8/20/19 5:20 PM, Brendan Higgins wrote:
Add support for aborting/bailing out of test cases, which is needed for
implementing assertions.
An assertion is like an expectation, but bails
On Fri, Aug 23, 2019 at 10:59:14AM +1000, Dave Chinner wrote:
> On Wed, Aug 21, 2019 at 11:02:00AM -0700, Ira Weiny wrote:
> > On Tue, Aug 20, 2019 at 08:55:15AM -0300, Jason Gunthorpe wrote:
> > > On Tue, Aug 20, 2019 at 11:12:10AM +1000, Dave Chinner wrote:
> > > > On Mon, Aug 19, 2019 at
On Fri, 23 Aug 2019 16:14:04 +
Parav Pandit wrote:
> > -Original Message-
> > From: Alex Williamson
> > Sent: Friday, August 23, 2019 9:22 PM
> > To: Parav Pandit
> > Cc: Jiri Pirko ; Jiri Pirko ; David S
> > . Miller
> > ; Kirti Wankhede ; Cornelia
> > Huck ;
On Tue, Aug 20, 2019 at 10:15 AM Nick Desaulniers
wrote:
>
> Hi Paul,
> Bumping this thread; we'd really like to be able to boot test another
> ISA in our CI. This lone patch is affecting our ability to boot. Can
> you please pick it up?
>
> Gesendet: Freitag, 23. August 2019 um 17:42 Uhr
> Von: "Matthias Brugger"
> I suppose that's because 3/10 has code that should be in 2/10 and for some
> reason 3/10 was not pushed for linux-next inclusion. Although it has the same
> Acked-for-mfd-by tag.
>
> @Frank, can you test if adding 3/10
On Fri, Aug 23, 2019 at 3:56 PM Cristian Marussi
wrote:
>
> Hi Andrey
>
> On 24/06/2019 15:33, Andrey Konovalov wrote:
> > This patch is a part of a series that extends kernel ABI to allow to pass
> > tagged user pointers (with the top byte set to something else other than
> > 0x00) as syscall
On Thu 2019-08-08 00:32:26, John Ogness wrote:
> --- /dev/null
> +++ b/kernel/printk/numlist.c
> @@ -0,0 +1,375 @@
> +// SPDX-License-Identifier: GPL-2.0
> +
> +#include
> +#include "numlist.h"
struct numlist is really special variant of a list. Let me to
do a short summary:
+ FIFO queue
This series is an experimental reimplementation of ELF property parsing
(see NT_GNU_PROPERTY_TYPE_0, [1]) for the ELF loader.
This is intended for comparison / merging with [2] (or could replace it,
if people think this approach is better).
This supersedes RFC v1 [3].
For changes see the
Pull the basic ELF definitions from Yu-Cheng Yu's series.
Signed-off-by: Yu-cheng Yu
Signed-off-by: Dave Martin
---
This patch should be merged with the next patch.
I kept it seprate for now to document where this code came from.
Changes since RFC v1:
* Move struct gnu_property to .
ELF program properties will needed for detecting whether to enable
optional architecture or ABI features for a new ELF process.
For now, there are no generic properties that we care about, so do
nothing unless CONFIG_ARCH_USE_GNU_PROPERTY=y.
Otherwise, the presence of properties using the
Your patch remove redundant code, which is fine.
Thanks for your constructive feedback.
> code you changed was simple enough to be understand quickly. I think replacing
> it with a crossed goto (even if it remove redundant code) might not be the
> best
> option.
>
> A solution might be to
On Fri, Aug 23, 2019 at 10:05 AM shuah wrote:
>
> On 8/23/19 10:48 AM, Brendan Higgins wrote:
> > On Fri, Aug 23, 2019 at 8:33 AM shuah wrote:
> >>
> >> Hi Brendan,
> >>
> >> On 8/20/19 5:20 PM, Brendan Higgins wrote:
> >>> Add core facilities for defining unit tests; this provides a common way
Dave Chiluk writes:
> On Wed, Aug 21, 2019 at 12:36 PM wrote:
>>
>> Qian Cai writes:
>>
>> > The linux-next commit "sched/fair: Fix low cpu usage with high
>> > throttling by removing expiration of cpu-local slices" [1] introduced a
>> > few compilation warnings,
>> >
>> > kernel/sched/fair.c:
On Fri, Aug 23, 2019 at 10:07 AM shuah wrote:
>
> On 8/23/19 10:56 AM, Brendan Higgins wrote:
> > On Fri, Aug 23, 2019 at 8:36 AM shuah wrote:
> >>
> >> Hi Brendan,
> >>
> >> On 8/20/19 5:20 PM, Brendan Higgins wrote:
> >>> Add support for aborting/bailing out of test cases, which is needed for
At the moment we use 2 IO devices per GICv3 redistributor: one
one for the RD_base frame and one for the SGI_base frame.
Instead we can use a single IO device per redistributor (the 2
frames are contiguous). This saves slots on the KVM_MMIO_BUS
which is currently limited to NR_IOBUS_DEVS (1000).
On Wed, Aug 21, 2019 at 09:09:07PM +0200, Thomas Gleixner wrote:
> Using struct task_cputime for the expiry cache is a pretty odd choice and
> comes with magic defines to rename the fields for usage in the expiry
> cache.
>
> struct task_cputime is basically a u64 array with 3 members, but it has
On 8/23/19 11:27 AM, Brendan Higgins wrote:
On Fri, Aug 23, 2019 at 10:05 AM shuah wrote:
On 8/23/19 10:48 AM, Brendan Higgins wrote:
On Fri, Aug 23, 2019 at 8:33 AM shuah wrote:
Hi Brendan,
On 8/20/19 5:20 PM, Brendan Higgins wrote:
Add core facilities for defining unit tests; this
On Fri, Aug 23, 2019 at 04:44:09PM +, Michael Kelley wrote:
> From: Branden Bonaby Sent: Thursday, August 22,
> 2019 8:39 PM
> > > > diff --git a/drivers/hv/connection.c b/drivers/hv/connection.c
> > > > index 09829e15d4a0..c9c63a4033cd 100644
> > > > --- a/drivers/hv/connection.c
> > > >
On Fri, Aug 23, 2019 at 02:28:53AM -0400, Sasha Levin wrote:
> On Fri, Aug 23, 2019 at 02:42:48AM +0200, Stefan Lippers-Hollmann wrote:
> > Hi
> >
> > On 2019-08-22, Greg KH wrote:
> > > On Fri, Aug 23, 2019 at 12:05:27AM +0200, Stefan Lippers-Hollmann wrote:
> > > > On 2019-08-22, Greg KH wrote:
On Fri, Aug 23, 2019 at 03:05:38AM +0100, Jon Hunter wrote:
>
> On 22/08/2019 18:18, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.4.190 release.
> > There are 78 patches in this series, all will be posted as a response
> > to this one. If anyone has any
On Fri, Aug 23, 2019 at 01:56:22PM +0530, Naresh Kamboju wrote:
> On Thu, 22 Aug 2019 at 22:53, Greg Kroah-Hartman
> wrote:
> >
> > This is the start of the stable review cycle for the 4.4.190 release.
> > There are 78 patches in this series, all will be posted as a response
> > to this one. If
On Fri, Aug 23, 2019 at 07:27:13AM -0700, Guenter Roeck wrote:
> On 8/22/19 10:18 AM, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.4.190 release.
> > There are 78 patches in this series, all will be posted as a response
> > to this one. If anyone has any
On Fri, Aug 23, 2019 at 04:29:49PM +1000, Adam Zerella wrote:
> As pointed out in https://kernelnewbies.org/KernelJanitors/Todo
> this patch replaces the outdated macro of DPRINTK for pr_debug()
>
> To: Dominik Brodowski
> To: Thomas Gleixner
> To: Greg Kroah-Hartman
> To: Adam Zerella
> To:
On Wed, Aug 21, 2019 at 04:15:13PM -0700, Rajat Jain wrote:
> Split the AER stats into multiple sysfs atributes. Note that
> this changes the ABI of the AER stats, but hopefully, there
> aren't active users that need to change. This is how the AERs
> are being exposed now:
>
> localhost
Use device_init_wakeup and pm_wakeup_hard_event instead of directly
calling pm_system_wakeup(). This is the preferred way to do this and
this will allow the user to disable wakeup through INT0002 events
through sysfs.
Signed-off-by: Hans de Goede
---
drivers/platform/x86/intel_int0002_vgpio.c |
Commit 871f1f2bcb01 ("platform/x86: intel_int0002_vgpio: Only implement
irq_set_wake on Bay Trail") removed the irq_set_wake method from the
struct irq_chip used on Cherry Trail, but it did not set
IRQCHIP_SKIP_SET_WAKE causing kernel/irq/manage.c: set_irq_wake_real()
to return -ENXIO.
This
Hi
On 23/08/2019 18:16, Andrey Konovalov wrote:
> On Fri, Aug 23, 2019 at 3:56 PM Cristian Marussi
> wrote:
>>
>> Hi Andrey
>>
>> On 24/06/2019 15:33, Andrey Konovalov wrote:
>>> This patch is a part of a series that extends kernel ABI to allow to pass
>>> tagged user pointers (with the top
On Wed, Aug 21, 2019 at 09:09:08PM +0200, Thomas Gleixner wrote:
> Now that the expiry cache can be accessed as an array, the per clock
> checking can be reduced to just comparing the corresponding array elements.
>
> Signed-off-by: Thomas Gleixner
Reviewed-by: Frederic Weisbecker
Hi Zenghui, Marc,
On 8/23/19 7:33 PM, Eric Auger wrote:
> At the moment we use 2 IO devices per GICv3 redistributor: one
> one for the RD_base frame and one for the SGI_base frame.
>
> Instead we can use a single IO device per redistributor (the 2
> frames are contiguous). This saves slots on
On Fri, Aug 23, 2019 at 10:34 AM shuah wrote:
>
> On 8/23/19 11:27 AM, Brendan Higgins wrote:
> > On Fri, Aug 23, 2019 at 10:05 AM shuah wrote:
> >>
> >> On 8/23/19 10:48 AM, Brendan Higgins wrote:
> >>> On Fri, Aug 23, 2019 at 8:33 AM shuah wrote:
>
> Hi Brendan,
>
> On
The pull request you sent on Fri, 23 Aug 2019 09:34:39 -0700:
> git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git tags/xfs-5.3-fixes-4
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/f576518c9ab5a6fbc7a4b9bbfc9be31aa18a1cc7
Thank you!
--
Deet-doot-dot, I am a bot.
> -Original Message-
> From: Alex Williamson
> Sent: Friday, August 23, 2019 10:47 PM
> To: Parav Pandit
> Cc: Jiri Pirko ; Jiri Pirko ; David S .
> Miller
> ; Kirti Wankhede ; Cornelia
> Huck ; k...@vger.kernel.org; linux-
> ker...@vger.kernel.org; cjia ; net...@vger.kernel.org
>
On Wed, Aug 21, 2019 at 09:09:09PM +0200, Thomas Gleixner wrote:
> The expiry cache can now be accessed as an array. Replace the per clock
> checks with a simple comparison of the clock indexed array member.
>
> Signed-off-by: Thomas Gleixner
Reviewed-by: Frederic Weisbecker
On Fri, Aug 23, 2019 at 10:28:02AM -0700 bseg...@google.com wrote:
> Dave Chiluk writes:
>
> > On Wed, Aug 21, 2019 at 12:36 PM wrote:
> >>
> >> Qian Cai writes:
> >>
> >> > The linux-next commit "sched/fair: Fix low cpu usage with high
> >> > throttling by removing expiration of cpu-local
On 8/14/19 6:20 PM, Dan Williams wrote:
> Jeff reported a scenario where ndctl was failing to unlock DIMMs [1].
> Through the course of debug it was discovered that the security
> interface on the DIMMs was in the 'frozen' state disallowing unlock, or
> any security operation. Unfortunately
On Wed, Aug 21, 2019 at 09:09:10PM +0200, Thomas Gleixner wrote:
> Use the array based expiry cache in check_thread_timers() and convert the
> store in check_process_timers() for consistency.
>
> Signed-off-by: Thomas Gleixner
> ---
> kernel/time/posix-cpu-timers.c | 26
On 22/08/2019 04:17, Rik van Riel wrote:
> Sometimes the hierarchical load of a sched_entity needs to be calculated.
> Rename task_h_load to task_se_h_load, and directly pass a sched_entity to
> that function.
>
> Move the function declaration up above where it will be used later.
>
> No
On 22/08/2019 04:17, Rik van Riel wrote:
> Flatten the hierarchical runqueues into just the per CPU rq.cfs runqueue.
>
> Iteration of the sched_entity hierarchy is rate limited to once per jiffy
> per sched_entity, which is a smaller change than it seems, because load
> average adjustments were
On 8/23/19 11:54 AM, Brendan Higgins wrote:
On Fri, Aug 23, 2019 at 10:34 AM shuah wrote:
On 8/23/19 11:27 AM, Brendan Higgins wrote:
On Fri, Aug 23, 2019 at 10:05 AM shuah wrote:
On 8/23/19 10:48 AM, Brendan Higgins wrote:
On Fri, Aug 23, 2019 at 8:33 AM shuah wrote:
Hi Brendan,
On
On Wed, Aug 21, 2019 at 09:09:11PM +0200, Thomas Gleixner wrote:
> The last users of the odd define based renaming of struct task_cputime
> members are gone. Good riddance.
>
> Signed-off-by: Thomas Gleixner
Reviewed-by: Frederic Weisbecker
In file included from ./include/linux/bitmap.h:9,
from ./include/linux/cpumask.h:12,
from ./arch/x86/include/asm/cpumask.h:5,
from ./arch/x86/include/asm/msr.h:11,
from ./arch/x86/include/asm/processor.h:21,
from
On 8/22/19 11:05 AM, Sasha Levin wrote:
This is the start of the stable review cycle for the 5.2.10 release.
There are 135 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
From: Stefano Stabellini
This is for the qualcomm-bsp-ghs_8x96autogvmquin44_d7 branch.
My checkout with this change is here:
/home/cat/tmontague/linux-kernels/qualcomm-bsp-ghs
Feel free to poke around.
Commit message:
This is a combination of 2 commits:
commit
Please ignore!
> -Original Message-
> From: Tim Montague [mailto:tmonta...@ghs.com]
> Sent: Friday, August 23, 2019 11:27 AM
> To: Chad Page
> Cc: rtos-code-rev...@ghs.com; Stefano Stabellini
> ; Mike Galbraith ; Peter
> Zijlstra ; Thomas Gleixner ;
> linux-kernel@vger.kernel.org; Tim
Hi Linus,
I didn't notice I was on my personal email identity when I sent the pull
request. Sorry about that. It's really me ;-)
On Fri, 2019-08-23 at 14:48 -0400, Doug Ledford wrote:
> Hi Linus,
>
> No beating around the bush: this is a monster pull request for an -rc5
> kernel. Intel hit
suggested by checkpatch
Signed-off-by: Forrest Fleming
---
.../net/ethernet/intel/e1000/e1000_param.c| 28 +--
1 file changed, 14 insertions(+), 14 deletions(-)
diff --git a/drivers/net/ethernet/intel/e1000/e1000_param.c
b/drivers/net/ethernet/intel/e1000/e1000_param.c
On HID report descriptor parsing error the code displays bogus
pointer instead of error offset (subtracts start=NULL from end).
Make the message more useful by displaying correct error offset
and include total buffer size for reference.
This was carried over from ancient times - "Fixed" commit
101 - 200 of 850 matches
Mail list logo
