This patch fixes up unnecessary parentheses warning found by checkpatch.pl
script.
Signed-off-by: Yash Omer
---
drivers/staging/wlan-ng/prism2mgmt.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/wlan-ng/prism2mgmt.c
b/drivers/staging/wlan-ng/prism2mgmt.c
i
On Fri, Feb 16, 2018 at 10:25:31AM +0800, Jin, Yao wrote:
SNIP
> > From my opinion, the option '--max-stack' in perf report looks not very
> > necessary. While it's just my personal opinion, need to hear from more
> > people. :)
> >
> > Thanks
> > Jin Yao
> >
> > > thanks,
> > > jirka
> > >
>
Hi Abhishek,
On 2/3/2018 1:28 PM, Abhishek Sahu wrote:
> Following are the major issues in current driver code
>
> 1. The current driver simply assumes the transfer completion
>whenever its gets any non-error interrupts and then simply do the
>polling of available/free bytes in FIFO.
> 2.
So pointer rings work fine, but they have a problem:
make them too small and not enough entries fit.
Make them too large and you start flushing your cache
and running out of memory.
This is a new idea of mine: a ring backed by a
linked list. Once you run out of rin entries,
instead of a drop you f
This patch fixes up a unncessary paratheses warning found by checkpatch.pl
script.
Signed-off-by: Yash Omer
---
drivers/staging/wlan-ng/prism2mgmt.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/wlan-ng/prism2mgmt.c
b/drivers/staging/wlan-ng/prism2mgmt.c
i
* Jerry Hoemann wrote:
> Gen8 and prior Proliant systems supported the "CRU" interface
> to firmware. This interfaces allows linux to "call back" into firmware
> to source the cause of an NMI. This feature isn't fully utilized
> as the actual source of the NMI isn't printed, the driver only
>
On Monday 05 February 2018 06:20 PM, Kishon Vijay Abraham I wrote:
> sdhci has a 10 second timeout to catch devices that stop responding.
> Instead of programming 10 second arbitrary value, calculate the total time
> it would take for the entire transfer to happen and program the timeout
> value
On Thu, Feb 15, 2018 at 11:29:42PM +, Andy Lutomirski wrote:
...
> >>> +bool pti_handle_segment_not_present(long error_code)
> >>> +{
> >>> + if (!static_cpu_has(X86_FEATURE_PTI))
> >>> + return false;
> >>> +
> >>> + if ((unsigned short)error_code != GDT_ENTRY_DEFAULT
On Wed, 7 Feb 2018 14:37:00 -0600
Bin Liu wrote:
> On Tue, Feb 06, 2018 at 08:00:24PM +0100, Andreas Kemnade wrote:
> > Hi,
> >
> > On Tue, 6 Feb 2018 12:46:05 -0600
> > Bin Liu wrote:
> >
> > > Hi,
> > >
> > > On Sat, Jan 27, 2018 at 09:34:03AM +0100, Andreas Kemnade wrote:
> > > > On dm
Am Mittwoch, 14. Februar 2018, 21:08:59 CET schrieb Jernej Skrabec:
> dw_hdmi shouldn't set drvdata since some drivers might need to store
> it's own data there. Rework dw_hdmi in a way to return struct dw_hdmi
> instead to store it in drvdata. This way drivers are responsible to
> store and pass s
> On 15 Feb 2018, at 04.51, Matias Bjørling wrote:
>
> On 02/13/2018 03:06 PM, Javier González wrote:
>> From: Javier González
>> The 2.0 spec provides a report chunk log page that can be retrieved
>> using the stangard nvme get log page. This replaces the dedicated
>> get/put bad block table in
On Thu, Feb 15, 2018 at 07:45:08PM -0700, Nathan Chancellor wrote:
> On Thu, Feb 15, 2018 at 04:15:57PM +0100, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.4.116 release.
> > There are 108 patches in this series, all will be posted as a response
> > to this o
On Thu, Feb 15, 2018 at 06:31:48PM -0800, Brian Norris wrote:
> On Thu, Feb 15, 2018 at 04:17:32PM +0100, Greg Kroah-Hartman wrote:
> > 4.4-stable review patch. If anyone has any objections, please let me know.
>
> Consider this an objection:
>
> I'm currently arguing that this is unnecessarily
> On 15 Feb 2018, at 05.11, Matias Bjørling wrote:
>
> The value of max_phys_sect is always static. Instead of
> defining it in the nvm_dev_ops structure, declare it as a global
> value.
>
> Signed-off-by: Matias Bjørling
> ---
> drivers/lightnvm/core.c | 28 +++---
> On 15 Feb 2018, at 02.59, Matias Bjørling wrote:
>
> On 02/13/2018 03:06 PM, Javier González wrote:
>> From: Javier González
>> In preparation of pblk supporting 2.0, implement the get log report
>> chunk in pblk.
>> This patch only replicates de bad block functionality as the rest of the
>>
> On 15 Feb 2018, at 02.20, Matias Bjørling wrote:
>
> On 02/13/2018 03:06 PM, Javier González wrote:
>> From: Javier González
>> Apart from showing the geometry returned by the different identify
>> commands, provide the generic geometry too, as this is the geometry that
>> targets will use to
On 2018-02-15 18:19, Richard Guy Briggs wrote:
> On 2018-02-15 18:07, Steve Grubb wrote:
> > On Monday, February 12, 2018 12:02:21 AM EST Richard Guy Briggs wrote:
> > > Tracefs or debugfs were causing hundreds to thousands of null PATH
> > > records to be associated with the init_module and finit_
These are basic device tree files needed to boot a SDM845 MTP
board to a ramfs based serial console shell
Bindings are based on whats proposed for pinctrl/serial/clock
drivers for SDM845 SoC
pinctrl: https://patchwork.kernel.org/patch/10157143/ (This is now pulled
in by Linus Walleij for 4.17)
clo
Add the qup uart node and geni se instance needed to
support the serial console on the MTP.
Signed-off-by: Rajendra Nayak
---
arch/arm64/boot/dts/qcom/sdm845-mtp.dts | 39 +
arch/arm64/boot/dts/qcom/sdm845.dtsi| 39 +
2 files ch
Add a SoC string 'sdm845' for the qualcomm SDM845 SoC
Signed-off-by: Rajendra Nayak
---
Documentation/devicetree/bindings/arm/qcom.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/arm/qcom.txt
b/Documentation/devicetree/bindings/arm/qcom.txt
index 0ed4d3
Add a skeletal sdm845 SoC dtsi and MTP board dts/dtsi files
Signed-off-by: Rajendra Nayak
Reviewed-by: Doug Anderson
---
arch/arm64/boot/dts/qcom/Makefile | 1 +
arch/arm64/boot/dts/qcom/sdm845-mtp.dts | 15 ++
arch/arm64/boot/dts/qcom/sdm845.dtsi| 277 +
Document the compatible string for the Kryo385 cpus found in qualcomm
SoCs.
Signed-off-by: Rajendra Nayak
Reviewed-by: Rob Herring
---
Documentation/devicetree/bindings/arm/cpus.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/arm/cpus.txt
b/Documentati
On 2018-02-15 18:07, Steve Grubb wrote:
> On Monday, February 12, 2018 12:02:21 AM EST Richard Guy Briggs wrote:
> > Tracefs or debugfs were causing hundreds to thousands of null PATH
> > records to be associated with the init_module and finit_module SYSCALL
> > records on a few modules when the fo
On 15 February 2018 at 20:45, Greg Kroah-Hartman
wrote:
> This is the start of the stable review cycle for the 4.15.4 release.
> There are 202 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Respo
On 15 February 2018 at 20:46, Greg Kroah-Hartman
wrote:
> This is the start of the stable review cycle for the 4.9.82 release.
> There are 88 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Respon
On 15 February 2018 at 20:44, Greg Kroah-Hartman
wrote:
> This is the start of the stable review cycle for the 4.14.20 release.
> There are 195 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Resp
- skip: 1, pass: 12,
Hikey results summary,
Summary
kernel: 4.4.116-rc1
git repo: https://git.linaro.org/lkft/arm64-stable-rc.git
git tag: 4.4.116-rc1-hikey-20180215-131
git commit: 4da825751e43ebd33e27ce2b70f1ede852310a87
git describe: 4.4.116-rc1-hikey-20180215-131
Test det
Hi Linus,
One nouveau regression fix, one AMD quirk and a full set of i915 fixes.
The i915 fixes are mostly for things caught by their CI system, main
ones being DSI panel fixes and GEM fixes.
Pretty quiet overall.
Dave.
The following changes since commit 7928b2cbe55b2a410a0f5c1f154610059c57b1
Hi Abhishek,
On 2/3/2018 1:28 PM, Abhishek Sahu wrote:
> According to I2c specification, “If a master-receiver sends a
> repeated START condition, it sends a not-acknowledge (A) just
> before the repeated START condition”. QUP v2 supports sending
> of NACK without stop with QUP_TAG_V2_DATARD_NACK
On Tue, Feb 13, 2018 at 4:15 PM, Chen-Yu Tsai wrote:
> Hi Nicolas, Dave,
>
> On Wed, Jan 17, 2018 at 4:46 PM, Chen-Yu Tsai wrote:
>> This is v4 of my sun9i SMP/hotplug support series which was started
>> over two years ago [1]. We've tried to implement PSCI for both the A80
>> and A83T. Results w
From: Dominik Bozek
ACM driver may accept data to transmit while system is not fully
resumed. In this case ACM driver buffers data and prepare URBs
on usb anchor list.
There is a little chance that two tasks put a char and initiate
acm_tty_flush_chars(). In such a case, driver will put one URB
tw
Hi Abhishek,
On 2/3/2018 1:28 PM, Abhishek Sahu wrote:
> The BAM mode requires buffer for start tag data and tx, rx SG
> list. Currently, this is being taken for maximum transfer length
> (65K). But an I2C transfer can have multiple messages and each
> message can be of this maximum length so the
Hi Baoquan,
I love your patch! Yet something to improve:
[auto build test ERROR on tip/auto-latest]
[also build test ERROR on v4.16-rc1 next-20180215]
[cannot apply to tip/x86/core]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url
On Mon, 2018-02-12 at 17:38 +1030, Joel Stanley wrote:
> The LPC Host Interface Controller is part of a BMC SoC that is used for
> communication with the host.
>
> Signed-off-by: Joel Stanley
> ---
> .../devicetree/bindings/mfd/aspeed-lpc.txt | 40
> ++
> 1 file chan
On Thursday 15 February 2018 01:38 AM, Jernej Skrabec wrote:
dw_hdmi shouldn't set drvdata since some drivers might need to store
it's own data there. Rework dw_hdmi in a way to return struct dw_hdmi
instead to store it in drvdata. This way drivers are responsible to
store and pass structure wh
On Thursday 15 February 2018 01:38 AM, Jernej Skrabec wrote:
Parts of PHY code could be useful also for custom PHYs. For example,
Allwinner A83T has custom PHY which is probably Synopsys gen2 PHY
with few additional memory mapped registers, so most of the Synopsys PHY
related code could be reus
On Thursday 15 February 2018 01:38 AM, Jernej Skrabec wrote:
Allwinner SoCs have dw hdmi controller v1.32a which exhibits same
magenta line issue as i.MX6Q and i.MX6DL. Enable workaround for it.
Tests show that one iteration is enough.
Acked-by: Laurent Pinchart
Reviewed-by: Archit Taneja
Andy Lutomirski wrote:
> On Fri, Feb 16, 2018 at 12:42 AM, Linus Torvalds
> wrote:
>> On Thu, Feb 15, 2018 at 4:22 PM, Nadav Amit wrote:
>>> It is not too pretty, I agree, but it should do the work. There is only one
>>> problematic descriptor that can be used to switch from compatibility-mode
On Thu, 2018-02-15 at 10:07 -0800, Rohit Jain wrote:
>
> > Rohit is running more tests with a patch that deletes
> > sysctl_sched_migration_cost from idle_balance, and for his patch but
> > with the 5000 usec mistake corrected back to 500 usec. So far both
> > give improvements over the baseline,
On Thu, Feb 15, 2018 at 07:37:44PM -0800, Kees Cook wrote:
> + [ TAINT_RANDSTRUCT ]= { 'T', ' ', true },
Something like this, yeah.
On 2/3/2018 1:28 PM, Abhishek Sahu wrote:
> Currently the completion timeout is being taken according to
> maximum transfer length which is too high if SCL is operating in
> high frequency. This patch calculates timeout on the basis of
> one-byte transfer time and uses the same for completion tim
On Fri, Feb 16, 2018 at 12:13:17AM +, Al Viro wrote:
> On Fri, Feb 16, 2018 at 12:41:13AM +0300, Alexey Dobriyan wrote:
> > On Thu, Feb 15, 2018 at 07:07:13PM +, Al Viro wrote:
> > > On Wed, Feb 14, 2018 at 11:19:35AM +0300, Alexey Dobriyan wrote:
> > >
> > > > The more the merrier.
> > >
On Thu, Feb 15, 2018 at 04:53:29PM -0800, Kees Cook wrote:
> On Wed, Feb 14, 2018 at 12:19 AM, Alexey Dobriyan wrote:
> > The more the merrier.
>
> What made you choose this structure, BTW?
Nothing depends on its layout. No funky memcpy/memset...
It is strange you didn't annotate like 95% of str
On Friday 16 February 2018 09:47 AM, Dave Gerlach wrote:
> Commit 2dc4940360d4 ("regulator: tps65218: Remove all the compatibles")
> changes the probe function of drivers/regulator/tps65218-regulator.c so
> that it iterates through all available regulators and assumes that the
> regulator IDs are
On 2/3/2018 1:28 PM, Abhishek Sahu wrote:
> Currently each message length in complete transfer is being
> checked for determining DMA mode and if any of the message length
> is less than FIFO length then non DMA mode is being used which
> will increase overhead. DMA can be used for any length and
On 2/3/2018 1:28 PM, Abhishek Sahu wrote:
> Currently the i2c error handling in BAM mode is not working
> properly in stress condition.
>
> 1. After an error, the FIFO are being written with FLUSH and
>EOT tags which should not be required since already these tags
>have been written in B
> > + wrmsrl(MSR_IA32_PRED_CMD, PRED_CMD_IBPB);
>
> Should this be wrmsrl_safe? I don't see where we've verified host
> support of this MSR.
In mainline all wrmsr are wrmsrl_safe now.
-Andi
Commit 2dc4940360d4 ("regulator: tps65218: Remove all the compatibles")
changes the probe function of drivers/regulator/tps65218-regulator.c so
that it iterates through all available regulators and assumes that the
regulator IDs are sequential and match the order present in the enum
tps65218_regula
On Tue, Feb 6, 2018 at 9:29 AM, David Woodhouse wrote:
> @@ -8946,6 +9017,27 @@ static void __noclone vmx_vcpu_run(struct kvm_vcpu
> *vcpu)
> #endif
> );
>
> + /*
> +* We do not use IBRS in the kernel. If this vCPU has used the
> +* SPEC_CTRL MSR it may have
On Fri, Feb 16, 2018 at 1:53 AM, Philipp Rossak wrote:
>
>
> On 15.02.2018 15:11, Maxime Ripard wrote:
>>
>> On Wed, Feb 14, 2018 at 02:56:12PM +0100, Philipp Rossak wrote:
>>>
>>> This patch fixes a bug, that prevents the Allwinner A83T and the A80
>>> from a successful boot.
>>>
>>> The bug is t
Hi Alex,
On Thu Feb 15, 2018 at 09:21:09AM -0700, Alex Williamson wrote:
> On Thu, 15 Feb 2018 16:34:06 +0530
> Linu Cherian wrote:
>
> > Hi,
> >
> > Was exploring the implications of an application crash while DMA
> > is active from a vfio PCI device; the DMA being configured and
> > started
On Tue, Feb 6, 2018 at 9:29 AM, David Woodhouse wrote:
> @@ -8828,6 +8890,15 @@ static void __noclone vmx_vcpu_run(struct kvm_vcpu
> *vcpu)
>
> vmx_arm_hv_timer(vcpu);
>
> + /*
> +* If this vCPU has touched SPEC_CTRL, restore the guest's value if
> +* it's non-zero.
On Fri, 16 Feb 2018 11:12:18 +0800
changbin...@intel.com wrote:
> From: Changbin Du
>
> Signed-off-by: Changbin Du
> ---
> .../trace/{ftrace-design.txt => ftrace-design.rst} | 248
> +++--
> Documentation/trace/index.rst | 2 +
> 2 files changed, 137 ins
On Wed, 14 Feb 2018, David Miller wrote:
> > Have you considered that implementing the ethtool hooks in the core
> > driver might allow removal of all 8390 driver 'msg_enable' module
> > parameters and msglevel ethtool hooks added by c45f812f0280, excepting
> > those in the core driver? But eve
On Thu, Feb 1, 2018 at 1:59 PM, KarimAllah Ahmed wrote:
> @@ -3684,6 +3696,22 @@ static int svm_set_msr(struct kvm_vcpu *vcpu, struct
> msr_data *msr)
> case MSR_IA32_TSC:
> kvm_write_tsc(vcpu, msr);
> break;
> + case MSR_IA32_PRED_CMD:
> +
On Thu, Feb 15, 2018 at 10:06 AM, Kees Cook wrote:
> On Thu, Feb 15, 2018 at 7:59 AM, Arnd Bergmann wrote:
>> On Thu, Feb 15, 2018 at 4:25 PM, Josh Poimboeuf wrote:
>>> On Thu, Feb 15, 2018 at 04:01:57PM +0100, Arnd Bergmann wrote:
On Wed, Feb 14, 2018 at 11:45 PM, Josh Poimboeuf
wro
This cleans up the taint flags and documentation before adding a new
one for randstruct. Patch 3/3 reads:
Since the randstruct plugin can intentionally produce extremely unusual
kernel structure layouts (even performance pathological ones), some
maintainers want to be able to trivially determine i
Since the randstruct plugin can intentionally produce extremely unusual
kernel structure layouts (even performance pathological ones), some
maintainers want to be able to trivially determine if an Oops is coming
from a randstruct-built kernel, so as to keep their sanity when debugging.
This adds th
This converts the taint bit defines to an enum, uses indexed initializers
instead of comments, and make sure that no one forgets to update the
taint_flags when adding new bits.
Signed-off-by: Kees Cook
---
include/linux/kernel.h | 40 ++--
kernel/panic.c
This consolidates the taint bit documentation into a single place with
both numeric and letter values. Additionally adds the missing TAINT_AUX
documentation.
Signed-off-by: Kees Cook
---
Documentation/sysctl/kernel.txt | 53 +
kernel/panic.c
Hi all,
Changes since 20180215:
The sound-asoc tree lost its build failure.
The mmc tree lost its build failure.
The xen-tip tree gained a conflict against Linus' tree.
Non-merge commits (relative to Linus' tree): 1950
2276 files changed, 94148 insertions(+), 45962
On 02/15/2018 06:27 PM, Brian Norris wrote:
Hi Hans,
On Tue, Feb 13, 2018 at 12:25:55PM +0100, Hans de Goede wrote:
On 13-02-18 03:24, Brian Norris wrote:
On Mon, Jan 08, 2018 at 10:44:16AM +0100, Hans de Goede wrote:
Commit 7d06d5895c15 ("Revert "Bluetooth: btusb: fix QCA...suspend/resume"")
From: Changbin Du
Signed-off-by: Changbin Du
---
Documentation/trace/ftrace-uses.rst | 23 ---
Documentation/trace/index.rst | 1 +
2 files changed, 13 insertions(+), 11 deletions(-)
diff --git a/Documentation/trace/ftrace-uses.rst
b/Documentation/trace/ftrace-uses.
From: Changbin Du
Hi All,
The linux tracers are so useful that I want to make the docs better. The kernel
now uses Sphinx to generate intelligent and beautiful documentation from
reStructuredText files. I converted two trace docs for your to preview.
http://docservice.askxiong.com/linux-kernel/t
From: Changbin Du
Signed-off-by: Changbin Du
---
.../trace/{ftrace-design.txt => ftrace-design.rst} | 248 +++--
Documentation/trace/index.rst | 2 +
2 files changed, 137 insertions(+), 113 deletions(-)
rename Documentation/trace/{ftrace-design.txt => ftr
From: Changbin Du
Signed-off-by: Changbin Du
---
Documentation/index.rst | 1 +
Documentation/trace/index.rst | 6 ++
2 files changed, 7 insertions(+)
create mode 100644 Documentation/trace/index.rst
diff --git a/Documentation/index.rst b/Documentation/index.rst
index ef5080c..3b99a
On Fri, Feb 16, 2018 at 12:51 AM, Nadav Amit wrote:
> Andrew Cooper wrote:
>
>> On 16/02/2018 00:25, Nadav Amit wrote:
>>> Dave Hansen wrote:
>>>
On 02/15/2018 08:35 AM, Nadav Amit wrote:
> I removed the PTI disabling while SMEP is unsupported, although I
> must admit I did not full
On 2018-02-15 18:34, Paul Moore wrote:
> On Wed, Feb 14, 2018 at 11:18 AM, Richard Guy Briggs wrote:
> > Audit link denied events for symlinks were missing the parent PATH
> > record. Add it. Since the full pathname may not be available,
> > reconstruct it from the path in the nameidata supplied
On Fri, Feb 16, 2018 at 12:42 AM, Linus Torvalds
wrote:
> On Thu, Feb 15, 2018 at 4:22 PM, Nadav Amit wrote:
>>
>> It is not too pretty, I agree, but it should do the work. There is only one
>> problematic descriptor that can be used to switch from compatibility-mode to
>> long-mode in the GDT (L
Hi Chris,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 1388c80438e69fc01d83fbe98da3cac24c3c8731
commit: bccd3b831185e75c4138bc3fd5201f3214dfeb3d drm/i915: Use trace_printk to
provide a death rattle for GEM
date:
Hi,
On Thu, Feb 15, 2018 at 06:24:16PM -0800, Matthias Kaehlcke wrote:
> On some systems a delay is needed after switching on the clocks, to allow
> the output to stabilize and avoid a popping noise at the beginning of
> the recording. Add the optional device tree property 'wakeup-delay-ms'
> and
On Thu, Feb 15, 2018 at 04:15:57PM +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.4.116 release.
> There are 108 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me kno
Adds basic support for the Nuvoton NPCM750 BMC.
Signed-off-by: Brendan Higgins
Reviewed-by: Tomer Maimon
Reviewed-by: Avi Fishman
Tested-by: Tomer Maimon
Tested-by: Avi Fishman
---
arch/arm/Kconfig | 2 +
arch/arm/Makefile| 1 +
arch/arm/mach-npcm/Kconfig | 48 +++
Add a common device tree for all Nuvoton NPCM750 BMCs and a board
specific device tree for the NPCM750 (Poleg) evaluation board.
Signed-off-by: Brendan Higgins
Reviewed-by: Tomer Maimon
Reviewed-by: Avi Fishman
Reviewed-by: Joel Stanley
Reviewed-by: Rob Herring
Tested-by: Tomer Maimon
Tested
Add maintainers and reviewers for the Nuvoton NPCM architecture.
Signed-off-by: Brendan Higgins
Reviewed-by: Tomer Maimon
Reviewed-by: Avi Fishman
---
MAINTAINERS | 14 ++
1 file changed, 14 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 3bdc260e36b7..02d1b0345298 1006
Addressed comments from:
- Arnd: https://www.spinics.net/lists/arm-kernel/msg634442.html
- Joel: https://www.spinics.net/lists/arm-kernel/msg634554.html
Summary of changes since previous update:
- More device tree and binding doc clean up.
All changes tested on Nuvoton NPCM750 EVB.
I went a
On Thu, Feb 15, 2018 at 04:17:32PM +0100, Greg Kroah-Hartman wrote:
> 4.4-stable review patch. If anyone has any objections, please let me know.
Consider this an objection:
I'm currently arguing that this is unnecessarily regressing power
consumption here:
https://patchwork.kernel.org/patch/101
Hi Hans,
On Tue, Feb 13, 2018 at 12:25:55PM +0100, Hans de Goede wrote:
> On 13-02-18 03:24, Brian Norris wrote:
> > On Mon, Jan 08, 2018 at 10:44:16AM +0100, Hans de Goede wrote:
> > > Commit 7d06d5895c15 ("Revert "Bluetooth: btusb: fix
> > > QCA...suspend/resume"")
> > > removed the setting of
On 2/13/2018 10:00 PM, Jin, Yao wrote:
On 2/13/2018 5:45 PM, Jiri Olsa wrote:
On Tue, Feb 13, 2018 at 04:44:28PM +0800, Jin Yao wrote:
Following command lines will cause perf crash.
perf record -j call -g -a
perf report --branch-history
*** Error in `perf': double free or corruption (!pr
On some systems a delay is needed after switching on the clocks, to allow
the output to stabilize and avoid a popping noise at the beginning of
the recording. Add the optional device tree property 'wakeup-delay-ms'
and apply the specified delay after enabling the mic. A blocking delay
can't be appl
On Fri, 16 Feb 2018, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the xen-tip tree got a conflict in:
>
> drivers/xen/pvcalls-front.c
>
> between commit:
>
> a9a08845e9ac ("vfs: do bulk POLL* -> EPOLL* replacement")
>
> from Linus' tree and commit:
>
> 1e7dbff356e5
On Tue, Feb 13, 2018 at 10:09:32PM +, Vadim Pasternak wrote:
> This patchset:
> - Adds define for the channels number for mux device.
> - Adds differed bus functionality.
> - Changes input for device create routine in mlxreg-hotplug driver.
> - Adds physical bus number auto detection.
Hi Vadim
Ion is designed to be a framework used by other clients who perform
operations on the buffer. Use the DRM vgem client as a simple consumer.
In conjunction with the dma-buf sync ioctls, this tests the full attach/map
path for the system heap.
Signed-off-by: Laura Abbott
---
tools/testing/selftest
Hi,
Ion hasn't had much in the way of unit tests and fixing that is
something that needs to happen before it can move out of staging. The
difficult part of testing parts of Ion is that it relies on having a
kernel driver to actually make some of the dma_buf calls. The vgem
DRM driver exists mostly
There's no need to print messages each time we alloc and free. Remove them.
Signed-off-by: Laura Abbott
---
tools/testing/selftests/android/ion/ionutils.c | 6 --
1 file changed, 6 deletions(-)
diff --git a/tools/testing/selftests/android/ion/ionutils.c
b/tools/testing/selftests/android/i
Hi all,
Today's linux-next merge of the xen-tip tree got a conflict in:
drivers/xen/pvcalls-front.c
between commit:
a9a08845e9ac ("vfs: do bulk POLL* -> EPOLL* replacement")
from Linus' tree and commit:
1e7dbff356e5 ("pvcalls-front: introduce a per sock_mapping refcount")
from the xen-
On 16/02/2018 00:51, Nadav Amit wrote:
> Andrew Cooper wrote:
>
>> On 16/02/2018 00:25, Nadav Amit wrote:
>>> Dave Hansen wrote:
>>>
On 02/15/2018 08:35 AM, Nadav Amit wrote:
> I removed the PTI disabling while SMEP is unsupported, although I
> must admit I did not fully understand w
On Thu, Feb 15, 2018 at 4:13 PM, Al Viro wrote:
> Guess what happens to cache footprint of dcache lookups if the bunch in the
> beginning gets spread over the entire thing? Right... And that's besides the
> outright miscompiles.
Mentioned in private communication, but just for posterity:
GCC_PL
From: Randy Dunlap
lib/test_firmware.c has build errors on some $ARCHes due to a
missing header file, so add it.
lib/test_firmware.c:134:2: error: implicit declaration of function 'vfree'
[-Werror=implicit-function-declaration]
lib/test_firmware.c:620:25: error: implicit declaration of func
On Wed, Feb 14, 2018 at 12:19 AM, Alexey Dobriyan wrote:
> The more the merrier.
What made you choose this structure, BTW?
> Signed-off-by: Alexey Dobriyan
> ---
>
> fs/proc/internal.h |2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> --- a/fs/proc/internal.h
> +++ b/fs/proc/inter
Andrew Cooper wrote:
> On 16/02/2018 00:25, Nadav Amit wrote:
>> Dave Hansen wrote:
>>
>>> On 02/15/2018 08:35 AM, Nadav Amit wrote:
I removed the PTI disabling while SMEP is unsupported, although I
must admit I did not fully understand why it is required.
>>> Do you mean you don't fu
From: Randy Dunlap
It seems that does not need
nor . 8 kernels builds are successful without
these 2 headers (allmodconfig, allyesconfig, allnoconfig, and
tinyconfig on both i386 and x86_64).
is #included 3875 times in 4.16-rc1, so this
reduces #include processing of these 2 files by a total
Hi Randy,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v4.16-rc1 next-20180215]
[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/linux
Dave Hansen wrote:
> On 02/15/2018 04:25 PM, Nadav Amit wrote:
>> Dave Hansen wrote:
>>
>>> On 02/15/2018 08:35 AM, Nadav Amit wrote:
I removed the PTI disabling while SMEP is unsupported, although I
must admit I did not fully understand why it is required.
>>>
>>> Do you mean you do
On 16/02/2018 00:25, Nadav Amit wrote:
> Dave Hansen wrote:
>
>> On 02/15/2018 08:35 AM, Nadav Amit wrote:
>>> I removed the PTI disabling while SMEP is unsupported, although I
>>> must admit I did not fully understand why it is required.
>> Do you mean you don't fully understand how PTI gives SME
On Thu, 15 Feb 2018, Matthew Wilcox wrote:
> What I was proposing was an intermediate page allocator where slab would
> request 2MB for its own uses all at once, then allocate pages from that to
> individual slabs, so allocating a kmalloc-32 object and a dentry object
> would result in 510 pages o
On 02/15/2018 04:25 PM, Nadav Amit wrote:
> Dave Hansen wrote:
>
>> On 02/15/2018 08:35 AM, Nadav Amit wrote:
>>> I removed the PTI disabling while SMEP is unsupported, although I
>>> must admit I did not fully understand why it is required.
>>
>> Do you mean you don't fully understand how PTI gi
On Thu, Feb 15, 2018 at 4:22 PM, Nadav Amit wrote:
>
> It is not too pretty, I agree, but it should do the work. There is only one
> problematic descriptor that can be used to switch from compatibility-mode to
> long-mode in the GDT (LDT descriptors always have the L-bit cleared).
> Changing the d
On 02/12/2018 02:20 PM, Mike Kravetz wrote:
> start_isolate_page_range() is used to set the migrate type of a
> page block to MIGRATE_ISOLATE while attempting to start a
> migration operation. It is assumed that only one thread is
> attempting such an operation, and due to the limited number of
>
On 16/02/2018 00:08, Linus Torvalds wrote:
> On Thu, Feb 15, 2018 at 3:29 PM, Andy Lutomirski wrote:
>> Linus, how would you feel about, by default, preventing 64-bit
>> programs from long-jumping to __USER32_CS and vice versa?
> How? It's a standard GDT entry. Are you going to start switching the
1 - 100 of 1436 matches
Mail list logo