The patch
ASoC: add mclk-fs support to audio graph card
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) and sent
On Fri, 10 Nov 2017, Linus Torvalds wrote:
> On Wed, Nov 8, 2017 at 9:19 PM, Fengguang Wu wrote:
> >
> > Yes it's accessing the list. Here is the faddr2line output.
>
> Ok, so it's a corrupted timer list. Which is not a big surprise.
>
> It's
>
>
Test the new MEMBARRIER_CMD_PRIVATE_EXPEDITED and
MEMBARRIER_CMD_REGISTER_PRIVATE_EXPEDITED commands.
Add checks expecting specific error values on system calls expected to
fail.
Signed-off-by: Mathieu Desnoyers
Acked-by: Shuah Khan
Test the new MEMBARRIER_CMD_PRIVATE_EXPEDITED_SYNC_CORE and
MEMBARRIER_CMD_REGISTER_PRIVATE_EXPEDITED_SYNC_CORE commands.
Signed-off-by: Mathieu Desnoyers
CC: Shuah Khan
CC: Greg Kroah-Hartman
CC: Peter
Provide core serializing membarrier command to support memory reclaim
by JIT.
Each architecture needs to explicitly opt into that support by
documenting in their architecture code how they provide the core
serializing instructions required when returning from the membarrier
IPI, and after the
From: Dave Hansen
KAISER has two copies of the page tables: one for the kernel and
one for when running in userspace. There is also a kernel
portion of each of the page tables: the part that *maps* the
kernel.
The kernel portion is relatively static and uses
From: Dave Hansen
All of the interrupt entry/exit code is in a special section
(.irqentry.text). This enables the ftrace code to figure out
when the kernel is executing in the "grey area" of interrupt
handling before the C code has taken over and marked the data
From: Dave Hansen
The IDT is another structure which the CPU references via a
virtual address. It also obviously needs these to handle an
interrupt in userspace, so these need to be mapped into the user
copy of the page tables.
Signed-off-by: Dave Hansen
From: Dave Hansen
If changing the page tables in such a way that an invalidation of
all contexts (aka. PCIDs / ASIDs) is required, they can be
actively invalidated by:
1. INVPCID for each PCID (works for single pages too).
2. Load CR3 with each PCID without the
From: Dave Hansen
If you paravirtualize the MMU, you can not use KAISER. This boils down
to the fact that KAISER needs to do CR3 writes in places that it is not
feasible to do real hypercalls.
If Xen PV is detected to be in use, do not do the KAISER CR3 switches.
From: Dave Hansen
With KAISER Kernel PGDs that map userspace are "poisoned" with
the NX bit. This ensures that if a kernel->user CR3 switch is
missed, userspace crashes instead of running in an unhardened
state.
This code will be needed in a moment when KAISER is
From: Dave Hansen
This is largely code from Andy Lutomirski. I fixed a few bugs
in it, and added a few SWITCH_TO_* spots.
KAISER needs to switch to a different CR3 value when it enters
the kernel and switch back when it exits. This essentially
needs to be done
From: Dave Hansen
init_mm is for kernel-exclusive use. If someone is allocating page
tables for it, do not set _PAGE_USER on them.
Signed-off-by: Dave Hansen
Reviewed-by: Thomas Gleixner
Cc: Moritz Lipp
From: Dave Hansen
Normally, a process has a NULL mm->context.ldt. But, there is a
syscall for a process to set a new one. If a process does that,
the LDT be mapped into the user page tables, just like the
default copy.
The original KAISER patch missed this case.
From: Dave Hansen
The KAISER code attempts to "poison" the user portion of the kernel page
tables. It detects entries that it wants that it wants to poison in two
ways:
* Looking for addresses >= PAGE_OFFSET
* Looking for entries without _PAGE_USER set
But, to
From: Dave Hansen
Global pages stay in the TLB across context switches. Since all contexts
share the same kernel mapping, these mappings are marked as global pages
so kernel entries in the TLB are not flushed out on a context switch.
But, even having these entries
These patches are based on work from a team at Graz University of
Technology posted here: https://github.com/IAIK/KAISER
The KAISER approach keeps two copies of the page tables: one for running
in the kernel and one for running userspace. But, there are a few
structures that are needed for
On Fri, Nov 10, 2017 at 7:25 AM, Arnd Bergmann wrote:
> I noticed that __getnstimeofday() is a rather odd interface, with
> a number of quirks:
>
> - The caller may come from NMI context, but the implementation is not NMI
> safe,
> one way to get there from NMI is
>
> NMI
Thanks, everyone for all the reviews thus far. I hope I managed to
address all the feedback given so far, except for the TODOs of
course. This is a pretty minor update compared to v1->v2.
These patches are all on top of Andy's entry changes here:
> Andi's idea would work and the code would become much cleaner, if
> smp_store_cpu_info() only overwrote cpu_data for new physically hotplugged
> cpus.
Can always just use a separate per_cpu variable for this that is not cleared.
-Andi
On Fri, 2017-11-10 at 20:35 +0100, Luis R. Rodriguez wrote:
> On Fri, Nov 10, 2017 at 12:58:23PM -0500, Mimi Zohar wrote:
> > Hi David,
> >
> > If you are interested in preventing the loading of unsigned firmware,
> > the patch below is straight forward. The patch has ONLY been tested
> > with
Dear user
Your mailbox has exceeded the 20GB storage limit set by the administrator, you
are currently running at 20.9 GB, you can not send or receive new messages
until you check your mailbox. Re-validate your account by mail, fill the
following information below and send to us to verify and
From: Markus Elfring
Date: Fri, 10 Nov 2017 20:50:15 +0100
Adjust jump targets so that a bit of exception handling can be better
reused at the end of this function.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
On Thu, Nov 9, 2017 at 1:49 PM, wrote:
>
> (Result of code inspection only, i do not have a bug, nor know a bug
> that would be explain by this issue. Is there a kernel trace database
> one can query for that ?)
This is intentional.
See the comment above the code you added:
On Fri, 10 Nov 2017, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Fri, 10 Nov 2017 20:50:15 +0100
>
> Adjust jump targets so that a bit of exception handling can be better
> reused at the end of this function.
Unless there is a strong motivation for
On Wed, Nov 08, 2017 at 03:39:44PM +0100, Christophe Leroy wrote:
> The watchdog core includes a worker function which pings the
> watchdog until user app starts pinging it and which also
> pings it if the HW require more frequent pings.
> Use that function instead of the dedicated timer.
> In the
x86 can return to user-space through sysexit and sysretq, which are not
core serializing. This breaks expectations from user-space about
sequential consistency from a single-threaded self-modifying program
point of view in specific migration patterns.
Feedback is welcome,
Thanks,
Mathieu
On Fri, Nov 10, 2017 at 02:36:04PM +0800, Chunyan Zhang wrote:
> This file defines all SC9860 clock indexes, it should be included in the
> device tree in which there's device using the clocks.
>
> Signed-off-by: Chunyan Zhang
> ---
>
> When a file does not have a license, again, all lawyers I have worked
> with said it is implicitly GPLv2
I am surprised that they did not immediately see the fact that since the
code contributor was not neccessarily the rights holder you could make no
assumption as to the actual licencing
On Fri, Nov 10, 2017 at 01:57:11PM -0600, Andrew F. Davis wrote:
This looks mostly good, a few small issues though:
> + dev_info(>dev, "%s() i2c->addr=%d\n", __func__, i2c->addr);
No need for this as standard, we already have I2C level logging
facilities if they're really needed. It's OK
On Tue, Nov 07, 2017 at 10:10:20PM +0800, Yixun Lan wrote:
> From: Xingyu Chen
>
> Update the doc as the SAR ADC modules doesn't require "sana" clock.
>
> Singed-off-by: Xingyu Chen
> Signed-off-by: Yixun Lan
> ---
>
On 11/09/2017 03:56 PM, Paul E. McKenney wrote:
> On Thu, Nov 09, 2017 at 03:13:24PM -0500, Jason Baron wrote:
>> On 11/08/2017 02:01 AM, Fengguang Wu wrote:
>>> On Tue, Nov 07, 2017 at 05:17:38PM -0500, Jason Baron wrote:
On 11/07/2017 04:27 AM, Fengguang Wu wrote:
> Hello,
2017-11-10 10:49+0100, Paolo Bonzini:
> Sometimes, a processor might execute an instruction while another
> processor is updating the page tables for that instruction's code page,
> but before the TLB shootdown completes. The interesting case happens
> if the page is in the TLB.
>
> In general,
Dear all,
This is an attempt to revive some patches from that [1] patchset, some
of them are still under discussion but I think there is no reason to not
have the other two in this fourth version to land upstream meanwhile we
discuss about the others.
[1] https://lkml.org/lkml/2017/7/12/182
rockchip_usb2phy_probe() does not disable clock in case of failure in
devm_of_phy_provider_register() and it ignores if clk_prepare_enable() fails.
Found by Linux Driver Verification project (linuxtesting.org).
Signed-off-by: Alexey Khoroshilov
---
From: Stephen Barber
On platforms with a Chrome OS EC, the EC can function as a simple RTC.
Add a basic driver with this functionality.
Signed-off-by: Stephen Barber
Signed-off-by: Enric Balletbo i Serra
Acked-by:
From: Stephen Barber
The EC can function as a simple RT, this patch adds the RTC related
definitions needed by the rtc-cros-ec driver.
Signed-off-by: Stephen Barber
Signed-off-by: Enric Balletbo i Serra
Acked-by: Lee
- On Nov 10, 2017, at 4:36 PM, Linus Torvalds torva...@linux-foundation.org
wrote:
> On Fri, Nov 10, 2017 at 1:12 PM, Mathieu Desnoyers
> wrote:
>> x86 can return to user-space through sysexit and sysretq, which are not
>> core serializing. This breaks
On Thu, Nov 9, 2017 at 2:30 PM, Rafael J. Wysocki wrote:
>
> c_start() can run aperfmperf_snapshot_khz() on all CPUs upfront (say
> in parallel), then wait for a while (say 5 ms; the current 20 ms wait
> is overkill) and then aperfmperf_snapshot_khz() can be run once on
> each
From: Dave Hansen
There are times where the kernel is entered but there is not a
safe stack, like at SYSCALL entry. To obtain a safe stack, the
per-cpu variables 'rsp_scratch' and 'cpu_current_top_of_stack'
are used to save the old %rsp value and to find where the
From: Dave Hansen
There is some rather arcane code to help when an IRET returns
to 16-bit segments. It is referred to as the "espfix" code.
This consists of a few per-cpu variables:
espfix_stack: tells us where the stack is allocated
On Fri, Nov 10, 2017 at 12:58:23PM -0500, Mimi Zohar wrote:
> Hi David,
>
> If you are interested in preventing the loading of unsigned firmware,
> the patch below is straight forward. The patch has ONLY been tested
> with IMA-appraisal enabled, and works as intended - allowing only
> signed
From: Dave Hansen
The GDT is used to control the x86 segmentation mechanism. It
must be virtually mapped when switching segments or at IRET
time when switching between userspace and kernel.
The original KAISER patch did not do this. I have no idea how
it ever
From: Hugh Dickins
[Dave] Add explicit _PAGE_GLOBAL
[Dave] remove KAISER #ifdefs by moving kmalloc() to plain page allocator
[Dave] reword the commit message a bit to be consistent with other patches
The BTS and PEBS buffers both have their virtual addresses
programmed into
On Fri, Nov 10, 2017 at 7:58 AM, Arnd Bergmann wrote:
> twl_aen_queue_event/twa_aen_queue_event, we use do_gettimeofday()
> to read the lower 32 bits of the current time in seconds, to pass
> them to the TW_IOCTL_GET_NEXT_EVENT ioctl or the 3ware_aen_read
> sysfs file.
>
> This
On Thu, Nov 9, 2017 at 8:45 PM, NeilBrown wrote:
>
> However your description of what it was that you didn't like gave me an
> idea - I can take the same approach as my original, but not pass flags
> around.
> I quite like how this turned out.
> Dropping the BUG_ON() in d_rehash()
From: Andreas Dannenberg
This is an initial version of the PCM186x codec driver supporting both
2-channel and 4-channel device variants. Not all device features are
supported yet such as master/slave mode PLL configuration for which the
codec driver currently relies on the
Add the dt-binding documentation for the TI PCM186x 2ch and 4ch Audio
ADCs With Universal Front End.
Signed-off-by: Andrew F. Davis
---
.../devicetree/bindings/sound/pcm186x.txt | 42 ++
1 file changed, 42 insertions(+)
create mode 100644
Following my recent transition from Imagination Technologies to the
reincarnated MIPS company add a .mailmap mapping for my work address,
so that `scripts/get_maintainer.pl' gets it right for past commits.
Signed-off-by: Maciej W. Rozycki
---
Linus, I hope this is something
From: Markus Elfring
Date: Fri, 10 Nov 2017 21:21:12 +0100
Two update suggestions were taken into account
from static source code analysis.
Markus Elfring (2):
Use common error handling code in trusted_update()
Use common error handling code in tpm_unseal()
On Fri, Nov 10, 2017 at 12:26 PM, Luis R. Rodriguez wrote:
> even if you *leave* the flag in place and a driver required
> this, but the kernel was compiled without CONFIG_FW_LOADER_USER_HELPER then
> calling fw_load_from_user_helper would just already return -ENOENT, as such
On 07.11.2017 18:29, Dmitry Osipenko wrote:
> On 07.11.2017 16:11, Mikko Perttunen wrote:
>> On 05.11.2017 19:14, Dmitry Osipenko wrote:
>>> On 05.11.2017 14:01, Mikko Perttunen wrote:
Add an option to host1x_channel_request to interruptibly wait for a
free channel. This allows IOCTLs
On Tue, Nov 07, 2017 at 09:52:15PM -0600, David Lechner wrote:
> This adds a new binding for display panels that use an Ilitek ILI9225
> controller.
>
> The "generic,2.2in-176x220-ili9225-tft" device listed has no identification
> markings whatsoever and an hour of googling turned up nothing,
Applied all three, thanks.
On Wed, Nov 08, 2017 at 04:26:15PM +0800, andy.t...@nxp.com wrote:
> From: Yuantian Tang
>
> More divider clocks are needed by IP. So enlarge the PLL divider
> array to accommodate more divider clocks.
>
> Signed-off-by: Tang Yuantian
> ---
>
2017-11-06 14:38-0600, Janakarajan Natarajan:
> I forgot to add Boris's Reviewed-by Tag. If the patchset is acceptable,
> please let me know if I should send another version with the Tag or if
> the Tag can be added when it is merged.
No problem, I have added that while applying, thanks for
On Thu, Nov 9, 2017 at 10:31 PM, Dave Hansen
wrote:
> On 11/09/2017 06:25 PM, Andy Lutomirski wrote:
>> Here are two proposals to address this without breaking vsyscalls.
>>
>> 1. Set NX on low mappings that are _PAGE_USER. Don't set NX on high
>> mappings but,
The name of the file -- pagetable.c -- is misleading: it only contains
helpers used for KASLR in 64-bin mode.
Let's rename the file to reflect its content.
Signed-off-by: Kirill A. Shutemov
---
arch/x86/boot/compressed/Makefile| 2 +-
Hi Ingo,
Here's updated changes that prepare the code to boot-time switching between
paging modes and handle booting in 5-level mode when bootloader put kernel
image above 4G, but haven't enabled 5-level paging for us.
I've updated patches based on your feedback.
Please review and consider
On 11/10/2017 1:02 PM, Mimi Zohar wrote:
> If the kernel is locked down and IMA-appraisal is not enabled, prevent
> loading of unsigned firmware.
>
> Signed-off-by: Mimi Zohar
> ---
>
> Changelog v1:
> - Lots of minor changes Kconfig, Makefile, fw_lsm.c for such a small
The series is a preparation series for individual architectures
to use 64 bit time_t syscalls in compat and 32 bit emulation modes.
This is a follow up to the series Arnd Bergmann posted:
https://sourceware.org/ml/libc-alpha/2015-05/msg00070.html
Big picture is as per the lwn article:
- On Nov 10, 2017, at 5:32 PM, Mathieu Desnoyers
mathieu.desnoy...@efficios.com wrote:
> - On Nov 10, 2017, at 5:20 PM, Mathieu Desnoyers
> mathieu.desnoy...@efficios.com wrote:
>
>> - On Nov 10, 2017, at 5:02 PM, Andy Lutomirski l...@kernel.org wrote:
>>
>>> On Fri, Nov 10, 2017
On Mon, 2017-11-06 at 13:49 +0200, Alexander Shishkin wrote:
> On Fri, Nov 03, 2017 at 11:00:05AM -0700, Megha Dey wrote:
> > +static int intel_bm_event_init(struct perf_event *event)
> > +{
>
> ...
>
> > + /*
> > +* Find a hardware counter for the target task
> > +*/
> > + for (i =
On Fri, 10 Nov 2017 13:54:59 +
Jean-Philippe Brucker wrote:
> /*
> * Note: I tried to synthesize what I believe would be useful to
> device
> * drivers and guests, with regards to the kind of faults that the ARM
> * SMMU is capable of reporting. Other IOMMUs
Hi Ingo,
Here are some small updates to Protection Keys documentation, and
some small fixes to the selftests that we discussed.
On Sat, 4 Nov 2017 21:20:06 +0100
Wolfram Sang wrote:
> For all block commands, try to allocate a DMA safe buffer and mark it
> accordingly. Only use the stack, if the buffers cannot be allocated.
>
> Signed-off-by: Wolfram Sang
si_pkey is now #defined to be the name of the new siginfo field that
protection keys uses. Rename it not to conflict.
---
b/tools/testing/selftests/x86/protection_keys.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff -puN
From: Dave Hansen
Now that CPUs that implement Memory Protection Keys are publicly
available we can be a bit less oblique about where it is available.
Signed-off-by: Dave Hansen
---
b/Documentation/x86/protection-keys.txt |9
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 we
are accessing the array out of bounds. Just make it a
From: Dave Hansen
write() is marked as having a must-check return value. Check it and
abort if we fail to write an error message from a signal handler.
Signed-off-by: Dave Hansen
---
b/tools/testing/selftests/x86/pkey-helpers.h |
On Fri, Nov 10, 2017 at 1:37 PM, Mathieu Desnoyers
wrote:
> Introduce an architecture function that ensures the current CPU
> issues a core serializing instruction before returning to usermode.
>
> This is needed to fix an existing core serialization bug on
>
On Fri, Nov 10, 2017 at 11:31 AM, Dave Hansen
wrote:
>
> From: Dave Hansen
>
> There are effectively two ASID types:
> 1. The one stored in the mmu_context that goes from 0->5
> 2. The one programmed into the hardware that goes from 1->6
On 11/10/2017 02:03 PM, Andy Lutomirski wrote:
>> +static inline u16 kern_asid(u16 asid)
>> +{
>> + VM_WARN_ON_ONCE(asid > MAX_ASID_AVAILABLE);
>> + /*
>> +* If PCID is on, ASID-aware code paths put the ASID+1 into the PCID
>> +* bits. This serves two purposes. It
On Fri, 10 Nov 2017 13:54:59 +
Jean-Philippe Brucker wrote:
> On 09/11/17 19:36, Jacob Pan wrote:
> > On Tue, 7 Nov 2017 11:38:50 +
> > Jean-Philippe Brucker wrote:
> >
> >> I think the IOMMU should pass the struct device
- On Nov 10, 2017, at 5:20 PM, Mathieu Desnoyers
mathieu.desnoy...@efficios.com wrote:
> - On Nov 10, 2017, at 5:02 PM, Andy Lutomirski l...@kernel.org wrote:
>
>> On Fri, Nov 10, 2017 at 1:37 PM, Mathieu Desnoyers
>> wrote:
>>> Introduce an architecture
- On Nov 10, 2017, at 5:36 PM, Andy Lutomirski l...@amacapital.net wrote:
>> On Nov 10, 2017, at 2:20 PM, Mathieu Desnoyers
>>
>> wrote:
>>
>> - On Nov 10, 2017, at 5:02 PM, Andy Lutomirski l...@kernel.org wrote:
>>
>>> On Fri, Nov 10, 2017 at 1:37 PM,
On Fri, Nov 10, 2017 at 04:02:55PM -0500, Mimi Zohar wrote:
> If the kernel is locked down and IMA-appraisal is not enabled, prevent
> loading of unsigned firmware.
>
> Signed-off-by: Mimi Zohar
> ---
>
> Changelog v1:
> - Lots of minor changes Kconfig, Makefile,
From: Arnd Bergmann
There are a total of 53 system calls (aside from ioctl) that pass a time_t
or derived data structure as an argument, and in order to extend time_t
to 64-bit, we have to replace them with new system calls and keep providing
backwards compatibility.
To avoid
The new struct __kernel_timespec is similar to current
internal kernel struct timespec64 on 64 bit architecture.
The compat structure however is similar to below on little
endian systems (padding and tv_nsec are switched for big
endian systems):
typedef s32compat_long_t;
typedef s64
get/put_timespec64() interfaces will eventually be used for
conversions between the new y2038 safe struct __kernel_timespec
and struct timespec64.
The new y2038 safe syscalls have a common entry for native
and compat interfaces.
On compat interfaces, the high order bits of nanoseconds are
should
Change over clock_settime, clock_gettime and clock_getres
syscalls to use __kernel_timespec times. This will enable
changing over of these syscalls to use new y2038 safe syscalls
when the architectures define the CONFIG_64BIT_TIME.
Cc: linux-...@vger.kernel.org
Signed-off-by: Deepa Dinamani
On 11/10/2017 02:06 PM, Andy Lutomirski wrote:
> On Thu, Nov 9, 2017 at 10:31 PM, Dave Hansen
> wrote:
>> On 11/09/2017 06:25 PM, Andy Lutomirski wrote:
>>> Here are two proposals to address this without breaking vsyscalls.
>>>
>>> 1. Set NX on low mappings that are
On Fri, Nov 10, 2017 at 10:09 AM, Ulf Hansson wrote:
> On 8 November 2017 at 14:25, Rafael J. Wysocki wrote:
>> From: Rafael J. Wysocki
>>
>> Define and document a new driver flag, DPM_FLAG_LEAVE_SUSPENDED, to
>> instruct
The mm-of-the-moment snapshot 2017-11-10-15-56 has been uploaded to
http://www.ozlabs.org/~akpm/mmotm/
mmotm-readme.txt says
README for mm-of-the-moment:
http://www.ozlabs.org/~akpm/mmotm/
This is a snapshot of my -mm patch queue. Uploaded at random hopefully
more than once a week.
You
On 2017-11-10 03:26 PM, Patrick McLean wrote:
>
>
> On 2017-11-10 10:42 AM, Linus Torvalds wrote:
>> On Thu, Nov 9, 2017 at 5:58 PM, Patrick McLean wrote:
>>>
>>> Something must have changed since 4.13.8 to trigger this though.
>>
>> Arnd pointed to some commits that might
This patch addresses shortcoming in current boot process on machines
that supports 5-level paging.
If bootloader enables 64-bit mode with 4-level paging, we need to
switch over to 5-level paging. The switching requires disabling paging.
It works fine if kernel itself is loaded below 4G.
If
If bootloader enables 64-bit mode with 4-level paging, we might need to
switch over to 5-level paging. The switching requires disabling paging.
It works fine if kernel itself is loaded below 4G.
If bootloader put the kernel above 4G (not sure if anybody does this),
we would loose control as soon
This patch prepare decompression code to boot-time switching between 4-
and 5-level paging.
Signed-off-by: Kirill A. Shutemov
---
arch/x86/boot/compressed/Makefile | 1 +
arch/x86/boot/compressed/head_64.S| 16
As Dan pointed out, the rework I did makes it harder for smatch and other
static checkers to figure out what is going on with the uninitialized
pointers.
By open-coding the call in create_udata(), we make it more readable for
both humans and tools.
Reported-by: Dan Carpenter
On Fri, Nov 10, 2017 at 2:09 PM, Dave Hansen
wrote:
> On 11/10/2017 02:03 PM, Andy Lutomirski wrote:
>>> +static inline u16 kern_asid(u16 asid)
>>> +{
>>> + VM_WARN_ON_ONCE(asid > MAX_ASID_AVAILABLE);
>>> + /*
>>> +* If PCID is on, ASID-aware code
Make use of the swap macro instead of _manually_ swapping values
and remove unnecessary variable swap.
This makes the code easier to read and maintain.
This code was detected with the help of Coccinelle.
Signed-off-by: Gustavo A. R. Silva
---
On 2017-11-09 04:12, Harinath Nampally wrote:
> This patch adds following related changes:
> - defines pulse event related registers
> - enables and handles single pulse interrupt for fxls8471
> - handles IIO_EV_DIR_EITHER in read/write callbacks (because
> event direction for pulse is either
Many of the compat time syscalls are also repurposed as 32 bit
native syscalls to provide backward compatibility while adding
new y2038 safe sycalls.
Enabling the helpers makes this possible.
Signed-off-by: Deepa Dinamani
---
include/linux/compat.h | 4
1 file
These functions are used in the repurposed compat syscalls
to provide backward compatibility for using 32 bit time_t
on 32 bit systems.
Signed-off-by: Deepa Dinamani
---
include/linux/compat.h | 2 -
include/linux/compat_time.h | 4 ++
kernel/Makefile
All the current architecture specific defines for these
are the same. Refactor these common defines to a common
header file.
The new common linux/compat_time.h is also useful as it
will eventually be used to hold all the defines that
are needed for compat time types that support non y2038
safe
Change over clock_nanosleep syscalls to use y2038 safe
__kernel_timespec times. This will enable changing over
of these syscalls to use new y2038 safe syscalls when
the architectures define the CONFIG_64BIT_TIME.
Note that nanosleep syscall is deprecated and does not have a
plan for making it
clock_gettime, clock_settime, clock_getres and clock_nanosleep
compat syscalls are also repurposed to provide backward compatibility
to support 32 bit time_t on 32 bit systems.
Note that nanosleep compat syscall will also be treated the same way
as the above syscalls as it shares common handler
Make use of the swap macro instead of _manually_ swapping values
and remove unnecessary variable temp.
This makes the code easier to read and maintain.
This code was detected with the help of Coccinelle.
Signed-off-by: Gustavo A. R. Silva
---
On Fri, Nov 10, 2017 at 8:11 PM, Linus Torvalds
wrote:
> On Thu, Nov 9, 2017 at 2:30 PM, Rafael J. Wysocki wrote:
>>
>> c_start() can run aperfmperf_snapshot_khz() on all CPUs upfront (say
>> in parallel), then wait for a while (say 5 ms; the
On 2017-11-10 10:42 AM, Linus Torvalds wrote:
> On Thu, Nov 9, 2017 at 5:58 PM, Patrick McLean wrote:
>>
>> Something must have changed since 4.13.8 to trigger this though.
>
> Arnd pointed to some commits that might be relevant for the cp210x
> module, but those are all
401 - 500 of 1268 matches
Mail list logo