To reset the UART the SRST needs be cleared (low active). According
to the documentation the bit will remain active for 4 module clocks
until it is cleared (set to 1).
Hence the real register need to be read in case the cached register
indcates that the SRST bit is zero.
This bug lead to wrong ba
On Mon, 16 Apr 2018 08:18:09 -0700
Linus Torvalds wrote:
> On Mon, Apr 16, 2018 at 6:30 AM, Steven Rostedt wrote:
> >
> > I wonder if the "AUTOSEL" patches should at least have an "ack-by" from
> > someone before they are pulled in. Otherwise there may be some subtle
> > issues that can find the
On 04/16/2018 02:15 AM, Kirill A. Shutemov wrote:
> On Mon, Apr 16, 2018 at 08:07:09AM +0200, Ingo Molnar wrote:
>>
>> * Eric Dumazet wrote:
>>
>>> Hi Kirill
>>>
>>> For some reason, my hosts instantly crash at boot time, with absolutely no
>>> log on console.
>>>
>>> Bisection pointed to :
>>>
On Mon, Apr 16, 2018 at 08:18:09AM -0700, Linus Torvalds wrote:
>On Mon, Apr 16, 2018 at 6:30 AM, Steven Rostedt wrote:
>>
>> I wonder if the "AUTOSEL" patches should at least have an "ack-by" from
>> someone before they are pulled in. Otherwise there may be some subtle
>> issues that can find the
On 04/16/2018 08:16 AM, Andy Lutomirski wrote:
> On Mon, Apr 16, 2018 at 2:43 AM, Joerg Roedel wrote:
>> From: Joerg Roedel
>>
>> The |= operator will let us end up with an invalid PTE. Use
>> the correct &= instead.
> D'oh! Looks good.
Yes, agreed. Thanks for finding that, Joerg!
On 04/16/2018 08:33 AM, Yafang Shao wrote:
> tcp_rcv_space_adjust is called every time data is copied to user space,
> introducing a tcp tracepoint for which could show us when the packet is
> copied to user.
> This could help us figure out whether there's latency in user process.
>
> When a tcp
arch/mips/boot/dts/Makefile collects objects from sub-directories
into built-in.a only when CONFIG_BUILTIN_DTB is enabled. Reflect
it also to the sub-directory Makefiles. This suppresses unneeded
built-in.a creation in arch/mips/boot/dts/*/ directories.
While I am here, I replaced $(patsubst %.d
Some lines used spaces instead of tabs at line start.
This can cause mangled lines in editors due to inconsistency.
Replace spaces for tabs where appropriate.
Signed-off-by: Thymo van Beers
---
Documentation/admin-guide/kernel-parameters.txt | 168
1 file changed, 84 in
Update the example to use the compatible string including the
vendor prefix instead of the ones deprecated in 3a872138e4b.
Signed-off-by: Fabian Mewes
---
Documentation/devicetree/bindings/iio/adc/mcp320x.txt |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/de
On Mon, Apr 16, 2018 at 4:04 AM, Paolo Bonzini wrote:
> On 14/04/2018 05:10, KarimAllah Ahmed wrote:
>> Update 'tsc_offset' on vmentry/vmexit of L2 guests to ensure that it always
>> captures the TSC_OFFSET of the running guest whether it is the L1 or L2
>> guest.
>>
>> Cc: Jim Mattson
>> Cc: Pao
Hi Rob,
On Thu, 2018-02-01 at 17:34 -0600, Rob Landley wrote:
>
> On 02/01/2018 04:41 PM, Taras Kondratiuk wrote:
> > Quoting Mimi Zohar (2018-02-01 13:51:52)
> >> On Thu, 2018-02-01 at 11:09 -0600, Rob Landley wrote:
> >>> On 02/01/2018 09:55 AM, Mimi Zohar wrote:
> On Thu, 2018-02-01 at 09
On Mon, Apr 16, 2018 at 05:30:31PM +0200, Pavel Machek wrote:
>On Mon 2018-04-16 08:18:09, Linus Torvalds wrote:
>> On Mon, Apr 16, 2018 at 6:30 AM, Steven Rostedt wrote:
>> >
>> > I wonder if the "AUTOSEL" patches should at least have an "ack-by" from
>> > someone before they are pulled in. Other
+++ Jia Zhang [11/04/18 11:53 +0800]:
The sig_enforce parameter could be always shown to reflect the
current status of modsign. For the case of CONFIG_MODULE_SIG_FORCE=y,
this modification does nothing harmless.
Signed-off-by: Jia Zhang
Both patches look fine to me. Queued on modules-next.
T
On Sat, Apr 14, 2018 at 3:44 PM, Theodore Y. Ts'o wrote:
> +linux...@kvack.org
> k...@vger.kernel.org, secur...@kernel.org moved to bcc
>
> On Sat, Apr 14, 2018 at 10:59:21PM +0300, Alexey Dobriyan wrote:
>> SLAB allocators got CONFIG_SLAB_FREELIST_RANDOM option which randomizes
>> allocation patt
On 04/16/2018 04:15 AM, Dmitry Vyukov wrote:
> On Sat, Apr 14, 2018 at 8:25 PM, Linus Torvalds
> wrote:
>> Coming back to this now that the merge window is almost over ]
>>
>> On Mon, Mar 26, 2018 at 1:46 AM, Dmitry Vyukov wrote:
>>>
>>> I've switched emails to links instead of attachments, here
On 27.03.2018 14:16, Dmitry Osipenko wrote:
> On 27.03.2018 14:54, Robin Murphy wrote:
>> On 26/03/18 22:20, Dmitry Osipenko wrote:
>>> On 25.03.2018 21:09, Stefan Agner wrote:
As documented in GCC naked functions should only use Basic asm
syntax. The Extended asm or mixture of Basic asm
On Mon, Apr 16, 2018 at 5:31 PM, Joseph Salisbury
wrote:
> On 04/13/2018 05:34 PM, Rafael J. Wysocki wrote:
>> On Fri, Apr 13, 2018 at 7:56 PM, Joseph Salisbury
>> wrote:
>>> Hi Rafael,
>>>
>>> A kernel bug report was opened against Ubuntu [0]. After a kernel
>>> bisect, it was found that revert
On Mon, Apr 16, 2018 at 02:43:01PM +0200, Vitaly Wool wrote:
> Hey Guenter,
>
> On 04/13/2018 07:56 PM, Guenter Roeck wrote:
>
> >On Fri, Apr 13, 2018 at 05:40:18PM +, Vitaly Wool wrote:
> >>On Fri, Apr 13, 2018, 7:35 PM Guenter Roeck wrote:
> >>
> >>>On Fri, Apr 13, 2018 at 05:21:02AM +
On 25.03.2018 20:09, Stefan Agner wrote:
> Mixing asm and C code is not recommended in a naked function by
> gcc and leads to an error when using clang:
> drivers/bus/arm-cci.c:2107:2: error: non-ASM statement in naked
> function is not supported
> unreachable();
> ^
>
> While
On 15/04/2018 23:22, Tony Krowiak wrote:
If the AP instructions are not available on the linux host, then
AP devices can not be interpreted by the SIE. The AP bus has a
function it uses to determine if the AP instructions are
available. This patch provides a new function that wraps the
AP bus's f
This patch series compose of 2 patches.
First patch, fixing incorrect order of banks for s5pv210 and exynos5410
Second patch, documenting required order of banks
Changes from v1:
- Limit changes to s5pv210 and Exynos5410. Exynos3250 will be handled later.
- Added cc stable
- Added fixes ta
All banks with GPIO interrupts should be at beginning
of bank array and without any other types of banks between them.
This order is expected by exynos_eint_gpio_irq, when doing
interrupt group to bank translation.
Otherwise, kernel NULL pointer dereference would happen
when trying to handle interr
This patch documents requirement coming from the way
exynos_eint_gpio_irq() is working now, which expects
EINTG banks to be at the beginning of the bank arrays.
Cc: sta...@vger.kernel.org
Signed-off-by: Paweł Chmiel
---
drivers/pinctrl/samsung/pinctrl-exynos-arm.c | 26
Use new return type vm_fault_t for fault handler
in struct vm_operations_struct. For now, this is
just documenting that the function returns a VM_
FAULT value rather than an errno. Once all inst
ances are converted, vm_fault_t will become a di
stinct type.
Signed-off-by: Souptick Joarder
Reviewe
On Mon, Apr 16, 2018 at 11:36:29AM -0400, Steven Rostedt wrote:
>On Mon, 16 Apr 2018 08:18:09 -0700
>Linus Torvalds wrote:
>
>> On Mon, Apr 16, 2018 at 6:30 AM, Steven Rostedt wrote:
>> >
>> > I wonder if the "AUTOSEL" patches should at least have an "ack-by" from
>> > someone before they are pul
Hi Linus,
On Mon, Apr 16, 2018 at 08:32:46AM -0700, Linus Torvalds wrote:
> Also, it would be nice to have performance numbers,
Here are some numbers I gathered for Ingo on v2 of the patch-set:
https://marc.info/?l=linux-kernel&m=151844711432661&w=2
I don't think they significantly chan
On Mon, Apr 16, 2018 at 11:43 PM, Eric Dumazet wrote:
>
>
> On 04/16/2018 08:33 AM, Yafang Shao wrote:
>> tcp_rcv_space_adjust is called every time data is copied to user space,
>> introducing a tcp tracepoint for which could show us when the packet is
>> copied to user.
>> This could help us figu
On Fri, Mar 30, 2018 at 9:55 AM, Kees Cook wrote:
> On the quest to remove all VLAs from the kernel[1], this avoids VLAs
> by just using the maximum allocation size (4 bytes) for stack arrays.
> All the VLAs in ecc were either 3 or 4 bytes (or a multiple), so just
> make it 4 bytes all the time. I
Quoting Geert Uytterhoeven (2018-04-10 05:51:37)
> The use of of_clk_get_parent_{count,name}() and of_clk_init() is not
> limited to clock providers.
>
> Hence move these helpers into their own header file, so callers that are
> not clock providers no longer have to include .
>
> Suggested-by: St
On Mon 2018-04-16 15:50:34, Sasha Levin wrote:
> On Mon, Apr 16, 2018 at 05:30:31PM +0200, Pavel Machek wrote:
> >On Mon 2018-04-16 08:18:09, Linus Torvalds wrote:
> >> On Mon, Apr 16, 2018 at 6:30 AM, Steven Rostedt
> >> wrote:
> >> >
> >> > I wonder if the "AUTOSEL" patches should at least have
On 16 Apr 16:40, Jan Kara wrote:
> Can you please run RIP through ./scripts/faddr2line to see where exactly
> are we looping? I expect the loop iterating over marks to notify but better
> be sure.
>
> How easily can you hit this? Are you able to run debug kernels / inspect
> crash dumps when the i
Hi Dennis,
> -Original Message-
> From: Dennis Gilmore [mailto:dgilm...@redhat.com]
> Sent: Friday, April 13, 2018 9:03 PM
> To: linux-kernel@vger.kernel.org; linux-a...@vger.kernel.org
> Cc: Limonciello, Mario
> Subject: issues with suspend on Dell XPS 13 2-in-1
>
> Hi All,
>
> I have a
On Mon, 16 Apr 2018 10:51:25 -0300
Arnaldo Carvalho de Melo wrote:
> Em Mon, Apr 16, 2018 at 11:23:45AM +0200, Jiri Olsa escreveu:
> > On Mon, Apr 16, 2018 at 01:22:40PM +0900, Namhyung Kim wrote:
> > > The map_groups__fixup_end() was called to set end addresses of kernel
> > > map and module map
Quoting Arnd Bergmann (2018-04-09 03:54:34)
> When power management is disabled, we get a harmless warning:
>
> drivers/clk/clk-cs2000-cp.c:544:12: error: 'cs2000_resume' defined but not
> used [-Werror=unused-function]
>
> Marking the function as __maybe_unused lets the compiler silently
> drop
On 04/16/2018 09:56 AM, Stefan Agner wrote:
On 27.03.2018 14:16, Dmitry Osipenko wrote:
On 27.03.2018 14:54, Robin Murphy wrote:
On 26/03/18 22:20, Dmitry Osipenko wrote:
On 25.03.2018 21:09, Stefan Agner wrote:
As documented in GCC naked functions should only use Basic asm
syntax. The Extend
On Fri, Apr 13 2018 at 16:40 -0600, Stephen Boyd wrote:
Quoting Lina Iyer (2018-04-11 14:24:31)
On Wed, Apr 11 2018 at 09:29 -0600, Stephen Boyd wrote:
>Quoting Lina Iyer (2018-04-09 09:08:00)
>> On Fri, Apr 06 2018 at 19:14 -0600, Stephen Boyd wrote:
>> >Quoting Lina Iyer (2018-04-05 09:18:26)
On Mon 2018-04-16 16:02:03, Sasha Levin wrote:
> On Mon, Apr 16, 2018 at 11:36:29AM -0400, Steven Rostedt wrote:
> >On Mon, 16 Apr 2018 08:18:09 -0700
> >Linus Torvalds wrote:
> >
> >> On Mon, Apr 16, 2018 at 6:30 AM, Steven Rostedt
> >> wrote:
> >> >
> >> > I wonder if the "AUTOSEL" patches sho
On Mon, Apr 16, 2018 at 11:01:57AM +0200, Geert Uytterhoeven wrote:
> On Mon, Apr 16, 2018 at 3:55 AM, Linus Torvalds
> wrote:
> > We actually have a fair amount of other removal and cleanups too. I
> > was somewhat pleasantly surprised by the number of pull requests that
> > actually ended up rem
Hello!
This series contains changes to the memory model, including the formal
model in tools/memory-model and documentation in memory-barriers.txt (plus
the Korean translation). These changes are ready for inclusion in -tip.
1. Rename LKMM's "link" and "rcu-path" relations to "rcu-link"
From: Alan Stern
This patch reorganizes the definition of rb in the Linux Kernel Memory
Consistency Model. The relation is now expressed in terms of
rcu-fence, which consists of a sequence of gp and rscs links separated
by rcu-link links, in which the number of occurrences of gp is >= the
number
From: Paolo Bonzini
"RWM" should be "RMW".
Signed-off-by: Paolo Bonzini
Signed-off-by: Paul E. McKenney
---
tools/memory-model/Documentation/cheatsheet.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/memory-model/Documentation/cheatsheet.txt
b/tools/memory-model
The key for "SELF" was missing completely and the key for "SV" was
a bit obtuse. This commit therefore adds a key for "SELF" and improves
the one for "SV".
Reported-by: Paolo Bonzini
Signed-off-by: Paul E. McKenney
---
tools/memory-model/Documentation/cheatsheet.txt | 3 ++-
1 file changed, 2
On Mon, 16 Apr 2018 16:02:03 +
Sasha Levin wrote:
> One of the things Greg is pushing strongly for is "bug compatibility":
> we want the kernel to behave the same way between mainline and stable.
> If the code is broken, it should be broken in the same way.
Wait! What does that mean? What's
From: Andrea Parri
This commit models 'smp_store_mb(x, val);' to be semantically equivalent
to 'WRITE_ONCE(x, val); smp_mb();'.
Suggested-by: Paolo Bonzini
Suggested-by: Peter Zijlstra
Signed-off-by: Andrea Parri
Signed-off-by: Paul E. McKenney
---
tools/memory-model/linux-kernel.def | 1 +
Linus,
The following changes since commit e01bca2fc698d7f0626f0214001af523e18ad60b:
kvm: x86: fix a prototype warning (2018-04-06 18:20:31 +0200)
are available in the git repository at:
git://git.kernel.org/pub/scm/virt/kvm/kvm.git tags/for-linus
for you to fetch changes up to d5edb7f8e7ab
From: SeongJae Park
This commit applies an upstream change, commit 40555946447a ("doc:
READ_ONCE() now implies smp_barrier_depends()") to the Korean version
document.
Signed-off-by: SeongJae Park
Signed-off-by: Paul E. McKenney
---
Documentation/translations/ko_KR/memory-barriers.txt | 15 +++
From: Andrea Parri
This commit fixes white spaces around semicolons.
Signed-off-by: Andrea Parri
Signed-off-by: Paul E. McKenney
---
tools/memory-model/linux-kernel.def | 28 ++--
1 file changed, 14 insertions(+), 14 deletions(-)
diff --git a/tools/memory-model/linux-
On Mon, Apr 16, 2018 at 9:01 AM, Joerg Roedel wrote:
>
> Okay, I verify if there are any global bits left in the page-tables.
> According to the PTDUMP_X86 the cpu_entry_area is mapped with G=1 (which
> should be fine?) and another 4M range in the kernel mapping. I need to
> check what that is.
A
From: Akira Yokosawa
Code generated by klitmus7 version 7.48 doesn't compile with kernel
header of 4.15 and later due to the absence of ACCESS_ONCE().
As the issue has been resolved in herdtools7 7.49, bump the required
version number in README.
Signed-off-by: Akira Yokosawa
Cc: Alan Stern
Cc:
The current cheat sheet does not claim that smp_mb__after_atomic()
orders later RMW atomic operations, which it must, at least against
earlier RMW atomic operations and whatever precedes them. This commit
therefore adds the needed "Y".
Signed-off-by: Paul E. McKenney
---
tools/memory-model/Docu
From: Andrea Parri
There appeared to be a certain, recurrent uncertainty concerning the
semantics of spin_is_locked(), likely a consequence of the fact that
this semantics remains undocumented or that it has been historically
linked to the (likewise unclear) semantics of spin_unlock_wait().
A re
From: Andrea Parri
Removes "#ifndef queued_spin_is_locked" from the generic code: this is
unused and it's reasonable to conclude that it will continue to be unused.
Also removes the comment about spin_is_locked() from mutex_is_locked():
the comment remains valid but not particularly useful.
Sug
On Tue, Apr 17, 2018 at 12:02:32AM +0900, Masahiro Yamada wrote:
> Follow up commit 788778b0d21a ("mmc: tmio: deprecate "toshiba,
> mmc-wrprotect-disable" DT property").
>
> Signed-off-by: Masahiro Yamada
Reviewed-by: Wolfram Sang
signature.asc
Description: PGP signature
From: SeongJae Park
This commit applies an upstream change, commit 9ad3c143d7d6 ("doc:
De-emphasize smp_read_barrier_depends") to the Korean version document.
Signed-off-by: SeongJae Park
Signed-off-by: Paul E. McKenney
---
Documentation/translations/ko_KR/memory-barriers.txt | 7 +--
1 f
From: SeongJae Park
This commit applies an upstream change, commit 621df431b0ac
("Documentation/memory-barriers.txt: Cross-reference
"tools/memory-model/"") to the Korean version document.
Signed-off-by: SeongJae Park
Signed-off-by: Paul E. McKenney
---
Documentation/translations/ko_KR/memory
From: SeongJae Park
This commit applies an upstream change, commit 51de78892b12
("memory-barriers: Fix description of data dependency barriers") to the
Korean version document.
Signed-off-by: SeongJae Park
Signed-off-by: Paul E. McKenney
---
Documentation/translations/ko_KR/memory-barriers.tx
On Mon, Apr 16, 2018 at 06:06:08PM +0200, Pavel Machek wrote:
>On Mon 2018-04-16 15:50:34, Sasha Levin wrote:
>> On Mon, Apr 16, 2018 at 05:30:31PM +0200, Pavel Machek wrote:
>> >On Mon 2018-04-16 08:18:09, Linus Torvalds wrote:
>> >> On Mon, Apr 16, 2018 at 6:30 AM, Steven Rostedt
>> >> wrote:
>
On Mon, Apr 16, 2018 at 8:54 AM Kees Cook wrote:
> On Sat, Apr 14, 2018 at 3:44 PM, Theodore Y. Ts'o wrote:
> > +linux...@kvack.org
> > k...@vger.kernel.org, secur...@kernel.org moved to bcc
> >
> > On Sat, Apr 14, 2018 at 10:59:21PM +0300, Alexey Dobriyan wrote:
> >> SLAB allocators got CONFIG_
From: SeongJae Park
This commit applies an upstream change, commit f28f0868feb1
("locking/memory-barriers: De-emphasize smp_read_barrier_depends() some
more") to the Korean version documentation.
Signed-off-by: SeongJae Park
Signed-off-by: Paul E. McKenney
---
.../translations/ko_KR/memory-ba
From: Andrea Parri
Commit 38b850a73034f ("arm64: spinlock: order spin_{is_locked,unlock_wait}
against local locks") added an smp_mb() to arch_spin_is_locked(), in order
"to ensure that the lock value is always loaded after any other locks have
been taken by the current CPU", and reported one exam
From: Will Deacon
The section of memory-barriers.txt that describes the dma_Xmb() barriers
has an incorrect example claiming that a wmb() is required after writing
to coherent memory in order for those writes to be visible to a device
before a subsequent MMIO access using writel() can reach the d
From: Alan Stern
This patch makes a simple non-functional change to the RCU portion of
the Linux Kernel Memory Consistency Model by renaming the "link" and
"rcu-path" relations to "rcu-link" and "rb", respectively.
The name "link" was an unfortunate choice, because it was too generic
and subject
> As far as I've understood the idea is that most "error" return values
> actually are a result of disabled runtime PM, and that should be
> transparent to the caller. Looking at the code, that's what the vast
> majority of callers do - they just ignore the return value of
> pm_runtime_get_sync, a
On Mon, Apr 16, 2018 at 12:12:24PM -0400, Steven Rostedt wrote:
>On Mon, 16 Apr 2018 16:02:03 +
>Sasha Levin wrote:
>
>> One of the things Greg is pushing strongly for is "bug compatibility":
>> we want the kernel to behave the same way between mainline and stable.
>> If the code is broken, it
There is no functional change, just replacing regmap_read()/modify/
regmap_write() with regmap_update_bits() function calls.
Signed-off-by: Sylwester Nawrocki
---
drivers/phy/samsung/phy-exynos-mipi-video.c | 34 -
1 file changed, 14 insertions(+), 20 deletions(-)
di
Add support for DMAs to STM32 timers. STM32 Timers can support up to 7
dma requests: up to 4 channels, update, compare and trigger.
DMAs may be used to transfer data from pwm capture for instance.
DMA support is made optional, PWM capture support is also an option.
This is much more wise system-wid
Enable pwm3 input capture on stm32f429i-eval, by using DMA.
Signed-off-by: Fabrice Gasnier
Reviewed-by: Benjamin Gaignard
---
arch/arm/boot/dts/stm32429i-eval.dts | 3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/arm/boot/dts/stm32429i-eval.dts
b/arch/arm/boot/dts/stm32429i-eval.dts
On Mon, 16 Apr 2018 18:06:08 +0200
Pavel Machek wrote:
> That means you want to ignore not-so-serious bugs, because benefit of
> fixing them is lower than risk of the regressions. I believe bugs that
> do not bother anyone should _not_ be fixed in stable.
>
> That was case of the LED patch. Yes,
Using input prescaler, capture unit will trigger DMA once every
configurable /2, /4 or /8 events (rising edge). This helps improve
period (only) capture accuracy at high rates.
Signed-off-by: Fabrice Gasnier
Reviewed-by: Benjamin Gaignard
Acked-by: Thierry Reding
---
Changes in v2:
- Adopt DMA
STM32 Timers can support up to 7 DMA requests:
- 4 channels, update, compare and trigger.
Optionally request part, or all DMAs from stm32-timers MFD core.
Also add routine to implement burst reads using DMA from timer registers.
This is exported. So, it can be used by child drivers, PWM capture
fo
Hello!
This series contains a few additional changes to tools/memory-model,
however, the members of this series need more discussion and feedback
before they are ready for inclusion.
1. Add LKMM test scripts.
2. Add litmus test for full-up multicopy atomicity.
3. Add experimental
Currently, capture is based on timeout window to configure prescaler.
PWM capture framework provides 1s window at the time of writing.
There's place for improvement, after input signal has been captured once:
- Finer tune counter clock prescaler, by using 1st capture result (with
arbitrary margin)
Add support for PMW input mode on pwm-stm32. STM32 timers support
period and duty cycle capture as long as they have at least two PWM
channels. One capture channel is used for period (rising-edge), one
for duty-cycle (falling-edge).
When there's only one channel available, only period can be captur
This commit adds a pair of scripts that run the memory model on litmus
tests, checking that the verification result of each litmus test matches
the result flagged in the litmus test itself. These scripts permit easier
checking of changes to the memory model against preconceived notions.
Signed-of
This commit flags WRC+pooncerelease+rmbonceonce+Once.litmus as being
forbidden by LKMM cumulativity and IRIW+mbonceonces+OnceOnce.litmus as
being forbidden by LKMM propagation.
Reported-by: Paolo Bonzini
Suggested-by: Andrea Parri
Signed-off-by: Paul E. McKenney
[ paulmck: Updated wording as su
This commit adds a litmus test suggested by Alan Stern that is forbidden
on multicopy atomic systems, but allowed on non-multicopy atomic systems.
Note that other-multicopy atomic systems are examples of non-multicopy
atomic systems.
Suggested-by: Alan Stern
Signed-off-by: Paul E. McKenney
---
From: Luc Maranget
This commit first adds a trivial macro for spin_is_locked() to
linux-kernel.def.
It also adds cat code for enumerating all possible matches of lock
write events (set LKW) with islocked events returning true (set RL,
for Read from Lock), and unlock write events (set UL) with is
On Mon, 16 Apr 2018 16:14:15 +
Sasha Levin wrote:
> Since the rate we're seeing now with AUTOSEL is similar to what we were
> seeing before AUTOSEL, what's the problem it's causing?
Does that mean we just doubled the rate of regressions? That's the
problem.
>
> How do you know if a bug bot
On Thu, Apr 12, 2018 at 8:12 AM, KarimAllah Ahmed wrote:
> v2 -> v3:
> - Remove the forced VMExit from L2 after reading the kvm_state. The actual
> problem is solved.
> - Rebase again!
> - Set nested_run_pending during restore (not sure if it makes sense yet or
> not).
This doesn't actually
This commit adds s390.cat and s390.cfg files to allow users to check
litmus tests for s390-specific code. Note that this change only enables
herd7 checking of C-language litmus tests. Larger changes are required
to enable the litmus7 and klitmus7 tools to check litmus tests on real
hardare.
Sugg
This series adds support for capture to stm32-pwm driver.
Capture is based on DMAs.
- First two patches add support for requesting DMAs to MFD core
- Next three patches add support for capture to stm32-pwm driver
- This has been tested on stm32429i-eval board.
---
Changes in v4:
- Lee's comments o
Quoting Jerome Brunet (2018-04-09 06:59:19)
> CLK_MUX_ROUND_CLOSEST is part of clk_mux and meson's clk_regmap
> documentation, so it should be honored by the determine_rate() callback.
>
> It is note the case ATM. The series fixes this problem.
I'll apply these for clk-fixes.
On Sun, Apr 15, 2018 at 6:12 AM, Raslan, KarimAllah wrote:
> On Sun, 2018-04-15 at 00:26 +0200, KarimAllah Ahmed wrote:
>> Switch 'requests' to be explicitly 64-bit and update BUILD_BUG_ON check to
>> use the size of "requests" instead of the hard-coded '32'.
>>
>> That gives us a bit more room ag
Hi Yamada-san,
On Mon, Apr 16, 2018 at 5:02 PM, Masahiro Yamada
wrote:
> Follow up commit 788778b0d21a ("mmc: tmio: deprecate "toshiba,
> mmc-wrprotect-disable" DT property").
Thanks for following up this work.
(I had the exact same changes queued up in my local branch, to be sent out
after v4
On Mon, Apr 16, 2018 at 12:20:19PM -0400, Steven Rostedt wrote:
>On Mon, 16 Apr 2018 18:06:08 +0200
>Pavel Machek wrote:
>
>> That means you want to ignore not-so-serious bugs, because benefit of
>> fixing them is lower than risk of the regressions. I believe bugs that
>> do not bother anyone shou
- On Apr 12, 2018, at 4:23 PM, Andi Kleen a...@firstfloor.org wrote:
>> Can we plan on merging just the plain rseq parts *without* this all
>> first, and then see the cpu_opv thing as a "maybe future expansion"
>> part.
>
> That would be the right way to go. I doubt anybody really needs cpu_o
On 15/04/2018 00:26, KarimAllah Ahmed wrote:
> Switch 'requests' to be explicitly 64-bit and update BUILD_BUG_ON check to
> use the size of "requests" instead of the hard-coded '32'.
>
> That gives us a bit more room again for arch-specific requests as we
> already ran out of space for x86 due to
> >> Is there a reason not to take LED fixes if they fix a bug and don't
> >> cause a regression? Sure, we can draw some arbitrary line, maybe
> >> designate some subsystems that are more "important" than others, but
> >> what's the point?
> >
> >There's a tradeoff.
> >
> >You want to fix serious
On Mon, 16 Apr 2018 16:19:14 +
Sasha Levin wrote:
> >Wait! What does that mean? What's the purpose of stable if it is as
> >broken as mainline?
>
> This just means that if there is a fix that went in mainline, and the
> fix is broken somehow, we'd rather take the broken fix than not.
>
>
On Mon, Apr 16, 2018 at 12:22:44PM -0400, Steven Rostedt wrote:
>On Mon, 16 Apr 2018 16:14:15 +
>Sasha Levin wrote:
>
>> Since the rate we're seeing now with AUTOSEL is similar to what we were
>> seeing before AUTOSEL, what's the problem it's causing?
>
>Does that mean we just doubled the rate
Hi Greg,
On 04/15/2018 10:31 AM, Greg Kroah-Hartman wrote:
On Fri, Apr 13, 2018 at 03:07:18PM +0200, Steffen Maier wrote:
Complements v2.6.31 commit 55782138e47d ("tracing/events: convert block
trace points to TRACE_EVENT()") to be equivalent to traditional blktrace
output. Also this allows eve
Quoting Ryder Lee (2018-04-15 19:31:58)
> The hdmitx_dig_cts clock signal is not a child of clk26m,
> and the actual output of the PLL block is derived from
> the tvdpll via a configurable PLL post-divider.
>
> It is used as the PLL reference input to the HDMI PHY module.
>
> Signed-off-by: Chunh
On Mon, Apr 16, 2018 at 12:30:19PM -0400, Steven Rostedt wrote:
>On Mon, 16 Apr 2018 16:19:14 +
>Sasha Levin wrote:
>
>> >Wait! What does that mean? What's the purpose of stable if it is as
>> >broken as mainline?
>>
>> This just means that if there is a fix that went in mainline, and the
>> f
On Mon, Apr 16, 2018 at 06:28:50PM +0200, Pavel Machek wrote:
>
>> >> Is there a reason not to take LED fixes if they fix a bug and don't
>> >> cause a regression? Sure, we can draw some arbitrary line, maybe
>> >> designate some subsystems that are more "important" than others, but
>> >> what's th
On Mon 2018-04-16 16:28:00, Sasha Levin wrote:
> On Mon, Apr 16, 2018 at 12:20:19PM -0400, Steven Rostedt wrote:
> >On Mon, 16 Apr 2018 18:06:08 +0200
> >Pavel Machek wrote:
> >
> >> That means you want to ignore not-so-serious bugs, because benefit of
> >> fixing them is lower than risk of the re
On Mon, Apr 16, 2018 at 8:28 AM, Steven Rostedt wrote:
> On Mon, 16 Apr 2018 14:31:49 +
> "Bean Huo (beanhuo)" wrote:
>
>> Print the request tag along with other information
>> while tracing a command.
>>
>> Signed-off-by: Bean Huo
Acked-by: Rajat Jain
>> ---
>
> I don't see any issue with
On Mon 2018-04-16 16:39:20, Sasha Levin wrote:
> On Mon, Apr 16, 2018 at 06:28:50PM +0200, Pavel Machek wrote:
> >
> >> >> Is there a reason not to take LED fixes if they fix a bug and don't
> >> >> cause a regression? Sure, we can draw some arbitrary line, maybe
> >> >> designate some subsystems t
On Mon, Apr 16, 2018 at 06:39:53PM +0200, Pavel Machek wrote:
>On Mon 2018-04-16 16:28:00, Sasha Levin wrote:
>> On Mon, Apr 16, 2018 at 12:20:19PM -0400, Steven Rostedt wrote:
>> >On Mon, 16 Apr 2018 18:06:08 +0200
>> >Pavel Machek wrote:
>> >
>> >> That means you want to ignore not-so-serious bu
On Mon, Apr 16, 2018 at 06:42:30PM +0200, Pavel Machek wrote:
>On Mon 2018-04-16 16:39:20, Sasha Levin wrote:
>> On Mon, Apr 16, 2018 at 06:28:50PM +0200, Pavel Machek wrote:
>> >
>> >> >> Is there a reason not to take LED fixes if they fix a bug and don't
>> >> >> cause a regression? Sure, we can
From: Hans Holmberg
When switching between different lun configurations, there is no
guarantee that all lines that contain closed/open chunks have some
valid data to recover.
Check that the smeta chunk has been written to instead. Also
skip bad lines (that does not have enough good chunks).
Sig
501 - 600 of 1099 matches
Mail list logo
