Allow the PCI quirk tables to be emitted in a way that avoids absolute
references to the hook functions. This reduces the size of the entries,
and, more importantly, makes them invariant under runtime relocation
(e.g., for KASLR)
Acked-by: Bjorn Helgaas
Signed-off-by: Ard
Allow the PCI quirk tables to be emitted in a way that avoids absolute
references to the hook functions. This reduces the size of the entries,
and, more importantly, makes them invariant under runtime relocation
(e.g., for KASLR)
Acked-by: Bjorn Helgaas
Signed-off-by: Ard Biesheuvel
---
On Thu 14 Dec 09:33 PST 2017, srinivas.kandaga...@linaro.org wrote:
> From: Srinivas Kandagatla
>
> This patch adds support to open, write and media format commands
> in the q6asm module.
>
> Signed-off-by: Srinivas Kandagatla
>
On Thu 14 Dec 09:33 PST 2017, srinivas.kandaga...@linaro.org wrote:
> From: Srinivas Kandagatla
>
> This patch adds support to open, write and media format commands
> in the q6asm module.
>
> Signed-off-by: Srinivas Kandagatla
> ---
> sound/soc/qcom/qdsp6/q6asm.c | 530
>
On Tue, Jan 02, 2018 at 02:11:25PM -0500, Neal Cardwell wrote:
> On Tue, Jan 2, 2018 at 1:32 PM, David Miller wrote:
> > From: Neal Cardwell
> > Date: Tue, 2 Jan 2018 11:57:59 -0500
> >
> >> On Mon, Jan 1, 2018 at 9:31 AM, Greg Kroah-Hartman
> >>
On Tue, Jan 02, 2018 at 02:11:25PM -0500, Neal Cardwell wrote:
> On Tue, Jan 2, 2018 at 1:32 PM, David Miller wrote:
> > From: Neal Cardwell
> > Date: Tue, 2 Jan 2018 11:57:59 -0500
> >
> >> On Mon, Jan 1, 2018 at 9:31 AM, Greg Kroah-Hartman
> >> wrote:
> >>> This is the start of the stable
On a randomly chosen distro kernel build for arm64, vmlinux.o shows the
following sections, containing jump label entries, and the associated
RELA relocation records, respectively:
...
[38088] __jump_table PROGBITS 00e19f30
0002ea10
On a randomly chosen distro kernel build for arm64, vmlinux.o shows the
following sections, containing jump label entries, and the associated
RELA relocation records, respectively:
...
[38088] __jump_table PROGBITS 00e19f30
0002ea10
In preparation of switching x86 to use place-relative references for
the code, target and key members of struct jump_entry, replace direct
references to the struct member with invocations of the new accessors.
This will allow us to make the switch by modifying the accessors only.
Signed-off-by:
Similar to the arm64 case, 64-bit x86 can benefit from using 32-bit
relative references rather than 64-bit absolute ones when emitting
struct jump_entry instances. Not only does this reduce the memory
footprint of the entries themselves by 50%, it also removes the need
for carrying relocation
In preparation of switching x86 to use place-relative references for
the code, target and key members of struct jump_entry, replace direct
references to the struct member with invocations of the new accessors.
This will allow us to make the switch by modifying the accessors only.
Signed-off-by:
Similar to the arm64 case, 64-bit x86 can benefit from using 32-bit
relative references rather than 64-bit absolute ones when emitting
struct jump_entry instances. Not only does this reduce the memory
footprint of the entries themselves by 50%, it also removes the need
for carrying relocation
Allow the initcall tables to be emitted using relative references that
are only half the size on 64-bit architectures and don't require fixups
at runtime on relocatable kernels.
Cc: Petr Mladek
Cc: Sergey Senozhatsky
Cc: Steven Rostedt
Allow the initcall tables to be emitted using relative references that
are only half the size on 64-bit architectures and don't require fixups
at runtime on relocatable kernels.
Cc: Petr Mladek
Cc: Sergey Senozhatsky
Cc: Steven Rostedt
Cc: James Morris
Cc: "Serge E. Hallyn"
Signed-off-by:
In preparation of allowing architectures to use relative references
in jump_label entries [which can dramatically reduce the memory
footprint], introduce abstractions for references to the 'code' and
'key' members of struct jump_entry.
Signed-off-by: Ard Biesheuvel
---
To avoid the need for relocating absolute references to tracepoint
structures at boot time when running relocatable kernels (which may
take a disproportionate amount of space), add the option to emit
these tables as relative references instead.
Cc: Ingo Molnar
Acked-by: Steven
In preparation of allowing architectures to use relative references
in jump_label entries [which can dramatically reduce the memory
footprint], introduce abstractions for references to the 'code' and
'key' members of struct jump_entry.
Signed-off-by: Ard Biesheuvel
---
To avoid the need for relocating absolute references to tracepoint
structures at boot time when running relocatable kernels (which may
take a disproportionate amount of space), add the option to emit
these tables as relative references instead.
Cc: Ingo Molnar
Acked-by: Steven Rostedt (VMware)
To allow existing C code to be incorporated into the decompressor or
the UEFI stub, introduce a CPP macro that turns all EXPORT_SYMBOL_xxx
declarations into nops, and #define it in places where such exports
are undesirable. Note that this gets rid of a rather dodgy redefine
of linux/export.h's
To allow existing C code to be incorporated into the decompressor or
the UEFI stub, introduce a CPP macro that turns all EXPORT_SYMBOL_xxx
declarations into nops, and #define it in places where such exports
are undesirable. Note that this gets rid of a rather dodgy redefine
of linux/export.h's
An ordinary arm64 defconfig build has ~64 KB worth of __ksymtab
entries, each consisting of two 64-bit fields containing absolute
references, to the symbol itself and to a char array containing
its name, respectively.
When we build the same configuration with KASLR enabled, we end
up with an
An ordinary arm64 defconfig build has ~64 KB worth of __ksymtab
entries, each consisting of two 64-bit fields containing absolute
references, to the symbol itself and to a char array containing
its name, respectively.
When we build the same configuration with KASLR enabled, we end
up with an
This adds support for emitting special sections such as initcall arrays,
PCI fixups and tracepoints as relative references rather than absolute
references. This reduces the size by 50% on 64-bit architectures, but
more importantly, it removes the need for carrying relocation metadata
for these
Before updating certain subsystems to use place relative 32-bit
relocations in special sections, to save space and reduce the
number of absolute relocations that need to be processed at runtime
by relocatable kernels, introduce the Kconfig symbol and define it
for some architectures that should
This adds support for emitting special sections such as initcall arrays,
PCI fixups and tracepoints as relative references rather than absolute
references. This reduces the size by 50% on 64-bit architectures, but
more importantly, it removes the need for carrying relocation metadata
for these
Before updating certain subsystems to use place relative 32-bit
relocations in special sections, to save space and reduce the
number of absolute relocations that need to be processed at runtime
by relocatable kernels, introduce the Kconfig symbol and define it
for some architectures that should
On 1/1/18 10:08 PM, Wei Yongjun wrote:
Fix the typo, 'status' should be instead of 'status2'.
well spotted, thanks!
Acked-by: Pierre-Louis Bossart
Fixes: b0a9c37b0178 ("soundwire: Add slave status handling")
Signed-off-by: Wei Yongjun
On 1/1/18 10:08 PM, Wei Yongjun wrote:
Fix the typo, 'status' should be instead of 'status2'.
well spotted, thanks!
Acked-by: Pierre-Louis Bossart
Fixes: b0a9c37b0178 ("soundwire: Add slave status handling")
Signed-off-by: Wei Yongjun
---
drivers/soundwire/bus.c | 10 +-
1
On 01/02, Stephen Rothwell wrote:
> Hi all,
>
> After merging the clk tree, today's linux-next build (x86_64 allmodconfig)
> failed like this:
>
> ERROR: "clk_regmap_mux_div_ops" [drivers/clk/qcom/apcs-msm8916.ko] undefined!
> ERROR: "__mux_div_set_src_div" [drivers/clk/qcom/apcs-msm8916.ko]
On 01/02, Stephen Rothwell wrote:
> Hi all,
>
> After merging the clk tree, today's linux-next build (x86_64 allmodconfig)
> failed like this:
>
> ERROR: "clk_regmap_mux_div_ops" [drivers/clk/qcom/apcs-msm8916.ko] undefined!
> ERROR: "__mux_div_set_src_div" [drivers/clk/qcom/apcs-msm8916.ko]
On Mon, 1 Jan 2018 20:43:35 +0100
SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Mon, 1 Jan 2018 20:38:14 +0100
>
> Omit an extra message for a memory allocation failure in this function.
>
> This issue was detected by
On Mon, 1 Jan 2018 20:43:35 +0100
SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Mon, 1 Jan 2018 20:38:14 +0100
>
> Omit an extra message for a memory allocation failure in this function.
>
> This issue was detected by using the Coccinelle software.
>
> Signed-off-by: Markus Elfring
On 1/2/18 12:21 PM, Richard Cochran wrote:
On Tue, Jan 02, 2018 at 11:15:45AM -0600, Pierre-Louis Bossart wrote:
I wrote the code for HDaudio and I remember wasting time trying to figure
out the gory details of the cycle counter stuff when all I wanted was a
conversion from a 24MHz counter to
On 1/2/18 12:21 PM, Richard Cochran wrote:
On Tue, Jan 02, 2018 at 11:15:45AM -0600, Pierre-Louis Bossart wrote:
I wrote the code for HDaudio and I remember wasting time trying to figure
out the gory details of the cycle counter stuff when all I wanted was a
conversion from a 24MHz counter to
From: Brendan Gregg
Date: Tue, 2 Jan 2018 11:46:26 -0800
> If I'm to use sock:inet_sock_set_state for TCP tracing, I'd like
> sk->sk_protocol exposed as a tracepoint argument so I can match on
> IPPROTO_TCP.
Agreed.
From: Brendan Gregg
Date: Tue, 2 Jan 2018 11:46:26 -0800
> If I'm to use sock:inet_sock_set_state for TCP tracing, I'd like
> sk->sk_protocol exposed as a tracepoint argument so I can match on
> IPPROTO_TCP.
Agreed.
From: SZ Lin (林上智)
Date: Fri, 29 Dec 2017 17:02:17 +0800
> This patch adds support for PID 0x9625 of YUGA CLM920-NC5.
>
> YUGA CLM920-NC5 needs to enable QMI_WWAN_QUIRK_DTR before QMI operation.
>
> qmicli -d /dev/cdc-wdm0 -p --dms-get-revision
> [/dev/cdc-wdm0] Device
From: SZ Lin (林上智)
Date: Fri, 29 Dec 2017 17:02:17 +0800
> This patch adds support for PID 0x9625 of YUGA CLM920-NC5.
>
> YUGA CLM920-NC5 needs to enable QMI_WWAN_QUIRK_DTR before QMI operation.
>
> qmicli -d /dev/cdc-wdm0 -p --dms-get-revision
> [/dev/cdc-wdm0] Device revision retrieved:
>
On Sat, Dec 30, 2017 at 7:06 PM, Yafang Shao wrote:
> On Sun, Dec 31, 2017 at 6:33 AM, Brendan Gregg
> wrote:
>> On Tue, Dec 19, 2017 at 7:12 PM, Yafang Shao wrote:
>>> As sk_state is a common field for struct sock, so the
On Sat, Dec 30, 2017 at 7:06 PM, Yafang Shao wrote:
> On Sun, Dec 31, 2017 at 6:33 AM, Brendan Gregg
> wrote:
>> On Tue, Dec 19, 2017 at 7:12 PM, Yafang Shao wrote:
>>> As sk_state is a common field for struct sock, so the state
>>> transition tracepoint should not be a TCP specific feature.
On Tue, Jan 02, 2018 at 01:00:03PM -0600, Bjorn Helgaas wrote:
> [+cc Greg, linux-kernel]
>
> Hi Max,
>
> Thanks for the report!
>
> On Tue, Jan 02, 2018 at 01:50:23AM +0200, Max Gurtovoy wrote:
> > hi all,
> > I encountered a strange phenomena using 2 different pci drivers
> > (nvme and
Hi,
On Tue, Jan 02, 2018 at 01:59:48PM +0100, Pavel Machek wrote:
>
> This adds support for volume up/down keys in the dts.
>
> Signed-off-by: Pavel Machek
Reviewed-by: Sebastian Reichel
-- Sebastian
>
> diff --git
On Tue, Jan 02, 2018 at 01:00:03PM -0600, Bjorn Helgaas wrote:
> [+cc Greg, linux-kernel]
>
> Hi Max,
>
> Thanks for the report!
>
> On Tue, Jan 02, 2018 at 01:50:23AM +0200, Max Gurtovoy wrote:
> > hi all,
> > I encountered a strange phenomena using 2 different pci drivers
> > (nvme and
Hi,
On Tue, Jan 02, 2018 at 01:59:48PM +0100, Pavel Machek wrote:
>
> This adds support for volume up/down keys in the dts.
>
> Signed-off-by: Pavel Machek
Reviewed-by: Sebastian Reichel
-- Sebastian
>
> diff --git a/arch/arm/boot/dts/omap3-n9.dts b/arch/arm/boot/dts/omap3-n9.dts
> index
Quoting Rodrigo Vivi (2018-01-02 19:21:08)
> On Sat, Dec 30, 2017 at 12:53:58PM +, Jiri Kosina wrote:
> > On Sat, 30 Dec 2017, Jiri Kosina wrote:
> >
> > > Seems like disabling RC6 on the kernel command line works this around,
> > > and
> > > I can dock / undock several times in a row with
Quoting Rodrigo Vivi (2018-01-02 19:21:08)
> On Sat, Dec 30, 2017 at 12:53:58PM +, Jiri Kosina wrote:
> > On Sat, 30 Dec 2017, Jiri Kosina wrote:
> >
> > > Seems like disabling RC6 on the kernel command line works this around,
> > > and
> > > I can dock / undock several times in a row with
Hi Martin,
On Tue, Jan 2, 2018 at 2:15 PM, Martin Kaiser wrote:
> Fabio, could you post the output of
>
> cat /sys/kernel/debug/suspend_stats
>
> after supend failed, to confirm that we're failing below
> device_suspend_noirq()?
Here it goes:
# cat
Hi Martin,
On Tue, Jan 2, 2018 at 2:15 PM, Martin Kaiser wrote:
> Fabio, could you post the output of
>
> cat /sys/kernel/debug/suspend_stats
>
> after supend failed, to confirm that we're failing below
> device_suspend_noirq()?
Here it goes:
# cat /sys/kernel/debug/suspend_stats
success: 0
On Tue, 2 Jan 2018 11:08:00 -0800
Tim Tianyang Chen wrote:
> Hi Steve, did your mailer find all the patches? I made sure they all
> reply to the same mail ID this time.
>
Yes, sorry due to end of year work, these were put on the back burner.
I'll see if I can get to
On Tue, 2 Jan 2018 11:08:00 -0800
Tim Tianyang Chen wrote:
> Hi Steve, did your mailer find all the patches? I made sure they all
> reply to the same mail ID this time.
>
Yes, sorry due to end of year work, these were put on the back burner.
I'll see if I can get to them sometime this week.
From: Masami Hiramatsu
Date: Fri, 29 Dec 2017 11:45:20 +0900
> This series is v7 of the replacement of jprobe usage with trace
> events. This version fixes net/dccp/trace.h to avoid sparse
> warning. Since the TP_STORE_ADDR_PORTS macro can be shared
> with
From: Masami Hiramatsu
Date: Fri, 29 Dec 2017 11:45:20 +0900
> This series is v7 of the replacement of jprobe usage with trace
> events. This version fixes net/dccp/trace.h to avoid sparse
> warning. Since the TP_STORE_ADDR_PORTS macro can be shared
> with trace/events/tcp.h, it also introduce a
This patch allows root to reserve some blocks via mount option.
"-o reserve_root=N" means N x 4KB-sized blocks for root only.
Signed-off-by: Jaegeuk Kim
---
Change log from v3:
- fix 0.2% calculation
- preserve reserve_root=%u from remount_fs
fs/f2fs/f2fs.h | 26
This patch allows root to reserve some blocks via mount option.
"-o reserve_root=N" means N x 4KB-sized blocks for root only.
Signed-off-by: Jaegeuk Kim
---
Change log from v3:
- fix 0.2% calculation
- preserve reserve_root=%u from remount_fs
fs/f2fs/f2fs.h | 26 ++
On 01/02, Chao Yu wrote:
> On 2018/1/1 9:29, Jaegeuk Kim wrote:
> > This patch allows root to reserve some blocks via mount option.
> >
> > "-o reserve_root=N" means N x 4KB-sized blocks for root only.
> >
> > Signed-off-by: Jaegeuk Kim
> > ---
> >
> > Change log from v2:
>
On 01/02, Chao Yu wrote:
> On 2018/1/1 9:29, Jaegeuk Kim wrote:
> > This patch allows root to reserve some blocks via mount option.
> >
> > "-o reserve_root=N" means N x 4KB-sized blocks for root only.
> >
> > Signed-off-by: Jaegeuk Kim
> > ---
> >
> > Change log from v2:
> > - wrong
Quoting Rodrigo Vivi (2018-01-02 19:12:18)
> On Sun, Dec 31, 2017 at 10:34:54PM +, Stefan Brüns wrote:
> > + edid = drm_get_edid(connector, i2c);
> > +
> > + if (!edid && !intel_gmbus_is_forced_bit(i2c)) {
> > + DRM_DEBUG_KMS("HDMI GMBUS EDID read failed, retry using GPIO
Quoting Rodrigo Vivi (2018-01-02 19:12:18)
> On Sun, Dec 31, 2017 at 10:34:54PM +, Stefan Brüns wrote:
> > + edid = drm_get_edid(connector, i2c);
> > +
> > + if (!edid && !intel_gmbus_is_forced_bit(i2c)) {
> > + DRM_DEBUG_KMS("HDMI GMBUS EDID read failed, retry using GPIO
On Mon, Jan 01, 2018 at 11:10:56PM +0100, Borislav Petkov wrote:
> On Mon, Jan 01, 2018 at 10:04:47AM +0800, Jia Zhang wrote:
>
> Ok, I went and massaged your version, here's what I committed:
>
> Signed-off-by: Jia Zhang
> Acked-by: Tony Luck
>
On Mon, Jan 01, 2018 at 11:10:56PM +0100, Borislav Petkov wrote:
> On Mon, Jan 01, 2018 at 10:04:47AM +0800, Jia Zhang wrote:
>
> Ok, I went and massaged your version, here's what I committed:
>
> Signed-off-by: Jia Zhang
> Acked-by: Tony Luck
> Cc: x86-ml
> Link:
>
On Friday 10 November 2017 00:38:22 Pali Rohár wrote:
> This patch series fix processing MAC address for wl1251 chip found in Nokia
> N900.
>
> Changes since v1:
> * Added Acked-by for Pavel Machek
> * Fixed grammar
> * Magic numbers for NVS offsets are replaced by defines
> * Check for validity
On Friday 10 November 2017 00:38:22 Pali Rohár wrote:
> This patch series fix processing MAC address for wl1251 chip found in Nokia
> N900.
>
> Changes since v1:
> * Added Acked-by for Pavel Machek
> * Fixed grammar
> * Magic numbers for NVS offsets are replaced by defines
> * Check for validity
On 01/02, Geert Uytterhoeven wrote:
> When exposing data access through debugfs, the correct
> debugfs_create_*() functions must be used, depending on data type.
>
> Remove all casts from data pointers passed to debugfs_create_*()
> functions, as such casts prevent the compiler from flagging
On 01/02, Geert Uytterhoeven wrote:
> When exposing data access through debugfs, the correct
> debugfs_create_*() functions must be used, depending on data type.
>
> Remove all casts from data pointers passed to debugfs_create_*()
> functions, as such casts prevent the compiler from flagging
On Sat, Dec 30, 2017 at 12:53:58PM +, Jiri Kosina wrote:
> On Sat, 30 Dec 2017, Jiri Kosina wrote:
>
> > Seems like disabling RC6 on the kernel command line works this around, and
> > I can dock / undock several times in a row with the image always coming
> > up properly on the external
On Sat, Dec 30, 2017 at 12:53:58PM +, Jiri Kosina wrote:
> On Sat, 30 Dec 2017, Jiri Kosina wrote:
>
> > Seems like disabling RC6 on the kernel command line works this around, and
> > I can dock / undock several times in a row with the image always coming
> > up properly on the external
On Tue, 2018-01-02 at 11:22 +0100, Ludovic Desroches wrote:
> On Wed, Dec 27, 2017 at 10:40:00PM +0100, Cyrille Pitchen wrote:
>
> > Or maybe no change at all is required at the at_xdmac.c driver side: we
> > just don't care about the provided flags in the "dmas" property, especially
> > the
On Tue, 2018-01-02 at 11:22 +0100, Ludovic Desroches wrote:
> On Wed, Dec 27, 2017 at 10:40:00PM +0100, Cyrille Pitchen wrote:
>
> > Or maybe no change at all is required at the at_xdmac.c driver side: we
> > just don't care about the provided flags in the "dmas" property, especially
> > the
On Fri, Dec 29, 2017 at 09:21:56PM +0100, Cyrille Pitchen wrote:
> Hi Bjorn,
>
> Le 28/12/2017 à 23:47, Bjorn Helgaas a écrit :
> > On Mon, Dec 18, 2017 at 07:16:01PM +0100, Cyrille Pitchen wrote:
> >> This patch cleans drivers/Makefile up by moving the pci/endpoint and
> >> pci/dwc entries from
On Fri, Dec 29, 2017 at 09:21:56PM +0100, Cyrille Pitchen wrote:
> Hi Bjorn,
>
> Le 28/12/2017 à 23:47, Bjorn Helgaas a écrit :
> > On Mon, Dec 18, 2017 at 07:16:01PM +0100, Cyrille Pitchen wrote:
> >> This patch cleans drivers/Makefile up by moving the pci/endpoint and
> >> pci/dwc entries from
On Tuesday, January 2, 2018 2:04:04 PM CET Lukas Wunner wrote:
> On Tue, Jan 02, 2018 at 12:02:18PM +0100, Rafael J. Wysocki wrote:
> > On Tue, Jan 2, 2018 at 11:51 AM, Lukas Wunner wrote:
> > > On Tue, Jan 02, 2018 at 01:56:28AM +0100, Rafael J. Wysocki wrote:
> > >> + if
On Tuesday, January 2, 2018 2:04:04 PM CET Lukas Wunner wrote:
> On Tue, Jan 02, 2018 at 12:02:18PM +0100, Rafael J. Wysocki wrote:
> > On Tue, Jan 2, 2018 at 11:51 AM, Lukas Wunner wrote:
> > > On Tue, Jan 02, 2018 at 01:56:28AM +0100, Rafael J. Wysocki wrote:
> > >> + if
On 01/01, Paul Cercueil wrote:
> diff --git a/drivers/clk/ingenic/tcu.c b/drivers/clk/ingenic/tcu.c
> new file mode 100644
> index ..36afe3f02f91
> --- /dev/null
> +++ b/drivers/clk/ingenic/tcu.c
> @@ -0,0 +1,336 @@
> +// SPDX-License-Identifier: GPL-2.0
> +/*
> + * Ingenic JZ47xx SoC
On 01/01, Paul Cercueil wrote:
> diff --git a/drivers/clk/ingenic/tcu.c b/drivers/clk/ingenic/tcu.c
> new file mode 100644
> index ..36afe3f02f91
> --- /dev/null
> +++ b/drivers/clk/ingenic/tcu.c
> @@ -0,0 +1,336 @@
> +// SPDX-License-Identifier: GPL-2.0
> +/*
> + * Ingenic JZ47xx SoC
From: Neal Cardwell
Date: Tue, 2 Jan 2018 14:11:25 -0500
> Looks like these 2 patches will cherry-pick cleanly if cherry-picked
> in the following sequence, on top of 4.9.74-rc1, which already has
> 6c9e73ef9aa7 ("tcp_bbr: record "full bw reached" decision in new
>
From: Neal Cardwell
Date: Tue, 2 Jan 2018 14:11:25 -0500
> Looks like these 2 patches will cherry-pick cleanly if cherry-picked
> in the following sequence, on top of 4.9.74-rc1, which already has
> 6c9e73ef9aa7 ("tcp_bbr: record "full bw reached" decision in new
> full_bw_reached bit"):
>
> $
On Sun, Dec 31, 2017 at 10:34:54PM +, Stefan Brüns wrote:
> The ACK/NACK implementation as found in e.g. the G965 has the falling
> clock edge and the release of the data line after the ACK for the received
> byte happen at the same time.
>
> This is conformant with the I2C specification,
On Sun, Dec 31, 2017 at 10:34:54PM +, Stefan Brüns wrote:
> The ACK/NACK implementation as found in e.g. the G965 has the falling
> clock edge and the release of the data line after the ACK for the received
> byte happen at the same time.
>
> This is conformant with the I2C specification,
On Tue, Jan 2, 2018 at 1:32 PM, David Miller wrote:
> From: Neal Cardwell
> Date: Tue, 2 Jan 2018 11:57:59 -0500
>
>> On Mon, Jan 1, 2018 at 9:31 AM, Greg Kroah-Hartman
>> wrote:
>>> This is the start of the stable review
On Tue, Jan 2, 2018 at 1:32 PM, David Miller wrote:
> From: Neal Cardwell
> Date: Tue, 2 Jan 2018 11:57:59 -0500
>
>> On Mon, Jan 1, 2018 at 9:31 AM, Greg Kroah-Hartman
>> wrote:
>>> This is the start of the stable review cycle for the 4.9.74 release.
>>> There are 75 patches in this series,
Hello, Ingo, and Happy New Year!
This pull request contains the following changes:
1. Updates to use cond_resched() instead of cond_resched_rcu_qs()
where feasible (currently everywhere except in kernel/rcu and
in kernel/torture.c). Also a couple of fixes to avoid sending
Hello, Ingo, and Happy New Year!
This pull request contains the following changes:
1. Updates to use cond_resched() instead of cond_resched_rcu_qs()
where feasible (currently everywhere except in kernel/rcu and
in kernel/torture.c). Also a couple of fixes to avoid sending
Hi Steve, did your mailer find all the patches? I made sure they all
reply to the same mail ID this time.
Thanks,
Tim
On 12/15/2017 03:20 PM, Tim Tianyang Chen wrote:
This patch set will let users define a mailer, an email address and when to
receive
notifications during automated testings.
Hi Steve, did your mailer find all the patches? I made sure they all
reply to the same mail ID this time.
Thanks,
Tim
On 12/15/2017 03:20 PM, Tim Tianyang Chen wrote:
This patch set will let users define a mailer, an email address and when to
receive
notifications during automated testings.
On 1/2/2018 2:02 PM, Bjorn Helgaas wrote:
> I read that as suggesting that we should enable DPC support in Linux
> if and only if we also enable AER. But I don't see anything in DPC
> that looks like that. Should there be something there? Should DPC be
> restructured so it's enabled and handled
On 1/2/2018 2:02 PM, Bjorn Helgaas wrote:
> I read that as suggesting that we should enable DPC support in Linux
> if and only if we also enable AER. But I don't see anything in DPC
> that looks like that. Should there be something there? Should DPC be
> restructured so it's enabled and handled
On Tue, Jan 02, 2018 at 01:02:15PM -0600, Bjorn Helgaas wrote:
> On Fri, Dec 29, 2017 at 12:54:15PM +0530, Oza Pawandeep wrote:
> > This patch set brings in support for DPC and AER to co-exist and not to
> > race for recovery.
> >
> > The current implementation of AER and error message
On Tue, Jan 02, 2018 at 01:02:15PM -0600, Bjorn Helgaas wrote:
> On Fri, Dec 29, 2017 at 12:54:15PM +0530, Oza Pawandeep wrote:
> > This patch set brings in support for DPC and AER to co-exist and not to
> > race for recovery.
> >
> > The current implementation of AER and error message
On Tue, 2018-01-02 at 17:50 +0100, Jan Kara wrote:
> On Fri 22-12-17 07:05:53, Jeff Layton wrote:
> > From: Jeff Layton
> >
> > We only really need to update i_version if someone has queried for it
> > since we last incremented it. By doing that, we can avoid having to
> >
On Tue, 2018-01-02 at 17:50 +0100, Jan Kara wrote:
> On Fri 22-12-17 07:05:53, Jeff Layton wrote:
> > From: Jeff Layton
> >
> > We only really need to update i_version if someone has queried for it
> > since we last incremented it. By doing that, we can avoid having to
> > update the inode if
On Fri, Dec 29, 2017 at 12:54:15PM +0530, Oza Pawandeep wrote:
> This patch set brings in support for DPC and AER to co-exist and not to
> race for recovery.
>
> The current implementation of AER and error message broadcasting to the
> EP driver is tightly coupled and limited to AER service
On Fri, Dec 29, 2017 at 12:54:15PM +0530, Oza Pawandeep wrote:
> This patch set brings in support for DPC and AER to co-exist and not to
> race for recovery.
>
> The current implementation of AER and error message broadcasting to the
> EP driver is tightly coupled and limited to AER service
On 12/31, Bryan O'Donoghue wrote:
> On 30/12/17 16:36, Mikko Perttunen wrote:
> >FWIW, we had this problem some years ago with the Tegra CPU clock
> >- then it was determined that a simpler solution was to have the
> >determine_rate callback support unsigned long rates - so clock
> >drivers that
On 12/31, Bryan O'Donoghue wrote:
> On 30/12/17 16:36, Mikko Perttunen wrote:
> >FWIW, we had this problem some years ago with the Tegra CPU clock
> >- then it was determined that a simpler solution was to have the
> >determine_rate callback support unsigned long rates - so clock
> >drivers that
On alpha, a process will crash if it attempts to start a thread and a
signal is delivered at the same time. The crash can be reproduced with
this program: https://cygwin.com/ml/cygwin/2014-11/msg00473.html
The reason for the crash is this:
* we call the clone syscall
* we go to the function
On alpha, a process will crash if it attempts to start a thread and a
signal is delivered at the same time. The crash can be reproduced with
this program: https://cygwin.com/ml/cygwin/2014-11/msg00473.html
The reason for the crash is this:
* we call the clone syscall
* we go to the function
[+cc Greg, linux-kernel]
Hi Max,
Thanks for the report!
On Tue, Jan 02, 2018 at 01:50:23AM +0200, Max Gurtovoy wrote:
> hi all,
> I encountered a strange phenomena using 2 different pci drivers
> (nvme and mlx5_core) since 4.15-rc1:
> when I try to unload the modules using "modprobe -r" cmd it
[+cc Greg, linux-kernel]
Hi Max,
Thanks for the report!
On Tue, Jan 02, 2018 at 01:50:23AM +0200, Max Gurtovoy wrote:
> hi all,
> I encountered a strange phenomena using 2 different pci drivers
> (nvme and mlx5_core) since 4.15-rc1:
> when I try to unload the modules using "modprobe -r" cmd it
Hi Wang,
I just updated my machine to Fedora 27 and 4.15.0-rc6 and the
only test failing for me is:
[root@jouet linux]# perf test bpf
39: BPF filter:
39.1: Basic BPF filtering : FAILED!
39.2: BPF pinning
Hi Wang,
I just updated my machine to Fedora 27 and 4.15.0-rc6 and the
only test failing for me is:
[root@jouet linux]# perf test bpf
39: BPF filter:
39.1: Basic BPF filtering : FAILED!
39.2: BPF pinning
501 - 600 of 1720 matches
Mail list logo