This patch moves AER error defines to drivers/pci/pci.h.
So that it unifies the error repoting codes at single place along with dpc
Signed-off-by: Oza Pawandeep
diff --git a/drivers/acpi/apei/ghes.c b/drivers/acpi/apei/ghes.c
index 1efefe9..7ae9bb3 100644
--- a/drivers/acpi/apei/ghes.c
+++ b/dri
Clients such as pciehp, dpc are using pcie_wait_link_active, which waits
till the link becomes active or inactive.
Made generic function and moved it to drivers/pci/pci.c
Signed-off-by: Oza Pawandeep
diff --git a/drivers/pci/hotplug/pciehp_hpc.c b/drivers/pci/hotplug/pciehp_hpc.c
index 18a42f8.
Implement error_resume callback in DPC so, after DPC trigger event
enumerates the devices beneath.
Signed-off-by: Oza Pawandeep
diff --git a/drivers/pci/pcie/pcie-dpc.c b/drivers/pci/pcie/pcie-dpc.c
index 0524bd3..382d5c5 100644
--- a/drivers/pci/pcie/pcie-dpc.c
+++ b/drivers/pci/pcie/pcie-dpc.c
This patch renames error recovery to generic name with pci prefix
Signed-off-by: Oza Pawandeep
diff --git a/drivers/pci/pcie/aer/aerdrv_core.c
b/drivers/pci/pcie/aer/aerdrv_core.c
index a4bfea5..306bf2f 100644
--- a/drivers/pci/pcie/aer/aerdrv_core.c
+++ b/drivers/pci/pcie/aer/aerdrv_core.c
@@
This patch factors out error reporting callbacks, which are currently
tightly coupled with AER.
DPC should be able to register callbacks and attmept recovery when DPC
trigger event occurs.
Signed-off-by: Oza Pawandeep
diff --git a/drivers/pci/pci.h b/drivers/pci/pci.h
index fcd8191..a5a79f0 1006
On 22/02/2018 at 07:48:03 -0800, Christoph Hellwig wrote:
> On Wed, Feb 21, 2018 at 09:54:55PM +0100, Alexandre Belloni wrote:
> > Hello,
> >
> > This series:
> > - removes useless calls to rtc_valid_tm in .read_time, .set_time and
> >.set_alarm
> > - removes code setting default values for
On 02/22/2018 06:44 PM, Michal Hocko wrote:
> On Thu 22-02-18 18:38:11, Andrey Ryabinin wrote:
with the patch:
best: 1.04 secs, 9.7G reclaimed
worst: 2.2 secs, 16G reclaimed.
without:
best: 5.4 sec, 35G reclaimed
worst: 22.2 sec, 136G reclaimed
>>>
>>> Co
On 02/22/2018 10:21 AM, mario.limoncie...@dell.com wrote:> I guess that
means we got this wrong and the patch should be reverted
> until we figure this out.
>
> Jeremy,
>
> Can you please confirm what BIOS version you are on?
> Also Is this a 9360 with 7th or 8th gen Intel CPU?
Hi Mario,
I've g
Access to the socket API and the root network namespace is only available
when networking is enabled:
ERROR: "kernel_sendmsg" [drivers/soc/qcom/qmi_helpers.ko] undefined!
ERROR: "sock_release" [drivers/soc/qcom/qmi_helpers.ko] undefined!
ERROR: "sock_create_kern" [drivers/soc/qcom/qmi_helpers.ko]
On 22.02.2018 01:28, Kees Cook wrote:
> The header files for some structures could get included in such a way
> that struct attributes (specifically __randomize_layout from path.h) would
> be parsed as variable names instead of attributes. This could lead to
> some instances of a structure being un
On 02/21/2018 02:18 PM, Al Viro wrote:
On Wed, Feb 21, 2018 at 01:59:55PM -0600, Brijesh Singh wrote:
Sure, checking access_ok() does not guarantee that later
copy_from_user() will not fail. But it does eliminate one possible
reason for the failure. We are trying to validate most of the user
gcc-6.3 and earlier show a new warning after a seemingly unrelated change
to the arm64 PAGE_KERNEL definition:
In file included from drivers/md/dm-bufio.c:14:0:
drivers/md/dm-bufio.c: In function 'alloc_buffer':
include/linux/sched/mm.h:182:56: warning: 'noio_flag' may be used uninitialized
in th
gcc-8 has a new warning that detects overlapping input and output arguments
in memcpy(). It triggers for sit_init_net() calling ipip6_tunnel_clone_6rd(),
which is actually correct:
net/ipv6/sit.c: In function 'sit_init_net':
net/ipv6/sit.c:192:3: error: 'memcpy' source argument is the same as
des
On Wed, Feb 21, 2018 at 09:53:58PM +0300, Sergei Shtylyov wrote:
> On 02/21/2018 09:23 PM, Simon Horman wrote:
>
> > ...
> >
> +clocks = <&cpg CPG_MOD 812>;
> +power-domains = <&sysc 32>;
> +resets = <&cpg 812>
The removal of the batched object freeing has caused the debug_objects_freed
to become read-only, and the reading is inside an ifdef, so gcc warns that it
is completely unused without CONFIG_DEBUG_FS:
lib/debugobjects.c:71:14: error: 'debug_objects_freed' defined but not used
[-Werror=unused-vari
On Thu, Feb 22, 2018 at 04:30:34PM +0100, Peter Zijlstra wrote:
> On Thu, Feb 22, 2018 at 11:12:10PM +0800, Boqun Feng wrote:
> > On Thu, Feb 22, 2018 at 03:26:14PM +0100, Peter Zijlstra wrote:
>
> > > However, I would suggest:
> > >
> > > static inline bool is_xr(u16 dep)
> > > {
> > > return
On Thu, Feb 22, 2018 at 2:58 PM, Waiman Long wrote:
> On 02/22/2018 06:45 AM, Arnd Bergmann wrote:
>> The removal of the batched object freeing has caused the debug_objects_freed
>> to become read-only, and the reading is inside an ifdef, so gcc warns that it
>> is completely unused without CONFIG
> > In the past the only guidance was to not load microcode at the same time to
> the
> > thread siblings of a core. We now have new guidance that the sibling must be
> > spinning and not doing other things that can introduce instability around
> loading
> > microcode.
>
> Document that properly
On Wed, Feb 21, 2018 at 09:54:55PM +0100, Alexandre Belloni wrote:
> Hello,
>
> This series:
> - removes useless calls to rtc_valid_tm in .read_time, .set_time and
>.set_alarm
> - removes code setting default values for RTCs (and lets the core
>handle it)
> - removes useless "time is in
On Thu, Feb 22, 2018 at 4:38 PM, Simon Horman wrote:
> On Thu, Feb 22, 2018 at 02:28:46PM +0100, Geert Uytterhoeven wrote:
>> Removing the .dts file removes the ability to boot the newly added board...
>>
>> The issue here is that we are sharing board .dtsi for boards that can be
>> equipped with
On Thu, 22 Feb 2018, Raj, Ashok wrote:
> On Thu, Feb 22, 2018 at 01:15:06PM +0100, Borislav Petkov wrote:
> > On Thu, Feb 22, 2018 at 03:55:54AM -0800, Raj, Ashok wrote:
> > > The current code wasn't trying to enforce checking the loaded microcode
> > > revision on a thread
> > > before attempting
While building the cross-toolchains, I noticed that overall, we can build almost
all linux target architectures with upstream binutils and gcc these days,
however there are still some exceptions, and I'd like to find out if anyone
has objections to removing the ones that do not have upstream suppor
On Thu, 22 Feb 2018 20:59:27 +0530
Shreeya Patel wrote:
> The log levels embedded with the name are more concise than
> printk.
If you don't mind, I'll replace the above sentence by:
"
Using pr_() is more concise than printk(KERN_).
"
The patch looks good otherwise, so I should apply it soon.
On Thu 22-02-18 18:38:11, Andrey Ryabinin wrote:
>
>
> On 02/22/2018 06:33 PM, Michal Hocko wrote:
> > On Thu 22-02-18 18:13:11, Andrey Ryabinin wrote:
> >>
> >>
> >> On 02/22/2018 05:09 PM, Michal Hocko wrote:
> >>> On Thu 22-02-18 16:50:33, Andrey Ryabinin wrote:
> On 02/21/2018 11:17 PM,
vmx_vcpu_run and svm_vcpu_run are large functions, and this can actually
make a substantial cycle difference by keeping the fast path contiguous
in memory. Without it, the retpoline guest/retpoline host case is about
50 cycles slower.
Cc: x...@kernel.org
Cc: Radim Krčmář
Cc: KarimAllah Ahmed
Cc
Two tiny patches for the IBRS code. They should go in
through the x86/pti tree and should apply to both 4.9 and 4.14 trees.
Thanks,
Paolo
v1->v2: remove patch 2, the same bug has already been fixed
Paolo Bonzini (3):
KVM: x86: use native MSR ops for SPEC_CTRL
KVM: VMX: mark RDMSR path as u
Having a paravirt indirect call in the IBRS restore path is not a
good idea, since we are trying to protect from speculative execution
of bogus indirect branch targets. It is also slower, so use
native_wrmsrl on the vmentry path too.
Fixes: d28b387fb74da95d69d2615732f50cceb38e9a4d
Cc: x...@kernel
On Thu, Feb 22, 2018 at 04:16:26PM +0100, Peter Zijlstra wrote:
> On Thu, Feb 22, 2018 at 03:54:34PM +0100, Peter Zijlstra wrote:
> > On Thu, Feb 22, 2018 at 03:08:53PM +0800, Boqun Feng wrote:
> >
> > > +static inline int hlock_conflict(struct lock_list *entry, void *data)
> > > +{
> > > + struct
I'm currently prototyping hsch()/csch() support for vfio-ccw, and
stumbled over this: We currently expect any I/O to be in command-mode,
but don't take care to actively reject transport-mode. This is not an
issue with QEMU (which rejects transport-mode ORBs before even the css
backend gets to it),
vfio-ccw only supports command mode for channel programs, not transport
mode. User space is supposed to already take care of that and pass us
command-mode ORBs only, but better make sure and return an error to
the caller instead of trying to process tcws as ccws.
Signed-off-by: Cornelia Huck
---
The only reason why I added this array on-stack was to allow consumers
that did not use ib_alloc_cq api to call it, but that seems like a
wrong decision when thinking it over again (as probably these users
did not set the wr_cqe correctly).
How about we make ib_process_cq_direct use the cq wc a
On Thu, Feb 22, 2018 at 02:28:46PM +0100, Geert Uytterhoeven wrote:
> Hi Arnd,
>
> On Thu, Feb 22, 2018 at 12:39 PM, Arnd Bergmann wrote:
> > On Wed, Feb 21, 2018 at 6:15 PM, Simon Horman wrote:
> >> On Tue, Feb 20, 2018 at 04:46:23PM +0100, Geert Uytterhoeven wrote:
> >>> On Tue, Feb 20, 2018 a
On 02/22/2018 02:52 PM, Linus Walleij wrote:
> Hi Amelie,
>
> thanks for your patch.
>
> On Thu, Feb 8, 2018 at 3:27 PM, Amelie Delaunay
> wrote:
>
>> The joystick on stm32746g-eval uses gpios on MFX gpio expander.
>>
>> Signed-off-by: Amelie Delaunay
> (...)
>> + joystick {
>> +
On 02/22/2018 06:33 PM, Michal Hocko wrote:
> On Thu 22-02-18 18:13:11, Andrey Ryabinin wrote:
>>
>>
>> On 02/22/2018 05:09 PM, Michal Hocko wrote:
>>> On Thu 22-02-18 16:50:33, Andrey Ryabinin wrote:
On 02/21/2018 11:17 PM, Andrew Morton wrote:
> On Fri, 19 Jan 2018 16:11:18 +0100 Micha
On 2/21/2018 2:13 PM, Raj, Ashok wrote:
> On Wed, Feb 21, 2018 at 08:06:11PM +0100, Borislav Petkov wrote:
>>> arch/x86/kernel/cpu/microcode/core.c | 113
>>> +-
>>
>> This is generic so Tom needs to ack whatever we end up doing for the AMD
>> side.
>
> Yes, i did
On 02/22/2018 02:54 PM, Linus Walleij wrote:
> On Thu, Feb 8, 2018 at 3:27 PM, Amelie Delaunay
> wrote:
>
>> MFX is used as gpio expander on stm32746g-eval.
>>
>> Signed-off-by: Amelie Delaunay
>
> (...)
>> + mfx: mfx@42 {
>> + compatible = "st,mfx";
>> + re
On Mon, Feb 19, 2018 at 11:29 PM, David Lechner wrote:
> This makes use of the gpio-ranges feature that connects GPIO
> controllers and PINMUX controllers.
>
> In da850.dtsi, pinctrl-single,gpio-range is added to the pinmux node
> and gpio-ranges is added to the GPIO node. Unfortunately, the way
On 02/22/2018 02:47 PM, Linus Walleij wrote:
> On Thu, Feb 8, 2018 at 3:27 PM, Amelie Delaunay
> wrote:
>
>> ST Multi-Function eXpander (MFX) can be used as GPIO expander.
>> It has 16 fast GPIOs and can have 8 extra alternate GPIOs
>> when other MFX features are not enabled.
>>
>> Signed-off-
On Thu 22-02-18 18:13:11, Andrey Ryabinin wrote:
>
>
> On 02/22/2018 05:09 PM, Michal Hocko wrote:
> > On Thu 22-02-18 16:50:33, Andrey Ryabinin wrote:
> >> On 02/21/2018 11:17 PM, Andrew Morton wrote:
> >>> On Fri, 19 Jan 2018 16:11:18 +0100 Michal Hocko wrote:
> >>>
> And to be honest, I
On 02/22/2018 02:44 PM, Linus Walleij wrote:
> On Thu, Feb 8, 2018 at 3:27 PM, Amelie Delaunay
> wrote:
>
> Thanks for working on this complex expander driver.
> It is a bit daunting. Sorry if there are lots of comments and
> considerations, but it reflects the complexity of the hardware.
>
>
On Thu, Feb 22, 2018 at 11:12:10PM +0800, Boqun Feng wrote:
> On Thu, Feb 22, 2018 at 03:26:14PM +0100, Peter Zijlstra wrote:
> > However, I would suggest:
> >
> > static inline bool is_xr(u16 dep)
> > {
> > return !!(dep & (DEP_NR_MASK | DEP_RR_MASK));
> > }
> >
> > static inline bool is_rx
On Mon, Feb 19, 2018 at 8:23 PM, Marc Zyngier wrote:
>> Am Montag, 19. Februar 2018, 19:03:27 CET schrieb Florian Fainelli:
>> > Can you indicate which DTS file is used for your Chromebook model? Sorry
>> > about the breakage.
>>
>> that should be
>> https://git.kernel.org/pub/scm/linux/kernel/g
The log levels embedded with the name are more concise than
printk.
Replace printks having a log level with the appropriate
pr_*() macros.
Define pr_fmt() and remove other additional macros from
the replaced printks.
Signed-off-by: Shreeya Patel
---
Changes in v2
-Merge previous patches of the
Hi
On 02/22/2018 03:03 PM, Herbert Xu wrote:
On Thu, Feb 15, 2018 at 02:03:07PM +0100, Lionel Debieve wrote:
This set of patches add extended functionalities for stm32 rng
driver.
Patch #1 includes a reset during probe to avoid any error status
which can occur during bootup process and keep saf
On Thu, 22 Feb 2018 20:15:58 +0530
Shreeya Patel wrote:
> On Thu, 2018-02-22 at 15:30 +0100, Richard Weinberger wrote:
> > Am Donnerstag, 22. Februar 2018, 14:10:14 CET schrieb Shreeya Patel:
> > >
> > > @@ -438,7 +438,7 @@ static void __init doc2000_count_chips(struct
> > > mtd_info
> > > *mt
On Thu, 22 Feb 2018, Daniel Schultz wrote:
> The Rockchip PMIC driver can automatically detect connected component
> versions by reading the ID_MSB and ID_LSB registers. The probe function
> will always fail with RK818 PMICs because the ID_MSK is 0xFFF0 and the
> RK818 template ID is 0x8181.
>
>
On Wed, 21 Feb 2018, Petr Mladek wrote:
> From: Jason Baron
>
> We are going to add a feature called atomic replace. It will allow to
> create a patch that would replace all already registered patches.
> For this, we will need to dynamically create funcs and objects
> for functions that are no l
> I have found one bug in v7. We were not able to initialize NOP
> struct klp_func when the patches module is not loaded. It was
> because func->new_func was NULL. I have fixed it in separate patch
> for an easier review.
This is embarassing. I'd swear I tested this. At least it was a part of my
Add group configuration for uarts that are cut down
variants, the standard being full, i.e. all signals,
flow control, i.e. rx/tx and cts/rts, and rx/tx only.
This allows us to be more precise in which pins we're
actually using.
Unfortunately the existing naming scheme leaves things
to be desired
Add missing pin group uart5nocts (all pins except cts), which has been
supported by the artpec6 pinctrl driver since its initial submission.
Fixes: 00df0582eab1 ("pinctrl: Add pincontrol driver for ARTPEC-6 SoC")
Signed-off-by: Niklas Cassel
---
Documentation/devicetree/bindings/pinctrl/axis,art
On Thu, Feb 22, 2018 at 08:51:30AM -0600, Shanker Donthineni wrote:
> +#define CTR_B31_SHIFT31
Since this is just a RES1 bit, I think we don't need a mnemonic for it,
but I'll defer to Will and Catalin on that.
> ENTRY(invalidate_icache_range)
> +#ifdef CONFIG_ARM64_SKIP_CACHE_PO
> -Original Message-
> From: Marco Martin [mailto:notm...@gmail.com]
> Sent: Thursday, February 22, 2018 9:16 AM
> To: Jeremy Cline
> Cc: Limonciello, Mario ; Pali Rohár
> ; Andy Shevchenko ;
> Matthew Garrett ; Darren Hart ;
> Platform Driver ; Linux Kernel Mailing
> List
>
> Subject: R
On Fri, Dec 29, 2017 at 9:14 PM, William Breathitt Gray
wrote:
> PC/104 device driver Kconfig options previously had an implicit EXPERT
> dependency by way of an explicit ISA_BUS_API dependency. Now that these
> driver Kconfig options select ISA_BUS_API rather than depend on it, the
> PC104 Kconf
On 02/22/2018 02:11 PM, Linus Walleij wrote:
> On Thu, Feb 8, 2018 at 3:27 PM, Amelie Delaunay
> wrote:
>
>> +Required properties:
>> +- compatible: must be "st,mfx"
>
> I bet this should be more specific. Tomorrow there will be a new
> version of this expander and then we will wish that we u
From: akarbown
In one of the previous patches we decreased NUM_CHANNELS from 8 to 4, but
it is not enough for Knights Landing which supports up to 6 channels.
This caused unattended writes to pvt->mirror_mode and pvt->tolm variables
which don't pay critical role on KNL code path, so driver was s
2018-02-21 3:17 GMT+09:00 Krzysztof Kozlowski :
> Driver uses alias from Device Tree as an index of pin controller data
> array. In case of a wrong DTB or an out-of-tree DTB, the alias could be
> outside of this data array leading to out-of-bounds access.
>
> Depending on binary and memory layout,
On Fri, Dec 29, 2017 at 9:14 PM, William Breathitt Gray
wrote:
> ISA_BUS_API is selected by drivers themselves when necessary. The
> ISA_BUS Kconfig option is now simply a mask for true ISA device drivers
> and relevant configuration. For now, the ISA_BUS Kconfig option is only
> available for X8
On Thu, Feb 22, 2018 at 03:54:34PM +0100, Peter Zijlstra wrote:
> On Thu, Feb 22, 2018 at 03:08:53PM +0800, Boqun Feng wrote:
>
> > +static inline int hlock_conflict(struct lock_list *entry, void *data)
> > +{
> > + struct held_lock *hlock = (struct held_lock *)data;
> > +
> > + return hlock_c
On Fri, Dec 29, 2017 at 9:13 PM, William Breathitt Gray
wrote:
> The ISA_BUS_API Kconfig option enables the compilation of the ISA bus
> driver. The ISA bus driver does not perform any hardware interaction,
> and is instead just a thin layer of software abstraction to eliminate
> boilerplate code
On 02/22/2018 02:22 PM, Linus Walleij wrote:
> On Mon, Feb 19, 2018 at 4:59 PM, Amelie DELAUNAY
> wrote:
>> On 02/19/2018 12:19 AM, Rob Herring wrote:
>>> On Thu, Feb 08, 2018 at 03:27:32PM +0100, Amelie Delaunay wrote:
>
+- interrupts = must be <0>
+- gpio-controller: marks the devi
On Thu, Feb 22, 2018 at 3:08 PM, Jeremy Cline wrote:
> Input driver version is 1.0.1
> Input device ID: bus 0x19 vendor 0x0 product 0x0 version 0x0
> Input device name: "Intel Virtual Button driver"
> Supported events:
> Event type 0 (EV_SYN)
> Event type 1 (EV_KEY)
> Event code 114 (KEY_V
On 02/22/2018 05:09 PM, Michal Hocko wrote:
> On Thu 22-02-18 16:50:33, Andrey Ryabinin wrote:
>> On 02/21/2018 11:17 PM, Andrew Morton wrote:
>>> On Fri, 19 Jan 2018 16:11:18 +0100 Michal Hocko wrote:
>>>
And to be honest, I do not really see why keeping retrying from
mem_cgroup_resiz
On Fri, Dec 29, 2017 at 9:13 PM, William Breathitt Gray
wrote:
> The ISA_BUS_API Kconfig option enables the compilation of the ISA bus
> driver. The ISA bus driver does not perform any hardware interaction,
> and is instead just a thin layer of software abstraction to eliminate
> boilerplate code
On Thu, Feb 15, 2018 at 01:24:18PM +0100, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Thu, 15 Feb 2018 11:38:30 +0100
>
> Omit extra messages for a memory allocation failure in these functions.
>
> This issue was detected by using the Coccinelle software.
>
> Signed-off-by: Markus E
On Fri, Dec 29, 2017 at 9:13 PM, William Breathitt Gray
wrote:
> The ISA_BUS_API Kconfig option enables the compilation of the ISA bus
> driver. The ISA bus driver does not perform any hardware interaction,
> and is instead just a thin layer of software abstraction to eliminate
> boilerplate code
Hi Linus,
Thanks for your review on the whole series.
On 02/22/2018 02:06 PM, Linus Walleij wrote:
> Hi Amelie,
>
> thanks a lot for your patches!
>
> On Thu, Feb 8, 2018 at 3:27 PM, Amelie Delaunay
> wrote:
>
>> This series adds support for STMicroelectronics MultiFunction eXpander
>> (ST M
On Wed, Feb 14, 2018 at 10:39:25PM +0100, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Wed, 14 Feb 2018 22:05:11 +0100
>
> Omit an extra message for a memory allocation failure in this function.
>
> This issue was detected by using the Coccinelle software.
>
> Signed-off-by: Markus E
On Wed, Feb 14, 2018 at 09:42:26PM +0100, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Wed, 14 Feb 2018 21:34:54 +0100
>
> Omit an extra message for a memory allocation failure in this function.
>
> This issue was detected by using the Coccinelle software.
>
> Signed-off-by: Markus E
On Wed, Feb 14, 2018 at 09:37:51AM -0800, Dave Watson wrote:
> This patch set refactors the x86 aes/gcm SSE crypto routines to
> support true scatter/gather by adding gcm_enc/dec_update methods.
>
> The layout is:
>
> * First 5 patches refactor the code to use macros, so changes only
> need to
On Wed, Feb 14, 2018 at 02:32:28PM +0100, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Wed, 14 Feb 2018 14:30:28 +0100
>
> Two update suggestions were taken into account
> from static source code analysis.
>
> Markus Elfring (2):
> Delete an error message for a failed memory allocat
On Wed, Jan 31, 2018 at 3:22 AM, William Breathitt Gray
wrote:
> On Tue, Jan 02, 2018 at 10:29:30AM +0100, Linus Walleij wrote:
>>On Fri, Dec 29, 2017 at 9:13 PM, William Breathitt Gray
>> wrote:
>>
>>> Linus, please pickup this entire patchset through your GPIO subsystem
>>> tree; a recursive dep
On Wed, Feb 14, 2018 at 05:17:08PM +0100, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Wed, 14 Feb 2018 17:05:13 +0100
>
> Omit an extra message for a memory allocation failure in this function.
>
> This issue was detected by using the Coccinelle software.
>
> Signed-off-by: Markus E
On Wed, Feb 14, 2018 at 11:16:39AM +0100, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Wed, 14 Feb 2018 11:12:34 +0100
>
> A few update suggestions were taken into account
> from static source code analysis.
>
> Markus Elfring (4):
> Delete an error message for a failed memory alloc
On Mon, Feb 12, 2018 at 10:52:37PM +0900, Jinbum Park wrote:
> Move the AES inverse S-box to the .rodata section
> where it is safe from abuse by speculation.
>
> Signed-off-by: Jinbum Park
Patch applied. Thanks.
--
Email: Herbert Xu
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: ht
On Thu, Feb 22, 2018 at 06:43:34PM +0530, George Cherian wrote:
> On 02/22/2018 04:50 AM, Bjorn Helgaas wrote:
> > On Wed, Feb 21, 2018 at 04:25:08PM +0530, George Cherian wrote:
> > > On 02/21/2018 03:24 PM, Lukas Wunner wrote:
> > > > On Wed, Feb 21, 2018 at 02:58:13PM +0530, George Cherian wrote
On Thu, Feb 22, 2018 at 03:26:14PM +0100, Peter Zijlstra wrote:
> On Thu, Feb 22, 2018 at 03:08:52PM +0800, Boqun Feng wrote:
> > Now we have four kinds of dependencies in the dependency graph, and not
> > all the pathes carry strong dependencies, for example:
> >
> > Given lock A, B, C, if we
Hi Boris,
We are very interested in your I3C subsystem proposal and we would like
to colaborate with you in order to add support for the Synopsys Host
Controller.
We are doing the review for this patch-set and will send our conclusions
as soon as possible.
Best regards,
Vitor Soares
Às
On Sun, Feb 18, 2018 at 4:47 AM, David Lechner wrote:
> On 02/07/2018 06:57 AM, Linus Walleij wrote:
>>
>> On Sun, Jan 21, 2018 at 9:32 PM, David Lechner
>> wrote:
>>
>>> This suppresses printing an error message during probe of gpio drivers
>>> when the error is EPROBE_DEFER.
>>>
>>> Cc: Linus W
On 02/22/2018 11:54 AM, Viresh Kumar wrote:
There are two clusters (2 + 4 CPUs) on this platform and a separate
cpufreq policy is available for each of the CPUs. The loop in
tegra186_cpufreq_init() tries to find the structure for the right CPU
and finish initialization. But it is missing a `break
Hi Andy,
Thanks for the review! Answers inline. I'll send a v3 when the two
open questions are resolved.
On Wed, Feb 21, 2018 at 10:57 PM, Andy Shevchenko
wrote:
> On Wed, Feb 21, 2018 at 9:45 PM, Pierre Bourdon wrote:
>> Ambient light sensor that supports visible light and IR measurements and
On Thu, 22 Feb 2018 18:40:14 +0530
Shreeya Patel wrote:
> The log levels embedded with the name are more concise than
> printk.
> Replace printks having a log level with the appropriate
> pr_*macro.
pr_*() macros.
> Define pr_fmt() and remove other additional macros from
> some of the replace
On Thu, 2018-02-22 at 16:54 +0200, Artem Bityutskiy wrote:
> Hi Christoph,
>
> one of our test box Skylake servers does not boot with v4.16-rcX.
> Bisection lead us to this commit:
>
> 84676c1f21e8 genirq/affinity: assign vectors to all possible CPUs
>
> Reverting this single commit fixes the pr
On Thu, Feb 22, 2018 at 03:08:53PM +0800, Boqun Feng wrote:
> +static inline int hlock_conflict(struct lock_list *entry, void *data)
> +{
> + struct held_lock *hlock = (struct held_lock *)data;
> +
> + return hlock_class(hlock) == entry->class &&
> +(hlock->read != 2 || !entry-
Hi Christoph,
one of our test box Skylake servers does not boot with v4.16-rcX.
Bisection lead us to this commit:
84676c1f21e8 genirq/affinity: assign vectors to all possible CPUs
Reverting this single commit fixes the problem.
The server is a Dell R640 machine with the latest Dell BIOS. It has
On Fri, Feb 16, 2018 at 8:12 PM, Daniel Kurtz wrote:
> On boot, gpiochip_add_data() initializes the FLAG_IS_OUT bit in
> desc->flags iff its gpio_chip does not have ->direction_input() handler,
> else it is initialized to 0, which implies the GPIO is an "input".
>
> Later, the sysfs "direction" h
On Thu, Feb 22, 2018 at 12:44:40PM +0100, Arnd Bergmann wrote:
> Declaring a static function in a header leads to a warning every
> time that header gets included without the function being used:
Acked-by: Richard Cochran
The DCache clean & ICache invalidation requirements for instructions
to be data coherence are discoverable through new fields in CTR_EL0.
The following two control bits DIC and IDC were defined for this
purpose. No need to perform point of unification cache maintenance
operations from software on s
On Thu, 22 Feb 2018 20:15:58 +0530
Shreeya Patel wrote:
> On Thu, 2018-02-22 at 15:30 +0100, Richard Weinberger wrote:
> > Am Donnerstag, 22. Februar 2018, 14:10:14 CET schrieb Shreeya Patel:
> > >
> > > @@ -438,7 +438,7 @@ static void __init doc2000_count_chips(struct
> > > mtd_info
> > > *mt
Hi Oza,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on pci/next]
[also build test WARNING on v4.16-rc2 next-20180222]
[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 Thu 22-02-18 14:49:44, Michal Hocko wrote:
> On Tue 20-02-18 19:01:01, Shakeel Butt wrote:
> > A lot of memory can be consumed by the events generated for the huge or
> > unlimited queues if there is either no or slow listener. This can cause
> > system level memory pressure or OOMs. So, it's be
On Wed, Feb 14, 2018 at 4:55 PM, Charles Keepax
wrote:
> Now GPIOD has support for both pdata systems and for non-standard DT
> bindings the Arizona reset GPIO can be converted to use it.
>
> Signed-off-by: Charles Keepax
(...)
> + pdata->reset = devm_gpiod_get_from_of_node(arizona->dev,
>
On Thu, 2018-02-22 at 15:30 +0100, Richard Weinberger wrote:
> Am Donnerstag, 22. Februar 2018, 14:10:14 CET schrieb Shreeya Patel:
> >
> > @@ -438,7 +438,7 @@ static void __init doc2000_count_chips(struct
> > mtd_info
> > *mtd) break;
> > }
> > doc->chips_per_floor = i;
> > - printk(KER
Hi Shreeya,
On Thu, 22 Feb 2018 18:40:14 +0530
Shreeya Patel wrote:
> diff --git a/drivers/mtd/nand/diskonchip.c b/drivers/mtd/nand/diskonchip.c
> index c3aa53c..8643512 100644
> --- a/drivers/mtd/nand/diskonchip.c
> +++ b/drivers/mtd/nand/diskonchip.c
[...]
> @@ -438,7 +438,7 @@ static void
Hi Linus,
On Thu, Feb 22, 2018 at 3:23 PM, Linus Walleij wrote:
> On Mon, Feb 12, 2018 at 2:55 PM, Geert Uytterhoeven
> wrote:
>
>> Since commit ab82fa7da4dce5c7 ("gpio: rcar: Prevent module clock disable
>> when wake-up is enabled"), when a GPIO is used for wakeup, the GPIO
>> block's module cl
On 2018-02-20 22:01, York Sun wrote:
> Sorry for top posting. I am on vacation and replying from my phone.
>
> The controller is compatible and the driver should work. Please double check
> to make sure you can inject errors and receive interrupt. After that you are
> good to go.
I can indeed i
From: Marcel Ziswiler
Since commit f8f8f1d04494 ("clk: Don't touch hardware when reparenting
during registration") ULPI has been broken on Tegra20 leading to the
following error message during boot:
[1.974698] ulpi_phy_power_on: ulpi write failed
[1.979384] tegra-ehci c5004000.usb: Faile
All the kernel_sendmsg() calls in rxrpc_send_data_packet() need to send
both parts of the iov[] buffer, but one of them does not. Fix it so that
it does.
Without this, short IPv6 rxrpc DATA packets may be seen that have the rxrpc
header included, but no payload.
Fixes: 5a924b8951f8 ("rxrpc: Don'
On Wed, Feb 14, 2018 at 3:51 AM, Baolin Wang wrote:
> On 13 February 2018 at 17:20, Linus Walleij wrote:
>> On Mon, Feb 5, 2018 at 2:55 AM, Baolin Wang wrote:
>>
>>> This patch adds the device tree bindings for the Spreadtrum
>>> GPIO controller. The gpios will be supported by the GPIO
>>> gener
On Sun, 2018-02-18 at 08:47 -0800, Randy Dunlap wrote:
> You could try (re)building with V=1 on the "make" command line and
> capture
> the output to see where the "pedantic" is coming from.
This is a late reply.
I did what you told me and the build failed at following point:
/bin/sh: /ho
On Thu 22-02-18 15:14:54, Kunal Shubham wrote:
> >> On Fri 16-02-18 15:14:40, t.vi...@samsung.com wrote:
> >> From: Vivek Trivedi
> >>
> >> If fanotify userspace response server thread is frozen first,
> >> it may fail to send response from userspace to kernel space listener.
> >> In this scenari
501 - 600 of 952 matches
Mail list logo
