Hi Philippe,
(CC'ing Daniel Vetter)
Thank you for the patch.
On Thursday, 25 January 2018 17:55:04 EET Philippe Cornu wrote:
> The "adjusted_mode" clock value (ie the real pixel clock) is more
> accurate than "mode" clock value (ie the panel/bridge requested
> clock value). It offers a better pr
On Mon, Jan 29, 2018 at 12:29:12AM +0100, Philipp Rossak wrote:
> This patch adds support for the H3 ths sensor.
>
> The H3 supports interrupts. The interrupt is configured to update the
> the sensor values every second. The calibration data is writen at the
> begin of the init process.
>
> Signe
On 01/25/2018 05:01 PM, Philippe Cornu wrote:
> There is a difference between the panel/bridge requested pixel clock
> value and the real one due to the hw platform clock preciseness (pll,
> dividers...). This patch updates the adjusted_mode clock value with
> the real hw clock value so then attach
Hi Linus, hi everyone,
Linus Torvalds - 28.01.18, 22:52:
> details), and perhaps equally importantly, to actually get the biggest
> fix for the indirect branch mitigations, you need not just the kernel
> updates, you need to have a compiler with support for the "retpoline"
> indirect branch model.
Attn
I was able to trace a huge sum of money in my department that bellongs
to our deceased customer according to my findings.I want to present
you as the beneficiary of this huge sum of money.I will give you the
full explanation as soon as you respond to this email.
Ahmed Zama
On Mon, Jan 29, 2018 at 12:29:13AM +0100, Philipp Rossak wrote:
> This patch adds support for the A83T ths sensor.
>
> The A83T supports interrupts. The interrupt is configured to update the
> the sensor values every second.
>
> Signed-off-by: Philipp Rossak
> ---
> drivers/iio/adc/sun4i-gpadc-
Hi Linus,
The following changes since commit 4fbd8d194f06c8a3fd2af1ce560ddb31f7ec8323:
Linux 4.15-rc1 (2017-11-26 16:01:47 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/geert/linux-m68k.git
tags/m68k-for-v4.16-tag1
for you to fetch ch
Hi,
On Mon, Jan 29, 2018 at 12:29:14AM +0100, Philipp Rossak wrote:
> As we have gained the support for the thermal sensor in H3 and H5,
> we can now add its device nodes to the device tree. The H3 and H5 share
> most of its compatible. The compatible and the thermal sensor cells
> will be added i
On Mon, Jan 29, 2018 at 12:29:16AM +0100, Philipp Rossak wrote:
> This patch adds the thermal zones to the H3. We have only one sensor and
> that is placed in the cpu.
>
> Signed-off-by: Philipp Rossak
> ---
> arch/arm/boot/dts/sun8i-h3.dtsi | 9 +
> 1 file changed, 9 insertions(+)
>
>
Linus,
Please pull the latest core-debug-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
core-debug-for-linus
# HEAD: 0f7cda2b824bb2afe0d75716a8664117fa03f5e0 Kconfig: Make STRICT_DEVMEM
default-y on x86 and arm64
Make CONFIG_STRICT_DEVMEM default-y on
On Mon, Jan 29, 2018 at 12:29:17AM +0100, Philipp Rossak wrote:
> This patch enables the the sid controller in the H3. It can be used
> for thermal calibration data.
>
> Signed-off-by: Philipp Rossak
> ---
> arch/arm/boot/dts/sun8i-h3.dtsi | 7 +++
> 1 file changed, 7 insertions(+)
>
> diff
On Mon, 2018-01-29 at 10:41 +0100, Martin Steigerwald wrote:
> From what I read gcc 7.3 was supposed to include back ported retpoline
> patches. What am I missing here?
Which did you update first? Kernel source or GCC?
Try removing .cache.mk which has 'remembered' that your GCC doesn't
support r
On Mon, Jan 29, 2018 at 07:57:24AM +0100, Ingo Molnar wrote:
>
> hi Paul,
>
> * Paul E. McKenney wrote:
>
> > Hello, Ingo,
> >
> > This pull request contains a single commit that adds a memory model to
> > the tools directory. This memory model can (roughly speaking) be thought
> > of as an a
On Mon, Jan 29, 2018 at 09:20:48AM +0100, Sebastian Sewior wrote:
> On 2018-01-26 14:09:17 [-0800], Paul E. McKenney wrote:
> > find this one. ;-) But it did pass rcutorture testing for a great many
> > years, didn't it? :-/
>
> It started to trigger better (or at all) on our test box with
>
Linus,
Please pull the latest core-rcu-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git core-rcu-for-linus
# HEAD: 475c5ee193fd682c6383b5e418e65e46a477d176 Merge branch 'for-mingo' of
git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu into co
Below is the list of build error/warning regressions/improvements in
v4.15[1] compared to v4.14[2].
Summarized:
- build errors: +4/-6
- build warnings: +1607/-786
JFYI, when comparing v4.15[1] to v4.15-rc9+1[3], the summaries are:
- build errors: +1/-0
- build warnings: +1225/-894
Note t
On 26 January 2018 at 14:28, Marc Zyngier wrote:
> Since PSCI 1.0 allows the SMCCC version to be (indirectly) probed,
> let's do that at boot time, and expose the version of the calling
> convention as part of the psci_ops structure.
>
> Signed-off-by: Marc Zyngier
> ---
> drivers/firmware/psci.
On 26 January 2018 at 14:28, Marc Zyngier wrote:
> In order to call into the firmware to apply workarounds, it is
> useful to find out whether we're using HVC or SMC. Let's expose
> this through the psci_ops.
>
> Signed-off-by: Marc Zyngier
> ---
> drivers/firmware/psci.c | 26 ++
On Mon, Jan 29, 2018 at 11:02 AM, Geert Uytterhoeven
wrote:
> JFYI, when comparing v4.15[1] to v4.15-rc9+1[3], the summaries are:
> - build errors: +1/-0
+ /home/kisskb/slave/src/drivers/gpu/drm/i915/selftests/i915_syncmap.c:
error: 'err' may be used uninitialized in this function
[-Werror=un
On 29/01/18 09:42, Ard Biesheuvel wrote:
> On 29 January 2018 at 09:36, Marc Zyngier wrote:
>> On 28/01/18 23:08, Ard Biesheuvel wrote:
>>> On 26 January 2018 at 14:28, Marc Zyngier wrote:
Add the detection and runtime code for ARM_SMCCC_ARCH_WORKAROUND_1.
It is lovely. Really.
>>>
On 29/01/18 10:04, Ard Biesheuvel wrote:
> On 26 January 2018 at 14:28, Marc Zyngier wrote:
>> In order to call into the firmware to apply workarounds, it is
>> useful to find out whether we're using HVC or SMC. Let's expose
>> this through the psci_ops.
>>
>> Signed-off-by: Marc Zyngier
>> ---
>
On Fri, Jan 5, 2018 at 10:17 AM, Chris Chiu wrote:
> On Wed, Dec 20, 2017 at 4:41 PM, Chris Chiu wrote:
>> Hi,
>> We've hit a suspend/resume issue on a Acer desktop caused by r8169
>> driver. The dmseg
>> https://gist.github.com/mschiu77/b741849b5070281daaead8dfee312d1a
>> shows it's still in
Hi Linus,
Here's the PR for MMC for v4.16. Details about the highlights are as usual found
in the signed tag.
Please pull this in!
Kind regards
Ulf Hansson
The following changes since commit 50c4c4e268a2d7a3e58ebb698ac74da0de40ae36:
Linux 4.15-rc3 (2017-12-10 17:56:26 -0800)
are available
2018-01-29 10:46 GMT+01:00 Yannick FERTRE :
> On 01/25/2018 05:01 PM, Philippe Cornu wrote:
>> There is a difference between the panel/bridge requested pixel clock
>> value and the real one due to the hw platform clock preciseness (pll,
>> dividers...). This patch updates the adjusted_mode clock va
>> I imagine that acceptance for these changes could be influenced
>> also by review comments from other contributors.
>
> Influenced yes, but I will also need to review them.
Yes. - This is the usual process.
> You can't 'go around' me, if that's what you're thinking.
I do not think this. - I
On 29 January 2018 at 10:07, Marc Zyngier wrote:
> On 29/01/18 09:42, Ard Biesheuvel wrote:
>> On 29 January 2018 at 09:36, Marc Zyngier wrote:
>>> On 28/01/18 23:08, Ard Biesheuvel wrote:
On 26 January 2018 at 14:28, Marc Zyngier wrote:
> Add the detection and runtime code for ARM_SMCC
Hi Laurent,
And many thanks for your comments :)
On 01/29/2018 10:46 AM, Laurent Pinchart wrote:
> Hi Philippe,
>
> (CC'ing Daniel Vetter)
>
> Thank you for the patch.
>
> On Thursday, 25 January 2018 17:55:04 EET Philippe Cornu wrote:
>> The "adjusted_mode" clock value (ie the real pixel clo
When opening a device with write access, ubiblock_open returns an error
code. Currently, this error code is -EPERM, but this is not the right
value.
The open function for other block devices returns -EROFS when opening
read-only devices with FMODE_WRITE set. When used with dm-verity, the
verityset
On 2018/01/26 09:03, Alexander Duyck wrote:
> On Fri, Jan 26, 2018 at 1:12 AM, Benjamin Poirier wrote:
> > This reverts commit 19110cfbb34d4af0cdfe14cd243f3b09dc95b013.
> > This reverts commit 4110e02eb45ea447ec6f5459c9934de0a273fb91.
> >
> > ... because they cause an extra 2s delay for the link t
On Mon 29-01-18 06:30:55, Naoya Horiguchi wrote:
> My apology, I forgot to CC to the mailing lists.
>
> On Mon, Jan 29, 2018 at 03:28:03PM +0900, Naoya Horiguchi wrote:
> > Recently the following BUG was reported:
> >
> > Injecting memory failure for pfn 0x3c at process virtual address
>
On Mon, Jan 29, 2018 at 05:18:53PM +0800, Yong Deng wrote:
> Add binding documentation for Allwinner V3s CSI.
>
> Reviewed-by: Rob Herring
> Signed-off-by: Yong Deng
Acked-by: Maxime Ripard
Thanks!
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux and Kernel engineering
http://free-ele
From: Tung Nguyen
Currently, hcd->shared_hcd always creates and registers to the usb-core.
If, for some reasons, USB3 downstream port is disabled, no roothub port for
USB3.0 is found. This causes kernel to display an error:
hub 2-0:1.0: config failed, hub doesn't have any ports! (err -19)
This pa
Hi Kieran,
Thank you for the patch.
On Monday, 22 January 2018 14:50:00 EET Kieran Bingham wrote:
> The ADV7511 has four 256-byte maps that can be accessed via the main I²C
> ports. Each map has it own I²C address and acts as a standard slave
> device on the I²C bus.
>
> Allow a device tree node
On Mon, Jan 29, 2018 at 10:25:21AM +0100, ufo19890607 wrote:
> From: yuzhoujian
>
> Introduce two new options for perf stat and update perf-stat documentation
> accordingly.
>
> The interval-count option can be used to print counts for fixed number of
> times, and it should be used specifically
On Fri, Jan 26, 2018 at 06:11:49PM +, Will Deacon wrote:
> On Fri, Jan 26, 2018 at 12:05:42PM +0300, Yury Norov wrote:
> > On Wed, Jan 24, 2018 at 10:22:13AM +, Will Deacon wrote:
> > > On Wed, Jan 24, 2018 at 12:05:16PM +0300, Yury Norov wrote:
> > > > This series adds API for 128-bit memo
On Sun, Jan 28, 2018 at 02:55:28PM +0900, Tetsuo Handa wrote:
> This warning seems to be caused by commit d92a8cfcb37ecd13
> ("locking/lockdep: Rework FS_RECLAIM annotation") which moved the
> location of
>
> /* this guy won't enter reclaim */
> if ((current->flags & PF_MEMALLOC) && !(gfp_mask
> Okay, applied to for-next, thanks both
Thanks for your acceptance.
How are the chances for integration of further software updates
from my selection of change possibilities?
Example:
IB/iser: Add spaces for better code readability
https://lkml.org/lkml/2017/4/7/667
https://patchwork.kernel.org
On 27.01.2018 09:50, Paolo Bonzini wrote:
> Group together the calls to alloc_vmcs and loaded_vmcs_init. Soon we'll also
> allocate an MSR bitmap there.
>
> Signed-off-by: Paolo Bonzini
> ---
> arch/x86/kvm/vmx.c | 36 ++--
> 1 file changed, 22 insertions(+), 14
Em Mon, Jan 29, 2018 at 02:04:17PM +0530, Ravi Bangoria escreveu:
> +++ b/tools/perf/util/syscalltbl.c
> @@ -30,6 +30,10 @@
> #include
> const int syscalltbl_native_max_id = SYSCALLTBL_S390_64_MAX_ID;
> static const char **syscalltbl_native = syscalltbl_s390_64;
> +#elif defined(__powerpc64__)
Linus,
Please pull the latest efi-core-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git efi-core-for-linus
# HEAD: a5c03c31af2291f13689d11760c0b59fb70c9a5a x86/efi: Clarify that reset
attack mitigation needs appropriate userspace
The biggest change in th
On 29/01/2018 05:02, Stephen Rothwell wrote:
> Hi all,
>
> On Wed, 17 Jan 2018 13:53:26 +0100 (CET) Thomas Gleixner
> wrote:
>>
>> On Wed, 17 Jan 2018, Stephen Rothwell wrote:
>>> On Wed, 17 Jan 2018 13:23:17 +0100 (CET) Thomas Gleixner
>>> wrote:
No. Keep it and lets next time coordina
On 27.01.2018 09:50, Paolo Bonzini wrote:
> Place the MSR bitmap in struct loaded_vmcs, and update it in place
> every time the x2apic or APICv state can change. This is rare and
> the loop can handle 64 MSRs per iteration, in a similar fashion as
> nested_vmx_prepare_msr_bitmap.
>
> This prepare
Linus,
Please pull the latest locking-core-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
locking-core-for-linus
# HEAD: 05b93801a23c21a6f355f4c492c51715d6ccc96d lockdep: Convert some users
to const
The main changes relate to making lock_is_held() et
On Thu, Jan 04, 2018 at 11:42:18AM +0530, Jagan Teki wrote:
> Series add LVDS panel attributes on panel drivers instead of defining
> them in dts nodes, and also added new icorem6 engicam boards
>
> Jagan Teki (7):
> drm/panel: simple: add support for Ampire AM-800480AYTZQW-00H
> ARM: dts: imx
On 29/01/2018 01:58, KarimAllah Ahmed wrote:
> Cc: Paolo Bonzini
> Cc: Radim Krčmář
> Cc: Thomas Gleixner
> Cc: Ingo Molnar
> Cc: H. Peter Anvin
> Cc: x...@kernel.org
> Cc: k...@vger.kernel.org
> Cc: linux-kernel@vger.kernel.org
> Signed-off-by: KarimAllah Ahmed
> ---
> arch/x86/kvm/cpuid.h
Hi Frank,
On Mon, Jan 29, 2018 at 3:53 AM, wrote:
> From: Frank Rowand
>
> The unittest-data overlays have been pulled into proper overlay
> devicetree source files without changing their format. The
> next step is to convert them to use sugar syntax instead of
> hand coding overlay fragments
On Mon, 2018-01-29 at 10:43 +0100, KarimAllah Ahmed wrote:
> On 01/29/2018 09:46 AM, David Woodhouse wrote:
> > Reading the code and comparing with the SDM, I can't see where we're
> > ever setting VM_EXIT_MSR_STORE_{ADDR,COUNT} except in the nested
> > case...
> Hmmm ... you are probably right! I
On Sun, Jan 28, 2018 at 01:31:48PM +0800, weiping zhang wrote:
> if use -G with one cgroup and -e with multiple events, only the first
> event has correct cgroup setting, all events from the second will track
> system-wide events.
>
> if user want track multiple events for a specific cgroup, user
On Fri, Jan 05, 2018 at 03:51:44AM +0800, Anson Huang wrote:
> Select CONFIG_CPUFREQ_DT by default to enable
> cpu-freq driver for i.MX7D.
>
> Signed-off-by: Anson Huang
Applied, thanks.
Hi Philippe,
On Monday, 29 January 2018 12:17:37 EET Philippe CORNU wrote:
> On 01/29/2018 10:46 AM, Laurent Pinchart wrote:
> > On Thursday, 25 January 2018 17:55:04 EET Philippe Cornu wrote:
> >
> >> The "adjusted_mode" clock value (ie the real pixel clock) is more
> >> accurate than "mode" clo
David Woodhouse - 29.01.18, 10:53:
> On Mon, 2018-01-29 at 10:41 +0100, Martin Steigerwald wrote:
> > From what I read gcc 7.3 was supposed to include back ported retpoline
> > patches. What am I missing here?
>
> Which did you update first? Kernel source or GCC?
Kernel source is existing git re
Hi Philippe,
On Thursday, 25 January 2018 18:01:01 EET Philippe Cornu wrote:
> There is a difference between the panel/bridge requested pixel clock
> value and the real one due to the hw platform clock preciseness (pll,
> dividers...). This patch updates the adjusted_mode clock value with
> the re
On 29/01/2018 01:58, KarimAllah Ahmed wrote:
> Add direct access to MSR_IA32_SPEC_CTRL for guests. This is needed for
> guests that will only mitigate Spectre V2 through IBRS+IBPB and will not
> be using a retpoline+IBPB based approach.
>
> To avoid the overhead of atomically saving and restoring
On 29/01/2018 01:58, KarimAllah Ahmed wrote:
> Add direct access to MSR_IA32_SPEC_CTRL for guests. Future intel processors
> will use this MSR to indicate RDCL_NO (bit 0) and IBRS_ALL (bit 1).
This has to be customizable per-VM (similar to the patches Amazon posted
a while ago for UCODE_REV for ex
On Fri 26-01-18 16:17:35, Andrew Morton wrote:
> On Fri, 26 Jan 2018 14:52:59 -0800 (PST) David Rientjes
> wrote:
[...]
> > Those use cases are also undocumented such that the user doesn't know the
> > behavior they are opting into. Nowhere in the patchset does it mention
> > anything about oo
2018-01-29 11:43 GMT+01:00 Laurent Pinchart :
> Hi Philippe,
>
> On Thursday, 25 January 2018 18:01:01 EET Philippe Cornu wrote:
>> There is a difference between the panel/bridge requested pixel clock
>> value and the real one due to the hw platform clock preciseness (pll,
>> dividers...). This pat
On 29/01/2018 09:46, David Woodhouse wrote:
> I'd actually quite like to repeat the benchmark on the new fixed
> microcode, if anyone has it yet, to see if that read/swap slowness is
> still quite as excessive. I'm certainly not ruling this out, but I'm
> just a little wary of premature optimisatio
On 26 January 2018 at 21:16, Matt Fleming wrote:
> On Thu, 18 Jan, at 01:01:04PM, Sai Praneeth Prakhya wrote:
>> From: Sai Praneeth
>>
>> Presently, in x86, to invoke any efi function like
>> efi_set_virtual_address_map() or any efi_runtime_service() the code path
>> typically involves read_cr3()
Hi Linus,
Please pull these hardened usercopy changes for v4.16-rc1. This is very
close to what I sent for v4.15, though now it has a couple more Acks,
I reorganized the WARN-by-default to be earlier in the series where
hopefully it stands out better, and I improved reporting (while also
dropping
On 29/01/2018 11:37, David Woodhouse wrote:
> On Mon, 2018-01-29 at 10:43 +0100, KarimAllah Ahmed wrote:
>> On 01/29/2018 09:46 AM, David Woodhouse wrote:
>>> Reading the code and comparing with the SDM, I can't see where we're
>>> ever setting VM_EXIT_MSR_STORE_{ADDR,COUNT} except in the nested
>>
Linus,
Please pull the latest perf-core-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git perf-core-for-linus
# HEAD: e4c1091cb495d9cbec8956d642644a71a1689958 Merge tag
'perf-core-for-mingo-4.16-20180125' of
git://git.kernel.org/pub/scm/linux/kernel/git/a
Hi Linus,
Please pull this tiny pstore change for v4.16-rc1. Only a header cleanup
this release; nice and quiet. :)
Thanks!
-Kees
The following changes since commit 4fbd8d194f06c8a3fd2af1ce560ddb31f7ec8323:
Linux 4.15-rc1 (2017-11-26 16:01:47 -0800)
are available in the git repository at:
Hi Jacopo,
Thank you for the patch.
On Friday, 26 January 2018 15:55:26 EET Jacopo Mondi wrote:
> Add support to ov772x driver for frame intervals handling and enumeration.
> Tested with 10MHz and 24MHz input clock at VGA and QVGA resolutions for
> 10, 15 and 30 frame per second rates.
>
> Signe
Linus,
Please pull the latest ras-core-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git ras-core-for-linus
# HEAD: 179eb850ac57c06edaed67fc744ba9d902172f96 x86/MCE: Make correctable
error detection look at the Deferred bit
The main changes:
- Various A
Linus,
Please pull the latest sched-core-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
sched-core-for-linus
# HEAD: 07881166a892fa4908ac4924660a7793f75d6544 sched/deadline: Make
bandwidth enforcement scale-invariant
The main changes in this cycle wer
I've missed that we need to change relocate_kernel() to set CR4.LA57
flag if the kernel has 5-level paging enabled.
I avoided to use ifdef CONFIG_X86_5LEVEL here and inferred if we need to
enabled 5-level paging from previous CR4 value. This way the code is
ready for boot-time switching between pa
Linus,
Please pull the latest x86-apic-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-apic-for-linus
# HEAD: 03dd604e1d515ca1ab02aaae12162e0a077858e9 x86/apic: Remove local var
in flat_send_IPI_allbutself()
A single change simplifying the APIC code
Linus,
Please pull the latest x86-cleanups-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
x86-cleanups-for-linus
# HEAD: 782bf20c2a1795f35dcd526aa8005cd1870745da x86: Remove unused
IOMMU_STRESS Kconfig
Misc cleanups.
Thanks,
Ingo
-
On 01/29/18 at 02:08pm, Kirill A. Shutemov wrote:
> I've missed that we need to change relocate_kernel() to set CR4.LA57
> flag if the kernel has 5-level paging enabled.
>
> I avoided to use ifdef CONFIG_X86_5LEVEL here and inferred if we need to
> enabled 5-level paging from previous CR4 value. T
Martin Steigerwald - 29.01.18, 11:42:
> > Try removing .cache.mk which has 'remembered' that your GCC doesn't
> > support retpoline.
>
> I bet there have been "*.cache.mk" files around from previous pre gcc-7.3
> compiles.
>
> Trying again after
>
> % find -name ".cache.mk" -delete
>
> on kerne
On 01/26/2018 07:02 AM, Alexandre Courbot wrote:
> Howdy. Here is your bi-weekly request API redesign! ;)
>
> Again, this is a simple version that only implements the flow of requests,
> without applying controls. The intent is to get an agreement on a base to work
> on, since the previous version
Linus,
Please pull the latest x86-hyperv-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
x86-hyperv-for-linus
# HEAD: 617ab45c9a8900e64a78b43696c02598b8cad68b x86/hyperv: Stop
suppressing X86_FEATURE_PCID
Enable PCID support on Hyper-V guests.
Thanks
When commit b27311e1cace ("MIPS: TXx9: Add RBTX4939 board support")
added board support for the RBTX4939, it added a call to
led_classdev_register even if the LED class is built as a module.
Built-in arch code cannot call module code directly like this. Commit
b33b44073734 ("MIPS: TXX9: use IS_ENAB
Hi Linus,
please pull the EDAC updates from this round.
Thanks.
---
The following changes since commit 4fbd8d194f06c8a3fd2af1ce560ddb31f7ec8323:
Linux 4.15-rc1 (2017-11-26 16:01:47 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/bp/bp.git tags/
On Mon, Jan 29, 2018 at 08:34:00AM +0100, Code Kipper wrote:
> I'm not sure..I was looking for a clean example of being able to
> override the number of bclks in the lrclk width and some other
> devices(Rpi) were doing it this way. I open to suggestions,
You're looking for set_bclk_ratio() I thi
The 'mms114_read_reg' and 'mms114_write_reg' are used when
reading or writing to the 'MMS114_MODE_CONTROL' register for
updating the 'cache_mode_control' variable.
Update the 'cache_mode_control' variable in the calling
mms114_set_active() function and get rid of all the custom i2c
read/write func
Hi Dmitry,
this patchset contains some cleanups for the mms114 driver. The
first two patches are the most important because they get rid of
the custom i2c read/write functions and use the smbus instead.
The others come from a "cleanup rush" I felt into.
I tested the patchest on the mms114 touchs
200ms seconds is a very long time to keep the CPU busy looping.
Use msleep instead.
Signed-off-by: Andi Shyti
---
drivers/input/touchscreen/mms114.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/input/touchscreen/mms114.c
b/drivers/input/touchscreen/mms114.c
index
Hi Michael,
Quoting Michael Ellerman :
On Wed, 2018-01-24 at 01:42:28 UTC, "Gustavo A. R. Silva" wrote:
Change the data type of the following variables from int to bool
across all macintosh drivers:
started
slots_started
pm121_started
wf_smu_started
Some of these issues were detected with th
The exchange of data to and from the mms114 touchscreen never
exceeds 256 bytes. In the worst case it goes up to 80 bytes in
the interrupt handler while reading the events.
Thus it's not needed to make use of custom read/write functions
for accessing the i2c. Replace, whenever possible, the use of
Signed-off-by: Andi Shyti
---
drivers/input/touchscreen/mms114.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/input/touchscreen/mms114.c
b/drivers/input/touchscreen/mms114.c
index fdf23bc416af..d70c03adf148 100644
--- a/drivers/input/touchscreen/mms114.c
+++ b/driv
'__packed' is not used anywhere, remove it.
Signed-off-by: Andi Shyti
---
drivers/input/touchscreen/mms114.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/input/touchscreen/mms114.c
b/drivers/input/touchscreen/mms114.c
index fb4435ae506b..11dba8bb48e3 100644
--- a/
Signed-off-by: Andi Shyti
---
drivers/input/touchscreen/mms114.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/drivers/input/touchscreen/mms114.c
b/drivers/input/touchscreen/mms114.c
index 11dba8bb48e3..fdf23bc416af 100644
--- a/drivers/input/touchscreen/mms114.c
Replace the original license statement with the SPDX identifier.
Signed-off-by: Andi Shyti
---
drivers/input/touchscreen/mms114.c | 13 +
1 file changed, 5 insertions(+), 8 deletions(-)
diff --git a/drivers/input/touchscreen/mms114.c
b/drivers/input/touchscreen/mms114.c
index d70c0
It's 'MMS114_INFORMATION', not 'MMS114_INFOMATION'
Signed-off-by: Andi Shyti
---
drivers/input/touchscreen/mms114.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/input/touchscreen/mms114.c
b/drivers/input/touchscreen/mms114.c
index 3230c92de1ed..5b609531b3aa 10
On Mon, 2018-01-29 at 12:19 +0100, Martin Steigerwald wrote:
>
> The whole thing works:
>
> % grep . /sys/devices/system/cpu/vulnerabilities/*
>
> /sys/devices/system/cpu/vulnerabilities/meltdown:Mitigation: PTI
> /sys/devices/system/cpu/vul
On 28.01.2018 23:43, Paul Menzel wrote:
Dear Linux folks,
Using Linux 4.15-rc9+ with KASAN enabled on the TUXEDO Book 1406, playing with
Bluetooth – disabling a device – I was able to trigger the warning below.
Thanks, first guess is that btusb calls usb_set_interface() with URBs still
sch
Peter Zijlstra wrote:
> On Sun, Jan 28, 2018 at 02:55:28PM +0900, Tetsuo Handa wrote:
> > This warning seems to be caused by commit d92a8cfcb37ecd13
> > ("locking/lockdep: Rework FS_RECLAIM annotation") which moved the
> > location of
> >
> > /* this guy won't enter reclaim */
> > if ((current
These patcheset is a preparation for boot-time switching between paging
modes. Please apply.
The first patch is pure cosmetic change: it gives file with KASLR helpers
a proper name.
The last three patches bring support of booting into 5-level paging mode if
a bootloader put the kernel above 4G.
On 29.01.2018 10:48, Maxime Ripard wrote:
On Mon, Jan 29, 2018 at 12:29:13AM +0100, Philipp Rossak wrote:
This patch adds support for the A83T ths sensor.
The A83T supports interrupts. The interrupt is configured to update the
the sensor values every second.
Signed-off-by: Philipp Rossak
--
This patch renames l5_paging_required() into paging_prepare() and
changes the interface of the function.
This is a preparation for the next patch, which would make the function
also allocate memory for the 32-bit trampoline.
The function now returns a 128-bit structure. RAX would return
trampolin
The name of the file -- pagetable.c -- is misleading: it only contains
helpers used for KASLR in 64-bit mode.
Let's rename the file to reflect its content.
Signed-off-by: Kirill A. Shutemov
---
arch/x86/boot/compressed/Makefile| 2 +-
arch/x86/boot/compressed/{pagetable.c =>
On 29.01.2018 10:49, Maxime Ripard wrote:
Hi,
On Mon, Jan 29, 2018 at 12:29:14AM +0100, Philipp Rossak wrote:
As we have gained the support for the thermal sensor in H3 and H5,
we can now add its device nodes to the device tree. The H3 and H5 share
most of its compatible. The compatible and t
This patch addresses a shortcoming in current boot process on machines
that supports 5-level paging.
If a bootloader enables 64-bit mode with 4-level paging, we might need to
switch over to 5-level paging. The switching requires the disabling
paging. It works fine if kernel itself is loaded below
From: Tim Chen
Flush indirect branches when switching into a process that marked itself
non dumpable. This protects high value processes like gpg better,
without having too high performance overhead.
If done naïvely, we could switch to a kernel idle thread and then back
to the original process,
Hi Jacopo,
On Friday, 26 January 2018 18:24:54 EET jacopo mondi wrote:
> On Thu, Jan 25, 2018 at 03:39:32PM +0100, Geert Uytterhoeven wrote:
> > Hi Jacopo,
>
> [snip]
>
> ---
>
> drivers/sh/clk/core.c | 9 ++---
> 1 file changed, 6 insertions(+), 3 deletions(-)
>
On 29.01.2018 10:50, Maxime Ripard wrote:
On Mon, Jan 29, 2018 at 12:29:16AM +0100, Philipp Rossak wrote:
This patch adds the thermal zones to the H3. We have only one sensor and
that is placed in the cpu.
Signed-off-by: Philipp Rossak
---
arch/arm/boot/dts/sun8i-h3.dtsi | 9 +
1
When I tried to use devm_ioremap function and review related
code, I found devm_ioremap_* almost have the similar realize
with each other, which can be combined.
In the former version, I have tried to kill ioremap_cache to
reduce the size of devres, which can not work for ioremap is
not the same a
On Mon, Jan 29, 2018 at 02:08:45PM +0300, Kirill A. Shutemov wrote:
> I've missed that we need to change relocate_kernel() to set CR4.LA57
> flag if the kernel has 5-level paging enabled.
>
> I avoided to use ifdef CONFIG_X86_5LEVEL here and inferred if we need to
> enabled 5-level paging from pre
[ Dropping large CC list ]
On 25/01/2018 18:16, Greg Kroah-Hartman wrote:
> On Thu, Jan 25, 2018 at 05:19:04PM +0100, Mason wrote:
>
>> On 23/01/2018 10:30, David Woodhouse wrote:
>>
>>> Skylake takes predictions from the generic branch target buffer when
>>> the RSB underflows.
>>
>> Adding LAK
101 - 200 of 1013 matches
Mail list logo
