On 05/11/2018 03:48:25+, Maciej W. Rozycki wrote:
> Fix an issue with the 32-bit range error path in `rtc_hctosys' where no
> error code is set and consequently the successful preceding call result
> from `rtc_read_time' is propagated to `rtc_hctosys_ret'. This in turn
> makes any
On 05/11/2018 03:48:25+, Maciej W. Rozycki wrote:
> Fix an issue with the 32-bit range error path in `rtc_hctosys' where no
> error code is set and consequently the successful preceding call result
> from `rtc_read_time' is propagated to `rtc_hctosys_ret'. This in turn
> makes any
On Wed, Nov 7, 2018 at 6:45 AM Andrey Ryabinin wrote:
>
> From: Arnd Bergmann
>
> gcc-8 complains about the prototype for this function:
>
> lib/ubsan.c:432:1: error: ignoring attribute 'noreturn' in declaration of a
> built-in function '__ubsan_handle_builtin_unreachable' because it conflicts
On Wed, 7 Nov 2018, Felipe Balbi wrote:
> Hi,
>
> Alan Stern writes:
> >> Alan Stern writes:
> >> > There's a similar race at the hardware level. What happens if the
> >> > controller receives a new SETUP packet and concurrently the driver is
> >> > setting up the controller registers for a
On Wed, Nov 7, 2018 at 6:45 AM Andrey Ryabinin wrote:
>
> From: Arnd Bergmann
>
> gcc-8 complains about the prototype for this function:
>
> lib/ubsan.c:432:1: error: ignoring attribute 'noreturn' in declaration of a
> built-in function '__ubsan_handle_builtin_unreachable' because it conflicts
On Wed, 7 Nov 2018, Felipe Balbi wrote:
> Hi,
>
> Alan Stern writes:
> >> Alan Stern writes:
> >> > There's a similar race at the hardware level. What happens if the
> >> > controller receives a new SETUP packet and concurrently the driver is
> >> > setting up the controller registers for a
On Wed, Nov 7, 2018 at 6:44 AM Frieder Schrempf
wrote:
>
> From: Frieder Schrempf
>
> The new driver at spi/spi-fsl-qspi.c replaces the old SPI NOR driver
> at mtd/fsl-quadspi.c. Switch to the new driver in the defconfigs.
>
> Signed-off-by: Frieder Schrempf
Hi Frieder,
This patch is part of
On Wed, Nov 7, 2018 at 6:44 AM Frieder Schrempf
wrote:
>
> From: Frieder Schrempf
>
> The new driver at spi/spi-fsl-qspi.c replaces the old SPI NOR driver
> at mtd/fsl-quadspi.c. Switch to the new driver in the defconfigs.
>
> Signed-off-by: Frieder Schrempf
Hi Frieder,
This patch is part of
There are no users of of_pdt_build_more since 2012, so remove it.
Cc: Frank Rowand
Signed-off-by: Rob Herring
---
drivers/of/pdt.c | 5 -
include/linux/of_pdt.h | 2 --
2 files changed, 7 deletions(-)
diff --git a/drivers/of/pdt.c b/drivers/of/pdt.c
index 013e65de074a..4fc0fd96ed04
There are no users of of_pdt_build_more since 2012, so remove it.
Cc: Frank Rowand
Signed-off-by: Rob Herring
---
drivers/of/pdt.c | 5 -
include/linux/of_pdt.h | 2 --
2 files changed, 7 deletions(-)
diff --git a/drivers/of/pdt.c b/drivers/of/pdt.c
index 013e65de074a..4fc0fd96ed04
We use a value to represent the priority of the RT task. But a smaller
value corresponds to a higher priority. If there are two RT task A and B,
their priorities are prio_a and prio_b, respectively. If prio_a is larger
than prio_b, which means that the priority of RT task A is lower than RT
task
We use a value to represent the priority of the RT task. But a smaller
value corresponds to a higher priority. If there are two RT task A and B,
their priorities are prio_a and prio_b, respectively. If prio_a is larger
than prio_b, which means that the priority of RT task A is lower than RT
task
On Tue, Nov 06, 2018 at 04:41:23PM +0100, Arnaud Pouliquen wrote:
> I would say force device to 0 if no_pcm (need probably to create the
> control in hdmi_of_xlate_dai_id instead of hdmi_codec_pcm_new).
> But keep in mind that solution has to work in case of multi HDMI codec
> instances, perhaps
On Tue, Nov 06, 2018 at 04:41:23PM +0100, Arnaud Pouliquen wrote:
> I would say force device to 0 if no_pcm (need probably to create the
> control in hdmi_of_xlate_dai_id instead of hdmi_codec_pcm_new).
> But keep in mind that solution has to work in case of multi HDMI codec
> instances, perhaps
Use DEFINE_SHOW_ATTRIBUTE macro to simplify the code.
Signed-off-by: Yangtao Li
---
drivers/cpufreq/s3c24xx-cpufreq-debugfs.c | 46 +++
1 file changed, 6 insertions(+), 40 deletions(-)
diff --git a/drivers/cpufreq/s3c24xx-cpufreq-debugfs.c
Use DEFINE_SHOW_ATTRIBUTE macro to simplify the code.
Signed-off-by: Yangtao Li
---
drivers/cpufreq/s3c24xx-cpufreq-debugfs.c | 46 +++
1 file changed, 6 insertions(+), 40 deletions(-)
diff --git a/drivers/cpufreq/s3c24xx-cpufreq-debugfs.c
On Wed, Nov 07, 2018 at 12:21:01PM +0100, Oleg Nesterov wrote:
> On 11/07, Elvira Khabirova wrote:
> >
> > In short, if a 64-bit task performs a syscall through int 0x80, its tracer
> > has no reliable means to find out that the syscall was, in fact,
> > a compat syscall, and misidentifies it.
> >
On Wed, Nov 07, 2018 at 12:21:01PM +0100, Oleg Nesterov wrote:
> On 11/07, Elvira Khabirova wrote:
> >
> > In short, if a 64-bit task performs a syscall through int 0x80, its tracer
> > has no reliable means to find out that the syscall was, in fact,
> > a compat syscall, and misidentifies it.
> >
On Wed, Nov 07, 2018 at 10:36:12AM +0100, Clément Péron wrote:
> The Cygnus architecture use a Kona PWM. This is already present
> in the device tree but can't be built actually. Hence, allow the
> Kona PWM to be built for Cygnus arch.
>
> Signed-off-by: Clément Péron
> ---
>
--
Hello Dear.
My name is Doctor Lilly Williams, I am 26 years old medical doctor
from USA united state of America. presently working and living in the
UK United kingdom, my mum is from french why my father is from USA, I
was just going through the Internet search when i saw your
On Wed, Nov 07, 2018 at 10:36:12AM +0100, Clément Péron wrote:
> The Cygnus architecture use a Kona PWM. This is already present
> in the device tree but can't be built actually. Hence, allow the
> Kona PWM to be built for Cygnus arch.
>
> Signed-off-by: Clément Péron
> ---
>
--
Hello Dear.
My name is Doctor Lilly Williams, I am 26 years old medical doctor
from USA united state of America. presently working and living in the
UK United kingdom, my mum is from french why my father is from USA, I
was just going through the Internet search when i saw your
> Yes, this may slow things down. I am not sure I agree with the impl.
> either.
> Could one not make cpu_to_je_X/jeX_to_cpu a function ptr which is set to
> a func. with the correct endian?
On x86 retpoline would make that quite slow.
--
dwmw2
> Yes, this may slow things down. I am not sure I agree with the impl.
> either.
> Could one not make cpu_to_je_X/jeX_to_cpu a function ptr which is set to
> a func. with the correct endian?
On x86 retpoline would make that quite slow.
--
dwmw2
On Wed, Nov 07, 2018 at 02:50:16PM +0100, Jan Kara wrote:
> On Wed 31-10-18 22:13:00, Vasily Averin wrote:
> > Fixes 3f2571c1f91f ("ext4: factor out xattr moving")
> > cc: Jan Kara
> > however issue was present in original ext4_expand_extra_isize_ea()
> > Fixes 6dd4ee7cab7e ("ext4: Expand
On Wed, Nov 07, 2018 at 02:50:16PM +0100, Jan Kara wrote:
> On Wed 31-10-18 22:13:00, Vasily Averin wrote:
> > Fixes 3f2571c1f91f ("ext4: factor out xattr moving")
> > cc: Jan Kara
> > however issue was present in original ext4_expand_extra_isize_ea()
> > Fixes 6dd4ee7cab7e ("ext4: Expand
On Wed, Oct 31, 2018 at 10:12:52PM +0300, Vasily Averin wrote:
> bs.bh was taken in previous ext4_xattr_block_find() call,
> it should be released before re-using
>
> Fixes 7e01c8e5420b ("ext3/4: fix uninitialized bs in ...") # 2.6.26
> cc: Tiger Yang
>
> Signed-off-by: Vasily Averin
Thanks,
On Wed, Oct 31, 2018 at 10:12:52PM +0300, Vasily Averin wrote:
> bs.bh was taken in previous ext4_xattr_block_find() call,
> it should be released before re-using
>
> Fixes 7e01c8e5420b ("ext3/4: fix uninitialized bs in ...") # 2.6.26
> cc: Tiger Yang
>
> Signed-off-by: Vasily Averin
Thanks,
On Wed, Oct 31, 2018 at 10:12:43PM +0300, Vasily Averin wrote:
> Fixes dec214d00e0d ("ext4: xattr inode deduplication") # 4.13
>
> Signed-off-by: Vasily Averin
Thanks, applied. I used the description line:
ext4: fix buffer leak in ext4_xattr_get_block() on error path
On Wed, Oct 31, 2018 at 10:12:43PM +0300, Vasily Averin wrote:
> Fixes dec214d00e0d ("ext4: xattr inode deduplication") # 4.13
>
> Signed-off-by: Vasily Averin
Thanks, applied. I used the description line:
ext4: fix buffer leak in ext4_xattr_get_block() on error path
On Wed, Nov 7, 2018 at 3:54 PM, Miklos Szeredi wrote:
> On Wed, Nov 7, 2018 at 4:42 PM, Daniel Colascione wrote:
>
>> configuration!" is something I've heard more than once. Who's to say
>> that sysfs is for exposing /proc/pid/stat,
>
> Patch is about /proc/stat not /proc/PID/stat. Please
On Wed, Nov 7, 2018 at 3:54 PM, Miklos Szeredi wrote:
> On Wed, Nov 7, 2018 at 4:42 PM, Daniel Colascione wrote:
>
>> configuration!" is something I've heard more than once. Who's to say
>> that sysfs is for exposing /proc/pid/stat,
>
> Patch is about /proc/stat not /proc/PID/stat. Please
On Tue, Nov 06, 2018 at 05:58:01AM -0800, Sean Christopherson wrote:
> On Tue, 2018-11-06 at 15:45 +0200, Jarkko Sakkinen wrote:
> > From: Sean Christopherson
> >
> > Similar to other large Intel features such as VMX and TXT, SGX must be
> > explicitly enabled in IA32_FEATURE_CONTROL MSR to be
On Tue, Nov 06, 2018 at 05:58:01AM -0800, Sean Christopherson wrote:
> On Tue, 2018-11-06 at 15:45 +0200, Jarkko Sakkinen wrote:
> > From: Sean Christopherson
> >
> > Similar to other large Intel features such as VMX and TXT, SGX must be
> > explicitly enabled in IA32_FEATURE_CONTROL MSR to be
On Wed, Oct 31, 2018 at 10:12:35PM +0300, Vasily Averin wrote:
> Fixes c8585c6fcaf2 ("ext4: fix races between changing inode journal ...") #
> 4.7
>
> cc: Daeho Jeong
> Signed-off-by: Vasily Averin
Thanks, applied.
- Ted
On Wed, Oct 31, 2018 at 10:12:35PM +0300, Vasily Averin wrote:
> Fixes c8585c6fcaf2 ("ext4: fix races between changing inode journal ...") #
> 4.7
>
> cc: Daeho Jeong
> Signed-off-by: Vasily Averin
Thanks, applied.
- Ted
On Wed, Nov 07, 2018 at 03:44:31PM +, Will Deacon wrote:
> Hi John,
>
> On Tue, Nov 06, 2018 at 08:39:33PM +0800, John Garry wrote:
> > Currently the NUMA distance map parsing does not validate the distance
> > table for the distance-matrix rules 1-2 in [1].
> >
> > However the arch NUMA
On Wed, Nov 07, 2018 at 03:44:31PM +, Will Deacon wrote:
> Hi John,
>
> On Tue, Nov 06, 2018 at 08:39:33PM +0800, John Garry wrote:
> > Currently the NUMA distance map parsing does not validate the distance
> > table for the distance-matrix rules 1-2 in [1].
> >
> > However the arch NUMA
On Wed, Nov 07, 2018 at 07:01:29AM -0500, Jeff Layton wrote:
> On Wed, 2018-11-07 at 16:43 +0800, kernel test robot wrote:
> > FYI, we noticed the following commit (built with gcc-7):
> >
> > commit: dee160df820de41ff2f59a715643680822a0ab06 ("locks: use properly
> > initialized file_lock when
On Wed, Nov 07, 2018 at 07:01:29AM -0500, Jeff Layton wrote:
> On Wed, 2018-11-07 at 16:43 +0800, kernel test robot wrote:
> > FYI, we noticed the following commit (built with gcc-7):
> >
> > commit: dee160df820de41ff2f59a715643680822a0ab06 ("locks: use properly
> > initialized file_lock when
On Wed, Nov 7, 2018 at 4:42 PM, Daniel Colascione wrote:
> configuration!" is something I've heard more than once. Who's to say
> that sysfs is for exposing /proc/pid/stat,
Patch is about /proc/stat not /proc/PID/stat. Please revise your
arguments based on that.
Thanks,
Miklos
On Wed, Nov 7, 2018 at 4:42 PM, Daniel Colascione wrote:
> configuration!" is something I've heard more than once. Who's to say
> that sysfs is for exposing /proc/pid/stat,
Patch is about /proc/stat not /proc/PID/stat. Please revise your
arguments based on that.
Thanks,
Miklos
Hello,
On Tue, Sep 25, 2018 at 04:34:16PM +0200, Juri Lelli wrote:
> It would be great if you could please have a look at the proposed change
> below (and the rest of the set of course :-).
Yeah, looks good to me. Please feel free to add
Acked-by: Tejun Heo
> Another bit that I'd be more
Hello,
On Tue, Sep 25, 2018 at 04:34:16PM +0200, Juri Lelli wrote:
> It would be great if you could please have a look at the proposed change
> below (and the rest of the set of course :-).
Yeah, looks good to me. Please feel free to add
Acked-by: Tejun Heo
> Another bit that I'd be more
Commit-ID: f26621e60b35369bca9228bc936dc723b3e421af
Gitweb: https://git.kernel.org/tip/f26621e60b35369bca9228bc936dc723b3e421af
Author: Borislav Petkov
AuthorDate: Mon, 5 Nov 2018 10:33:07 +0100
Committer: Ingo Molnar
CommitDate: Wed, 7 Nov 2018 16:47:47 +0100
resource/docs: Complete
Commit-ID: f26621e60b35369bca9228bc936dc723b3e421af
Gitweb: https://git.kernel.org/tip/f26621e60b35369bca9228bc936dc723b3e421af
Author: Borislav Petkov
AuthorDate: Mon, 5 Nov 2018 10:33:07 +0100
Committer: Ingo Molnar
CommitDate: Wed, 7 Nov 2018 16:47:47 +0100
resource/docs: Complete
On Wed, Nov 07, 2018 at 04:27:51AM +0100, Elvira Khabirova wrote:
[...]
> The structure was chosen according to [2], except for two changes.
> First: instead of an arch field with a value of AUDIT_ARCH_*, a boolean
> is_compat value is returned, because a) not all arches have an AUDIT_ARCH_*
>
On Wed, Nov 07, 2018 at 04:27:51AM +0100, Elvira Khabirova wrote:
[...]
> The structure was chosen according to [2], except for two changes.
> First: instead of an arch field with a value of AUDIT_ARCH_*, a boolean
> is_compat value is returned, because a) not all arches have an AUDIT_ARCH_*
>
Ryder Lee writes:
> The issue was introduced by Kernel CI:
> https://kernelci.org/boot/id/5bbdcbad59b5146fc5b43592/
The issue was *found* by kernelCI, not introduced by kernelCI. ;)
> Fix this by using a 'stdout-path' property that points to the device.
>
> Fixes: c0d9f9ad4f76 ("arm64: dts:
Ryder Lee writes:
> The issue was introduced by Kernel CI:
> https://kernelci.org/boot/id/5bbdcbad59b5146fc5b43592/
The issue was *found* by kernelCI, not introduced by kernelCI. ;)
> Fix this by using a 'stdout-path' property that points to the device.
>
> Fixes: c0d9f9ad4f76 ("arm64: dts:
From: Heiko Stuebner
This commit add support for STMicroelectronics lis3de accelerometer.
Datasheet for this device can be found here:
https://www.st.com/resource/en/datasheet/lis3de.pdf
Signed-off-by: Heiko Stuebner
---
Documentation/devicetree/bindings/iio/st-sensors.txt | 1 +
From: Heiko Stuebner
This commit add support for STMicroelectronics lis3de accelerometer.
Datasheet for this device can be found here:
https://www.st.com/resource/en/datasheet/lis3de.pdf
Signed-off-by: Heiko Stuebner
---
Documentation/devicetree/bindings/iio/st-sensors.txt | 1 +
Hi John,
On Tue, Nov 06, 2018 at 08:39:33PM +0800, John Garry wrote:
> Currently the NUMA distance map parsing does not validate the distance
> table for the distance-matrix rules 1-2 in [1].
>
> However the arch NUMA code may enforce some of these rules, but not all.
> Such is the case for the
Hi John,
On Tue, Nov 06, 2018 at 08:39:33PM +0800, John Garry wrote:
> Currently the NUMA distance map parsing does not validate the distance
> table for the distance-matrix rules 1-2 in [1].
>
> However the arch NUMA code may enforce some of these rules, but not all.
> Such is the case for the
On Wed, Nov 7, 2018 at 10:03 AM, Miklos Szeredi wrote:
> On Wed, Nov 7, 2018 at 12:48 AM, Andrew Morton
> wrote:
>> On Mon, 29 Oct 2018 23:04:45 + Daniel Colascione
>> wrote:
>>
>>> On Mon, Oct 29, 2018 at 7:25 PM, Davidlohr Bueso wrote:
>>> > This patch introduces a new /proc/stat2 file
On Wed, Nov 7, 2018 at 10:03 AM, Miklos Szeredi wrote:
> On Wed, Nov 7, 2018 at 12:48 AM, Andrew Morton
> wrote:
>> On Mon, 29 Oct 2018 23:04:45 + Daniel Colascione
>> wrote:
>>
>>> On Mon, Oct 29, 2018 at 7:25 PM, Davidlohr Bueso wrote:
>>> > This patch introduces a new /proc/stat2 file
On Tue, Nov 06, 2018 at 05:17:14PM -0800, Andy Lutomirski wrote:
> On Tue, Nov 6, 2018 at 4:02 PM Sean Christopherson
> wrote:
> >
> > On Tue, Nov 06, 2018 at 03:39:48PM -0800, Andy Lutomirski wrote:
> > > On Tue, Nov 6, 2018 at 3:35 PM Sean Christopherson
> > > wrote:
> > > >
> > > > On Tue,
On Tue, Nov 06, 2018 at 05:17:14PM -0800, Andy Lutomirski wrote:
> On Tue, Nov 6, 2018 at 4:02 PM Sean Christopherson
> wrote:
> >
> > On Tue, Nov 06, 2018 at 03:39:48PM -0800, Andy Lutomirski wrote:
> > > On Tue, Nov 6, 2018 at 3:35 PM Sean Christopherson
> > > wrote:
> > > >
> > > > On Tue,
Explicit clock enabling is required on 6sll and 6ull so mention that
standard clock bindings are used.
Signed-off-by: Leonard Crestez
Reviewed-by: Fabio Estevam
Reviewed-by: Rob Herring
---
Documentation/devicetree/bindings/crypto/fsl-dcp.txt | 2 ++
1 file changed, 2 insertions(+)
diff
Explicit clock enabling is required on 6sll and 6ull so mention that
standard clock bindings are used.
Signed-off-by: Leonard Crestez
Reviewed-by: Fabio Estevam
Reviewed-by: Rob Herring
---
Documentation/devicetree/bindings/crypto/fsl-dcp.txt | 2 ++
1 file changed, 2 insertions(+)
diff
On Wed, Oct 31, 2018 at 10:12:27PM +0300, Vasily Averin wrote:
> Fixes bfe0a5f47ada ("ext4: add more mount time checks of the superblock") #
> 4.18
>
> Signed-off-by: Vasily Averin
> ---
> fs/ext4/super.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git
On Wed, Oct 31, 2018 at 10:12:27PM +0300, Vasily Averin wrote:
> Fixes bfe0a5f47ada ("ext4: add more mount time checks of the superblock") #
> 4.18
>
> Signed-off-by: Vasily Averin
> ---
> fs/ext4/super.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger
crash:
Reported-and-tested-by:
syzbot+6339eda9cb4ebbc4c...@syzkaller.appspotmail.com
Tested on:
commit: 59fc453b21f7 Merge branch 'akpm' (patches from Andrew)
git tree:
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger
crash:
Reported-and-tested-by:
syzbot+6339eda9cb4ebbc4c...@syzkaller.appspotmail.com
Tested on:
commit: 59fc453b21f7 Merge branch 'akpm' (patches from Andrew)
git tree:
On Wed, Oct 31, 2018 at 10:12:18PM +0300, Vasily Averin wrote:
> Fixes dc6982ff4db1 ("ext4: refactor code to read directory blocks ...") # 3.9
>
> Signed-off-by: Vasily Averin
> ---
> fs/ext4/namei.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/fs/ext4/namei.c b/fs/ext4/namei.c
>
On Wed, Oct 31, 2018 at 10:12:18PM +0300, Vasily Averin wrote:
> Fixes dc6982ff4db1 ("ext4: refactor code to read directory blocks ...") # 3.9
>
> Signed-off-by: Vasily Averin
> ---
> fs/ext4/namei.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/fs/ext4/namei.c b/fs/ext4/namei.c
>
On Fri 2018-11-02 22:31:57, Tetsuo Handa wrote:
> syzbot is sometimes getting mixed output like below due to concurrent
> printk(). Mitigate such output by using line-buffered printk() API.
>
> @@ -2421,18 +2458,20 @@ static void check_chain_key(struct task_struct *curr)
>
On Fri 2018-11-02 22:31:57, Tetsuo Handa wrote:
> syzbot is sometimes getting mixed output like below due to concurrent
> printk(). Mitigate such output by using line-buffered printk() API.
>
> @@ -2421,18 +2458,20 @@ static void check_chain_key(struct task_struct *curr)
>
Hi Neil-
> On Nov 6, 2018, at 11:12 PM, NeilBrown wrote:
>
> 1/ discard 'struct unx_cred'. We don't need any data that
> is not already in 'struct rpc_cred'.
> 2/ Don't keep these creds in a hash table. When a credential
> is needed, simply allocate it. When not needed, discard it.
>
Hi Neil-
> On Nov 6, 2018, at 11:12 PM, NeilBrown wrote:
>
> 1/ discard 'struct unx_cred'. We don't need any data that
> is not already in 'struct rpc_cred'.
> 2/ Don't keep these creds in a hash table. When a credential
> is needed, simply allocate it. When not needed, discard it.
>
On Wed, Nov 07, 2018 at 03:03:27PM +, Mark Brown wrote:
> The patch
>
>spi: Add QuadSPI driver for Atmel SAMA5D2
>
> has been applied to the spi tree at
>
>https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git
Sorry, I got confused about which patch series Boris had
On Wed, Nov 07, 2018 at 03:03:27PM +, Mark Brown wrote:
> The patch
>
>spi: Add QuadSPI driver for Atmel SAMA5D2
>
> has been applied to the spi tree at
>
>https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git
Sorry, I got confused about which patch series Boris had
PIOBU pins do not lose their voltage during Backup/Self-refresh.
This patch adds a simple GPIO controller for them.
This driver adds support for using the pins as GPIO
offering the possibility to read/set the voltage.
Signed-off-by: Andrei Stefanescu
---
drivers/gpio/Kconfig | 10
This patch describes the compatible and the device tree
bindings necessary for the sama5d2 PIOBU GPIO
controller driver.
Signed-off-by: Andrei Stefanescu
---
.../bindings/gpio/gpio-sama5d2-piobu.txt | 23 ++
1 file changed, 23 insertions(+)
create mode 100644
On sama5d2 SoC the PIOBU pins do not lose their
voltage during Backup/Self-refresh mode. This can
be useful, for example, when the voltage must remain
positive for a peripheral during Backup/Self-refresh
mode (suspend-to ram is the Linux equivalent state).
This patch series:
- documents the
PIOBU pins do not lose their voltage during Backup/Self-refresh.
This patch adds a simple GPIO controller for them.
This driver adds support for using the pins as GPIO
offering the possibility to read/set the voltage.
Signed-off-by: Andrei Stefanescu
---
drivers/gpio/Kconfig | 10
This patch describes the compatible and the device tree
bindings necessary for the sama5d2 PIOBU GPIO
controller driver.
Signed-off-by: Andrei Stefanescu
---
.../bindings/gpio/gpio-sama5d2-piobu.txt | 23 ++
1 file changed, 23 insertions(+)
create mode 100644
On sama5d2 SoC the PIOBU pins do not lose their
voltage during Backup/Self-refresh mode. This can
be useful, for example, when the voltage must remain
positive for a peripheral during Backup/Self-refresh
mode (suspend-to ram is the Linux equivalent state).
This patch series:
- documents the
This patch adds a maintainer for the sama5d2 GPIO controller
driver.
Signed-off-by: Andrei Stefanescu
---
MAINTAINERS | 7 +++
1 file changed, 7 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index f485597..88369f1 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -9760,6 +9760,13 @@ M:
This patch adds a maintainer for the sama5d2 GPIO controller
driver.
Signed-off-by: Andrei Stefanescu
---
MAINTAINERS | 7 +++
1 file changed, 7 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index f485597..88369f1 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -9760,6 +9760,13 @@ M:
On Wed, Nov 7, 2018 at 3:59 PM, Will Deacon wrote:
> On Wed, Nov 07, 2018 at 03:56:03PM +0100, Andrey Konovalov wrote:
>> On Tue, Nov 6, 2018 at 6:30 PM, Andrey Konovalov
>> wrote:
>> > This patchset adds a new software tag-based mode to KASAN [1].
>> > (Initially this mode was called KHWASAN,
On Wed, Nov 7, 2018 at 3:59 PM, Will Deacon wrote:
> On Wed, Nov 07, 2018 at 03:56:03PM +0100, Andrey Konovalov wrote:
>> On Tue, Nov 6, 2018 at 6:30 PM, Andrey Konovalov
>> wrote:
>> > This patchset adds a new software tag-based mode to KASAN [1].
>> > (Initially this mode was called KHWASAN,
#syz test: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
59fc453b21f7
---
fs/fuse/dev.c |4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
--- a/fs/fuse/dev.c
+++ b/fs/fuse/dev.c
@@ -1768,8 +1768,10 @@ static int fuse_retrieve(struct fuse_con
req->in.args[1].size =
#syz test: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
59fc453b21f7
---
fs/fuse/dev.c |4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
--- a/fs/fuse/dev.c
+++ b/fs/fuse/dev.c
@@ -1768,8 +1768,10 @@ static int fuse_retrieve(struct fuse_con
req->in.args[1].size =
syzbot has found a reproducer for the following crash on:
HEAD commit:d881de30d29e Add linux-next specific files for 20181107
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=10a0102b40
kernel config: https://syzkaller.appspot.com/x/.config?x
syzbot has found a reproducer for the following crash on:
HEAD commit:d881de30d29e Add linux-next specific files for 20181107
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=10a0102b40
kernel config: https://syzkaller.appspot.com/x/.config?x
The patch
mtd: spi-nor: atmel-quadspi: Add spi-mem support to atmel-quadspi
has been applied to the spi tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24
The patch
mtd: spi-nor: atmel-quadspi: Add spi-mem support to atmel-quadspi
has been applied to the spi tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24
On 07-Nov 15:55, Peter Zijlstra wrote:
> On Wed, Nov 07, 2018 at 02:48:09PM +, Patrick Bellasi wrote:
> > On 07-Nov 14:35, Peter Zijlstra wrote:
> > You mean se_count overflow ?
>
> Yah..
>
> > > And I'm not really a fan of hiding that error in a define like you keep
> > > doing.
> >
> >
On 07-Nov 15:55, Peter Zijlstra wrote:
> On Wed, Nov 07, 2018 at 02:48:09PM +, Patrick Bellasi wrote:
> > On 07-Nov 14:35, Peter Zijlstra wrote:
> > You mean se_count overflow ?
>
> Yah..
>
> > > And I'm not really a fan of hiding that error in a define like you keep
> > > doing.
> >
> >
The patch
spi: Add QuadSPI driver for Atmel SAMA5D2
has been applied to the spi tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus
The patch
mtd: spi-nor: atmel-quadspi: Remove unused code from atmel-quadspi driver
has been applied to the spi tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the
The patch
spi: Add QuadSPI driver for Atmel SAMA5D2
has been applied to the spi tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus
The patch
mtd: spi-nor: atmel-quadspi: Remove unused code from atmel-quadspi driver
has been applied to the spi tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the
On 07.11.2018 16:53, Mark Brown wrote:
> On Fri, Oct 26, 2018 at 04:19:48PM +, claudiu.bez...@microchip.com wrote:
>
>> +static unsigned int act8945a_of_map_mode(unsigned int mode)
>> +{
>> +if (mode == ACT8945A_DCDC_MODE_POWER_SAVING)
>> +return REGULATOR_MODE_STANDBY;
>>
On 07.11.2018 16:53, Mark Brown wrote:
> On Fri, Oct 26, 2018 at 04:19:48PM +, claudiu.bez...@microchip.com wrote:
>
>> +static unsigned int act8945a_of_map_mode(unsigned int mode)
>> +{
>> +if (mode == ACT8945A_DCDC_MODE_POWER_SAVING)
>> +return REGULATOR_MODE_STANDBY;
>>
On Wed, Nov 07, 2018 at 09:56:27AM -0500, Steven Rostedt wrote:
> On Wed, 7 Nov 2018 12:10:32 +0100
> Juri Lelli wrote:
>
> > check_dl_overrun is used to send a SIGXCPU to users that asked to be
> > informed when SCHED_DEADLINE runtime overruns occur.
> >
> > The function is called by
On Wed, Nov 07, 2018 at 09:56:27AM -0500, Steven Rostedt wrote:
> On Wed, 7 Nov 2018 12:10:32 +0100
> Juri Lelli wrote:
>
> > check_dl_overrun is used to send a SIGXCPU to users that asked to be
> > informed when SCHED_DEADLINE runtime overruns occur.
> >
> > The function is called by
The patch
spi: omap-spi: Add compatible for AM654 SoC
has been applied to the spi tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to
The patch
spi: Kconfig: Enable McSPI driver for K3 platforms
has been applied to the spi tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent
901 - 1000 of 1460 matches
Mail list logo
