Hi Eric,
On Wed, 2018-01-10 at 20:48 -0800, Eric Biggers wrote:
> Hi André,
>
> On Wed, Jan 10, 2018 at 12:44:18PM +, André Draszik wrote:
> > diff --git a/Documentation/security/keys/fscrypt.rst
> > b/Documentation/security/keys/fscrypt.rst
> > new file mode 100644
> > index ..e4
> Hi,
>
> On Mon, Jan 15, 2018 at 12:20:48PM -0800, kan.li...@intel.com wrote:
> > From: Kan Liang
> >
> > For overwrite mode, the ringbuffer will be paused. The event lost is
> > expected. It needs a way to notify the browser not print the warning.
> >
> > It will be used later for perf top to d
zc770 is based board which is extended by FMC/DC cards for SoC
validation. FMCs/DCs are supposed to cover all SoC configurations.
FMC/DC contains ethernet port, can, i2c, sd, qspi, spi, uart and usb.
Signed-off-by: Michal Simek
---
arch/arm/boot/dts/Makefile | 1 +
arch/arm/boot/dt
Hi,
this patchset is adding 5 new dts files which target cc108 and zc770
boards.
Please let me know if you see any issue with them.
Thakns,
Michal
Michal Simek (5):
arm: zynq: Add Xilinx cc108 board
arm: zynq: Add support for Xilinx zc770 xm010 dc1 board
arm: zynq: Add support for Xilinx
zc770 is based board which is extended by FMC/DC cards for SoC
validation. FMCs/DCs are supposed to cover all SoC configurations.
FMC/DC contains can, ethernet, i2c, qspi, spi and uart.
Signed-off-by: Michal Simek
---
arch/arm/boot/dts/Makefile | 1 +
arch/arm/boot/dts/zynq-zc770-x
zc770 is based board which is extended by FMC/DC cards for SoC
validation. FMCs/DCs are supposed to cover all SoC configurations.
FMC/DC contains can, i2c, nand uart, spi and usb.
Signed-off-by: Michal Simek
---
arch/arm/boot/dts/Makefile | 1 +
arch/arm/boot/dts/zynq-zc770-xm011.d
zc770 is based board which is extended by FMC/DC cards for SoC
validation. FMCs/DCs are supposed to cover all SoC configurations.
FMC/DC contains can, 2x i2c, nor flash, spi and uart.
Signed-off-by: Michal Simek
---
arch/arm/boot/dts/Makefile | 1 +
arch/arm/boot/dts/zynq-zc770-xm0
The board contains 7z010 with 512MB memory, ethernet, qspi, uart, usbs
and sd. But board is not supporting booting from sd card.
Signed-off-by: Michal Simek
---
arch/arm/boot/dts/Makefile | 1 +
arch/arm/boot/dts/zynq-cc108.dts | 75
2 files chang
On Wed, Jan 17, 2018 at 03:14:18PM +0100, Joerg Roedel wrote:
> On Wed, Jan 17, 2018 at 06:00:07AM -0800, Brian Gerst wrote:
> > On Wed, Jan 17, 2018 at 5:57 AM, Brian Gerst wrote:
> > But then again, you could take a fault on the trampoline stack if you
> > get a bad segment. Perhaps just pushin
>> https://bottest.wiki.kernel.org/coccicheck#types_of_tests
>
> Fixed.
How do you think about to mention a date in this document
since when the changed file name may be used?
Regards,
Markus
- Original Message -
|
|
| On 16/01/18 20:51, Stephen Rothwell wrote:
| > Hi all,
| >
| > Commit
| >
| >7d2040199855 ("gfs2: Add gfs2_blk2rgrpd comment and fix incorrect use")
| >
| > is missing a Signed-off-by from its author.
| >
| Bob, can you add that?
|
| Steve.
This should be
On Tue, 16 Jan 2018, Matthew Wilcox wrote:
> On Tue, Jan 16, 2018 at 12:17:01PM -0600, Christopher Lameter wrote:
> > Draft patch of how the data structs could change. kmem_cache_attr is read
> > only.
>
> Looks good. Although I would add Kees' user feature:
Sure I tried to do this quickly so th
A cleanup left one variable behind that is no longer needed and
can be removed, as shown by the gcc warning:
drivers/iio/adc/stm32-dfsdm-core.c: In function 'stm32_dfsdm_probe':
drivers/iio/adc/stm32-dfsdm-core.c:245:29: error: unused variable 'of_id'
[-Werror=unused-variable]
Fixes: abaca806fd1
do_gettimeofday() overflows in 2038 on 32-bit architectures and
is deprecated, so convert this driver to call ktime_get_real()
directly. This also simplifies the calculation.
Signed-off-by: Arnd Bergmann
---
Sent originally in Nov 2017, no comments. Please apply
---
drivers/scsi/megaraid/megarai
On Tue, 16 Jan 2018, Mike Galbraith wrote:
> > I tried to remove isolcpus or at least change the way it works so that its
> > effects are reversible (ie: affine the init task instead of isolating
> > domains)
> > but that got nacked due to the behaviour's expectations for userspace.
>
> So we pai
On 01/17/2018 07:41 AM, Jiri Kosina wrote:
> On Wed, 17 Jan 2018, Martin Schwidefsky wrote:
>
>> Implement nospec_load() and nospec_ptr() for s390 with the new
>> gmb() barrier between the boundary condition and the load that
>> may not be done speculatively.
Thanks for the patches, Martin et al.
On 17/01/18 14:38, Dave Martin wrote:
On Wed, Jan 17, 2018 at 01:22:19PM +, Suzuki K Poulose wrote:
On 17/01/18 12:25, Dave Martin wrote:
On Wed, Jan 17, 2018 at 10:05:56AM +, Suzuki K Poulose wrote:
When a CPU is brought up after we have finalised the system
wide capabilities (i.e, fe
On Tue, Jan 16, 2018 at 04:33:29PM +0200, Andy Shevchenko wrote:
> On Tue, Jan 16, 2018 at 11:01 AM, Ludovic Desroches
> wrote:
> > On Mon, Jan 15, 2018 at 10:19:39PM +0200, Andy Shevchenko wrote:
> >> On Mon, Jan 15, 2018 at 6:22 PM, Ludovic Desroches
> >> wrote:
> >>
> >> Did I miss cover lette
On Wed, Jan 17, 2018 at 3:36 PM, Arnd Bergmann wrote:
> On Wed, Jan 17, 2018 at 9:27 AM, Daniel Vetter wrote:
>> On Tue, Jan 16, 2018 at 03:57:10PM +0100, Arnd Bergmann wrote:
>>> The two functions pass a partially initialized structure back to the
>>> caller after a memset() on the destination.
On 17/01/18 14:01, Daniel Vetter wrote:
The backlight power state handling is supremely confusing. We have:
- props.power, using FB_BLANK_* defines
- props.fb_blank, using the same, but deprecated int favour of
props.state
- props.state, using the BL_CORE_* defines
- and finally a bunch of bac
From: Peter Enderborg
Holding the preempt_disable is very bad for low latency tasks
as audio and therefore we need to break out the rule-set dependent
part from this disable. By using a rwsem instead of rwlock we
have an efficient locking and less preemption interference.
Selinux uses a lot of r
do_gettimeofday() is deprecated since it will stop working in 2038 on
32-bit platforms. The firmware interface here actually supports times
until year 25500, so we should use longer timestamps.
Using ktime_get_real_seconds() to get a 64-bit seconds value
and time64_to_tm() to convert it into the r
On Monday 08 January 2018 07:47 AM, David Lechner wrote:
> +void __init dm646x_psc_clk_init(void __iomem *psc)
> +{
> + struct clk_onecell_data *clk_data;
> +
> + clk_data = davinci_psc_register_clocks(psc, dm646x_psc_info, 41);
> + if (!clk_data)
> + return;
> +
> + cl
On Tue, 16 Jan 2018 18:44:45 -0500
Daniel Micay wrote:
> > Do you have any backing from makers of such devices? I'd like to hear
> > from Google's Android team or whoever that would turn this feature on.
>
> (I'm not a Google employee, but I work on Android security and
> contribute some of th
On Wed, 17 Jan 2018, Keith Busch wrote:
> On Wed, Jan 17, 2018 at 10:32:12AM +0100, Thomas Gleixner wrote:
> > On Wed, 17 Jan 2018, Thomas Gleixner wrote:
> > > That doesn't sound right. The vectors should be spread evenly accross the
> > > CPUs. So ENOSPC should never happen.
> > >
> > > Can you
On 16/01/18 18:57, Catalin Marinas wrote:
> On Fri, Jan 12, 2018 at 11:48:32AM +0100, Jerome Marchand wrote:
>> diff --git a/arch/arm64/kernel/stacktrace.c b/arch/arm64/kernel/stacktrace.c
>> index 76809ccd309c..5a528c58ef68 100644
>> --- a/arch/arm64/kernel/stacktrace.c
>> +++ b/arch/arm64/kernel/
On Wed, 2018-01-17 at 14:34 +0100, Peter Rosin wrote:
> Without such a range, gpiolib fails with -EPROBE_DEFER, pending the
> addition of the range. So, without a range, gpiolib will keep
> deferring indefinitely.
>
> Fixes: e10f72bf4b3e ("gpio: gpiolib: Generalise state persistence beyond
> slee
On 1/17/2018 1:22 AM, Dave Young wrote:
> [Modify the subject since this is a new problem, original io vector
> issue has been fixed with one commit from Thomas]
>
> Add more cc according to below old discussion:
> https://lkml.org/lkml/2017/7/27/574
>
> Tom, I'm not sure why you finally did not
The trailing semicolon is an empty statement that does no operation.
Removing it since it doesn't do anything.
Signed-off-by: Luis de Bethencourt
---
Hi,
After fixing the same thing in drivers/staging/rtl8723bs/, Joe Perches
suggested I fix it treewide [0].
Best regards,
Luis
[0]
http://dri
3.18.91-rt98-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Sebastian Andrzej Siewior
extract_crng() will use sleeping locks while in a preempt_disable()
section due to get_cpu_var().
Work around it with local_locks.
Cc: stable...@vger.kerne
From: Matthew Wilcox
There are several places in the kernel which would like to pass a const
pointer to lockdep_is_held(). Constify the entire path so nobody has to
trick the compiler.
Signed-off-by: Matthew Wilcox
---
include/linux/lockdep.h | 4 ++--
kernel/locking/lockdep.c | 13 +++-
From: Matthew Wilcox
I am not for one moment suggesting that the concept of a read-only lock
makes sense. You can't sensibly put one in ROM or in read-only mappings.
What does make sense is some APIs want to specify a const pointer to
indicate that they do not modify the object being pointed to.
Hello,
On Wed, Jan 17, 2018 at 10:12:08AM +0100, Petr Mladek wrote:
> IMHO, the bad scenario with OOM was that any printk() called in
> the OOM report became console_lock owner and was responsible
> for pushing all new messages to the console. There was a possible
> livelock because OOM Killer was
From: Matthew Wilcox
These users of lockdep_is_held() either wanted lockdep_is_held to
take a const pointer, or would benefit from providing a const pointer.
Signed-off-by: Matthew Wilcox
---
include/linux/backing-dev.h | 2 +-
include/linux/srcu.h| 4 ++--
include/net/sock.h
Hi Kirill,
Thanks for reviewing this series.
On 16/01/2018 16:11, Kirill A. Shutemov wrote:
> On Fri, Jan 12, 2018 at 06:25:44PM +0100, Laurent Dufour wrote:
>> --
>> Benchmarks results
>>
>> Base kernel is 4.15-rc6-mmotm-2018-01-04-16-19
>> SPF is BASE + this series
>
> Do you h
do_gettimeofday() is deprecated because of the y2038 overflow.
Here, we use the result to pass into a 32-bit field in the firmware,
which still risks an overflow, but if the firmware is written
to expect unsigned values, it can at least last until y2106,
and there is not much we can do about it.
T
From: Matthew Wilcox
Lockdep was assigning lock keys when a lock was looked up. This is
unnecessary; if the lock has never been registered then we know it is
not locked. It also complicates the calling convention. Switch to
assigning the lock key in register_lock_class().
Signed-off-by: Matth
3.18.91-rt98-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Thomas Gleixner
Locking an rt mutex killable does not work because signal handling is
restricted to TASK_INTERRUPTIBLE.
Use signal_pending_state() unconditionaly.
Cc: rt-sta...@vge
From: Rob Clark
It looks like in all cases 'struct vmw_connector_state' is used. But
only in stdu connectors, was atomic_{duplicate,destroy}_state() properly
subclassed. Leading to writes beyond the end of the allocated connector
state block and all sorts of fun memory corruption related crashe
3.18.91-rt98-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Sebastian Andrzej Siewior
required for following networking patch which does recursive try-lock.
While at it, add the !RT version of it because it did not yet exist.
Cc: stable...@v
struct timespec is deprecated since it overflows in 2038 on 32-bit
architectures, so we should use timespec64 consistently.
I'm slightly adapting the format strings here, to make sure we
print the nanoseconds with the correct number of leading zeroes.
Signed-off-by: Arnd Bergmann
---
Originally
3.18.91-rt98-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: "Steven Rostedt (VMware)"
---
localversion-rt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/localversion-rt b/localversion-rt
index f5eca15b92de..195e539be979
3.18.91-rt98-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Sebastian Andrzej Siewior
The locking path can be recursive (same as for sk->sk_lock.slock) and
therefore we need a trylock version for the locallock, too.
Cc: stable...@vger.kernel
3.18.91-rt98-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Sebastian Andrzej Siewior
This reverts commit "fs: jbd2: pull your plug when waiting for space".
This was a duct-tape fix which shouldn't be needed since commit
"locking/rt-mutex: fi
3.18.91-rt98-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Alex Shi
This patch replace a rwlock and raw notifier by atomic notifier which
protected by spin_lock and rcu.
The first to reason to have this replace is due to a 'scheduling while
Dear RT Folks,
This is the RT stable review cycle of patch 3.18.91-rt98-rc1.
Please scream at me if I messed something up. Please test the patches too.
The -rc release will be uploaded to kernel.org and will be deleted when
the final release is out. This is just a review release (or release can
3.18.91-rt98-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Mike Galbraith
kernel/hrtimer: don't wakeup a process while holding the hrtimer base lock
missed a path, namely hrtimers_dead_cpu() -> migrate_hrtimer_list(). Defer
raising softirq
3.18.91-rt98-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Sebastian Andrzej Siewior
hrtimers, which were deferred to the softirq context, and expire between
softirq shutdown and hrtimer migration are dangling around. If the CPU
goes back up
3.18.91-rt98-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Mikulas Patocka
When some block device driver creates a bio and submits it to another
block device driver, the bio is added to current->bio_list (in order to
avoid unbounded recursio
On Tue, Jan 16, 2018 at 10:51 PM, Nicolin Chen wrote:
> [ Maciej, could you please send your Tested-by/Reviewed-by for AC97
> once you confirm this series?
>
> And Caleb, this version does not need a test for non-AC97 cases.
>
> Thanks both! ]
>
> ==Change log==
> v5
> * Reworked the series
Dear Linux folks,
On 01/17/18 15:20, Paul Menzel wrote:
Testing Linux 4.15-rc8 on a Lenovo T60 (32 bit) and Dell XPS 13 9360 (64
bit) suspend to and resume from ACPI S3 doesn’t work anymore.
`./sleepgraph.py -config config/suspend-callgraph.cfg` [1] is used to
enable the FTRACE framework.
3.18.91-rt98-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Thomas Gleixner
Mathias and others reported GDB failures on RT.
The following scenario leads to task state corruption:
CPU0CPU1
T1->sta
3.18.91-rt98-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Sebastian Andrzej Siewior
We convert all BH_Uptodate_Lock based bit-spinlocks to use
bh_uptodate_lock_irqsave() instead. Those two were introduced after the
initial change in -RT and
3.18.91-rt98-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Sebastian Andrzej Siewior
|BUG: sleeping function called from invalid context at
kernel/locking/rtmutex.c:974
|in_atomic(): 0, irqs_disabled(): 1, pid: 2992, name: lvm
|CPU: 2 PID:
On 15/01/18 22:25, Ladislav Michl wrote:
> Allocating memory to store clk array together with driver
> data simplifies error unwinding and allows deleting memory
> allocation failure message as there is now only single point
> of failure already covered by allocation failure report.
>
> Signed-off
Linus,
Please pull the latest locking-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
locking-urgent-for-linus
# HEAD: fbe0e839d1e22d88810f3ee3e2f1479be4c0aa4a futex: Prevent overflow by
strengthen input validation
Two futex fixes: a input param
> Hi,
> this is a revised version of the patch series I sent under a similar
> subject in mid December.
> Improvements are:
>- new wait_event_idle* macros are now in include/linux/wait.h which
> Ack from peterz.
>- *all* waits are now TASK_IDLE or TASK_INTERRUPTIBLE and so don't
>
On Wed, 17 Jan 2018 14:04:07 +0100
Petr Mladek wrote:
> On Wed 2018-01-17 11:18:56, Sergey Senozhatsky wrote:
> > On (01/16/18 10:45), Steven Rostedt wrote:
> > [..]
> > > > [1] https://marc.info/?l=linux-mm&m=145692016122716
> > >
> > > Especially since Konstantin is working on pulling in a
INIT_STRUCT_PID in place.
These macros can then be discarded.
The patches can be found here also:
http://git.kernel.org/cgit/linux/kernel/git/dhowells/linux-fs.git/log/?h=init_task
tagged as:
init_task-20180117
David
---
David Howells (8):
cris: Make THREAD_SIZE
On 01/17/2018 09:04 AM, Andrew Cooper wrote:
> On 17/01/18 09:02, Joerg Roedel wrote:
>> Hi Boris,
>>
>> thanks for testing this :)
>>
>> On Tue, Jan 16, 2018 at 09:47:06PM -0500, Boris Ostrovsky wrote:
>>> On 01/16/2018 11:36 AM, Joerg Roedel wrote:
+.macro SWITCH_TO_KERNEL_STACK nr_regs=0 ch
Make THREAD_SIZE available to vmlinux.lds on openrisc by including
asm/thread_info.h the linker script.
This allows init_stack to be allocated in the linker script in a subsequent
patch.
Reported-by: Guenter Roeck
Signed-off-by: David Howells
Tested-by: Guenter Roeck
Acked-by: Stafford Horne
Make THREAD_SIZE available to vmlinux.lds on hexagon by including
asm/thread_info.h the linker script.
This allows init_stack to be allocated in the linker script in a subsequent
patch.
Reported-by: Guenter Roeck
Signed-off-by: David Howells
Reviewed-by: Guenter Roeck
Acked-by: Richard Kuo
cc
This series fixes some issues in rockchip iommu driver, and add of_iommu
support in it.
Changes in v3:
Also remove remove() and module_exit() as Tomasz suggested.
Loop platform_get_irq() as Robin suggested.
Add struct rk_iommudata.
Squash iommu/rockchip: Use iommu_group_get_for_dev() for add_devi
Expand INIT_STRUCT_PID in the single place that uses it and then remove it.
There doesn't seem any point in the macro.
Signed-off-by: David Howells
Tested-by: Tony Luck
Tested-by: Will Deacon (arm64)
Tested-by: Palmer Dabbelt
Acked-by: Thomas Gleixner
---
include/linux/init_task.h | 15 --
There doesn't seem to be any need to have the INIT_SIGNALS and INIT_SIGHAND
macros, so expand them in their single places of use and remove them.
Signed-off-by: David Howells
Tested-by: Tony Luck
Tested-by: Will Deacon (arm64)
Tested-by: Palmer Dabbelt
Acked-by: Thomas Gleixner
---
include/
It's no longer necessary to have an INIT_TASK() macro, and this can be
expanded into the one place it is now used and removed.
Signed-off-by: David Howells
Tested-by: Tony Luck
Tested-by: Will Deacon (arm64)
Tested-by: Palmer Dabbelt
Acked-by: Thomas Gleixner
---
include/linux/init_task.h |
From: Tomasz Figa
Currently if the driver encounters an error while attaching device, it
will leave the IOMMU in an inconsistent state. Even though it shouldn't
really happen in reality, let's just add proper error path to keep
things consistent.
Signed-off-by: Tomasz Figa
Signed-off-by: Jeffy
Construct the init thread stack in the linker script rather than doing it
by means of a union so that ia64's init_task.c can be got rid of.
The following symbols are then made available from INIT_TASK_DATA() linker
script macro:
init_thread_union
init_stack
INIT_TASK_DATA() also
From: Tomasz Figa
This patch converts the rockchip-iommu driver to use the in-kernel
iopoll helpers to wait for certain status bits to change in registers
instead of an open-coded custom macro.
Signed-off-by: Tomasz Figa
Signed-off-by: Jeffy Chen
---
Changes in v3: None
Changes in v2: None
From: Tomasz Figa
Due to the bug in current code, only first IOMMU has the TLB lines
flushed in rk_iommu_zap_lines. This patch fixes the inner loop to
execute for all IOMMUs and properly flush the TLB.
Signed-off-by: Tomasz Figa
Signed-off-by: Jeffy Chen
---
Changes in v3: None
Changes in v2:
> This flag is never set, so remove checks and remove
> the flag.
Reviewed-by: James Simmons
> Signed-off-by: NeilBrown
> ---
> drivers/staging/lustre/lustre/include/lustre_net.h |6 --
> drivers/staging/lustre/lustre/ptlrpc/sec_gc.c |4 +---
> 2 files changed, 1 insertion(+
From: Tomasz Figa
Current code relies on master driver enabling necessary clocks before
IOMMU is accessed, however there are cases when the IOMMU should be
accessed while the master is not running yet, for example allocating
V4L2 videobuf2 buffers, which is done by the VB2 framework using DMA
map
Converts the rockchip-iommu driver to use the OF_IOMMU infrastructure,
which allows attaching master devices to their IOMMUs automatically
according to DT properties.
Signed-off-by: Jeffy Chen
---
Changes in v3:
Add struct rk_iommudata.
Squash iommu/rockchip: Use iommu_group_get_for_dev() for ad
Use the first registered IOMMU device for dma mapping operations, and
drop the domain platform device.
This is similar to exynos iommu driver.
Signed-off-by: Jeffy Chen
Reviewed-by: Tomasz Figa
---
Changes in v3: None
Changes in v2: None
drivers/iommu/rockchip-iommu.c | 85 --
Linus,
Please pull the latest perf-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
perf-urgent-for-linus
# HEAD: 1289e0e29857e606a70a0200bf7849ae38d3493a perf/x86/rapl: Fix Haswell
and Broadwell server RAPL event
An Intel RAPL events fix.
Than
Hi everybody!
Richard and I have been working on extending UBIFS' security features and came
up with the following concept to add full file contents and metadata
authentication.
For block devices like eMMCs dm-crypt and dm-verity/dm-integrity can be used to
get full data confidentiality and auth
> When the lwi arg has a timeout, but no timeout
> callback function, l_wait_event() acts much the same as
> wait_event_idle_timeout() - the wait is not interruptible and
> simply waits for the event or the timeouts.
>
> The most noticable difference is that the return value is
> -ETIMEDOUT or 0,
Hi Arnd,
On 01/17/2018 03:46 PM, Arnd Bergmann wrote:
> A cleanup left one variable behind that is no longer needed and
> can be removed, as shown by the gcc warning:
>
> drivers/iio/adc/stm32-dfsdm-core.c: In function 'stm32_dfsdm_probe':
> drivers/iio/adc/stm32-dfsdm-core.c:245:29: error: unuse
There would be some masters sharing the same IOMMU device. Put them in
the same iommu group and share the same iommu domain.
Signed-off-by: Jeffy Chen
---
Changes in v3:
Remove rk_iommudata->domain.
Changes in v2: None
drivers/iommu/rockchip-iommu.c | 22 --
1 file changed
On 17/01/18 14:46, Arnd Bergmann wrote:
A cleanup left one variable behind that is no longer needed and
can be removed, as shown by the gcc warning:
drivers/iio/adc/stm32-dfsdm-core.c: In function 'stm32_dfsdm_probe':
drivers/iio/adc/stm32-dfsdm-core.c:245:29: error: unused variable 'of_id'
[-W
When the power domain is powered off, the IOMMU cannot be accessed and
register programming must be deferred until the power domain becomes
enabled.
Add runtime PM support, and use runtime PM device link from IOMMU to
master to startup and shutdown IOMMU.
Signed-off-by: Jeffy Chen
---
Changes i
> When the lwi arg is full of zeros, l_wait_event() behaves almost
> identically to the standard wait_event_idle() interface, so use that
> instead.
>
> l_wait_event() uses TASK_INTERRUPTIBLE, but blocks all signals.
> wait_event_idle() uses the new TASK_IDLE and so avoids adding
> to the load av
> cfs_time_seconds() converts a number of seconds to the
> matching number of jiffies.
> The standard way to do this in Linux is "* HZ".
> So discard cfs_time_seconds() and use "* HZ" instead.
This doesn't collide as bad as I thought it did. Also it builds
now that the lnet seltest changes lande
From: Anurag Kumar Vulisha
This patch adds the sata port phy OOB timing values in the sata
device-tree node.
Signed-off-by: Anurag Kumar Vulisha
Signed-off-by: Michal Simek
---
arch/arm64/boot/dts/xilinx/zynqmp-ep108.dts | 9 +
1 file changed, 9 insertions(+)
diff --git a/arch/arm64
Trivial changes.
Signed-off-by: Michal Simek
---
arch/arm64/boot/dts/xilinx/zynqmp-ep108.dts | 2 +-
arch/arm64/boot/dts/xilinx/zynqmp.dtsi | 8
2 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/arch/arm64/boot/dts/xilinx/zynqmp-ep108.dts
b/arch/arm64/boot/dts/xilinx
From: P L Sai Krishna
This patch add 8-bit bus width property to eMMC node.
Signed-off-by: P L Sai Krishna
Signed-off-by: Michal Simek
---
arch/arm64/boot/dts/xilinx/zynqmp-ep108.dts | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm64/boot/dts/xilinx/zynqmp-ep108.dts
b/arch/arm64
Add missing aliases for gem0/spis and usbs
spi0 alias is allocated for qspi which is out of tree driver now.
Signed-off-by: Michal Simek
---
arch/arm64/boot/dts/xilinx/zynqmp-ep108.dts | 5 +
1 file changed, 5 insertions(+)
diff --git a/arch/arm64/boot/dts/xilinx/zynqmp-ep108.dts
b/arch/a
this patchset is adding minor dt pieces for ep108.
Also adding SPDX headers, fixing minor coding style issue and extending
gem compatible string for all boards.
The next patchset will add much more zynqmp based board.
Thanks,
Michal
Anurag Kumar Vulisha (1):
arm64: zynqmp: Added OOB timing s
> lustre sometimes wants to wait for an event, but abort if
> one of a specific list of signals arrives. This is a little
> bit like wait_event_killable(), except that the signals are
> identified a different way.
>
> So introduce l_wait_event_abortable() which provides this
> functionality.
> H
From: Tina Ruchandani
'struct frame' uses two variables to store the sent timestamp - 'struct
timeval' and jiffies. jiffies is used to avoid discrepancies caused by
updates to system time. 'struct timeval' is deprecated because it uses
32-bit representation for seconds which will overflow in year
On 01/17/2018 04:16 PM, Rob Clark wrote:
From: Rob Clark
It looks like in all cases 'struct vmw_connector_state' is used. But
only in stdu connectors, was atomic_{duplicate,destroy}_state() properly
subclassed. Leading to writes beyond the end of the allocated connector
state block and all so
> If l_wait_event() is given a function to be called on a signal,
> but no timeout or timeout handler, then the intr function is simply
> called at the end if the wait was aborted by a signal.
> So a simpler way to write the code (in the one place this case is
> used) it to open-code the body of t
Add SPDX identifier as was done by for example by:
"License cleanup: add SPDX GPL-2.0 license identifier to files with no
license" (commit )
Signed-off-by: Michal Simek
---
arch/arm64/boot/dts/xilinx/Makefile | 1 +
arch/arm64/boot/dts/xilinx/zynqmp-ep108-clk.dtsi | 1 +
arch/arm64
> If a signal-callback (lwi_on_signal) is set without lwi_allow_intr, as
> is the case in ldlm_completion_ast(), the behavior depends on the
> timeout set.
>
> If a timeout is set, then signals are ignored. If the timeout is
> reached, the timeout handler is called. If the timeout handler
> ret
Since tm->tm_year is the offset relative to 1900, it needs to check for
positive value to avoid overflow in YEARS_REG register.
The system will hang at the following stage on the next boot when overflow
has occurred.
[2.221192] systemd[1]: Time has been changed
This patch fixes the above han
> This waiter currently wakes up every second to re-test if
> imp_flight is zero. If we ensure wakeup is called whenever
> imp_flight is decremented to zero, we can just have a simple
> wait_event_idle_timeout().
>
> So add a wake_up_all to the one place it is missing, and simplify
> the wait_ev
> Two places that LWI_TIMEOUT_INTERVAL() is used, the outcome is a
> simple polling loop that polls every second for some event (with a
> limit).
>
> So write a simple loop to make this more apparent.
Reviewed-by: James Simmons
> Signed-off-by: NeilBrown
> ---
> drivers/staging/lustre/lustr
Linus,
please pull the latest timers-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
timers-urgent-for-linus
A one-liner fix which prevents deferrable timers becoming stale when the
system does not switch into NOHZ mode.
Thanks,
tglx
-
> This use of l_wait_event() is a polling loop that re-checks
> every second. Make this more obvious with a while loop
> and wait_event_idle_timeout().
Reviewed-by: James Simmons
> Signed-off-by: NeilBrown
> ---
> drivers/staging/lustre/lustre/ptlrpc/niobuf.c | 15 ---
> 1 fil
On Monday 08 January 2018 07:47 AM, David Lechner wrote:
> This adds a new driver for the gate and multiplexer clocks in the
> CFGCHIPn syscon registers on TI DA8XX-type SoCs.
>
> Signed-off-by: David Lechner
> ---
> drivers/clk/davinci/Makefile| 2 +
> drivers/clk/davinci/da8xx-cfgchi
401 - 500 of 1318 matches
Mail list logo
