On Thu, Feb 21, 2019 at 01:39:09PM +0100, Jiri Olsa wrote:
> On Thu, Feb 21, 2019 at 01:23:06PM +0100, Jonas Rabenstein wrote:
> > In __hists__add_entry the srcline of the addr_location is duplicated
> > for the hist_entry. If hists__findnew_entry returns an already existing
> > hist_entry the
On Sun 2019-02-17 02:32:22, John Ogness wrote:
> Hi Petr,
>
> I've made changes to the patch that hopefully align with what you are
> looking for. I would appreciate it if you could go over it and see if
> the changes are in the right direction. And if so, you should decide
> whether I should
From: Joerg Roedel
The stable backport of upstream commit
904e14fb7cb96 KVM: VMX: make MSR bitmaps per-VCPU
has a bug in vmx_msr_bitmap_mode(). It enables the x2apic
MSR-bitmap when the kernel emulates x2apic for the guest in
software. The upstream version of the commit checkes whether
On Thu, Feb 21, 2019 at 11:34:50AM +, Steven Price wrote:
> From: James Morse
>
> Exposing the pud/pgd levels of the page tables to walk_page_range() means
> we may come across the exotic large mappings that come with large areas
> of contiguous memory (such as the kernel's linear map).
>
>
Right now, the driver will create a device node for each output port,
with the intent to provide read access to that port's data. However,
only the memory ports are readable this way (msc0, msc1). Other output
ports don't need device nodes, so remove them.
Signed-off-by: Alexander Shishkin
---
consider pulling or applying. Thanks!
The following changes since commit bfeffd155283772bbe78c6a05dec7c0128ee500c:
Linux 5.0-rc1 (2019-01-06 17:08:20 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/ash/stm.git
tags/intel_th-stm-for-greg-20190221
Christophe Leroy writes:
> Now that mmu_mapin_ram() is able to handle other blocks
> than the one starting at 0, the WII can use it for all
> its blocks.
>
> Signed-off-by: Christophe Leroy
> ---
> arch/powerpc/mm/pgtable_32.c | 27 +--
> 1 file changed, 9
From: "Gustavo A. R. Silva"
In preparation to enabling -Wimplicit-fallthrough, mark switch
cases where we are expecting to fall through.
This patch fixes the following warnings:
drivers/hwtracing/intel_th/sth.c: In function ‘sth_stm_packet’:
drivers/hwtracing/intel_th/sth.c:86:7: warning: this
Commit a753bfcfdb1f3 ("intel_th: Make the switch allocate its subdevices")
changed the behavior so that the output port devices are created only for
the ports reported by the hardware and their initial state is "unassigned"
until a corresponding output port driver is loaded. Reflect this fact in
When an output port driver is removed, also remove references to it from
any masters. Failing to do this causes a NULL ptr dereference when
configuring another output port:
> BUG: unable to handle kernel NULL pointer dereference at 000d
> RIP: 0010:master_attr_store+0x9d/0x160
Using STP_POLICY_ID_SET ioctl command with dummy_stm device, or any STM
device that supplies zero mmio channel size, will trigger a division by
zero bug in the kernel.
Prevent this by disallowing channel widths other than 1 for such devices.
Signed-off-by: Alexander Shishkin
---
From: Zhi Jin
There is a bug in the channel allocation logic that leads to an endless
loop when looking for a contiguous range of channels in a range with a
mixture of free and occupied channels. For example, opening three
consequtive channels, closing the first two and requesting 4 channels in
From: Andy Shevchenko
Use sysfs_match_string() helper instead of open coded variant.
Signed-off-by: Andy Shevchenko
Signed-off-by: Alexander Shishkin
---
drivers/hwtracing/intel_th/pti.c | 16 +++-
1 file changed, 7 insertions(+), 9 deletions(-)
diff --git
On Thu, Feb 21, 2019 at 08:12:25AM -0500, Prarit Bhargava wrote:
> Users cannot disable multiple CPU features with the kernel parameter
> clearcpuid=. For example, "clearcpuid=154 clearcpuid=227" only disables
> CPUID bit 154.
>
> Previous to commit 0c2a3913d6f5 ("x86/fpu: Parse clearcpuid= as
From: Claudiu Beznea
Add support for SAM9X60 shutdown controller.
Signed-off-by: Claudiu Beznea
Acked-by: Nicolas Ferre
---
drivers/power/reset/at91-sama5d2_shdwc.c | 11 +++
1 file changed, 11 insertions(+)
diff --git a/drivers/power/reset/at91-sama5d2_shdwc.c
> -Original Message-
> From: Gustavo A. R. Silva [mailto:gust...@embeddedor.com]
> Sent: Wednesday, February 20, 2019 8:03 PM
> To: Wan, Kaike ; Marciniszyn, Mike
> ; Dalessandro, Dennis
> ; Doug Ledford ;
> Jason Gunthorpe
> Cc: linux-r...@vger.kernel.org; linux-kernel@vger.kernel.org;
On Tue, Feb 19, 2019 at 2:00 PM Heikki Krogerus
wrote:
>
> In ACPI, and now also in DT, the USB connectors usually have
> their own device nodes. In case of USB Type-C, those
> connector (port) nodes are child nodes of the controller or
> PHY device, in our case the fusb302. The software fwnodes
From: Claudiu Beznea
Add documentation for SAM9X60 shutdown controller.
Signed-off-by: Claudiu Beznea
---
Documentation/devicetree/bindings/arm/atmel-sysregs.txt | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/arm/atmel-sysregs.txt
From: Claudiu Beznea
Add RTT wakeup capability.
Signed-off-by: Claudiu Beznea
Acked-by: Nicolas Ferre
---
drivers/power/reset/at91-sama5d2_shdwc.c | 14 ++
1 file changed, 14 insertions(+)
diff --git a/drivers/power/reset/at91-sama5d2_shdwc.c
From: Claudiu Beznea
Hi,
This series adapt SAMA5D2's shutdown controller driver to work for
SAM9X60's shutdown controller. The difference is that SAM9X60 have
option for RTT timer wakeup.
Thank you,
Claudiu Beznea
Changes in v2:
- collect Acked-by tags
- in patch 3/3 use "optional
Hi!
Much better, thanks! One nit below:
On 2019-02-21 13:48, Pankaj Bansal wrote:
> Generic register bitfield-based multiplexer that controls the multiplexer
> producer defined under a parent node.
> The driver corresponding to parent node provides register read/write
> capabilities.
>
>
On Thu, 21 Feb 2019 at 14:17, Axel Lin wrote:
>
> Signed-off-by: Axel Lin
> ---
> drivers/regulator/s5m8767.c | 6 +-
> 1 file changed, 1 insertion(+), 5 deletions(-)
Reviewed-by: Krzysztof Kozlowski
Best regards,
Krzysztof
On 02/21/2019 02:35 PM, kernel test robot wrote:
>
> FYI, we noticed the following commit (built with gcc-7):
>
> commit: 568f196756ad9fe2b49c46bbf6a9de1b190438b4 ("bpf: check that BPF
> programs run with preemption disabled")
> https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git
On Thu, Feb 21, 2019 at 11:34:52AM +, Steven Price wrote:
> From: James Morse
>
> Exposing the pud/pgd levels of the page tables to walk_page_range() means
> we may come across the exotic large mappings that come with large areas
> of contiguous memory (such as the kernel's linear map).
>
>
This patch add support for perf callchain sampling on csky platform.
As fp is used to unwind the stack, the program being sampled and the
C library need to be compiled with -mbacktrace for user callchains,
kernel callchains require CONFIG_STACKTRACE = y.
Signed-off-by: Mao Han
---
On Thu, Feb 21, 2019 at 10:56:42AM +0100, Jonas Gorski wrote:
> The switch to the generic dma ops made dma masks mandatory, breaking
> devices having them not set. In case of bcm63xx, it broke ethernet with
> the following warning when trying to up the device:
Looks good:
Reviewed-by: Christoph
hi Russell & Ulf
On 2/21/19 11:30 AM, Russell King - ARM Linux admin wrote:
On Thu, Feb 21, 2019 at 10:27:39AM +, Russell King - ARM Linux admin wrote:
On Thu, Feb 21, 2019 at 11:10:49AM +0100, Ludovic Barre wrote:
From: Ludovic Barre
This patch series introduces a bitmap of hardware
On Thu, Feb 21, 2019 at 08:12:25AM -0500, Prarit Bhargava wrote:
> Users cannot disable multiple CPU features with the kernel parameter
> clearcpuid=. For example, "clearcpuid=154 clearcpuid=227" only disables
> CPUID bit 154.
>
> Previous to commit 0c2a3913d6f5 ("x86/fpu: Parse clearcpuid= as
On Thu, Feb 21, 2019 at 2:40 AM Darren Hart wrote:
> On Wed, Feb 13, 2019 at 08:45:56PM +0530, Bhardwaj, Rajneesh wrote:
> > On 07-Feb-19 9:25 PM, Andy Shevchenko wrote:
> > > On Thu, Feb 7, 2019 at 4:06 AM Bhardwaj, Rajneesh
> > > wrote:
> > > > On 07-Feb-19 4:27 AM, Stephen Rothwell wrote:
>
The headers-install.sh already supports __packed conversion to
__attribute__((packed)) for uAPI headers but it does not support similar
__aligned(x) conversion.
Add support for __aligned(x).
Signed-off-by: Sakari Ailus
---
scripts/headers_install.sh | 1 +
1 file changed, 1 insertion(+)
diff
On Wed, 2019-02-20 at 15:41 +0100, Matthias Brugger wrote:
>
> On 20/02/2019 13:33, Qii Wang wrote:
> > Add i2c compatible for MT8183. Compare to MT2712 i2c controller,
> > MT8183 has different registers, offsets and clock.
> >
> > Signed-off-by: Qii Wang
>
> So you introduce arb clock,
On Wed, 2019-02-20 at 16:25 +0100, Matthias Brugger wrote:
>
> On 20/02/2019 13:33, Qii Wang wrote:
> > Add MT8183 i2c binding to binding file. Compare to MT2712 i2c
> > controller, MT8183 has different registers, offsets, and clock.
> >
> > Signed-off-by: Qii Wang
> > ---
> >
On Thu 21-02-19 01:23:50, Meelis Roos wrote:
> > > First, I found out that both the problematic alphas had memory compaction
> > > and
> > > page migration and bounce buffers turned on, and working alphas had them
> > > off.
> > >
> > > Next, turing off these options makes the problematic
[+CC dvyukov ]
On 20/02/2019 18:21, Johannes Thumshirn wrote:
> On 20/02/2019 17:15, Dan Williams wrote:> I wouldn't be opposed to
> syzkaller fuzzing the nvdimm-ioctl path.
> As a heads up, I've started adding the ioctl() definitions to syzcaller.
> Just so we don't duplicate any efforts.
So
On Thu, Feb 21, 2019 at 3:22 AM Darren Hart wrote:
>
> On Thu, Jan 10, 2019 at 06:58:41PM +0100, Lubomir Rintel wrote:
> > It's based off the driver from the OLPC kernel sources. Somewhat
> > modernized and cleaned up, for better or worse.
> >
> > Modified to plug into the olpc-ec driver
On Thu, Feb 21, 2019 at 03:08:39PM +0200, Jani Nikula wrote:
> On Thu, 21 Feb 2019, Gerd Hoffmann wrote:
> > It'll be useful for other drivers too, so move it to drm_fb_helper.c
> > (and rename it of course). Also add docs.
> >
> > Signed-off-by: Gerd Hoffmann
> > ---
> >
On Thu, Feb 21, 2019 at 06:55:54PM +0800, Rundong Ge wrote:
> Hi Andrew
>
> Before the "net: phy: marvell: Errata for mv88e6390 internal PHYs",
> phydev will only be soft reset when register value was changed.
> But after this patch, the phydev will always be reset when entering
> the
Hi Leon,
On Thu, 21 Feb 2019 13:16:31 + Leon Romanovsky wrote:
>
> > The xarray API changes (to xa_alloc and __xa_alloc) have been in
> > linux-next for about 2 weeks ...
>
> I looked on the latest update of pulled branch
>
On Thu, Feb 21, 2019 at 11:35 AM Heikki Krogerus
wrote:
>
> On Wed, Feb 20, 2019 at 05:55:21PM +0200, Andy Shevchenko wrote:
> > On Tue, Feb 19, 2019 at 2:00 PM Heikki Krogerus
> > wrote:
> > >
> > > In ACPI, and now also in DT, the USB connectors usually have
> > > their own device nodes. In
On Thu, 21 Feb 2019 at 14:17, Axel Lin wrote:
>
> The s5m8767_opmode_reg should never change, make it const.
>
> Signed-off-by: Axel Lin
> ---
> drivers/regulator/s5m8767.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Reviewed-by: Krzysztof Kozlowski
Best regards,
Krzysztof
On 21/02/2019 14:01, Christian Borntraeger wrote:
On 21.02.2019 13:51, Pierre Morel wrote:
On 21/02/2019 13:35, Christian Borntraeger wrote:
[..]
Go ahead and send this as v3?
OK
CC stable ?
Yes, also add a "Fixes:" tag.
Yes, I will not forget this time :)
Thanks
Pierre
--
Document support for ADIS16480 Inertial Measurement Unit.
Signed-off-by: Stefan Popa
---
.../devicetree/bindings/iio/imu/adi,adis16480.txt | 49 ++
MAINTAINERS| 1 +
2 files changed, 50 insertions(+)
create mode 100644
Signed-off-by: Axel Lin
---
drivers/regulator/s5m8767.c | 6 +-
1 file changed, 1 insertion(+), 5 deletions(-)
diff --git a/drivers/regulator/s5m8767.c b/drivers/regulator/s5m8767.c
index 5b0e1fe6723f..bb9d1a083299 100644
--- a/drivers/regulator/s5m8767.c
+++ b/drivers/regulator/s5m8767.c
All supported devices provide internal temperature measurement from -40 C
to +85 C, with +25 C representing value 0x00.
This patch treats the temperature scale in a generic way, similar to the
accelerometer and gyroscope scales. So far, there are no temperature max
scale differences between the
The FNCTIO_CTRL register provides configuration control for each I/O pin
(DIO1, DIO2, DIO3 and DIO4).
This patch adds the option to configure each DIOx pin as data ready
indicator with positive or negative polarity by reading the 'interrupts'
and 'interrupt-names' properties from the devicetree.
The ADIS16495 and ADIS16497 are inertial systems that include a triaxis
gyroscope and a triaxis accelerometer. The serial peripheral interface
(SPI) provide a simple interface for data collection and configuration
control. The devices are similar to ADIS16475, ADIS16480, ADIS16485 and
ADIS16488,
The s5m8767_opmode_reg should never change, make it const.
Signed-off-by: Axel Lin
---
drivers/regulator/s5m8767.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/regulator/s5m8767.c b/drivers/regulator/s5m8767.c
index b581f01f3395..5b0e1fe6723f 100644
---
The driver does not have a struct of_device_id table, but supported
devices are registered via Device Trees. This patch adds OF device ID
table.
Signed-off-by: Stefan Popa
---
drivers/iio/imu/adis16480.c | 10 ++
1 file changed, 10 insertions(+)
diff --git a/drivers/iio/imu/adis16480.c
This series has as main goal to add support for ADIS1649x family of devices as
part of the already existing adis16480, but on the way it also deals with some
outstanding items:
* Make drdy pin configurable
* Add OF device ID table
* Deal with the temperature max scale in a generic way
* Add
On Thu, Feb 21, 2019 at 10:45 AM Masahiro Yamada
wrote:
> On Thu, Feb 21, 2019 at 6:23 PM Arnd Bergmann wrote:
> > On Thu, Feb 21, 2019 at 5:14 AM Masahiro Yamada
> > wrote:
> >
> > I like how this cleans up the logic and documents it better.
> > I've had my own plans to move this (and most
On Thu, Feb 21, 2019 at 11:48:01PM +1100, Stephen Rothwell wrote:
> Hi Leon,
>
> On Thu, 21 Feb 2019 12:34:42 + Leon Romanovsky
> wrote:
> >
> > Matthew, really? change of API in -rc7? And it after you pushed us to
> > base our -next on -rc5 after another API change? What should we do now?
>
Users cannot disable multiple CPU features with the kernel parameter
clearcpuid=. For example, "clearcpuid=154 clearcpuid=227" only disables
CPUID bit 154.
Previous to commit 0c2a3913d6f5 ("x86/fpu: Parse clearcpuid= as early XSAVE
argument") it was possible to pass multiple clearcpuid options
On Thu, 21 Feb 2019 14:10:29 +0100,
Stephen Rothwell wrote:
>
> Hi Takashi,
>
> In commit
>
> de73e99af971 ("ALSA: hda/realtek: Enable audio jacks of ASUS UX362FA with
> ALC294")
>
> Fixes tag
>
> Fixes: 4e0511067 ("ALSA: hda/realtek: Enable audio jacks of ASUS UX533FD
> with ALC294")
>
On 21/02/19 4:11 PM, Bean Huo (beanhuo) wrote:
> Hi, Vignesh
>
>>
>> Cadence OSPI controller IP supports Octal IO (x8 IO lines), It also has an
>> integrated PHY. IP register layout is very similar to existing QSPI IP
>> except for
>> additional bits to support Octal and Octal DDR mode.
Hi Takashi,
In commit
de73e99af971 ("ALSA: hda/realtek: Enable audio jacks of ASUS UX362FA with
ALC294")
Fixes tag
Fixes: 4e0511067 ("ALSA: hda/realtek: Enable audio jacks of ASUS UX533FD with
ALC294")
has these problem(s):
- SHA1 should be at least 12 digits long
Can be fixed by
> Thank you very much for your hints. Yes that works indeed too. I
> just assumed it was intended to work automatically with the
> built-in phys as it does with the other switches I am using.
Hi Marcel
The basic assumption is there is a one to one mapping of port number
to PHY address. All the
On Wed, Feb 20, 2019 at 01:20:58PM -0800, Kees Cook wrote:
> On Wed, Feb 20, 2019 at 10:49 AM Solar Designer wrote:
> >
> > On Wed, Feb 20, 2019 at 10:09:34AM -0800, Kees Cook wrote:
> > > + if (WARN_ONCE((val & cr4_pin) != cr4_pin, "cr4 bypass attempt?!\n"))
> > > + goto again;
>
On Thu, 21 Feb 2019, Gerd Hoffmann wrote:
> It'll be useful for other drivers too, so move it to drm_fb_helper.c
> (and rename it of course). Also add docs.
>
> Signed-off-by: Gerd Hoffmann
> ---
> include/drm/drm_fb_helper.h | 2 ++
> drivers/gpu/drm/drm_fb_helper.c | 39
On Thu, Feb 21, 2019 at 01:20:11PM +0100, Daniel Vetter wrote:
> On Thu, Feb 21, 2019 at 12:35:34PM +0100, Gerd Hoffmann wrote:
> > Problem: qxl switches from native mode back into vga compatibility mode
> > when it notices someone is accessing vga registers. And vgacon does
> > exactly that
On 21.02.2019 13:51, Pierre Morel wrote:
> On 21/02/2019 13:35, Christian Borntraeger wrote:
>>
>>
[..]
>> Go ahead and send this as v3?
>>
>
> OK
> CC stable ?
Yes, also add a "Fixes:" tag.
On Thu, Feb 21, 2019 at 01:12:40PM +0100, Cornelia Huck wrote:
> On Thu, 21 Feb 2019 11:42:25 +0100
> Harald Freudenberger wrote:
>
> > On 30.01.19 19:32, Sebastian Ott wrote:
> > > On Wed, 30 Jan 2019, Tony Krowiak wrote:
>
> > >> /*
> > >> +* A config change has happened, Force an ap bus
On Wed, Feb 20, 2019 at 05:20:48PM +0300, Yury Norov wrote:
> On Wed, Feb 20, 2019 at 03:52:36PM +0200, Andy Shevchenko wrote:
> > On Wed, Feb 20, 2019 at 03:51:01PM +0200, Andy Shevchenko wrote:
> > > On Wed, Feb 20, 2019 at 11:37:03AM +0300, Yury Norov wrote:
> > > > test_bitmap_parselist
On 21/02/2019 13:35, Christian Borntraeger wrote:
On 21.02.2019 13:10, Pierre Morel wrote:
On 20/02/2019 13:51, Halil Pasic wrote:
On Wed, 20 Feb 2019 10:27:31 +0100
Cornelia Huck wrote:
On Tue, 19 Feb 2019 22:31:17 +0100
Pierre Morel wrote:
On 19/02/2019 19:52, Tony Krowiak wrote:
On
Am 20.02.2019 um 15:46 schrieb Hangbin Liu:
Could you please include more details about the setup that's broken ?
Note that we were warned[1] of potential breakage from this change
Sorry I missed Linus's reply after Ying Xu replied. I will read it and
disscuss with Ying Xu.
after it went in
On 20/02/2019 12:54, Halil Pasic wrote:
On Thu, 14 Feb 2019 14:51:07 +0100
Pierre Morel wrote:
We register the AP PQAP instruction hook during the open
of the mediated device. And unregister it on release.
In the AP PQAP instruction hook, if we receive a demand to
enable IRQs,
- we retrieve
Generic register bitfield-based multiplexer that controls the multiplexer
producer defined under a parent node.
The driver corresponding to parent node provides register read/write
capabilities.
Signed-off-by: Pankaj Bansal
---
Notes:
V2:
- removed seperate driver regmap.c and added the
Hi Leon,
On Thu, 21 Feb 2019 12:34:42 + Leon Romanovsky wrote:
>
> Matthew, really? change of API in -rc7? And it after you pushed us to
> base our -next on -rc5 after another API change? What should we do now?
The xarray API changes (to xa_alloc and __xa_alloc) have been in
linux-next for
Hi Jason,
On Wed, 13 Feb 2019 22:09:36 + Jason Gunthorpe wrote:
>
> I personally think it is not good to put major logic changes in merge
> commits, so I would prefer the #2 approach for this case.
These are not difficult merge fixes or logic changes.
> Also, the general philosophy that
On Wed, Feb 20, 2019 at 02:55:59PM -0800, H. Peter Anvin wrote:
> On 2/19/19 4:48 AM, Will Deacon wrote:
> >
> > I think you'll still hate this, but could we not disable preemption during
> > the uaccess-enabled region, re-enabling it on the fault path after we've
> > toggled uaccess off and
From: Maulik Shah
The return index value from bitmap_find_next_zero_area can be higher
than available slot. So correct the check to return error in such case.
Signed-off-by: Maulik Shah
Signed-off-by: Raju P.L.S.S.S.N
---
drivers/soc/qcom/rpmh-rsc.c | 2 +-
1 file changed, 1 insertion(+), 1
Fix the redundant call being made to send the sleep and wake requests
immediately to the controller.
As per the patch[1], the sleep and wake request votes are cached in rpmh
controller and sent during rpmh_flush(). These requests needs to be sent
only during entry of deeper system low power modes
Hi,
This series consists of couple of fixes identified in RPMh driver.
Please consider reviewing the patches.
Maulik Shah (1):
drivers: soc: qcom: rpmh-rsc: Correct check for slot number
Raju P.L.S.S.S.N (1):
drivers: qcom: rpmh: avoid sending sleep/wake sets immediately
On 19/02/2019 23:36, Tony Krowiak wrote:
On 2/19/19 2:50 PM, Pierre Morel wrote:
On 18/02/2019 23:42, Cornelia Huck wrote:
On Mon, 18 Feb 2019 19:29:10 +0100
Pierre Morel wrote:
On 15/02/2019 23:02, Tony Krowiak wrote:
On 2/14/19 8:51 AM, Pierre Morel wrote:
+/*
+ * handle_pqap:
In error path of IPU, we didn't account iostat correctly, fix it.
Signed-off-by: Chao Yu
---
fs/f2fs/segment.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/fs/f2fs/segment.c b/fs/f2fs/segment.c
index 3602acee4985..86a6fcbe8484 100644
--- a/fs/f2fs/segment.c
+++
On Thu, Feb 21, 2019 at 01:23:06PM +0100, Jonas Rabenstein wrote:
> In __hists__add_entry the srcline of the addr_location is duplicated
> for the hist_entry. If hists__findnew_entry returns an already existing
> hist_entry the srcline has to be freed again as no further reference to
> that
On Tue, Jan 29, 2019 at 5:55 PM Jonathan Neuschäfer
wrote:
> AFAICS from the i.MX50 Reference Manual, the i.MX50 IOMUXC works the
> same as the one in i.MX51, so I copied fsl,imx51-pinctrl.txt and changed
> the text to imx50.
>
> Signed-off-by: Jonathan Neuschäfer
> Cc: Dong Aisheng
> Cc:
For IPU path of f2fs_do_write_data_page(), in its error path, we
need to release encrypted page and fscrypt context, otherwise it
will cause memory leak.
Signed-off-by: Chao Yu
---
fs/f2fs/data.c | 9 +++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/fs/f2fs/data.c
From: Colin Ian King
The call to ieee80211_probereq_get can return NULL if a skb allocation
fails, so add a null pointer check and free an earlier skb on the error
exit return path.
Fixes: 7fdcb8e12660 ("rsi: add support for hardware scan offload")
Signed-off-by: Colin Ian King
---
On 21.02.2019 13:10, Pierre Morel wrote:
> On 20/02/2019 13:51, Halil Pasic wrote:
>> On Wed, 20 Feb 2019 10:27:31 +0100
>> Cornelia Huck wrote:
>>
>>> On Tue, 19 Feb 2019 22:31:17 +0100
>>> Pierre Morel wrote:
>>>
On 19/02/2019 19:52, Tony Krowiak wrote:
> On 2/18/19 1:08 PM, Pierre
On Thu, Feb 21, 2019 at 05:13:32PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> After merging the xarray tree, today's linux-next build (powerpc
> ppc64_defconfig) failed like this:
>
> In file included from include/linux/uio.h:12,
> from include/linux/socket.h:8,
>
On Tue, Feb 19, 2019 at 02:54:29PM +0530, Amit Daniel Kachhap wrote:
> This feature will allow the KVM guest to allow the handling of
> pointer authentication instructions or to treat them as undefined
> if not set. It uses the existing vcpu API KVM_ARM_VCPU_INIT to
> supply this parameter instead
On 2019/02/21 20:09, Greg Kroah-Hartman wrote:
> On Thu, Feb 21, 2019 at 07:40:20PM +0900, Tetsuo Handa wrote:
>> On 2019/02/21 4:52, Dmitry Torokhov wrote:
>>> On Wed, Feb 20, 2019 at 7:07 AM Greg Kroah-Hartman
>>> wrote:
But I would argue that this is not ok, as the remove uevent did NOT
Hi,
On 19-02-19 22:47, Lendacky, Thomas wrote:
On 2/19/19 3:01 PM, Thomas Gleixner wrote:
Hans,
On Tue, 19 Feb 2019, Hans de Goede wrote:
Cc+: ACPI/AMD folks
Various people are reporting false positive "do_IRQ: #.55 No irq handler for
vector"
messages on AMD ryzen based laptops, see e.g.:
On Tue, Feb 19, 2019 at 02:54:28PM +0530, Amit Daniel Kachhap wrote:
> From: Mark Rutland
>
> When pointer authentication is supported, a guest may wish to use it.
> This patch adds the necessary KVM infrastructure for this to work, with
> a semi-lazy context switch of the pointer auth state.
>
Hi,
On 19-02-19 22:01, Thomas Gleixner wrote:
Hans,
On Tue, 19 Feb 2019, Hans de Goede wrote:
Cc+: ACPI/AMD folks
Various people are reporting false positive "do_IRQ: #.55 No irq handler for
vector"
messages on AMD ryzen based laptops, see e.g.:
On Thu, Feb 21, 2019 at 12:52:30PM +0100, Greg KH wrote:
> I would, but I do not see this patch in Linus's tree yet :)
You will soon :)
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
On Wed, Feb 20, 2019 at 8:01 AM Balakrishna Godavarthi
wrote:
>
>
> Hi,
>
> The following changes since commit
> 710963fe53ee3f227556d36839df3858daf6e232:
>
>Merge https://github.com/ajaykuee/linux-firmware (2019-02-13 07:42:20
> -0500)
>
> are available in the Git repository at:
>
>
In __hists__add_entry the srcline of the addr_location is duplicated
for the hist_entry. If hists__findnew_entry returns an already existing
hist_entry the srcline has to be freed again as no further reference to
that duplicated srcline would exists anymore.
Signed-off-by: Jonas Rabenstein
---
From: Lina Iyer
Controllers may be in 'solver' state, where they could be in autonomous
mode executing low power modes for their hardware and as such are not
available for sending active votes. Device driver may notify RPMH API
that the controller is in solver mode and when in such mode,
On Tue, Feb 19, 2019 at 3:30 AM Baolin Wang wrote:
> Use SoC compatible string instead of wildcard string.
>
> Reviewed-by: Rob Herring
> Signed-off-by: Baolin Wang
Patch applied.
Yours,
Linus Walleij
Resending the patches. Kindly review.
Changes in v3:
- Simplify TCS locking - added a new patch
- Add lock check to avoid potential race as suggested by Matthias
- Add functionality to RSC controller to disallow active requests
if solver mode is not set
- Removed independent patches and
On Thu, Feb 21, 2019 at 12:35:34PM +0100, Gerd Hoffmann wrote:
> Problem: qxl switches from native mode back into vga compatibility mode
> when it notices someone is accessing vga registers. And vgacon does
> exactly that before fbcon takes over. So make sure we kick out vgacon
> early enough
From: Lina Iyer
Allow the controller status be queried. The controller is busy if it is
actively processing request. Also allow the controller state be read by
platform drivers. This is useful for PM drivers which can choose to
disallow idle modes when the controller is busy.
Signed-off-by:
On Tue, Feb 19, 2019 at 3:30 AM Baolin Wang wrote:
> Change to use SoC compatible string instead of wildcard string.
>
> The Spreadtrum SC9860 platform device trees and drivers' development
> are still in progress, and now we will always recompile and ship
> device trees at the same time as we
tcs->lock was introduced to serialize access with in TCS group. But
even without tcs->lock, drv->lock is serving the same purpose. So
use single drv->lock.
Other optimizations include -
- Remove locking around clear_bit() in IRQ handler. clear_bit() is
atomic.
- Remove redundant read of TCS
Hi Vaishali,
Thank you for the patch.
On Wed, Feb 20, 2019 at 10:28:29AM +0530, Vaishali Thakkar wrote:
> The Qualcomm socinfo provides a number of additional attributes,
> add these to the socinfo driver and expose them via debugfs
> functionality.
What is the use case for these attributes ? I
On Wed, Feb 20, 2019 at 09:00:42AM -0700, Jason Gunthorpe wrote:
> On Wed, Feb 20, 2019 at 08:31:59AM +0200, Jarkko Sakkinen wrote:
> > On Wed, Feb 20, 2019 at 10:23:00AM +0800, YueHaibing wrote:
> > > calc_tpm2_event_size() has an invalid signature because
> > > it returns a 'size_t' where as its
On Tue, Feb 19, 2019 at 8:12 PM Bjorn Andersson
wrote:
> It's reasonable to expect that people turn to the "gpio" debugfs file to
> first and foremost learn about the direction and value of a gpio, and
> second to that about it's pinconf. So reorder the value so each line
> reads:
>
> gpioN:
On Thu, 21 Feb 2019 11:42:25 +0100
Harald Freudenberger wrote:
> On 30.01.19 19:32, Sebastian Ott wrote:
> > On Wed, 30 Jan 2019, Tony Krowiak wrote:
> >> /*
> >> +* A config change has happened, Force an ap bus rescan.
> >> +*/
> >> +void ap_bus_cfg_chg(void)
> >> +{
> >> +
On 20/02/2019 13:51, Halil Pasic wrote:
On Wed, 20 Feb 2019 10:27:31 +0100
Cornelia Huck wrote:
On Tue, 19 Feb 2019 22:31:17 +0100
Pierre Morel wrote:
On 19/02/2019 19:52, Tony Krowiak wrote:
On 2/18/19 1:08 PM, Pierre Morel wrote:
Libudev relies on having a subsystem link for non-root
801 - 900 of 1235 matches
Mail list logo
