On Mon, Apr 16, 2018 at 02:26:53PM -0400, Steven Rostedt wrote:
>On Mon, 16 Apr 2018 17:42:38 +
>Sasha Levin wrote:
>> Also note that all of these patches were tagged for stable and actually
>> ended up in at least one tree.
>>
>> This is why I'm basing a lot of my decision making on the rejec
On Mon, 16 Apr 2018 18:17:17 +
Sasha Levin wrote:
> I thought we agreed that this is bad? We wanted users to be closer to
> mainline, and we can't do it without bringing -stable closer to mainline
> as well.
I guess the question comes down to, what do the users of stable kernels
want? For my
- On Apr 14, 2018, at 6:44 PM, Andy Lutomirski l...@amacapital.net wrote:
> On Thu, Apr 12, 2018 at 12:43 PM, Linus Torvalds
> wrote:
>> On Thu, Apr 12, 2018 at 12:27 PM, Mathieu Desnoyers
>> wrote:
>>> The cpu_opv system call executes a vector of operations on behalf of
>>> user-space on a
On Mon, Apr 16, 2018 at 11:15 AM, Linus Torvalds
wrote:
>
> Ingo/Thomas: I will be just taking this directly, since it's so
> trivial and obvious and I got cc'd on the discussion.
.. and I also verified that it actually fixes the problem Shuah
reported. Not that there really was any question abou
Quoting Anson Huang (2018-03-18 19:30:44)
> i.MX6SX has lvds2 (analog clock2), an I/O clock like lvds1.
> And this lvds2, along with lvds1, can be used to provide
> external clock source to the internal pll, such as pll4_audio
> and pll5_video.
>
> This patch mainly adds the lvds2 to the clock tre
Use new return type vm_fault_t for fault handler
in struct vm_operations_struct. For now, this is
just documenting that the function returns a VM_
FAULT value rather than an errno. Once all inst
ances are converted, vm_fault_t will become a di
stinct type.
Reference - 1c8f422059ae ("mm: change re
On Mon, Apr 16, 2018 at 11:26 AM, Steven Rostedt wrote:
>
> The problem is that it only fixed a critical bug, but didn't go far
> enough to keep the bug fix from breaking API.
An API breakage that gets noticed *is* a crtitical bug.
You can't call something else critical and then say "but it brok
On Fri, Apr 6, 2018 at 7:22 AM, Alexander Popov wrote:
> This commit introduces the architecture-specific code filling the used
> part of the kernel stack with a poison value before returning to the
> userspace. Full STACKLEAK feature also contains the gcc plugin which
> comes in a separate commit
Update my e-mail address to a working address.
Signed-off-by: Christoffer Dall
---
MAINTAINERS | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 0a1410d5a621..3e9c99d2620b 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -7738,7 +7738,7 @@ F:
On Sun, Apr 15, 2018 at 3:34 PM, Al Viro wrote:
> On Sun, Apr 15, 2018 at 10:54:55PM +0100, Al Viro wrote:
>> On Sun, Apr 15, 2018 at 09:40:54PM +0100, Al Viro wrote:
>>
>> > BTW, the current placement of cond_resched() looks bogus; suppose we
>> > have collected a lot of victims and ran into need
On Mon, 16 Apr 2018 17:42:38 +
Sasha Levin wrote:
> >> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit?id=a918d2bcea6aab6e671bfb0901cbecc3cf68fca1
> >>
> >
> >Sure. Even if it has a subtle regression, that's a critical bug being
> >fixed.
>
> This was late
The values of bclk and fsync are inverted WRT the codec. But the existing
solution already works for Broadwell, see the alsa-lib config:
`alsa-lib/src/conf/topology/broadwell/broadwell.conf`
This commit provides the backwards-compatible solution to fix this misuse.
This commit goes in pair with t
Clock gating parameter is a part of `dai_fmt`. It is supported by
`alsa-lib` when creating a topology binary file, but ignored by kernel
when loading this topology file.
After applying this commit, the clock gating parameter is not ignored any
more. This solution is backwards compatible. The exist
The patch
spi: zynqmp: Add pm runtime support
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 during
On 16.04.2018 18:08, Stephen Warren wrote:
> On 04/16/2018 09:56 AM, Stefan Agner wrote:
>> On 27.03.2018 14:16, Dmitry Osipenko wrote:
>>> On 27.03.2018 14:54, Robin Murphy wrote:
On 26/03/18 22:20, Dmitry Osipenko wrote:
> On 25.03.2018 21:09, Stefan Agner wrote:
>> As documented in
On Wed, Apr 04, 2018 at 01:51:47PM +0200, Bartosz Golaszewski wrote:
> We want to work towards phasing out the at24_platform_data structure.
> There are few users and its contents can be represented using generic
> device properties. Using device properties only will allow us to
> significantly sim
On Mon, Apr 16, 2018 at 8:56 PM, Greg KH wrote:
> On Mon, Apr 16, 2018 at 08:24:40PM +0530, Souptick Joarder wrote:
>> Use new return type vm_fault_t for fault handler
>> in struct vm_operations_struct. For now, this is
>> just documenting that the function returns a
>> VM_FAULT value rather than
On Wed, Apr 11, 2018 at 11:47:01AM +0200, Amelie Delaunay wrote:
> This patch adds documentation of device tree bindings for the
> STMicroelectronics Multi-Function eXpander (STMFX) GPIO expander.
>
> Signed-off-by: Amelie Delaunay
> ---
> .../devicetree/bindings/pinctrl/pinctrl-stmfx.txt | 118
On Mon, Apr 16, 2018 at 01:44:23PM -0400, Steven Rostedt wrote:
>On Mon, 16 Apr 2018 17:16:10 +
>Sasha Levin wrote:
>
>
>> So if a user is operating a nuclear power plant, and has 2 leds: green
>> one that says "All OK!" and a red one saying "NUCLEAR MELTDOWN!", and
>> once in a blue moon a ra
On Mon, Apr 16, 2018 at 11:04 AM, Linus Torvalds
wrote:
>
> I was going through the bisection, with just a couple more rounds to
> go, but I guess I don't even need it.
Ingo/Thomas: I will be just taking this directly, since it's so
trivial and obvious and I got cc'd on the discussion.
On Mon, Apr 16, 2018 at 08:11:26PM +0200, Krzysztof Kozlowski wrote:
> The PMU node is the actual block responsible for power management,
> including typical Exynos on/off/restart procedures. Therefore the
> syscon poweroff and restart nodes logically belong to it.
>
> Signed-off-by: Krzysztof Ko
On Tue, Apr 10, 2018 at 11:32:09AM -0700, Jae Hyun Yoo wrote:
> This commit adds dt-bindings documents for PECI cputemp and dimmtemp client
> drivers.
"dt-bindings: hwmon: ..." for the subject.
>
> Signed-off-by: Jae Hyun Yoo
> Reviewed-by: Haiyue Wang
> Reviewed-by: James Feist
> Reviewed-by
On Mon, Apr 16, 2018 at 08:11:25PM +0200, Krzysztof Kozlowski wrote:
> The PMU node is the actual block responsible for power management,
> including typical Exynos on/off/restart procedures. Therefore the
> syscon poweroff and restart nodes logically belong to it.
>
> Signed-off-by: Krzysztof Ko
The PMU node is the actual block responsible for power management,
including typical Exynos on/off/restart procedures. Therefore the
syscon poweroff and restart nodes logically belong to it.
Signed-off-by: Krzysztof Kozlowski
---
Previously was "Fix missing missing reg warning for syscon resta
The PMU node is the actual block responsible for power management,
including typical Exynos on/off/restart procedures. Therefore the
syscon poweroff and restart nodes logically belong to it.
Signed-off-by: Krzysztof Kozlowski
---
Previously was "Fix missing missing reg warning for syscon resta
On Tue, Apr 10, 2018 at 11:32:06AM -0700, Jae Hyun Yoo wrote:
> This commit adds a dt-bindings document of PECI adapter driver for Aspeed
> AST24xx/25xx SoCs.
>
> Signed-off-by: Jae Hyun Yoo
> Reviewed-by: Haiyue Wang
> Reviewed-by: James Feist
> Reviewed-by: Vernon Mauery
> Cc: Alan Cox
> Cc
On Monday, April 16, 2018 10:11:01 AM EDT Richard Guy Briggs wrote:
> On 2018-04-16 09:26, Ondrej Mosnacek wrote:
> > 2018-04-10 1:34 GMT+02:00 Richard Guy Briggs :
> > > There were two formats of the audit MAC_STATUS record, one of which was
> > > more standard than the other. One listed enforcin
On Sun, 15 Apr 2018 18:55:38 -0700
Linus Torvalds wrote:
> End result: we actually removed more lines than we added:
>
> 13538 files changed, 627723 insertions(+), 818855 deletions(-)
>
> which is probably a first. Ever. In the history of the universe. Or at
> least kernel releases.
For the c
On Mon, Apr 16, 2018 at 10:58 AM, Dave Hansen
wrote:
>
> Joerg just found and fixed something that would be poked by the x86
> selftests:
>
> https://lkml.org/lkml/2018/4/16/230
Yup.
And that silly bug explains the all-ones PTE.
I was going through the bisection, with just a couple more rounds
On Sat, Apr 14, 2018 at 03:21:53PM +0530, Vignesh R wrote:
> From: Grygorii Strashko
>
> Prevent system suspend while user has finger on touch screen,
> because TSC is wakeup source and suspending device while in use will
> result in failure to disable the module.
> This patch uses pm_stay_awake(
On 2018-04-16 10:55, Kees Cook wrote:
> On Wed, Mar 21, 2018 at 1:42 AM, Richard Guy Briggs wrote:
> > In commit 45b578fe4c3cade6f4ca1fc934ce199afd857edc
> > ("audit: link denied should not directly generate PATH record")
> > the need for the struct path *link parameter was removed.
> > Remove the
On 04/16/2018 10:56 AM, Linus Torvalds wrote:
> On Mon, Apr 16, 2018 at 10:43 AM, Linus Torvalds
> wrote:
>>
>> I don't see *why* it would be badly set up, and that test works fine
>> for me, though.
>
> AHHAH!
>
> I'm wrong. I can see it too. My desktop was running 18b7fd1c93e5 (my
> kernel fro
On 04/16/18 08:24, Joerg Roedel wrote:
> Hi,
>
> here is the 5th iteration of my PTI enablement patches for
> x86-32. There are no real changes between v4 and v5 besides
> that I rebased the whole patch-set to v4.17-rc1 and resolved
> the numerous conflicts that this caused.
>
Please don't use t
On Tue, Apr 10, 2018 at 11:32:03AM -0700, Jae Hyun Yoo wrote:
> This commit adds documents of generic PECI bus, adapter and client drivers.
"dt-bindings: ..." for the subject prefix please.
>
> Signed-off-by: Jae Hyun Yoo
> Reviewed-by: Haiyue Wang
> Reviewed-by: James Feist
> Reviewed-by: Ve
On Sat, Apr 14, 2018 at 03:21:52PM +0530, Vignesh R wrote:
> From: Grygorii Strashko
>
> It is seen that just enabling the TSC module triggers a HW_PEN IRQ
> without any interaction with touchscreen by user. This results in first
> suspend/resume sequence to fail as system immediately wakes up fr
From: Salvatore Mesoraca
Disallows open of FIFOs or regular files not owned by the user in world
writable sticky directories, unless the owner is the same as that of the
directory or the file is opened without the O_CREAT flag. The purpose
is to make data spoofing attacks harder. This protection
Hi Segei,
On 04/14/2018 01:35 AM, Sergei Shtylyov wrote:
Please indent with tabs (as above and below), not spaces.
Thanks for the comments. I will fix it in v2.
--
Sathyanarayanan Kuppuswamy
Linux kernel developer
Add the possibility to apply and query the clock signal duty cycle ratio.
This is useful when the duty cycle of the clock signal depends on some
other parameters controlled by the clock framework.
Signed-off-by: Jerome Brunet
---
drivers/clk/clk.c| 196 +++
A clock gate does not resample the clock signal, it give the same
signal as the parent if enabled, so it can use the duty cycle
passthrough operations
Signed-off-by: Jerome Brunet
---
drivers/clk/clk-gate.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/clk/clk-gate.c b/drivers/cl
This patchset adds the possibility to control the duty cycle ratio of a
clock within the clock framework.
This useful when the duty cycle ratio depends on another parameter
controlled by the clock framework. For example, the duty cycle ratio may
depends on the value of a divider (ratio = N / div).
A clock mux does not resample the clock signal, it give the same
signal as the selected parent, so it can use the duty cycle
passthrough operations.
Signed-off-by: Jerome Brunet
---
drivers/clk/clk-mux.c | 4
1 file changed, 4 insertions(+)
diff --git a/drivers/clk/clk-mux.c b/drivers/clk/
This improves the coding style of this piece of code.
Signed-off-by: Kirill Marinushkin
Cc: Mark Brown
Cc: Pierre-Louis Bossart
Cc: Jaroslav Kysela
Cc: Takashi Iwai
Cc: Pan Xiuli
Cc: Liam Girdwood
Cc: linux-kernel@vger.kernel.org
Cc: alsa-de...@alsa-project.org
---
sound/soc/soc-topology.c
On Mon, Apr 16, 2018 at 10:43 AM, Linus Torvalds
wrote:
>
> I don't see *why* it would be badly set up, and that test works fine
> for me, though.
AHHAH!
I'm wrong. I can see it too. My desktop was running 18b7fd1c93e5 (my
kernel from Saturday, I hadn't rebooted it since), but I had 4.17-rc1
in
On Wed, Mar 21, 2018 at 1:42 AM, Richard Guy Briggs wrote:
> In commit 45b578fe4c3cade6f4ca1fc934ce199afd857edc
> ("audit: link denied should not directly generate PATH record")
> the need for the struct path *link parameter was removed.
> Remove the now useless struct path argument.
>
> Signed-of
From: Ahsan Hussain
Upstream commit 8d008c0c ("hwmon: (ina2xx) Make calibration register
value fixed"), makes ina2xx_set_shunt() call mutex_lock on an
un-initialized mutex. Initialize it prior so we don't get a NULL pointer
dereference error.
Fixes: 8d008c0c ("hwmon: (ina2xx) Make calibration re
On Mon, Apr 16, 2018 at 10:48:03PM +0500, Ahsan Hussain wrote:
>
>
> On 04/16/2018 10:28 PM, Guenter Roeck wrote:
> > On Mon, Apr 16, 2018 at 10:08:19PM +0500, Ahsan Hussain wrote:
> >>
> >> Upstream commit
> >>
> >> 8d008c0c ("hwmon: (ina2xx) Make calibration register value fixed")
> >>
> > This
On 04/16/2018 10:28 PM, Guenter Roeck wrote:
> On Mon, Apr 16, 2018 at 10:08:19PM +0500, Ahsan Hussain wrote:
>>
>> Upstream commit
>>
>> 8d008c0c ("hwmon: (ina2xx) Make calibration register value fixed")
>>
> This doesn't have to be on separate lines; as written, it just causes
> confusion.
>
W
On Sat, Apr 14, 2018 at 03:21:51PM +0530, Vignesh R wrote:
> On AM335x, ti_am335x_tsc can wake up the system from suspend, mark the
> IRQ as wakeup capable, so that device irq is not disabled during system
> suspend.
>
> Signed-off-by: Vignesh R
> ---
>
> v2: No changes
>
> drivers/input/touch
On Mon, 16 Apr 2018 17:16:10 +
Sasha Levin wrote:
> So if a user is operating a nuclear power plant, and has 2 leds: green
> one that says "All OK!" and a red one saying "NUCLEAR MELTDOWN!", and
> once in a blue moon a race condition is causing the red one to go on and
> cause panic in the
From: Ryder Lee
Date: Mon, 16 Apr 2018 10:33:41 +0800
> The usage of of_device_get_match_data() reduce the code size a bit.
>
> Also, the only way to call mtk_probe() is to match an entry in
> of_mtk_match[], so match cannot be NULL.
>
> Signed-off-by: Ryder Lee
Applied to net-next.
On Mon, Apr 16, 2018 at 10:01 AM, Shuah Khan wrote:
>
> [ 884.496588] BUG: unable to handle kernel paging request at fe810030
This is the LDT remap area.
> [ 884.496614] Oops: 0009 [#1] SMP KASAN PTI
This is RSVD + P, so it's a system read access that got a protection
fault due to res
On Mon, Apr 16, 2018 at 01:33:21PM -0400, Steven Rostedt wrote:
>On Mon, 16 Apr 2018 17:09:38 +
>Sasha Levin wrote:
>
>> Let's play a "be the -stable maintainer" game. Would you take any
>> of the following commits?
>>
>> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/
On Mon, Apr 16, 2018 at 09:19:21AM +0200, Andrzej Hajda wrote:
>
> +CC: linux-input list and maintainer
>
>
> On 05.04.2018 11:49, Enric Balletbo i Serra wrote:
> > From: "Kristian H. Kristensen"
> >
> > To improve PSR exit latency, we speculatively start exiting when we
> > receive input event
Quoting Taniya Das (2018-04-13 19:36:40)
> Add RPMh clock device bindings for Qualcomm Technology Inc's SoCs. These
> devices would be used for communicating resource state requests to control
> the clocks managed by RPMh.
>
> Signed-off-by: Amit Nischal
Is Amit the author? Needs a "From: Amit .
Quoting Taniya Das (2018-04-13 19:36:41)
> Add the RPMh clock driver to control the RPMh managed clock resources on
> some of the Qualcomm Technologies, Inc. SoCs.
>
> Signed-off-by: David Collins
> Signed-off-by: Amit Nischal
Your signoff chain is very confused. The first signoff should match
On Thu, Apr 12 2018 at 05:14 -0600, Ulf Hansson wrote:
A caller of pm_genpd_init() that provides some states for the genpd via the
->states pointer in the struct generic_pm_domain, should also provide a
governor. This because it's the job of the governor to pick a state that
satisfies the constra
On Mon, 16 Apr 2018 17:09:38 +
Sasha Levin wrote:
> Let's play a "be the -stable maintainer" game. Would you take any
> of the following commits?
>
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit?id=fc90441e728aa461a8ed1cfede08b0b9efef43fb
No, not automatica
On Thu, Apr 12 2018 at 05:14 -0600, Ulf Hansson wrote:
Instead of returning -EINVAL from of_genpd_parse_idle_states() in case none
compatible states was found, let's return 0 to indicate success. Assign
also the out-parameter *states to NULL and *n to 0, to indicate to the
caller that zero states
On Mon, Apr 16, 2018 at 10:08:19PM +0500, Ahsan Hussain wrote:
>
> Upstream commit
>
> 8d008c0c ("hwmon: (ina2xx) Make calibration register value fixed")
>
This doesn't have to be on separate lines; as written, it just causes
confusion.
> makes ina2xx_set_shunt() call mutex_lock on an un-initia
The GPU subsystem node was a workaround to have a central device to
bind V3D and display to. Following the lead of 246774d17fc0
("drm/etnaviv: remove the need for a gpu-subsystem DT node"), remove
the subsystem node usage and just create a platform device for the DRM
device to attach to if any of
On Mon, 16 Apr 2018 13:58:00 -0300
Arnaldo Carvalho de Melo wrote:
> Em Mon, Apr 16, 2018 at 11:07:30AM -0500, Kim Phillips escreveu:
> > On Mon, 16 Apr 2018 10:51:25 -0300
> > Arnaldo Carvalho de Melo wrote:
> >
> > > Em Mon, Apr 16, 2018 at 11:23:45AM +0200, Jiri Olsa escreveu:
> > > > On Mon
On Mon, Apr 16, 2018 at 07:06:04PM +0200, Pavel Machek wrote:
>On Mon 2018-04-16 16:37:56, Sasha Levin wrote:
>> On Mon, Apr 16, 2018 at 12:30:19PM -0400, Steven Rostedt wrote:
>> >On Mon, 16 Apr 2018 16:19:14 +
>> >Sasha Levin wrote:
>> >
>> >> >Wait! What does that mean? What's the purpose o
Hi Rishabh,
+MODULE_DESCRIPTION("QTI sdm845 LLCC driver");
I think it should be QCOM or Qualcomm and not QTI
+
+ desc = devm_kzalloc(dev, sizeof(struct llcc_slice_desc), GFP_KERNEL);
Can use *desc instead
+struct llcc_slice_desc *llcc_slice_getd(struct device *dev, const char
*name
The patch
spi: stm32: Fix error handling in stm32_spi_probe()
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
On Mon, Apr 16, 2018 at 07:05:01PM +0200, Pavel Machek wrote:
>Hi!
>
>> How do you know if a bug bothers someone?
>>
>> If a user is annoyed by a LED issue, is he expected to triage the bug,
>> report it on LKML and patiently wait for the appropriate patch to be
>> backported?
>
>If the user is ann
The patch
ASoC: topology: Add definitions for mclk_direction values
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours)
The patch
ASoC: topology: Fix bclk and fsync inversion in set_link_hw_format()
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the nex
On Mon, 2018-04-16 at 09:22 -0700, Jim Mattson wrote:
> On Thu, Apr 12, 2018 at 8:12 AM, KarimAllah Ahmed wrote:
>
> >
> > v2 -> v3:
> > - Remove the forced VMExit from L2 after reading the kvm_state. The actual
> > problem is solved.
> > - Rebase again!
> > - Set nested_run_pending during res
On 2018-04-16 20:16, Sinan Kaya wrote:
On 4/15/2018 11:17 PM, Bjorn Helgaas wrote:
It doesn't seem right to me that we handle both ERR_NONFATAL and
ERR_FATAL events differently if we happen to have DPC support in a
switch.
Maybe we should consider triggering DPC only on ERR_FATAL? That would
k
The patch
ASoC: topology: Add missing clock gating parameter when parsing hw_configs
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in t
On Fri, Apr 13, 2018 at 4:08 PM wrote:
> On 2018-04-12 15:02, Evan Green wrote:
> > Hi Rishabh,
> >
> > On Tue, Apr 10, 2018 at 1:09 PM Rishabh Bhatnagar
> >
> > wrote:
> >
> >> LLCC (Last Level Cache Controller) provides additional cache memory
> >> in the system. LLCC is partitioned into multi
On 04/16/18 10:05, Bean Huo (beanhuo) wrote:
On Mon, 2018-04-16 at 09:41 -0700, Rajat Jain wrote:
On Mon, Apr 16, 2018 at 8:28 AM, Steven Rostedt
wrote:
On Mon, 16 Apr 2018 14:31:49 +
"Bean Huo (beanhuo)" wrote:
Print the request tag along with other information while tracing a
command
+++ Mathieu Malaterre [11/04/18 21:05 +0200]:
In commit 8c8ef42aee8f ("module: include other structures in module version
check"), the function `struct_module` was renamed to `module_layout` but no
prototype was added to `include/linux/module.h`. Remove warning triggered
at W=1:
kernel/module.c
On Mon, Apr 16, 2018 at 12:53:07PM -0400, Steven Rostedt wrote:
>On Mon, 16 Apr 2018 16:43:13 +
>Sasha Levin wrote:
>
>> >If you are worried about people not putting enough "Stable: " tags in
>> >their commits, perhaps you can write them emails "hey, I think this
>> >should go to stable, do yo
Upstream commit
8d008c0c ("hwmon: (ina2xx) Make calibration register value fixed")
makes ina2xx_set_shunt() call mutex_lock on an un-initialized mutex.
Initialize it prior so we don't get a NULL pointer dereference error
Signed-off-by: Ahsan Hussain
---
drivers/hwmon/ina2xx.c | 4 ++--
1 file
Hi, Bart
>On Mon, 2018-04-16 at 09:41 -0700, Rajat Jain wrote:
>> On Mon, Apr 16, 2018 at 8:28 AM, Steven Rostedt
>wrote:
>> > On Mon, 16 Apr 2018 14:31:49 +
>> > "Bean Huo (beanhuo)" wrote:
>> >
>> > > Print the request tag along with other information while tracing a
>> > > command.
>> > >
From: Zhu Yi
Add Rohm BU21029 resistive touch panel controller support with I2C
interface.
Signed-off-by: Zhu Yi
Signed-off-by: Mark Jonas
Reviewed-by: Heiko Schocher
---
Changes in v2:
- make ABS_PRESSURE proportionally rising with finger pressure
- fix race between interrupt and timer dur
On Mon 2018-04-16 16:37:56, Sasha Levin wrote:
> On Mon, Apr 16, 2018 at 12:30:19PM -0400, Steven Rostedt wrote:
> >On Mon, 16 Apr 2018 16:19:14 +
> >Sasha Levin wrote:
> >
> >> >Wait! What does that mean? What's the purpose of stable if it is as
> >> >broken as mainline?
> >>
> >> This just m
Hi!
> How do you know if a bug bothers someone?
>
> If a user is annoyed by a LED issue, is he expected to triage the bug,
> report it on LKML and patiently wait for the appropriate patch to be
> backported?
If the user is annoyed by a LED issue, you are actually expected to
tell him that it is
> Single-stepping is only a subset of the rseq limitations addressed
> by cpu_opv. Anoher major limitation is algorithms requiring data
> migration between per-cpu data structures safely against CPU hotplug,
> and without having to change the cpu affinity mask. This is the case
And how many people
Andy/Ingo,
While running test_vsyscall_64 and fsgsbase_64 tests, I am seeing
the following errors in dmesg.
Also these tests either take forever to run or hang. I killed it after
waiting for an hour or so. Unfortunately it makes the kselftest suite
pain to run. Could you please take a look and s
Hi!
> >> Let me ask my wife (who is happy using Linux as a regular desktop user)
> >> how comfortable she would be with triaging kernel bugs...
> >
> >That's really up to the distribution, not the main kernel stable. Does
> >she download and compile the kernels herself? Does she use LEDs?
> >
> >T
On Fri, Mar 30, 2018 at 11:41:23AM +0200, Arkadiusz Kwiatkowski wrote:
> This commit fixes the order of parameters passed to regmap_update_bits
> function inside spi-ti-qspi driver. Accidentally the code worked
> correctly when cs=0, but it is not the case for other values.
This doesn't apply agai
On Mon 2018-04-16 12:53:07, Steven Rostedt wrote:
> On Mon, 16 Apr 2018 16:43:13 +
> Sasha Levin wrote:
>
> > >If you are worried about people not putting enough "Stable: " tags in
> > >their commits, perhaps you can write them emails "hey, I think this
> > >should go to stable, do you agree"
From: Ingo Molnar
(cherry picked from commit d72f4e29e6d84b7ec02ae93088aa459ac70e733b)
firmware_restrict_branch_speculation_*() recently started using
preempt_enable()/disable(), but those are relatively high level
primitives and cause build failures on some 32-bit builds.
Since we want to keep
Em Mon, Apr 16, 2018 at 11:07:30AM -0500, Kim Phillips escreveu:
> On Mon, 16 Apr 2018 10:51:25 -0300
> Arnaldo Carvalho de Melo wrote:
>
> > Em Mon, Apr 16, 2018 at 11:23:45AM +0200, Jiri Olsa escreveu:
> > > On Mon, Apr 16, 2018 at 01:22:40PM +0900, Namhyung Kim wrote:
> > > > The map_groups__f
Em Mon, Apr 16, 2018 at 01:54:30PM -0300, Arnaldo Carvalho de Melo escreveu:
> Em Sun, Apr 15, 2018 at 11:23:50AM +0200, Jiri Olsa escreveu:
> > Return immediately when we find issue in the user
> > stack checks. The error value could get overwritten
> > by following check for PERF_SAMPLE_REGS_INTR
On Mon 2018-04-16 16:45:16, Sasha Levin wrote:
> On Mon, Apr 16, 2018 at 06:42:30PM +0200, Pavel Machek wrote:
> >On Mon 2018-04-16 16:39:20, Sasha Levin wrote:
> >> On Mon, Apr 16, 2018 at 06:28:50PM +0200, Pavel Machek wrote:
> >> >
> >> >> >> Is there a reason not to take LED fixes if they fix a
Em Sun, Apr 15, 2018 at 11:23:50AM +0200, Jiri Olsa escreveu:
> Return immediately when we find issue in the user
> stack checks. The error value could get overwritten
> by following check for PERF_SAMPLE_REGS_INTR.
>
> Signed-off-by: Jiri Olsa
Also, since you're sending this to syskaller-bugs,
On Mon, Apr 16, 2018 at 12:47:11PM -0400, Steven Rostedt wrote:
>On Mon, 16 Apr 2018 16:31:09 +
>Sasha Levin wrote:
>
>> On Mon, Apr 16, 2018 at 12:22:44PM -0400, Steven Rostedt wrote:
>> >On Mon, 16 Apr 2018 16:14:15 +
>> >Sasha Levin wrote:
>> >
>> >> Since the rate we're seeing now wit
On Mon, 16 Apr 2018 16:43:13 +
Sasha Levin wrote:
> >If you are worried about people not putting enough "Stable: " tags in
> >their commits, perhaps you can write them emails "hey, I think this
> >should go to stable, do you agree"? You should get people marking
> >their commits themselves pr
On Wed, Apr 04, 2018 at 06:19:38AM +0200, Kirill Marinushkin wrote:
> + /* clock gating */
> + if (hw_config->clock_gated == SND_SOC_TPLG_DAI_CLK_GATE_GATED)
> + link->dai_fmt |= SND_SOC_DAIFMT_GATED;
> + else if (hw_config->clock_gated ==
>
Em Sun, Apr 15, 2018 at 11:23:50AM +0200, Jiri Olsa escreveu:
> Return immediately when we find issue in the user
> stack checks. The error value could get overwritten
> by following check for PERF_SAMPLE_REGS_INTR.
Applied, together with a:
Cc: Stephane Eranian
Cc: Ingo Molnar
Fixes: 60e2364e6
On 04/16/2018 11:58 AM, Rafael J. Wysocki wrote:
> On Mon, Apr 16, 2018 at 5:31 PM, Joseph Salisbury
> wrote:
>> On 04/13/2018 05:34 PM, Rafael J. Wysocki wrote:
>>> On Fri, Apr 13, 2018 at 7:56 PM, Joseph Salisbury
>>> wrote:
Hi Rafael,
A kernel bug report was opened against Ubunt
On Mon, Apr 9, 2018 at 4:05 PM, Dan Williams wrote:
> On Mon, Apr 9, 2018 at 1:52 PM, Rob Herring wrote:
>> On Mon, Apr 9, 2018 at 2:46 AM, Oliver O'Halloran wrote:
>>> Some OF platforms (pseries and some SPARC systems) has their own
>>> implementations of NUMA affinity detection rather than usi
On Mon, 2018-04-16 at 09:41 -0700, Rajat Jain wrote:
> On Mon, Apr 16, 2018 at 8:28 AM, Steven Rostedt wrote:
> > On Mon, 16 Apr 2018 14:31:49 +
> > "Bean Huo (beanhuo)" wrote:
> >
> > > Print the request tag along with other information
> > > while tracing a command.
> > >
> > > Signed-off
On Mon, 16 Apr 2018 16:31:09 +
Sasha Levin wrote:
> On Mon, Apr 16, 2018 at 12:22:44PM -0400, Steven Rostedt wrote:
> >On Mon, 16 Apr 2018 16:14:15 +
> >Sasha Levin wrote:
> >
> >> Since the rate we're seeing now with AUTOSEL is similar to what we were
> >> seeing before AUTOSEL, what'
From: Hans Holmberg
This is a couple of bugfixes, nothing very urgent.
Hans Holmberg (2):
lightnvm: pblk: only try to recover lines with written smeta
lightnvm: pblk: kick writer on new flush points
drivers/lightnvm/pblk-cache.c| 10 ++
drivers/lightnvm/pblk-core.c | 2 +-
From: Hans Holmberg
When switching between different lun configurations, there is no
guarantee that all lines that contain closed/open chunks have some
valid data to recover.
Check that the smeta chunk has been written to instead. Also
skip bad lines (that does not have enough good chunks).
Sig
From: Hans Holmberg
Unless we kick the writer directly when setting a new flush point, the
user risks having to wait for up to one second (the default timeout for
the write thread to be kicked) for the IO to complete.
Signed-off-by: Hans Holmberg
---
drivers/lightnvm/pblk-cache.c | 10 ++--
401 - 500 of 1099 matches
Mail list logo
