Great news, that it works for you!
Thanks a lot!
Pavel
On 11/22/2017 03:49 AM, Stuart Hayes wrote:
My apologies... yes, your patch also fixes my issue. I was looking at the two
new places from which you were calling scsi_eh_wakeup(), and didn't notice that
you moved the spinlock in
Le 22/11/2017 à 00:07, Balbir Singh a écrit :
On Wed, Nov 22, 2017 at 1:28 AM, Christophe Leroy
wrote:
On powerpc32, patch_instruction() is called by apply_feature_fixups()
which is called from early_init()
There is the following note in front of early_init():
*
Reviewed-by: Keiji Hayashibara
Thanks.
-
Best Regards,
Keiji Hayashibara
> -Original Message-
> From: Kunihiko Hayashi [mailto:hayashi.kunih...@socionext.com]
> Sent: Wednesday, November 22, 2017 2:15 PM
> To: Srinivas Kandagatla
> > > On 10/20/2017 08:12 PM, alexander.stef...@infineon.com wrote:
> > > >> The TPM burstcount status indicates the number of bytes that can
> > > >> be sent to the TPM without causing bus wait states. Effectively,
> > > >> it is the number of empty bytes in the command FIFO.
> > > >>
> > > >>
On Wed, Nov 22, 2017 at 12:31:09AM -0500, Sinan Kaya wrote:
> pci_get_bus_and_slot() is restrictive such that it assumes domain=0 as
> where a PCI device is present. This restricts the device drivers to be
> reused for other domain numbers.
>
> Use pci_get_domain_bus_and_slot() with a domain
On Fri, Nov 17, 2017 at 02:33:04PM -0600, Tom Zanussi wrote:
> @@ -1387,6 +1405,8 @@ static struct trace_event_file *find_var_file(struct
> trace_array *tr,
> list_for_each_entry(var_data, >hist_vars, list) {
> var_hist_data = var_data->hist_data;
> file =
* Andy Lutomirski wrote:
> The cpu_entry_area will contain stacks. Make sure that KASAN has
> appropriate shadow mappings for them.
>
> Cc: Andrey Ryabinin
> Cc: Alexander Potapenko
> Cc: Dmitry Vyukov
> Cc:
* Ingo Molnar wrote:
>
> * Andy Lutomirski wrote:
>
> > This sets up stack switching, including for SYSCALL. I think it's
> > in decent shape.
> >
> > Known issues:
> > - I think we're going to want a way to turn the stack switching on and
> >off
tree: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git
rcu/dev
head: b151f93a71fc9fecb560e823a92402d882516483
commit: b151f93a71fc9fecb560e823a92402d882516483 [62/62] torture: Eliminate
torture_runnable
config: i386-randconfig-x001-201747 (attached as .config)
compiler:
tree: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git
rcu/dev
head: b151f93a71fc9fecb560e823a92402d882516483
commit: b151f93a71fc9fecb560e823a92402d882516483 [62/62] torture: Eliminate
torture_runnable
config: i386-randconfig-x008-201747 (attached as .config)
compiler:
* Andy Lutomirski wrote:
> This sets up stack switching, including for SYSCALL. I think it's
> in decent shape.
>
> Known issues:
> - I think we're going to want a way to turn the stack switching on and
>off either at boot time or at runtime. It should be fairly
Thanks Tobin, for your detailed comments.
On Wed, Nov 22, 2017 at 5:29 AM, Tobin C. Harding wrote:
> You don't typically need [xxx v1] for version 1, the v1 is implicit.
>
> Please use the git brief description prefix that is already in use i.e
>
> leaking_addresses: add
2017-11-22 14:14 GMT+09:00 Kunihiko Hayashi :
> The efuse on UniPhier allows 8bit access according to the specification.
> Since bit offset of nvmem is limited to 0-7, it is desiable to change
> access unit of nvmem to 8bit.
>
> Signed-off-by: Kunihiko Hayashi
Hi Tim,
On Thu, Nov 09, 2017 at 10:45:33AM -0800, Tim Harvey wrote:
> Cc: Rob Herring
> Signed-off-by: Tim Harvey
> ---
> v3:
> - fix typo
>
> v2:
> - add vendor prefix and remove _ from vidout-portcfg
> - remove _ from labels
> - remove
* Andy Lutomirski wrote:
> This sets up stack switching, including for SYSCALL. I think it's
> in decent shape.
>
> Known issues:
> - I think we're going to want a way to turn the stack switching on and
>off either at boot time or at runtime. It should be fairly
Hi,
I am trying to bring up suspend-to-disk (snapshot boot) on jetson-tx2
board (nvidia tegra186).
Suspend is working fine, but during boot with snapshot image, emmc
resume is failing.
Kernel version: 4.4
Repo: https://nv-tegra.nvidia.com/gitweb/?p=linux-4.4.git;a=summary
repo: tegra-l4t-r27.1
On 11/22/2017 2:31 PM, Ravi Bangoria wrote:
On 11/20/2017 08:13 PM, Jin Yao wrote:
@@ -76,6 +97,17 @@ static struct rb_node *saved_value_new(struct
rblist *rblist __maybe_unused,
return >rb_node;
}
+static void saved_value_delete(struct rblist *rblist __maybe_unused,
+
* Ian Abbott [2017-11-20 10:46:36 +]:
On 20/11/17 10:29, Ian Abbott wrote:
On 20/11/17 07:50, Jesse Chan wrote:
This change resolves a new compile-time warning
when built as a loadable module:
WARNING: modpost: missing MODULE_LICENSE() in
* Ingo Molnar wrote:
>
> * Andy Lutomirski wrote:
>
> > This sets up stack switching, including for SYSCALL. I think it's
> > in decent shape.
> >
> > Known issues:
> > - I think we're going to want a way to turn the stack switching on and
> >off
From: Satheesh Rajendran
Certain systems are designed to have sparse/discontiguous nodes.
On such systems, perf bench numa hangs, shows wrong number of nodes
and shows values for non-existent nodes. Handle this by only
taking nodes that are exposed by kernel to
On 11/21/17 11:55 PM, Sinan Kaya wrote:
For places where domain number information is available, I extracted domain
number
and added into pci_get_domain_bus_and_slot() call such as xen or bn drivers.
My suggestion is that you restrict your first patch set to only these
patches.
The
Jens, please don't just revert the commit in your for-linus tree.
On its own this will totally mess up the interrupt assignments. Give
me a bit of time to sort this out properly.
Hi Jesse,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on linuxtv-media/master]
[also build test ERROR on v4.14 next-20171121]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci
On 21/11/17 17:39, Ulf Hansson wrote:
> On 21 November 2017 at 14:42, Adrian Hunter wrote:
>> card_busy_detect() has a 10 minute timeout. However the correct timeout is
>> the data timeout. Change card_busy_detect() to use the data timeout.
>
> Unfortunate I don't think
On 11/22/2017 02:58 AM, Ben Hutchings wrote:
> 3.16.51-rc1 review patch. If anyone has any objections, please let me know.
I don't really care much in the end, but is "fix wrong comment" really a
stable patch material these days? :)
> --
>
> From: SeongJae Park
From: Satheesh Rajendran
Certain systems would have sparse/discontinguous
numa nodes.
perf bench numa doesnt work well on such nodes.
1. It shows wrong values.
2. It can hang.
3. It can show redundant information for non-existant nodes.
#numactl -H
available: 2
From: Wanpeng Li
Reported by syzkaller:
[ cut here ]
WARNING: CPU: 5 PID: 2939 at arch/x86/kvm/vmx.c:3844
free_loaded_vmcs+0x77/0x80 [kvm_intel]
CPU: 5 PID: 2939 Comm: repro Not tainted 4.14.0+ #26
RIP:
On 11/20/2017 08:13 PM, Jin Yao wrote:
@@ -76,6 +97,17 @@ static struct rb_node *saved_value_new(struct rblist *rblist
__maybe_unused,
return >rb_node;
}
+static void saved_value_delete(struct rblist *rblist __maybe_unused,
+ struct rb_node *rb_node)
+{
On 11/21/17 23:41, kbuild test robot wrote:
> Hi Jesse,
>
> Thank you for the patch! Yet something to improve:
missing
#include
Jesse, did you build all of these driver changes?
> [auto build test ERROR on linuxtv-media/master]
> [also build test ERROR on v4.14 next-20171
On Wed, Nov 22, 2017 at 12:08:45AM -0600, Timur Tabi wrote:
> On 11/21/17 11:55 PM, Sinan Kaya wrote:
> > For places where domain number information is available, I extracted domain
> > number
> > and added into pci_get_domain_bus_and_slot() call such as xen or bn drivers.
>
> My suggestion is
As per APIs each mc-portal is of 64K size while currently
16bits (type u16) is used to store size of mc-portal.
In these cases upper bit of portal size gets truncated.
Signed-off-by: Bharat Bhushan
---
v2->v3:
- v2 patch: https://patchwork.kernel.org/patch/10067661/
-
Commit-ID: 548c3050ea8d16997ae27f9e080a8338a606fc93
Gitweb: https://git.kernel.org/tip/548c3050ea8d16997ae27f9e080a8338a606fc93
Author: Andy Lutomirski
AuthorDate: Tue, 21 Nov 2017 20:43:56 -0800
Committer: Ingo Molnar
CommitDate: Wed, 22 Nov 2017
On Wed, Nov 22, 2017 at 12:31:14AM -0500, Sinan Kaya wrote:
> pci_get_bus_and_slot() is restrictive such that it assumes domain=0 as
> where a PCI device is present. This restricts the device drivers to be
> reused for other domain numbers.
>
> Use pci_get_domain_bus_and_slot() with a domain
Commit-ID: f68d62a56708b0c19dca7a998f408510f2fbc3a8
Gitweb: https://git.kernel.org/tip/f68d62a56708b0c19dca7a998f408510f2fbc3a8
Author: Andrey Ryabinin
AuthorDate: Wed, 15 Nov 2017 17:36:35 -0800
Committer: Ingo Molnar
CommitDate: Wed, 22 Nov
On Tue, 21 Nov 2017 17:25:05 +0100,
Takashi Iwai wrote:
>
> On Tue, 21 Nov 2017 17:14:42 +0100,
> Laura Abbott wrote:
> >
> > Hi,
> >
> > Fedora got a bug report
> > (https://bugzilla.redhat.com/show_bug.cgi?id=1512853)
> > that Line Out stopped working between 4.13.9 and 4.13.10. Reverting
>
On Wed, Nov 22, 2017 at 12:30:57AM -0500, Sinan Kaya wrote:
> pci_get_bus_and_slot() is restrictive such that it assumes domain=0 as
> where a PCI device is present. This restricts the device drivers to be
> reused for other domain numbers.
>
> Use pci_get_domain_bus_and_slot() with a domain
/commits/Eddie-James/drivers-fsi-Add-SBEFIFO-client-driver/20171121-024602
config: um-allmodconfig (attached as .config)
compiler: gcc-6 (Debian 6.4.0-9) 6.4.0 20171026
reproduce:
# save the attached .config to linux build tree
make ARCH=um
All errors (new ones prefixed
On 11/21/2017 07:48 AM, Laurent Pinchart wrote:
> Hi Hans,
>
> Thank you for the patch.
>
> On Monday, 20 November 2017 22:57:34 EET Hans Verkuil wrote:
>> If the device tree for a board did not specify a cec clock, then
>> adv7511_cec_init would return an error, which would cause
Hi Gustavo
On 11/20/2017 03:00 PM, Gustavo A. R. Silva wrote:
> _channel_ is being dereferenced before it is null checked, hence there is a
> potential null pointer dereference. Fix this by moving the pointer dereference
> after _channel_ has been null checked.
>
> This issue was detected with
The rt5514 dsp captures pcm data through spi directly, so we should not
use rockchip-i2s as it's cpu dai like other codecs.
Use dummy_dai for rt5514 dsp dailink to make voice wakeup work again.
Reported-by: Jimmy Cheng-Yi Chiang
Fixes: (72cfb0f20c75 ASoC: rockchip: Use
Commit-ID: fd11a6496e12848d4eeb21029c2c288bbc638048
Gitweb: https://git.kernel.org/tip/fd11a6496e12848d4eeb21029c2c288bbc638048
Author: Ricardo Neri
AuthorDate: Mon, 20 Nov 2017 19:04:36 -0800
Committer: Ingo Molnar
CommitDate:
There are just a few new defines which do not affect perf tools.
Signed-off-by: Adrian Hunter
---
tools/perf/util/intel-pt-decoder/inat.h | 10 ++
1 file changed, 10 insertions(+)
diff --git a/tools/perf/util/intel-pt-decoder/inat.h
Hi Alan,
> Which raises another question. If there are multiple GPL 2.0 texts which
> are *supposedly* legally identical but this has never been tested in law
> -that implies SPDX is wrong in tagging them identically in case they turn
> out not to be...
For the cases, and the differences we're
On 11/20/2017 09:52 PM, Jens Axboe wrote:
> On 11/20/2017 01:49 PM, Christian Borntraeger wrote:
>>
>>
>> On 11/20/2017 08:42 PM, Jens Axboe wrote:
>>> On 11/20/2017 12:29 PM, Christian Borntraeger wrote:
On 11/20/2017 08:20 PM, Bart Van Assche wrote:
> On Fri, 2017-11-17 at
* Adrian Hunter wrote:
> Print file names of files that differ. For example, instead of:
>
> Warning: Intel PT: x86 instruction decoder differs from kernel
>
> print:
>
> Warning: Intel PT: x86 instruction decoder header at
>
On Tue, Nov 21, 2017 at 08:58:51AM +0100, Greg KH wrote:
> On Mon, Nov 20, 2017 at 01:39:31PM +0100, Daniel Vetter wrote:
> > Of course our CI is open, so if someone is supremely bored and wants to
> > backport more stuff for drm/i915, they could do that. But atm it doesn't
> > happen, and then
Hi Linus,
We see the below boot error IDs in 0day testing on your pre-RC1
merge commits. Most of them are not new regressions, and some are
known problems that have fixup patches planned for the upcoming -RC1.
In this thread, I'll show details and reproduce information for some
of them, hoping
Hello Jarkko,
On 11/21/2017 12:15 AM, Jarkko Sakkinen wrote:
> On Fri, Nov 17, 2017 at 11:07:24AM +0100, Javier Martinez Canillas wrote:
>> According to the TPM Library Specification, a TPM device must do a command
>> header validation before processing and return a TPM_RC_COMMAND_CODE code
>> if
The SPMI_PMIC clock divider driver configures the clkdiv modules present
on Qualcomm Technologies, Inc. SPMI PMIC. This driver provides a clock
interface for each clkdiv module and allows clock operations such as enable,
disable, set_rate, recalc_rate and round_rate.
Tirupathi Reddy (2):
clk:
Clkdiv module provides a clock output on the PMIC with CXO as
the source. This clock can be routed through PMIC GPIOs. Add
a device driver to configure this clkdiv module.
Signed-off-by: Stephen Boyd
Signed-off-by: Tirupathi Reddy
---
On 11/18/2017 5:26 AM, Stephen Boyd wrote:
On 11/17, Tirupathi Reddy wrote:
diff --git a/Documentation/devicetree/bindings/clock/clk-spmi-pmic-div.txt
b/Documentation/devicetree/bindings/clock/clk-spmi-pmic-div.txt
new file mode 100644
index 000..2cf2aba
--- /dev/null
+++
On 11/18/2017 1:52 AM, Rob Herring wrote:
On Fri, Nov 17, 2017 at 03:18:47PM +0530, Tirupathi Reddy wrote:
Clkdiv module provides a clock output on the PMIC with CXO as
the source. This clock can be routed through PMIC GPIOs. Add
a device driver to configure this clkdiv module.
This patch adds device tree bindings for Qualcomm SPMI PMIC
clock divider module.
Signed-off-by: Tirupathi Reddy
---
.../bindings/clock/qcom,spmi-pmic-div.txt | 59 ++
1 file changed, 59 insertions(+)
create mode 100644
On Tue, 2017-11-21 at 09:37 +0100, Thomas Gleixner wrote:
> On Tue, 21 Nov 2017, Mike Galbraith wrote:
> > On Mon, 2017-11-20 at 16:33 -0500, Mikulas Patocka wrote:
> > >
> > > Is there some specific scenario where you need to call
> > > blk_schedule_flush_plug from rt_spin_lock_fastlock?
> >
>
QMP V3 USB3 PHY is a DisplayPort (DP) and USB combo PHY
with dual RX/TX lanes to support type-c. There is a
separate block DP_COM for configuration related to type-c
or DP. Add support for dp_com region and secondary rx/tx
lanes initialization.
Signed-off-by: Manu Gautam
Driver is currently performing PHY reset after starting
SERDES/PCS. As per hardware datasheet reset must be done
before starting PHY. Hence, update the sequence.
Signed-off-by: Manu Gautam
---
drivers/phy/qualcomm/phy-qcom-qmp.c | 6 +++---
1 file changed, 3
Use register layout to add additional registers present
on QUSB2 PHY V2 version for PHY initialization.
Other than new registers on V2, following two register's
offset and bit definitions are different: POWERDOWN control
and PLL_STATUS.
Signed-off-by: Manu Gautam
---
Disable clocks and enable DP/DM wakeup interrupts when
suspending PHY.
Core driver should notify speed to PHY driver to enable
appropriate DP/DM wakeup interrupts polarity in suspend state.
Signed-off-by: Manu Gautam
---
drivers/phy/qualcomm/phy-qcom-qusb2.c | 181
Update generic compatible string for QUSB2 V2 PHY. This will allow
all targets using QUSB2 V2 use same string.
Acked-by: Rob Herring
Signed-off-by: Manu Gautam
---
Documentation/devicetree/bindings/phy/qcom-qusb2-phy.txt | 5 -
1 file changed, 4
New version of QUSB2 PHY has some registers offset changed.
Add support to have register layout for a target and update
the same in phy_configuration.
Signed-off-by: Manu Gautam
---
drivers/phy/qualcomm/phy-qcom-qusb2.c | 131 --
1 file
Update compatible string and clock names for QMP version V3
USB PHY.
Acked-by: Rob Herring
Signed-off-by: Manu Gautam
---
Documentation/devicetree/bindings/phy/qcom-qmp-phy.txt | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git
> -Original Message-
> From: Chao Yu [mailto:yuch...@huawei.com]
> Sent: Monday, November 20, 2017 11:00 AM
> To: LiFan; 'Chao Yu'; 'Jaegeuk Kim'
> Cc: linux-kernel@vger.kernel.org; linux-f2fs-de...@lists.sourceforge.net
> Subject: Re: [f2fs-dev] [PATCH RESEND] f2fs: fix concurrent
On Mon, 2017-11-20 at 17:00 -0700, Jim Davis wrote:
> On Mon, Nov 20, 2017 at 2:22 PM, Luc Van Oostenryck
> wrote:
>
> > Should it be possible to somehow keep the distinction between
> > the flags coming from KBUILD_CFLAGS and the pure CHECKFLAGS?
>
> Well, the
Hi Hans,
Thank you for the patch.
On Tuesday, 21 November 2017 10:17:43 EET Hans Verkuil wrote:
> If the device tree for a board did not specify a cec clock, then
> adv7511_cec_init would return an error, which would cause adv7511_probe()
> to fail and thus there is no HDMI output.
>
> There is
On Mon, Nov 20, 2017 at 03:10:45PM -0600, Rob Herring wrote:
> On Sat, Nov 18, 2017 at 03:22:32AM +0100, Jonathan Neuschäfer wrote:
> > This device's bindings are not trivial: Additional properties are
> > documented in in Documentation/devicetree/bindings/mfd/mc13xxx.txt.
> >
> > Signed-off-by:
From: Kai Heng Feng
On Asus GL502VSK and UX305LA, ACPI incorrectly reports discharging when
battery is full and AC is plugged.
However rate_now is correct under this circumstance, hence we can use
"rate_now == 0" as a predicate to report battery full status
* Dave Hansen wrote:
>
> The MPX hardware data structurse are defined in a weird way: they define
> their size in bytes and then union that with the type with which we want
> to access them.
>
> Yes, this is weird, but it does work. But, new GCC's complain that
* Dave Hansen wrote:
>
> si_pkey is now #defined to be the name of the new siginfo field that
> protection keys uses. Rename it not to conflict.
>
> ---
Ditto: added your Signed-off-by which I presume was intended.
Thanks,
Ingo
Whoops, my bad. Sorry
Thanks,
Romain
2017-11-20 21:34 GMT+01:00 Bjorn Helgaas :
> On Mon, Nov 20, 2017 at 08:32:47PM +0100, Romain Perier wrote:
>> From: Romain Perier
>>
>> Now that all the drivers use dma pool API, we can remove the macro
>>
JFYI these patch is in Virtuozzo7 kernel from September, and we have no
issues found with it until now by out testing, and initial problem does
not reproduce for 2.5 months.
Commit-ID: 7b659ee3e1fe0e8eb39730afb903c64e25490ec4
Gitweb: https://git.kernel.org/tip/7b659ee3e1fe0e8eb39730afb903c64e25490ec4
Author: Dave Hansen
AuthorDate: Fri, 10 Nov 2017 16:12:32 -0800
Committer: Ingo Molnar
CommitDate: Tue, 21 Nov
Commit-ID: 91c49c2deb96ffc3c461eaae70219d89224076b7
Gitweb: https://git.kernel.org/tip/91c49c2deb96ffc3c461eaae70219d89224076b7
Author: Dave Hansen
AuthorDate: Fri, 10 Nov 2017 16:12:31 -0800
Committer: Ingo Molnar
CommitDate: Tue, 21 Nov
Commit-ID: a6400120d042397675fcf694060779d21e9e762d
Gitweb: https://git.kernel.org/tip/a6400120d042397675fcf694060779d21e9e762d
Author: Dave Hansen
AuthorDate: Fri, 10 Nov 2017 16:12:29 -0800
Committer: Ingo Molnar
CommitDate: Tue, 21 Nov
On 21 November 2017 at 03:12, Stephen Boyd wrote:
> On 11/20, Chunyan Zhang wrote:
>> From: Cai Li
>>
>> In some cases the clock parent would be set NULL when doing re-parent,
>> it will cause a NULL pointer accessing if clk_set trace event is
On Mon, Nov 20, 2017 at 10:44 PM, Andy Lutomirski wrote:
> On Mon, Nov 20, 2017 at 9:07 AM, Andy Lutomirski wrote:
>> This sets up stack switching, including for SYSCALL. I think it's
>> in decent shape.
>>
>> Known issues:
>> - KASAN is likely to be busted.
PHY must be powered on before turning ON clocks and
attempting to initialize it. Driver is exposing
separate init and power_on routines for this.
Apparently USB dwc3 core driver performs power-on
after init. Also, poweron and init for QUSB2 PHY
need to be executed together always, hence remove
New revision (v3) of QMP PHY uses different offsets
for almost all of the registers. Hence, move these
definitions to header file so that updated offsets
can be added for QMP v3.
Signed-off-by: Manu Gautam
---
drivers/phy/qualcomm/phy-qcom-qmp.c | 119
PHY must be powered on before turning ON clocks and
attempting to initialize it. Driver is exposing
separate init and power_on routines for this.
Apparently USB dwc3 core driver performs power-on after
init. Also, poweron and init for QMP PHY need to be
executed together always, hence remove
PHY block or asynchronous reset requires signal
to be asserted before de-asserting. Driver is only
de-asserting signal which is already low, hence
reset operation is a no-op. Fix this by asserting
signal first. Also, resetting requires PHY clocks
to be turned ON only after reset is finished. Fix
Disable clocks and enable PHY autonomous mode to detect
wakeup events when PHY is suspended.
Core driver should notify speed to PHY driver to enable
LFPS and/or RX_DET interrupts.
Signed-off-by: Manu Gautam
---
drivers/phy/qualcomm/phy-qcom-qmp.c | 185
QCOM USB PHYs can monitor resume/remote-wakeup event in
suspended state. However PHY driver must know current
operational speed of PHY in order to set correct polarity of
wakeup events for detection. E.g. QUSB2 PHY monitors DP/DM
signals depending on speed is LS or FS/HS to detect resume.
Registers offsets for QMP V3 PHY are changed from
previous versions (1/2), update same in header file.
Signed-off-by: Manu Gautam
---
drivers/phy/qualcomm/phy-qcom-qmp.h | 149
1 file changed, 149 insertions(+)
diff --git
On 11/21/2017 10:07 AM, Javier Martinez Canillas wrote:
> On 11/21/2017 12:15 AM, Jarkko Sakkinen wrote:
>
>> matters less than breaking the sandbox.
>>
>
> Yes, sorry for that. It wasn't clear to me that there was a sandbox and my
> lack of familiarity with the code was the reason why I posted
On 11/20/2017 10:11 PM, Stuart Hayes wrote:
When a command is added to the host's error handler command queue, there is a
chance that the error handler will not be woken up. This can happen when one CPU
is running scsi_eh_scmd_add() at the same time as another CPU is running
On Tue, Nov 21, 2017 at 4:05 AM, Richard Cochran
wrote:
> On Mon, Nov 20, 2017 at 11:53:02PM +0100, Arnd Bergmann wrote:
>> .B EINVAL
>> +The
>> +.I clk_id
>> +specified is not supported on this system.
>
> We return EINVAL when the clockid is not valid. That can mean
My patch should also fix your issue too, please see explanation in reply
to your patch. Do your testing show that it doesn't?
Thanks, Pavel.
On 11/21/2017 09:10 AM, Stuart Hayes wrote:
Pavel,
It turns out that the error handler on our systems was not getting woken up for
a different
If the device tree for a board did not specify a cec clock, then
adv7511_cec_init would return an error, which would cause adv7511_probe()
to fail and thus there is no HDMI output.
There is no need to have adv7511_probe() fail if the CEC initialization
fails, so just change adv7511_cec_init() to
On Friday, 17 November 2017 10:41:05 EET Geert Uytterhoeven wrote:
> On Fri, Nov 17, 2017 at 1:10 AM, Kuninori Morimoto wrote:
> >>> +static void rcar_dmac_chcr_de_barrier(struct rcar_dmac_chan *chan)
> >>> +{
> >>> + u32 chcr;
> >>> + int i;
> >>
> >> unsigned int
> >>
> >>> +
> >>>
alloc_nid_failed and scan_nat_page can be called at the same time,
and we haven't protected add_free_nid and update_free_nid_bitmap
with the same nid_list_lock. That could lead to
Thread AThread B
- __build_free_nids
- scan_nat_page
On Tue, 21 Nov 2017, "Tobin C. Harding" wrote:
> On Wed, Nov 15, 2017 at 04:09:32PM +0200, Jani Nikula wrote:
>> On Wed, 15 Nov 2017, "Tobin C. Harding" wrote:
>> > Original email thread
>> >
>> > https://lkml.org/lkml/2017/11/14/184
>>
>> Please use
On 2017/11/20 15:33, Jiri Olsa wrote:
On Wed, Nov 15, 2017 at 09:00:03AM +0800, zhangmengting wrote:
Hi Jiri, thanks for your detailed review, please see my comments inline.
On 2017/11/10 18:39, Jiri Olsa wrote:
On Fri, Nov 10, 2017 at 04:28:37PM +0800, Mengting Zhang wrote:
SNIP
diff
On Mon, 20 Nov 2017, Andy Lutomirski wrote:
> On Mon, Nov 20, 2017 at 2:01 PM, Thomas Gleixner wrote:
> > On Mon, 20 Nov 2017, Andy Lutomirski wrote:
> >> + * to avoid circular header dependencies.
> >
> > :(
>
> Hmm. I could probably fix this, but it involves (at least)
Commit-ID: aa5222e92f8000ed3c1c38dddf11c83222aadfb3
Gitweb: https://git.kernel.org/tip/aa5222e92f8000ed3c1c38dddf11c83222aadfb3
Author: Dan Carpenter
AuthorDate: Fri, 13 Oct 2017 10:01:22 +0300
Committer: Ingo Molnar
CommitDate: Tue, 21 Nov
Print file names of files that differ. For example, instead of:
Warning: Intel PT: x86 instruction decoder differs from kernel
print:
Warning: Intel PT: x86 instruction decoder header at
'tools/perf/util/intel-pt-decoder/inat.h' differs from latest version at
'arch/x86/include/asm/inat.h'
Hi
Here are 2 patches for Intel PT to improve build messages and bring
instruction decoder files into line with the kernel.
Adrian Hunter (2):
perf intel-pt: Improve build messages for files that differ from the
kernel
perf intel-pt: Bring instruction decoder files into line with
* Dave Hansen wrote:
> Hi Ingo,
>
> Here are some small updates to Protection Keys documentation, and
> some small fixes to the selftests that we discussed.
Note that even with all the patches applied, a build warning remains:
gcc -m32 -o
Hi Yury,
On Thu, Nov 9, 2017 at 3:07 PM, Yury Norov wrote:
> find_bit functions are widely used in the kernel, including hot paths.
> This module tests performance of that functions in 2 typical scenarios:
> randomly filled bitmap with relatively equal distribution of
On 2017/11/21 11:44, Chen Feng wrote:
> With kaslr and kasan enable both, I got the follow issue.
>
> [ 16.130523s]kasan: reg->base = 1, phys_end =1c000,start =
> 4000, end = ffc0
> [ 16.142517s]___alloc_bootmem_nopanic:257
> [
On Tue, 21 Nov 2017, Mike Galbraith wrote:
> On Mon, 2017-11-20 at 16:33 -0500, Mikulas Patocka wrote:
> >
> > Is there some specific scenario where you need to call
> > blk_schedule_flush_plug from rt_spin_lock_fastlock?
>
> Excellent question. What's the difference between not getting IO
>
Commit-ID: c51ff2c7fc45da8b18b28c4f15eca5a9975dfb59
Gitweb: https://git.kernel.org/tip/c51ff2c7fc45da8b18b28c4f15eca5a9975dfb59
Author: Dave Hansen
AuthorDate: Fri, 10 Nov 2017 16:12:28 -0800
Committer: Ingo Molnar
CommitDate: Tue, 21 Nov
1 - 100 of 1990 matches
Mail list logo