For debugging purposes it may be useful to know what are the devices whose
probe function was deferred. Add a debugfs entry showing that information.
$ cat /sys/kernel/debug/deferred_devices
4807.i2c:twl@48:bci
musb-hdrc.0.auto
omapdrm.0
Signed-off-by: Javier Martinez Canillas
---
On Tue, Jun 19, 2018 at 06:13:17PM +0100, Quentin Perret wrote:
> I agree having one list per root_domain should be better. I'll change that
> in v4. But I also think the idea of a global static_key is broken then.
Static keys are global per definition, there is only a single copy of
the code.
On Thu, Jun 14, 2018 at 05:47:03AM -0700, syzbot wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:d2d741e5d189 kmsan: add initialization for shmem pages
> git tree: https://github.com/google/kmsan.git/master
> console output:
The PATCH_MAX_SIZE macro should contain the maximum of all family patch
sizes.
Since these sizes are defined in an other place than this macro, let's add
a reminder to them so people will remember to verify PATCH_MAX_SIZE
correctness when modifying a family patch size or adding a new family.
Convert the late loader in the AMD microcode update driver to use newly
introduced microcode container data checking functions as it was previously
done for the early loader.
Signed-off-by: Maciej S. Szmigiero
---
arch/x86/kernel/cpu/microcode/amd.c | 67 +
1 file
Add verify_container(), verify_equivalence_table(), verify_patch_section()
and verify_patch() functions to the AMD microcode update driver.
These functions check whether a passed buffer contains the relevant
structure, whether it isn't truncated and (for actual microcode patches)
whether the size
Convert the early loader in the AMD microcode update driver to use the
container data checking functions introduced by previous commits.
We have to be careful to call these functions with 'early' parameter set,
so they won't try to print errors as the early loader runs too early for
Randy Dunlap writes:
> Hi Dirk,
>
> On 06/17/2018 05:15 AM, Dirk Gouders wrote:
>>
>> At any time, at most one i-search is active and the navigation path to
>> the current menu is displayed in the subtitle, the second line in the
>> menu window.
>
> Nice.
>
> And the highlight of the current
On Tue, 2018-06-19 at 11:36 -0700, Matthias Kaehlcke wrote:
> On Tue, Jun 19, 2018 at 11:07:47AM -0700, Joe Perches wrote:
> > On Tue, 2018-06-19 at 19:35 +0200, Paolo Bonzini wrote:
> > > On 19/06/2018 19:23, Joe Perches wrote:
> > > > On Tue, 2018-06-19 at 10:08 -0700, Nick Desaulniers wrote:
>
On Tue, 19 Jun 2018, Peter Zijlstra wrote:
> On Tue, Jun 19, 2018 at 07:32:49PM +0200, Thomas Gleixner wrote:
> > On Fri, 15 Jun 2018, Pavel Tatashin wrote:
> >
> > > tsc_disabled is set when notsc is passed as kernel parameter. The reason
> > > we
> > > have notsc is to avoid timing problems on
On Tue, Jun 19, 2018 at 8:19 AM Jason A. Donenfeld wrote:
>
> On Tue, Jun 19, 2018 at 5:08 PM Shakeel Butt wrote:
> > > > Are you using SLAB or SLUB? We stress kernel pretty heavily, but with
> > > > SLAB, and I suspect Shakeel may also be using SLAB. So if you are
> > > > using SLUB, there is
Hi Boris,
On 06/19/2018 04:46 AM, Borislav Petkov wrote:
On Thu, Jun 14, 2018 at 07:08:26AM -0500, Brijesh Singh wrote:
I think depends should look like this:
config KVM_AMD_SEV
def_bool y
bool "AMD Secure Encrypted Virtualization (SEV) support"
depends KVM_AMD && X86_64
Switching to Thumb-2 mode can be done using a single 'sub' instruction
so use that instead of the badr macro in various places in the code.
This allows us to reimplement the macro in a way that does not allow
it to be used in ARM code sequences when building a Thumb2 kernel.
Signed-off-by: Ard
To work around recent issues where ADR references to Thumb function
symbols may or may not have the Thumb bit set already when they are
resolved by GAS, reference the symbol indirectly via a local symbol
typed as 'function', and emit the reference in a way that prevents
the assembler from
Work around the mindless and backward incompatible change in GAS that
prevents us from using a simple addition to set the Thumb bit in local
symbol references taken using 'adr' instructions (#2)
As a preparatory step, remove badr occurrences in ARM code sequences
contained in Thumb2 kernels.
Ard
The AM654 SoC is a lead device of the K3 Multicore SoC architecture
platform, targeted for broad market and industrial control with aim to
meet the complex processing needs of modern embedded products.
Some highlights of this SoC are:
* Quad ARMv8 A53 cores split over two clusters
* GICv3
Secure Proxy is another communication scheme in Texas Instrument's
devices intended to provide an unique communication path from various
processors in the System on Chip(SoC) to a central System Controller.
Secure proxy is, in effect, an evolution of current generation Message
Manager hardware
Hi,
This is an update from RFC posted earlier:
https://marc.info/?l=linux-arm-kernel=152817866312732=2
The following series enables support for newest addition in TI's SoC
portfolio - AM654 SoC.
The series is based off v4.18-rc1, also available here:
Hi Tomer,
I love your patch! Perhaps something to improve:
[auto build test WARNING on hwmon/hwmon-next]
[also build test WARNING on v4.18-rc1 next-20180619]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci
Texas Instrument's System Control Interface (TISCI) permits
the ability for OSs running in virtual machines to be able to
independently communicate with the firmware without the need going
through an hypervisor.
The "host-id" in effect is the hardware representation of the
host (example: VMs
Add option to build AM6 SoC specific components
Signed-off-by: Benjamin Fair
Signed-off-by: Nishanth Menon
---
(new patch broken out from: https://patchwork.kernel.org/patch/10447719/)
drivers/soc/ti/Kconfig | 14 ++
1 file changed, 14 insertions(+)
diff --git
On Tue, Jun 19, 2018 at 02:22:53PM -0500, Brijesh Singh wrote:
> It would be nice to have a single depends. But the main issue is, PSP
> support is provided through the ccp driver (aka CRYPTO_DEV_CCP_DD).
And this sentence states also your dependency:
KVM_AMD_SEV <- PSP driver <- CCP driver
but
Add support for Texas Instrument's K3 Multicore SoC architecture
processors.
Signed-off-by: Nishanth Menon
---
Changes since RFC:
* None
RFC: https://patchwork.kernel.org/patch/10447633/
arch/arm64/Kconfig.platforms | 7 +++
1 file changed, 7 insertions(+)
diff --git
The AM654 SoC is a lead device of the K3 Multicore SoC architecture
platform, targeted for broad market and industrial control with aim to
meet the complex processing needs of modern embedded products.
Some highlights of this SoC are:
* Quad ARMv8 A53 cores split over two clusters
* GICv3
AM654 uses a UART controller that is compatible (partially) with
existing 8250 UART, however, has a few differences with respect to DMA
support and control paths. Introduce a base definition that allows us
to build up the differences in follow on patches.
Cc: Sekhar Nori
Cc: Vignesh R
AM654 uses a UART controller that is only partially compatible with
existing 8250 UART. UART DMA integration is substantially different
and even a match against standard 8250 or omap4 would result in
non-working UART once DMA is enabled by default.
Introduce a specific compatible to help build up
Texas Instrument's System Control Interface (TISCI) permits the
ability for Operating Systems to running in virtual machines to be
able to independently communicate with the firmware without the need
going through an hypervisor.
The "host-id" in effect is the hardware representation of the
host
On 19 June 2018 at 20:20, Ard Biesheuvel wrote:
> On 19 June 2018 at 20:17, Ard Biesheuvel wrote:
>> On 19 June 2018 at 19:24, Guenter Roeck wrote:
>>> On Tue, Jun 19, 2018 at 03:35:07PM +0200, Ard Biesheuvel wrote:
>>
>> + /* this needs to be a separate macro or \@ does not
On Tue, Jun 19, 2018 at 11:07:47AM -0700, Joe Perches wrote:
> On Tue, 2018-06-19 at 19:35 +0200, Paolo Bonzini wrote:
> > On 19/06/2018 19:23, Joe Perches wrote:
> > > On Tue, 2018-06-19 at 10:08 -0700, Nick Desaulniers wrote:
> > > > On Tue, Jun 19, 2018 at 8:19 AM Paolo Bonzini
> > > > wrote:
On Tue, Jun 19, 2018 at 07:13:41PM +0200, Paolo Bonzini wrote:
> On 19/06/2018 19:08, Nick Desaulniers wrote:
> >> This one really makes the code uglier though, so I'm not really inclined
> >> to applying the patch.
> > Note that of the three variables (w, u, x), only u is used later on.
> > What
From: Randy Dunlap
At over 4000 #includes, is the 9th most
#included header file in the Linux kernel. It does not need
, so drop that header and explicitly add
to source files that need it.
4146 #include
After this patch, there are 225 files that use ,
for a reduction of around 3900
verify_and_add_patch() returned a single "int" value which encoded both
this function error status and also a length of microcode container data to
skip.
Unfortunately, ranges of these two values collide: the length of data to
skip can be any value between 1 and UINT_MAX, so, for example, error
verify_patch_size() verifies whether the remaining size of the microcode
container file is large enough to contain a patch of the indicated size.
However, the section header length is not included in this indicated
size but it is present in the leftover file length so it should be
subtracted from
Currently, the code scanning the CPU equivalence table read from a
microcode container file assumes that it actually contains a terminating
zero entry.
Let's check also the size of this table to make sure that we don't read
past it in case it actually doesn't.
Signed-off-by: Maciej S. Szmigiero
Currently, it is very easy to make the AMD microcode update driver crash
or spin on a malformed microcode container file since it does very little
consistency checking on data loaded from such file.
This series introduces various checks, mostly on length-type fields,
so all corrupted microcode
Integrating verify_patch_size() into verify_patch() allows us to check
whether the indicated patch size makes sense for its indicated CPU family -
for all CPU families known to the driver.
If we spot a patch that is longer than expected for its family we'll
carefully skip over only the expected
On Tue, Jun 19, 2018 at 07:32:49PM +0200, Thomas Gleixner wrote:
> On Fri, 15 Jun 2018, Pavel Tatashin wrote:
>
> > tsc_disabled is set when notsc is passed as kernel parameter. The reason we
> > have notsc is to avoid timing problems on multi-socket systems. We already
> > have a mechanism,
Convert pointer to CPU equivalence table global static variable into a
struct descriptor in preparation for tracking also the size of this table.
Signed-off-by: Maciej S. Szmigiero
---
arch/x86/kernel/cpu/microcode/amd.c | 24 +---
1 file changed, 13 insertions(+), 11
update_permission_bitmask() negates u8 bitmask values and assigns them
to variables of type u8. Since the MSB is set in the bitmask values the
compiler expands the negated values to int, which then is assigned to
an u8 variable. Cast the negated value back to u8.
This fixes several warnings like
On 06/19/2018 11:47 AM, Dirk Gouders wrote:
> Randy Dunlap writes:
>
>> Hi Dirk,
>>
>> On 06/17/2018 05:15 AM, Dirk Gouders wrote:
>>>
>>> At any time, at most one i-search is active and the navigation path to
>>> the current menu is displayed in the subtitle, the second line in the
>>> menu
The EValuation Module(EVM) platform for AM654 consists of a
common Base board + one or more of daughter cards, which include:
a) "Personality Modules", which can be specific to a profile, such as
ICSSG enabled or Multi-media (including audio).
b) SERDES modules, which may be 2 lane PCIe or two
In a much bigger system SoCs, the number of Rx channels can be
many and mostly unused based on the system of choice, and not all
Rx channels need IRQs and allocating all memory at probe will be
inefficient. Some SoCs could have total threads in the 100s and usage
would be just 1 Rx thread.
Thus,
Hi,
The following series enables support for Secure Proxy in newest addition in
TI's SoC
portfolio - AM654 SoC (posted previously as RFC).
The series is based on v4.18-rc1 and is available here:
https://github.com/nmenon/linux-2.6-playground/commits/upstream/v4.18-rc1/k3-1-am6-sproxy
There are
For newer generation of the hardware, the naming of the region is
decided at integration level and there could be additional regions
as well. Hence move the region naming to be described from compatible
descriptor.
Signed-off-by: Nishanth Menon
---
Changes since RFC: None
RFC:
On Wed, May 16, 2018 at 05:12:21PM -0600, Keith Busch wrote:
> On Wed, May 16, 2018 at 06:44:22PM -0400, Sinan Kaya wrote:
> > On 5/16/2018 5:33 PM, Alexandru Gagniuc wrote:
> > > AER status bits are sticky, and they survive system resets. Downstream
> > > devices are usually taken care of after
On Tue, 19 Jun 2018 09:01:01 +0100 David Howells wrote:
> Andrew Morton wrote:
>
> > Please cc Alexey on /proc patches.
>
> If Alexey is responsible for procfs he should declare this in MAINTAINERS.
oop. I thought we did that but it isn't there.
> > What are the user-visible runtime
On Wed, 30 May, at 04:22:36PM, Peter Zijlstra wrote:
> Hi all,
>
> This is all still very preliminary and could all still go up in flames (it has
> only seen hackbench so far). This is mostly the same code I posted yesterday,
> but hopefully in a more readable form.
>
> This fixes the SIS_PROP
From: "Joel Fernandes (Google)"
When rcutorture is built as a built-in, we can detect that and raise the
priority of RCU's kthreads enough that rcutorture's boost threads will
not be able to starve them. We do so in earlier patches.
However, if rcutorture is built as a module, we wouldn't have
The pinctrl settings were incorrect for the touchscreen interrupt line, causing
an interrupt storm. This change has been tested with both the atmel_mxt_ts and
RMI4 drivers on the RDU1 units.
Signed-off-by: Nick Dyer
---
arch/arm/boot/dts/imx51-zii-rdu1.dts | 4 ++--
1 file changed, 2
On Sat, May 19, 2018 at 12:52:49PM -0400, Sinan Kaya wrote:
> A PCIe endpoint carries the process address space identifier (PASID) in
> the TLP prefix as part of the memory read/write transaction. The address
> information in the TLP is relevant only for a given PASID context.
>
> A translation
From: "Joel Fernandes (Google)"
rcutorture boost tests fail even with CONFIG_RCU_BOOST set because
rcutorture's threads are equal priority to the default RCU kthreads (RT
class with priority of 1).
This patch checks if RCU torture is built into the kernel and if so,
assigns a higher priority to
at 4:34 PM, Yang Shi wrote:
> When running some mmap/munmap scalability tests with large memory (i.e.
>> 300GB), the below hung task issue may happen occasionally.
>
> INFO: task ps:14018 blocked for more than 120 seconds.
> Tainted: GE 4.9.79-009.ali3000.alios7.x86_64 #1
>
On Tue, Jun 19, 2018 at 08:41:39AM -0700, Paul E. McKenney wrote:
> On Tue, Jun 19, 2018 at 09:12:23AM -0400, Steven Rostedt wrote:
> > On Tue, 19 Jun 2018 00:31:15 -0700
> > Joel Fernandes wrote:
> >
> > > Hi Paul,
> > > Think some more about this counter, I think you mean 'successes' as in
> >
From: "Joel Fernandes (Google)"
rcutorture currently increments both successes and error for barrier
test incase of errors. It should only increment the error counter incase
of errors so make it do so.
Test: Introduced rcu_barrier errors by returning from the barrier
callback without
On Tue, Jun 19, 2018 at 09:00:24AM -0700, Paul E. McKenney wrote:
> On Mon, Jun 18, 2018 at 11:34:21PM -0700, Joel Fernandes wrote:
> > On Mon, Jun 18, 2018 at 11:22:14PM -0700, Joel Fernandes wrote:
> > > From: "Joel Fernandes (Google)"
> > >
> > > rcutorture boost tests fail even with
On Tue, 19 Jun 2018 14:33:52 -0700 Shakeel Butt wrote:
> For !CONFIG_SLUB_DEBUG, SLUB does not maintain the number of slabs
> allocated per node for a kmem_cache. Thus, slabs_node() in
> __kmem_cache_empty() will always return 0. So, in such situation, it is
> required to check per-cpu slabs to
On 6/19/2018 5:43 PM, Bjorn Helgaas wrote:
>> Hotplug driver removes the device from system when a link down interrupt
>> is observed and performs re-enumeration when link up interrupt is observed.
>>
>> This conflicts with what this code is trying to do. Try secondary bus reset
>> only if
On 19 June 2018 at 22:45, Guenter Roeck wrote:
> On Tue, Jun 19, 2018 at 10:34:38PM +0200, Ard Biesheuvel wrote:
>> On 19 June 2018 at 22:32, Guenter Roeck wrote:
>> > On Tue, Jun 19, 2018 at 09:26:31PM +0200, Ard Biesheuvel wrote:
>> >> Work around the mindless and backward incompatible change
The ashmem driver did not check that the size/offset of the vma passed
to its .mmap() function was not larger than the ashmem object being
mapped. This could cause mmap() to succeed, even though accessing parts
of the mapping would later fail with a segmentation fault.
Ensure an error is returned
From: Randy Dunlap
At over 4000 #includes, is the 9th most
#included header file in the Linux kernel. It does not need
, so drop that header and explicitly add
to source files that need it.
4146 #include
After this patch, there are 225 files that use ,
for a reduction of around 3900
On Tue, 12 Jun 2018 11:32:05 -0400 Christian Hansen wrote:
> Adding a new flag that will read kpagecount for each PFN
> and print out the number of time the page is mapped along
> with the flags in the listing view.
tools/vm/page-types.c isn't particularly documented, although it might
be
On Tue, Jun 19, 2018 at 11:12:05AM +0200, Thomas Gleixner wrote:
> On Fri, 15 Jun 2018, Fenghua Yu wrote:
>
> > A few new user wait instructions UMONITOR, UMWAIT, and TPAUSE are
> > published in the latest Intel Instruction Set Extensions document.
> >
> > Define the APIs for user or kernel to
On Tue, 12 Jun 2018 11:32:05 -0400 Christian Hansen wrote:
> Adding a new flag that will read kpagecount for each PFN
> and print out the number of time the page is mapped along
> with the flags in the listing view.
Also... the above describes what the patch does, but not why it does
it. Why
On Tue, 19 Jun 2018, Fenghua Yu wrote:
> On Tue, Jun 19, 2018 at 10:57:44AM +0200, Thomas Gleixner wrote:
> > On Fri, 15 Jun 2018, Fenghua Yu wrote:
> >
> > > MOVDIRI moves doubleword or quadword from register to memory through
> > > direct store which is implemented by using write combining
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: ba4dbdedd3edc2798659bcd8b1a184ea8bdd04dc
commit: ce08eaeb6388e78daf35a5ce2e72a19026def8a7 staging: typec: rt1711h typec
chip driver
date: 8 weeks ago
config: x86_64-randconfig-s4-06200335 (attached as
On Wed, Jun 20, 2018 at 12:32:14AM +0200, Thomas Gleixner wrote:
> On Tue, 19 Jun 2018, Fenghua Yu wrote:
>
> > On Tue, Jun 19, 2018 at 10:57:44AM +0200, Thomas Gleixner wrote:
> > > On Fri, 15 Jun 2018, Fenghua Yu wrote:
> > >
> > > > MOVDIRI moves doubleword or quadword from register to memory
On Tue, 19 Jun 2018, Fenghua Yu wrote:
> On Tue, Jun 19, 2018 at 11:12:05AM +0200, Thomas Gleixner wrote:
> > On Fri, 15 Jun 2018, Fenghua Yu wrote:
> >
> > > A few new user wait instructions UMONITOR, UMWAIT, and TPAUSE are
> > > published in the latest Intel Instruction Set Extensions document.
On Wed, Jun 20, 2018 at 12:34:32AM +0200, Thomas Gleixner wrote:
> On Tue, 19 Jun 2018, Fenghua Yu wrote:
> > On Tue, Jun 19, 2018 at 11:12:05AM +0200, Thomas Gleixner wrote:
> > > On Fri, 15 Jun 2018, Fenghua Yu wrote:
> > >
> > > > A few new user wait instructions UMONITOR, UMWAIT, and TPAUSE
On Tue, 12 Jun 2018 11:32:23 -0400 Christian Hansen wrote:
> Adding a flag which will use the kernels's idle
> page tracking to mark pages idle. As the tool already
> prints the idle flag if set, subsequent runs will show
> which pages have been accessed since last run.
That sounds useful.
On Tue, 12 Jun 2018 11:32:23 -0400 Christian Hansen wrote:
> Adding a flag which will use the kernels's idle
> page tracking to mark pages idle. As the tool already
> prints the idle flag if set, subsequent runs will show
> which pages have been accessed since last run.
Also, it would be
On Tue 19 Jun 06:11 PDT 2018, Raju P L S S S N wrote:
> From: Lina Iyer
>
> Add device binding documentation for Qualcomm Technology Inc's RPMH RSC
> driver. The driver is used for communicating resource state requests for
> shared resources.
>
> Cc: devicet...@vger.kernel.org
> Signed-off-by:
On Wed, Jun 20, 2018 at 12:23:56AM +0200, Ard Biesheuvel wrote:
>
> OK, so even the linker handling is inconsistent.
>
> Working (binutils 2.30)
>
> c0301164 :
> c0301164: f8d9 a000 ldr.w sl, [r9]
> c0301168: e92d 0030 stmdb sp!, {r4, r5}
> c030116c: f01a 0ff0
On Tue, Jun 19, 2018 at 10:59:14PM +0200, Javier Martinez Canillas wrote:
> For debugging purposes it may be useful to know what are the devices whose
> probe function was deferred. Add a debugfs entry showing that information.
>
> $ cat /sys/kernel/debug/deferred_devices
>
On Fri, 15 Jun 2018, Pavel Tatashin wrote:
> This patch adds early clock feature to x86 platforms.
See Documentation about 'This patch' We already know that this is a
patch otherwise it would not be marked as such ...
> +/*
> + * Finish clock for early time stamps, and hand over to
On Wed, Jun 20, 2018 at 5:23 AM Benjamin Herrenschmidt
wrote:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/benh/powerpc.git merge
I love the alleged line removal, but there's nothing in that 'merge'
branch. It points to an ancient powerpc commit from 2016.
And please, signed tags. I know
On Tue, Jun 19, 2018 at 9:09 AM Johannes Weiner wrote:
>
> Hi Shakeel,
>
> this looks generally reasonable to me.
>
> However, patch 1 introduces API that isn't used until patch 2 and 3,
> which makes reviewing harder since you have to jump back and forth
> between emails. Please fold patch 1 and
On Mon, 9 Aug 2010, Andi Kleen wrote:
^^^
Care to fix your system clock?
On Tue, Jun 19, 2018 at 03:24:44PM -0700, Alistair Strachan wrote:
> The ashmem driver did not check that the size/offset of the vma passed
> to its .mmap() function was not larger than the ashmem object being
> mapped. This could cause mmap() to succeed, even though accessing parts
> of the
On Mon, 11 Jun 2018 13:10:04 +0200 Dmitry Vyukov wrote:
> Currently task hung checking interval is equal to timeout,
> as the result hung is detected anywhere between timeout and 2*timeout.
> This is fine for most interactive environments, but this hurts automated
> testing setups (syzbot). In
Hi Randy,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v4.18-rc1 next-20180619]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux
On 05/24/2018 09:26 PM, Waiman Long wrote:
> It was found that the use of up_read_non_owner() in NFS was causing
> the following warning when DEBUG_RWSEMS was configured.
>
> DEBUG_LOCKS_WARN_ON(sem->owner != ((struct task_struct *)(1UL << 0)))
>
> Looking into the rwsem.c file, it was
On Fri, 15 Jun 2018, Pavel Tatashin wrote:
> Early boot clock might differ from the clock that is used later on,
> therefore add a new field to pv_time_ops, that shows currently active
> clock. If platform supports early boot clock, this field will be changed
> to use that clock early in boot, and
On Fri, 15 Jun 2018, Pavel Tatashin wrote:
> cpu_khz = x86_platform.calibrate_cpu();
> @@ -1380,7 +1466,7 @@ void __init tsc_init(void)
> if (!tsc_khz) {
> mark_tsc_unstable("could not calculate TSC khz");
>
Hi Heinrich,
Am Donnerstag, 14. Juni 2018, 14:55:27 CEST schrieb Heiko Stuebner:
> Am Montag, 4. Juni 2018, 19:15:23 CEST schrieb Heinrich Schuchardt:
> > Without this patch the Firefly-RK3399 board boot process hangs after these
> > lines:
> >
> >fan53555-regulator 0-0040: FAN53555
Hi Thomas,
On Tue, Jun 05, 2018 at 12:00:20PM +0200, Thomas Bogendoerfer wrote:
> Use fixed width integer types for ecoff structs to make elf2ecoff work
> on 64bit host machines
>
> Signed-off-by: Thomas Bogendoerfer
> Reviewed-by: Paul Burton
> ---
>
> v3: include stdint.h in ecoff.h
>
Hi Nicholas,
On Sat, Jun 16, 2018 at 09:26:32AM +0200, Nicholas Mc Guire wrote:
> Booleans should be assigned true/false not 1/0 as comparison is not needed
>
> Signed-off-by: Nicholas Mc Guire
> ---
>
> Problem located by scripts/coccinelle/misc/boolinit.cocci
>
On Tue, Jun 19, 2018 at 9:22 AM Johannes Weiner wrote:
>
> On Mon, Jun 18, 2018 at 10:13:25PM -0700, Shakeel Butt wrote:
> > @@ -248,6 +248,30 @@ static inline void memalloc_noreclaim_restore(unsigned
> > int flags)
> > current->flags = (current->flags & ~PF_MEMALLOC) | flags;
> > }
> >
>
On 19 June 2018 at 17:20, Will Deacon wrote:
> Hi Ard,
>
> Sorry, I forgot to reply to this.
>
> On Wed, May 30, 2018 at 11:53:20AM +0200, Ard Biesheuvel wrote:
>> On 30 May 2018 at 11:14, Will Deacon wrote:
>> > On Wed, May 30, 2018 at 12:48:06PM +0800, YaoJun wrote:
>> >> To protect against
Michal Hocko writes:
> On Tue 19-06-18 15:54:26, Punit Agrawal wrote:
> [...]
>> In terms of $SUBJECT, I wonder if it's worth taking the original patch
>> as a temporary fix (it'll also be easier to backport) while we work on
>> fixing these other issues and enabling memoryless nodes.
>
> Well,
On Tue, Jun 19, 2018 at 09:12:23AM -0400, Steven Rostedt wrote:
> On Tue, 19 Jun 2018 00:31:15 -0700
> Joel Fernandes wrote:
>
> > Hi Paul,
> > Think some more about this counter, I think you mean 'successes' as in
> > 'successful attempts' than 'successful test' ? If so, then perhaps you can
>
On 19 June 2018 at 17:37, Will Deacon wrote:
> On Tue, Jun 19, 2018 at 05:29:03PM +0200, Ard Biesheuvel wrote:
>> On 19 June 2018 at 17:28, Will Deacon wrote:
>> > On Tue, Jun 19, 2018 at 05:23:41PM +0200, Ard Biesheuvel wrote:
>> >> On 19 June 2018 at 17:20, Will Deacon wrote:
>> >> > Hi Ard,
On 2018-06-19 07:08, Jarkko Sakkinen wrote:
On Fri, Jun 08, 2018 at 11:21:48AM -0700, Jethro Beekman wrote:
On 2018-06-08 10:09, Jarkko Sakkinen wrote:
+/*
+ * Writing the LE hash MSRs is extraordinarily expensive, e.g.
+ * 3-4x slower than normal MSRs, so we use a per-cpu cache to
+ * track
The audio divider is one based. This offset was mistakenly dropped from
recalc_rate() when migrating to clk_regmap.
Fixes: 88a4e1283681 ("clk: meson: migrate the audio divider clock to
clk_regmap")
Signed-off-by: Jerome Brunet
---
drivers/clk/meson/clk-audio-divider.c | 2 +-
1 file changed, 1
Hi,
On Mon, Jun 18, 2018 at 1:52 PM, Stephen Boyd wrote:
> When requesting a gpio as an interrupt, we should make sure to mux the
> pin as the GPIO function and configure it to be an input so that various
> functions or output signals don't affect the interrupt state of the pin.
> So far, we've
machine_real_restart() is annotated as '__noreturn", so add it to the
objtool noreturn list. This fixes the following warning with clang and
CONFIG_CC_OPTIMIZE_FOR_SIZE=y:
arch/x86/kernel/reboot.o: warning: objtool:
native_machine_emergency_restart() falls through to next function
Remove arch dependent setjump/longjump functions
and unused fields in kprobe_ctlblk for jprobes
from arch/arm64.
Signed-off-by: Masami Hiramatsu
Acked-by: Will Deacon
Cc: Catalin Marinas
Cc: linux-arm-ker...@lists.infradead.org
---
arch/arm64/include/asm/kprobes.h |1 -
Remove arch dependent setjump/longjump functions
and unused fields in kprobe_ctlblk for jprobes
from arch/arm.
Signed-off-by: Masami Hiramatsu
Cc: Russell King
Cc: linux-arm-ker...@lists.infradead.org
---
arch/arm/include/asm/kprobes.h |2 -
arch/arm/include/asm/probes.h |1
Don't call the ->break_handler() from the arm64 kprobes code,
because it was only used by jprobes which got removed.
Signed-off-by: Masami Hiramatsu
Acked-by: Will Deacon
Cc: Catalin Marinas
Cc: linux-arm-ker...@lists.infradead.org
---
arch/arm64/kernel/probes/kprobes.c |8
1
This patchset adds support to basic version of Qualcomm NGD SLIMBus
controller driver found SoCs from B family.
This controller is light-weight SLIMBus controller driver responsible for
communicating with slave HW directly over the bus using messaging
interface, and communicating with master
Rearrange struct slim_eaddr so that the structure is packed correctly
to be able to send in SLIMBus messages.
Signed-off-by: Srinivas Kandagatla
---
include/linux/slimbus.h | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/include/linux/slimbus.h
1 - 100 of 1770 matches
Mail list logo
