Arnaldo,
On Mon, Feb 11, 2019 at 10:55 AM Arnaldo Carvalho de Melo
wrote:
>
> Em Mon, Feb 11, 2019 at 10:34:16AM -0800, Stephane Eranian escreveu:
> > Jiri,
> >
> > On Mon, Feb 11, 2019 at 2:20 AM Jiri Olsa wrote:
> > >
> > > On Tue, Feb 05, 2019 at 02:37:27PM +0100, Jiri Olsa wrote:
> > > > On
On Sun, Feb 10, 2019 at 3:39 PM Robert Eshleman wrote:
>
> This patch adds support for the ap3216c ambient light and proximity
> sensor.
PS
Why not use the chip in the mode where the interrupt is automatically cleared by
reading the data? This could work if you read the data in the
interrupt
On Thu, Feb 7, 2019 at 4:45 AM Denis Efremov wrote:
>
> Recent "New LSM Hooks" discussion has led me to the
> thought that it might be a good idea to slightly
> update the current documentation. The patchset adds
> nothing new to the documentation, only fixes the old
> description of hooks to
On Mon, Feb 11, 2019 at 7:33 AM Masahiro Yamada
wrote:
>
> On Sat, Feb 9, 2019 at 2:27 AM Nick Desaulniers
> wrote:
> >
> > On Thu, Feb 7, 2019 at 9:51 PM Nathan Chancellor
> > wrote:
> > >
> > > On Thu, Feb 07, 2019 at 02:01:51PM -0800, ndesaulni...@google.com wrote:
> > > > This is needed
On Mon, Feb 11, 2019 at 10:12:46AM -0800, Reinette Chatre wrote:
> Hi Greg,
>
> On 2/11/2019 6:15 AM, Greg Kroah-Hartman wrote:
> > 4.19-stable review patch. If anyone has any objections, please let me know.
> >
> > --
> >
> > [ Upstream commit
Background we are discussing __replace_page() in:
kernel/events/uprobes.c
and wether this can be call on page that can be written too through
its virtual address mapping.
On Fri, Feb 01, 2019 at 07:50:22PM -0500, Andrea Arcangeli wrote:
> On Thu, Jan 31, 2019 at 01:37:03PM -0500, Jerome
> On Feb 11, 2019, at 11:10 AM, Borislav Petkov wrote:
>
> On Mon, Feb 11, 2019 at 11:09:25AM -0800, Nadav Amit wrote:
>> It is just that I find the use of static_cpu_has()/boot_cpu_has() to be very
>> inconsistent. I doubt that show_cpuinfo_misc(), copy_fpstate_to_sigframe(),
>> or
On Mon, 2019-02-11 at 20:09 +0100, Borislav Petkov wrote:
> On Mon, Jan 28, 2019 at 04:34:15PM -0800, Rick Edgecombe wrote:
> > This adds two new functions set_alias_default_noflush and
>
> s/This adds/Add/
>
> > set_alias_nv_noflush for setting the alias mapping for the page to its
>
> Please
On Mon, Feb 11, 2019 at 11:01 AM wrote:
>
> From: Enrico Granata
>
> ACPI 5 added support for GpioInt resources as a way to provide
> information about interrupts mediated via a GPIO controller.
>
> Several device buses (e.g. SPI, I2C) have support for retrieving
> an IRQ specified via this type
On 2/11/19 11:15 AM, Raj, Ashok wrote:
On Fri, Feb 08, 2019 at 11:49:55PM -0500, Sinan Kaya wrote:
On 2/8/2019 8:02 PM, sathyanarayanan kuppuswamy wrote:
This means that you should probably have some kind of version check
here.
There is no version field in ATS v1.0 spec. Also, If I follow
On Mon, Feb 11, 2019 at 10:30:10AM -0800, Alexander Duyck wrote:
> On Mon, 2019-02-11 at 12:48 -0500, Michael S. Tsirkin wrote:
> > On Mon, Feb 11, 2019 at 09:41:19AM -0800, Dave Hansen wrote:
> > > On 2/9/19 4:44 PM, Michael S. Tsirkin wrote:
> > > > So the policy should not leak into host/guest
On Mon, Feb 11, 2019 at 10:11:53AM -0800, Andi Kleen wrote:
> On Mon, Feb 11, 2019 at 03:20:18PM +0100, Greg Kroah-Hartman wrote:
> > 4.9-stable review patch. If anyone has any objections, please let me know.
> >
> > --
> >
> > From: Andi Kleen
> >
> > commit
On Sun, Feb 10, 2019 at 08:20:20PM +0100, Thomas Gleixner wrote:
> On Tue, 5 Feb 2019, Peter Zijlstra wrote:
> > On Tue, Feb 05, 2019 at 07:19:16AM -0800, Dave Hansen wrote:
> > > On 2/5/19 12:48 AM, Peter Zijlstra wrote:
> > > This isn't something we want everybody and their grandma to turn on;
>
Hi Maxime,
I spotted few minor issues, but otherwise it looks very well.
I'll do detailed review at a later time.
Dne ponedeljek, 11. februar 2019 ob 15:39:03 CET je Maxime Ripard napisal(a):
> Introduce some basic H264 decoding support in cedrus. So far, only the
> baseline profile videos
On Mon, 11 Feb 2019 14:08:22 -0500 Johannes Weiner wrote:
> On Wed, Dec 19, 2018 at 09:37:48AM -0800, Roman Gushchin wrote:
> > The patchset contains few changes to the vmalloc code, which are
> > leading to some performance gains and code simplification.
> >
> > Also, it exports a number of
On Mon, Feb 11, 2019 at 7:57 PM Takashi Iwai wrote:
>
> On Mon, 11 Feb 2019 19:25:12 +0100,
> Sam Ravnborg wrote:
> >
> > Hi Daniel.
> >
> > On Mon, Feb 11, 2019 at 06:15:20PM +0100, Daniel Vetter wrote:
> > > Hi all,
> > >
> > > Here's the typed component topic branch.
> > >
> > > drm-intel
> On Feb 11, 2019, at 11:07 AM, Andy Lutomirski wrote:
>
> I'm certainly amenable to other solutions, but this one does seem the
> least messy. I looked at my old patch, and it doesn't do what you
> want. I'd suggest you just add a percpu variable like cpu_dr7 and rig
> up some accessors so
On Fri, Feb 08, 2019 at 11:49:55PM -0500, Sinan Kaya wrote:
> On 2/8/2019 8:02 PM, sathyanarayanan kuppuswamy wrote:
> >>This means that you should probably have some kind of version check
> >>here.
> >
> >There is no version field in ATS v1.0 spec. Also, If I follow the history
> >log in PCI
Hello Marcos,
On Sun, Feb 10, 2019 at 5:05 PM Marcos Paulo de Souza
wrote:
>
>
>
> On 2/10/19 9:45 PM, Andy Shevchenko wrote:
> > On Sun, Feb 10, 2019 at 9:24 PM Marcos Paulo de Souza
> > wrote:
> >>
> >> Hi,
> >>
> >> Since 5.0.0-rc4 I vefiried that my ASUS laptop
> >
> > Can you be more
On Mon, Feb 11, 2019 at 12:41:40PM -0600, Alan Tull wrote:
> On Fri, Nov 9, 2018 at 12:58 AM Frank Rowand wrote:
>
> What LTSI's are these patches likely to end up in? Just to be clear,
> I'm not pushing for any specific answer, I just want to know what to
> expect.
I have no idea what you are
> On Feb 11, 2019, at 10:45 AM, Dan Carpenter wrote:
>
> We added some locking to this function but forgot to drop the lock on
> these two error paths. This bug would lead to an immediate deadlock.
>
> Fixes: c7b3690fb152 ("vmw_balloon: stats rework")
> Signed-off-by: Dan Carpenter
Cc:
On Mon, Feb 11, 2019 at 9:59 AM Will Deacon wrote:
>
> Hi all,
>
> I attended an interesting talk at LCA last month that described some of the
> security features deployed in OpenBSD [1]. One hardening feature that piqued
> my interest was, on syscall entry and page faults from userspace,
Drop switchdev_ops.switchdev_port_attr_get and _set. Drop the uses of
this field from all clients, which were migrated to use switchdev
notification in the previous patches.
Add a new function switchdev_port_attr_notify() that sends the switchdev
notifications SWITCHDEV_PORT_ATTR_GET and _SET.
Following patches will change the way we communicate getting or setting
a port's attribute and use a blocking notifier to perform those tasks.
Prepare DSA to support receiving notifier events targeting
SWITCHDEV_PORT_ATTR_GET/SET and simply translate that into the existing
Now that we have converted all possible callers to using a switchdev
notifier for attributes we do not have a need for implementing
switchdev_ops anymore, and this can be removed from all drivers the
net_device structure.
Acked-by: Jiri Pirko
Signed-off-by: Florian Fainelli
---
On Mon, Feb 11, 2019 at 11:09:25AM -0800, Nadav Amit wrote:
> It is just that I find the use of static_cpu_has()/boot_cpu_has() to be very
> inconsistent. I doubt that show_cpuinfo_misc(), copy_fpstate_to_sigframe(),
> or i915_memcpy_init_early() that use static_cpu_has() are any hotter than
>
Following patches will change the way we communicate getting or setting
a port's attribute and use a blocking notifier to perform those tasks.
Prepare rocker to support receiving notifier events targeting
SWITCHDEV_PORT_ATTR_GET/SET and simply translate that into the existing
Following patches will change the way we communicate getting or setting
a port's attribute and use a blocking notifier to perform those tasks.
Prepare ocelot to support receiving notifier events targeting
SWITCHDEV_PORT_ATTR_GET/SET and simply translate that into the existing
Following patches will change the way we communicate getting or setting
a port's attribute and use a blocking notifier to perform those tasks.
Prepare ethsw to support receiving notifier events targeting
SWITCHDEV_PORT_ATTR_GET/SET and simply translate that into the existing
In preparation for allowing switchdev enabled drivers to veto specific
attribute settings from within the context of the caller, introduce a
new switchdev notifier type for port attributes.
Suggested-by: Ido Schimmel
Acked-by: Jiri Pirko
Signed-off-by: Florian Fainelli
---
Following patches will change the way we communicate getting or setting
a port's attribute and use a blocking notifier to perform those tasks.
Prepare mlxsw to support receiving notifier events targeting
SWITCHDEV_PORT_ATTR_GET/SET and simply translate that into the existing
Hi all,
This patch series finishes by the removal of switchdev_ops. To get there
we convert the existing switchdev_port_attr_{set,get} switchdev_ops to
use a blocking notifier, thus making it consistent with how the objects
are pushed to the switchdev enabled devices.
Please review and let me
Update the section about switchdev drivers having to implement a
switchdev_port_attr_get() function to return
SWITCHDEV_ATTR_ID_PORT_PARENT_ID since that is no longer valid after
commit bccb30254a4a ("net: Get rid of
SWITCHDEV_ATTR_ID_PORT_PARENT_ID").
Fixes: bccb30254a4a ("net: Get rid of
On Mon, Jan 28, 2019 at 04:34:15PM -0800, Rick Edgecombe wrote:
> This adds two new functions set_alias_default_noflush and
s/This adds/Add/
> set_alias_nv_noflush for setting the alias mapping for the page to its
Please end function names with parentheses, below too.
> default valid
> On Feb 11, 2019, at 11:01 AM, Borislav Petkov wrote:
>
> On Mon, Feb 11, 2019 at 10:45:26AM -0800, Nadav Amit wrote:
>> Are you sure about that? This path is still used when modules are loaded.
>
> Yes, I'm sure. Loading a module does a gazillion things so saving a
> couple of insns - yes,
On Fri, Feb 01, 2019 at 06:57:38PM -0500, Andrea Arcangeli wrote:
> Hello everyone,
>
> On Thu, Jan 31, 2019 at 01:37:02PM -0500, Jerome Glisse wrote:
> > From: Jérôme Glisse
> >
> > This patchset is on top of my patchset to add context information to
> > mmu notifier [1] you can find a branch
Hi Robert,
On Sun, Feb 10, 2019 at 3:39 PM Robert Eshleman wrote:
>
> This patch adds support for the ap3216c ambient light and proximity
> sensor.
Comments below.
>
> Supported features include:
>
> * Illuminance (lux)
> * Proximity (raw)
> * IR (raw)
> * Rising/falling threshold events for
These slipped through the cracks. +CC Andrew directly.
Andrew, if it's not too late yet, could you consider them for 5.1?
On Wed, Dec 19, 2018 at 09:37:48AM -0800, Roman Gushchin wrote:
> The patchset contains few changes to the vmalloc code, which are
> leading to some performance gains and code
On Mon, Feb 11, 2019 at 10:05 AM Nadav Amit wrote:
>
> > On Feb 10, 2019, at 9:18 PM, Andy Lutomirski wrote:
> >
> >
> >
> > On Feb 10, 2019, at 4:39 PM, Nadav Amit wrote:
> >
> >>> On Jan 28, 2019, at 4:34 PM, Rick Edgecombe
> >>> wrote:
> >>>
> >>> From: Nadav Amit
> >>>
> >>> To prevent
On Mon, Feb 11, 2019 at 04:38:46PM +0800, Huang, Ying wrote:
> +struct swap_info_struct *get_swap_device(swp_entry_t entry)
> +{
> + struct swap_info_struct *si;
> + unsigned long type, offset;
> +
> + if (!entry.val)
> + goto out;
> + type = swp_type(entry);
> +
Hello Fabrice,
On Mon, Feb 11, 2019 at 05:12:02PM +0100, Fabrice Gasnier wrote:
> Add a device link between the PWM consumer and the PWM provider. This
> enforces the PWM user to get suspended before the PWM provider. It
> allows proper synchronization of suspend/resume sequences: the PWM user
>
On Fri, 08 Feb 2019 20:26:07 PST (-0800), david.abdurachma...@gmail.com wrote:
On Sat, Feb 9, 2019 at 12:03 AM Atish Patra wrote:
On 2/8/19 1:11 AM, Christoph Hellwig wrote:
>> + * We don't support running Linux on hertergenous ISA systems.
>> + * But first "okay" processor might not
On Mon, Feb 11, 2019 at 10:45:26AM -0800, Nadav Amit wrote:
> Are you sure about that? This path is still used when modules are loaded.
Yes, I'm sure. Loading a module does a gazillion things so saving a
couple of insns - yes, boot_cpu_has() is usually a RIP-relative MOV and a
TEST - doesn't show
From: Enrico Granata
ACPI 5 added support for GpioInt resources as a way to provide
information about interrupts mediated via a GPIO controller.
Several device buses (e.g. SPI, I2C) have support for retrieving
an IRQ specified via this type of resource, and providing it
directly to the driver
On Fri, Feb 08, 2019 at 10:44:19PM +, Chris Down wrote:
> memory.stat and other files already consider subtrees in their output,
> and we should too in order to not present an inconsistent interface.
>
> The current situation is fairly confusing, because people interacting
> with cgroups
Add dynamic power coefficients for the Silver and Gold CPU cores of
the Qualcomm SDM845.
Signed-off-by: Matthias Kaehlcke
---
arch/arm64/boot/dts/qcom/sdm845.dtsi | 8
1 file changed, 8 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/sdm845.dtsi
On 2019-02-11 03:13, Ryder Lee wrote:
> There is no need to retun 0 in mt76_dma_attach(), so switch it to void.
>
> Signed-off-by: Ryder Lee
Applied, thanks.
- Felix
In preparation to enabling -Wimplicit-fallthrough, mark switch
cases where we are expecting to fall through.
This patch fixes the following warning:
drivers/gpu/drm/nouveau/nouveau_bo.c: In function ‘nouveau_ttm_io_mem_reserve’:
drivers/gpu/drm/nouveau/nouveau_bo.c:1434:53: warning: this
On Mon, Feb 11, 2019 at 9:22 AM Todd Kjos wrote:
>
> +Alistair Strachan
>
> On Mon, Feb 11, 2019 at 9:11 AM Greg KH wrote:
> >
> > On Mon, Feb 11, 2019 at 10:15:18PM +0530, Souptick Joarder wrote:
> > > On Mon, Feb 11, 2019 at 9:27 PM Greg KH
> > > wrote:
> > > >
> > > > On Mon, Feb 11, 2019
If a parent to a clock comes from outside that clock's provider, the parent
may not be present at the time the clock is registered (ie the parent comes
from another driver that has not yet probed). The clock can still be
registered, and a reference to it obtained, however that clock may not be
On Mon, 11 Feb 2019 19:25:12 +0100,
Sam Ravnborg wrote:
>
> Hi Daniel.
>
> On Mon, Feb 11, 2019 at 06:15:20PM +0100, Daniel Vetter wrote:
> > Hi all,
> >
> > Here's the typed component topic branch.
> >
> > drm-intel maintainers: Please pull, I need this for the mei hdcp work from
> > Ram.
>
Em Mon, Feb 11, 2019 at 10:34:16AM -0800, Stephane Eranian escreveu:
> Jiri,
>
> On Mon, Feb 11, 2019 at 2:20 AM Jiri Olsa wrote:
> >
> > On Tue, Feb 05, 2019 at 02:37:27PM +0100, Jiri Olsa wrote:
> > > On Mon, Feb 04, 2019 at 02:44:37PM -0800, Stephane Eranian wrote:
> > > > Jiri,
> > > >
> > >
On Fri, Feb 08, 2019 at 10:43:19PM +, Chris Down wrote:
> I spent literally an hour trying to work out why an earlier version of
> my memory.events aggregation code doesn't work properly, only to find
> out I was calling memcg->events instead of memcg->memory_events, which
> is fairly
Fix the following warning by adding a missing break:
drivers/gpu/drm/nouveau/nouveau_abi16.c: In function
‘nouveau_abi16_ioctl_getparam’:
drivers/gpu/drm/nouveau/nouveau_abi16.c:202:3: warning: this statement may fall
through [-Wimplicit-fallthrough=]
switch (device->info.platform) {
In multi-master environment, this driver's master cannot know
exactly when a peer master sends data to this driver's slave so
cases can be happened that this master tries sending data through
the master_xfer function but slave data from a peer master is still
being processed or slave xfer is
On Fri, Feb 01, 2019 at 10:02:30PM +0100, Jan Kara wrote:
> On Thu 31-01-19 11:10:06, Jerome Glisse wrote:
> >
> > Andrew what is your plan for this ? I had a discussion with Peter Xu
> > and Andrea about change_pte() and kvm. Today the change_pte() kvm
> > optimization is effectively disabled
Em Fri, Feb 08, 2019 at 05:16:56PM -0800, Song Liu escreveu:
> This series enables annotation of BPF programs in perf.
>
> perf tool gathers information via sys_bpf and (optionally) stores them in
> perf.data as headers.
Jiri, Stephane, this is the patchkit I mentioned in the context of doing
On Mon, Feb 11, 2019 at 10:34:16AM -0800, Stephane Eranian wrote:
> Jiri,
>
> On Mon, Feb 11, 2019 at 2:20 AM Jiri Olsa wrote:
> >
> > On Tue, Feb 05, 2019 at 02:37:27PM +0100, Jiri Olsa wrote:
> > > On Mon, Feb 04, 2019 at 02:44:37PM -0800, Stephane Eranian wrote:
> > > > Jiri,
> > > >
> > > >
On Mon, Feb 11, 2019 at 7:25 PM Sam Ravnborg wrote:
>
> Hi Daniel.
>
> On Mon, Feb 11, 2019 at 06:15:20PM +0100, Daniel Vetter wrote:
> > Hi all,
> >
> > Here's the typed component topic branch.
> >
> > drm-intel maintainers: Please pull, I need this for the mei hdcp work from
> > Ram.
> >
> >
Fix the following warning by adding a missing break:
drivers/gpio/gpio-eic-sprd.c: In function ‘sprd_eic_irq_set_type’:
drivers/gpio/gpio-eic-sprd.c:403:3: warning: this statement may fall through
[-Wimplicit-fallthrough=]
switch (flow_type) {
^~
drivers/gpio/gpio-eic-sprd.c:435:2:
From: Florian Fainelli
Date: Mon, 11 Feb 2019 09:31:42 -0800
> David, I will be reposting a v4 with Jiri's Acked-by as well as adding
> fallthrough switch/case annotations so we don't regress on that front.
> Thank you.
Ok, thanks for letting me know.
We added some locking to this function but forgot to drop the lock on
these two error paths. This bug would lead to an immediate deadlock.
Fixes: c7b3690fb152 ("vmw_balloon: stats rework")
Signed-off-by: Dan Carpenter
---
drivers/misc/vmw_balloon.c | 5 +++--
1 file changed, 3 insertions(+), 2
> On Feb 11, 2019, at 10:29 AM, Borislav Petkov wrote:
>
>> diff --git a/arch/x86/kernel/alternative.c b/arch/x86/kernel/alternative.c
>> index 76d482a2b716..69f3e650ada8 100644
>> --- a/arch/x86/kernel/alternative.c
>> +++ b/arch/x86/kernel/alternative.c
>> @@ -667,15 +667,29 @@ void __init
Add missing break statement in order to prevent the code from falling
through to case ISCSI_BOOT_TGT_NAME, which is unnecessary.
This bug was found thanks to the ongoing efforts to enable
-Wimplicit-fallthrough.
Fixes: b33a84a38477 ("ibft: convert iscsi_ibft module to iscsi boot lib")
Cc:
On Fri, Nov 9, 2018 at 12:58 AM Frank Rowand wrote:
What LTSI's are these patches likely to end up in? Just to be clear,
I'm not pushing for any specific answer, I just want to know what to
expect.
Thanks,
Alan
>
> On 11/8/18 10:56 PM, Frank Rowand wrote:
> > Hi Rob,
> >
> > Please pull the
On Mon, Feb 11, 2019 at 11:26:49AM -0700, Jason Gunthorpe wrote:
> On Mon, Feb 11, 2019 at 10:19:22AM -0800, Ira Weiny wrote:
> > What if user space then writes to the end of the file with a regular write?
> > Does that write end up at the point they truncated to or off the end of the
> > mmaped
On Mon, Feb 11, 2019 at 10:34:09AM -0800, Linus Torvalds wrote:
On Sun, Feb 10, 2019 at 7:19 PM Eduardo Valentin wrote:
On Sun, Feb 10, 2019 at 04:25:16AM +, pr-tracker-...@kernel.org wrote:
> The pull request you sent on Sat, 9 Feb 2019 20:17:23 -0800:
>
> >
In preparation to enabling -Wimplicit-fallthrough, mark switch
cases where we are expecting to fall through.
This patch fixes the following warnings:
drivers/clk/samsung/clk-s3c2443.c: In function ‘s3c2443_common_clk_init’:
drivers/clk/samsung/clk-s3c2443.c:390:3: warning: this statement may
On Mon, Jan 28, 2019 at 04:34:13PM -0800, Rick Edgecombe wrote:
> From: Nadav Amit
>
> There are only two types of poking: early and breakpoint based. The use
> of a function pointer to perform poking complicates the code and is
> probably inefficient due to the use of indirect branches.
>
>
On Mon, Oct 29, 2018 at 10:54 AM Nick Desaulniers
wrote:
>
> On Wed, Oct 24, 2018 at 1:37 AM Jarkko Sakkinen
> wrote:
> >
> > On Mon, 22 Oct 2018, ndesaulni...@google.com wrote:
> > > Fixes the warning reported by Clang:
> > > security/keys/trusted.c:146:17: warning: passing an object that
> > >
The pull request you sent on Sun, 10 Feb 2019 20:46:15 -0800:
> git://git.kernel.org/pub/scm/linux/kernel/git/mattst88/alpha.git for-linus
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/244cce14c17705e6376cd12c20c27f8712793acc
Thank you!
--
Deet-doot-dot, I am a
In preparation to enabling -Wimplicit-fallthrough, mark switch
cases where we are expecting to fall through.
This patch fixes the following warnings:
In file included from drivers/block/drbd/drbd_actlog.c:30:
drivers/block/drbd/drbd_int.h: In function ‘__drbd_chk_io_error_’:
The pull request you sent on Mon, 11 Feb 2019 08:04:36 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux.git tags/s390-5.0-3
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/fb7453e61a2b6c29ab08f87b71e2647efe816526
Thank you!
--
Deet-doot-dot, I am a
On Sun, Feb 10, 2019 at 7:19 PM Eduardo Valentin wrote:
>
> On Sun, Feb 10, 2019 at 04:25:16AM +, pr-tracker-...@kernel.org wrote:
> > The pull request you sent on Sat, 9 Feb 2019 20:17:23 -0800:
> >
> > > git://git.kernel.org/pub/scm/linux/kernel/git/evalenti/linux-soc-thermal
> > > fixes
>
Jiri,
On Mon, Feb 11, 2019 at 2:20 AM Jiri Olsa wrote:
>
> On Tue, Feb 05, 2019 at 02:37:27PM +0100, Jiri Olsa wrote:
> > On Mon, Feb 04, 2019 at 02:44:37PM -0800, Stephane Eranian wrote:
> > > Jiri,
> > >
> > > While you're looking at the output format, I think it would be good
> > > time to
Add missing break statement in order to prevent the code from falling
through to case S_DIN_to_DES.
This bug was found thanks to the ongoing efforts to enable
-Wimplicit-fallthrough.
Fixes: 63ee04c8b491 ("crypto: ccree - add skcipher support")
Cc: sta...@vger.kernel.org
Signed-off-by: Gustavo A.
On 11-Feb-19 10:11 PM, Anshuman Gupta wrote:
On Fri, Feb 01, 2019 at 01:02:33PM +0530, Rajneesh Bhardwaj wrote:
This patch introduces a new debugfs entry to read current Package
cstate residency counters. A similar variant of this patch was discussed
earlier
On Mon, 2019-02-11 at 12:48 -0500, Michael S. Tsirkin wrote:
> On Mon, Feb 11, 2019 at 09:41:19AM -0800, Dave Hansen wrote:
> > On 2/9/19 4:44 PM, Michael S. Tsirkin wrote:
> > > So the policy should not leak into host/guest interface.
> > > Instead it is better to just keep the pages pinned and
>
> Subject: Re: [PATCH v2 10/20] x86: avoid W^X being broken during modules
> loading
For your next submission, please fix all your subjects:
The tip tree preferred format for patch subject prefixes is
'subsys/component:', e.g. 'x86/apic:', 'x86/mm/fault:', 'sched/fair:',
'genirq/core:'. Please
On 2/11/2019 10:16 AM, Wolfram Sang wrote:
Can you please apply above changes on top of this patch? Or I can submit
v2 with it.
Please send v2.
Okay, I'll send v2.
Thanks,
Jae
On Sun, Feb 10, 2019 at 9:08 PM wrote:
>
> arch/csky patches for 5.0-rc6
The bulk of this seems to be new hardware support code.
Please send it during the 5.1 merge window, not as fixes at post-rc6 time.
Linus
> -Original Message-
> From: Jeremy Linton [mailto:jeremy.lin...@arm.com]
> Sent: Friday, February 8, 2019 4:47 PM
> To: linux-arm-ker...@lists.infradead.org
> Cc: linux-kernel@vger.kernel.org; linux-a...@vger.kernel.org;
> de...@acpica.org; catalin.mari...@arm.com; will.dea...@arm.com;
On Mon, Feb 11, 2019 at 10:19:22AM -0800, Ira Weiny wrote:
> On Mon, Feb 11, 2019 at 11:06:54AM -0700, Jason Gunthorpe wrote:
> > On Mon, Feb 11, 2019 at 09:22:58AM -0800, Dan Williams wrote:
> >
> > > I honestly don't like the idea that random subsystems can pin down
> > > file blocks as a side
Hi Daniel.
On Mon, Feb 11, 2019 at 06:15:20PM +0100, Daniel Vetter wrote:
> Hi all,
>
> Here's the typed component topic branch.
>
> drm-intel maintainers: Please pull, I need this for the mei hdcp work from
> Ram.
>
> drm-misc maintainers: Please pull, there's a drm doc patch follow-up
>
Hi Philipp,
On 2/11/19 1:58 AM, Philipp Zabel wrote:
On Fri, 2019-02-08 at 17:47 -0800, Steve Longerbeam wrote:
The ycbcr2rgb and inverse rgb2ycbcr matrices define the BT.601 encoding
coefficients, so rename them to indicate that. And add some comments
to make clear these are BT.601
Only nitpicks:
> Subject: Re: [PATCH v2 09/20] x86/kprobes: instruction pages initialization
> enhancements
Subject needs a verb.
On Mon, Jan 28, 2019 at 04:34:11PM -0800, Rick Edgecombe wrote:
> From: Nadav Amit
>
> Make kprobes instruction pages read-only (and executable) after they are
>
On Mon, 11 Feb 2019 at 17:21, Martin Sebor wrote:
>
> On 2/9/19 5:31 AM, Miguel Ojeda wrote:
> > On Sat, Feb 9, 2019 at 12:26 PM Ard Biesheuvel
> > wrote:
> >>
> >> On Sat, 9 Feb 2019 at 12:19, Miguel Ojeda
> >> wrote:
> >>>
> >>> It also affects the optimizer in two different ways AFAIK:
> >>>
On 2/11/19 9:58 AM, Michael S. Tsirkin wrote:
>>> Really it seems we want a virtio ring so we can pass a batch of these.
>>> E.g. 256 entries, 2M each - that's more like it.
>> That only makes sense for a system that's doing high-frequency,
>> discontiguous frees of 2M pages. Right now, a 2M
On Mon, Feb 11, 2019 at 11:06:54AM -0700, Jason Gunthorpe wrote:
> On Mon, Feb 11, 2019 at 09:22:58AM -0800, Dan Williams wrote:
>
> > I honestly don't like the idea that random subsystems can pin down
> > file blocks as a side effect of gup on the result of mmap. Recall that
> > it's not just
On Sat, Feb 9, 2019 at 9:28 AM Stefan Agner wrote:
>
> Thanks for the reviews so far.
>
> During some more testing I stumbled upon another issue:
>
> On 07.02.2019 10:48, Stefan Agner wrote:
> > Use unified assembler syntax (UAL) in inline assembler. Divided
> > syntax is considered depricated.
> Can you please apply above changes on top of this patch? Or I can submit
> v2 with it.
Please send v2.
signature.asc
Description: PGP signature
On Mon, Feb 11, 2019 at 11:53:39AM +0100, Ingo Molnar wrote:
> > + do_trap(trapnr, signr, str, regs, error_code, BUS_ADRALN, NULL);
> > + }
> > +}
>
> Is there any experience with how frequently this signal is killing
> user-space processes on a modern distro? Any expectation of how
On Mon, Feb 11, 2019 at 10:07 AM Jason Gunthorpe wrote:
>
> On Mon, Feb 11, 2019 at 09:22:58AM -0800, Dan Williams wrote:
>
> > I honestly don't like the idea that random subsystems can pin down
> > file blocks as a side effect of gup on the result of mmap. Recall that
> > it's not just RDMA that
> Am 11.02.2019 um 17:20 schrieb Andreas Kemnade :
>
> The lcd display of the gta04 has a backlight but the backlight
> was not referenced in the lcd node, so screen blanking did
> not turn off the backlight. Fix that.
>
> Signed-off-by: Andreas Kemnade
Works fine.
Tested-by: H. Nikolaus
Hi Greg,
On 2/11/2019 6:15 AM, Greg Kroah-Hartman wrote:
> 4.19-stable review patch. If anyone has any objections, please let me know.
>
> --
>
> [ Upstream commit 723f1a0dd8e26a7523ba068204bee11c95ded38d ]
>
> Fix the messages in rdt_last_cmd_printf() and rdt_last_cmd_puts()
On Mon, Feb 11, 2019 at 03:20:18PM +0100, Greg Kroah-Hartman wrote:
> 4.9-stable review patch. If anyone has any objections, please let me know.
>
> --
>
> From: Andi Kleen
>
> commit a7e3ed1e470116c9d12c2f778431a481a6be8ab6 upstream.
The patch doesn't seem to match the
On Mon, 2019-02-11 at 12:36 -0500, Michael S. Tsirkin wrote:
> On Mon, Feb 11, 2019 at 08:31:34AM -0800, Alexander Duyck wrote:
> > On Sat, 2019-02-09 at 19:49 -0500, Michael S. Tsirkin wrote:
> > > On Mon, Feb 04, 2019 at 10:15:52AM -0800, Alexander Duyck wrote:
> > > > From: Alexander Duyck
> >
Hmmm, the #ifdeffery quite increases with this patch. Maybe it is easier
to select I2C_SLAVE in Kconfig? I'll let you decide.
My code checkers found this:
CPPCHECK
drivers/i2c/busses/i2c-aspeed.c:694:10: warning: Variable 'ret' is assigned a
value that is never used. [unreadVariable]
On 2/11/19 12:41 PM, Michael S. Tsirkin wrote:
> On Mon, Feb 11, 2019 at 11:24:02AM -0500, Nitesh Narayan Lal wrote:
>> On 2/11/19 9:17 AM, Michael S. Tsirkin wrote:
>>> On Mon, Feb 11, 2019 at 08:30:03AM -0500, Nitesh Narayan Lal wrote:
On 2/9/19 7:57 PM, Michael S. Tsirkin wrote:
> On
> From: Sasha Levin
> Sent: Monday, February 11, 2019 9:26 AM
> To: Sasha Levin ; Dexuan Cui ;
> Lorenzo Pieralisi
> Cc: linux-kernel@vger.kernel.org; sta...@vger.kernel.org; Stephen Hemminger
> ; sta...@vger.kernel.org
> Subject: Re: [PATCH] PCI: hv: Add hv_pci_remove_slots() when we unload the
501 - 600 of 2376 matches
Mail list logo
