3.16.74-rc1 review patch. If anyone has any objections, please let me know.
--
From: Liang Chen
commit a4b732a248d12cbdb46999daf0bf288c011335eb upstream.
There is a race between cache device register and cache set unregister.
For an already registered cache device,
3.16.74-rc1 review patch. If anyone has any objections, please let me know.
--
From: Hui Peng
commit daac07156b330b18eb5071aec4b3ddca1c377f2c upstream.
The `uac_mixer_unit_descriptor` shown as below is read from the
device side. In `parse_audio_mixer_unit`, `baSourceID` field
3.16.74-rc1 review patch. If anyone has any objections, please let me know.
--
From: Takashi Iwai
commit 89781d0806c2c4f29072d3f00cb2dd4274aabc3d upstream.
The recent change to shuffle the codec initialization procedure for
Realtek via commit 607ca3bd220f ("ALSA: hda/realtek
3.16.74-rc1 review patch. If anyone has any objections, please let me know.
--
From: Colin Ian King
commit a6d2a5a92e67d151c98886babdc86d530d27111c upstream.
Currently if alloc_skb fails to allocate the skb a null skb is passed to
t4_set_arp_err_handler and this ends up
3.16.74-rc1 review patch. If anyone has any objections, please let me know.
--
From: Andrew Vasquez
commit 5cbdae10bf11f96e30b4d14de7b08c8b490e903c upstream.
Commit e6f77540c067 ("scsi: qla2xxx: Fix an integer overflow in sysfs
code") incorrectly set 'optrom_region_size' to
3.16.74-rc1 review patch. If anyone has any objections, please let me know.
--
From: YueHaibing
commit 9ee8578d953023cc57e7e736ae48502c707c0210 upstream.
Since commit 1c459de1e645 ("ARM: pxa: ssp: use devm_ functions")
kfree, iounmap, clk_put etc are not needed anymore in
3.16.74-rc1 review patch. If anyone has any objections, please let me know.
--
From: Takashi Iwai
commit 328e9f6973be2ee67862cb17bf6c0c5c5918cd72 upstream.
The error from snd_usb_mixer_apply_create_quirk() is ignored in the
current usb-audio driver code, which will continue
3.16.74-rc1 review patch. If anyone has any objections, please let me know.
--
From: Tetsuo Handa
commit c03a0fd0b609e2f5c669c2b7f27c8e1928e9196e upstream.
syzbot is hitting use-after-free bug in uinput module [1]. This is because
kobject_uevent(KOBJ_REMOVE) is called again
3.16.74-rc1 review patch. If anyone has any objections, please let me know.
--
From: Christoph Vogtländer
commit b00ef53053191d3025c15e8041699f8c9d132daf upstream.
It must be made sure that immediate mode is not already set, when
modifying shadow register value in
Thanks for your patent review
--
Cheers,
Justin (Jia He)
> -Original Message-
> From: Kirill A. Shutemov
> Sent: 2019年9月20日 22:21
> To: Justin He (Arm Technology China)
> Cc: Catalin Marinas ; Will Deacon
> ; Mark Rutland ; James Morse
> ; Marc Zyngier ; Matthew
> Wilcox ; Kirill
On 9/19/19 6:34 AM, Halil Pasic wrote:
On Fri, 13 Sep 2019 17:26:52 -0400
Tony Krowiak wrote:
+static void vfio_ap_mdev_get_crycb_matrix(struct ap_matrix_mdev *matrix_mdev)
+{
+ unsigned long apid, apqi;
+ unsigned long masksz = BITS_TO_LONGS(AP_DEVICES) *
+
3.16.74-rc1 review patch. If anyone has any objections, please let me know.
--
From: Stuart Menefy
commit b7ed69d67ff0788d8463e599dd5dd1b45c701a7e upstream.
Fix the interrupt information for the GPIO lines with a shared EINT
interrupt.
Fixes: 16d7ff2642e7 ("ARM: dts: add dts
On Fri, Sep 20, 2019 at 02:54:26PM +0100, Jon Hunter wrote:
>
> On 19/09/2019 23:03, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 5.3.1 release.
> > There are 21 patches in this series, all will be posted as a response
> > to this one. If anyone has any
3.16.74-rc1 review patch. If anyone has any objections, please let me know.
--
From: Geert Uytterhoeven
commit 26843bb128590edd7eba1ad7ce22e4b9f1066ce3 upstream.
While the sequencer is reset after each SPI message since commit
880c6d114fd79a69 ("spi: rspi: Add support for
* Colin King [190920 12:21]:
> From: Colin Ian King
>
> The call to pinctrl_count_index_with_args checks for a -EINVAL return
> however this function calls pinctrl_get_list_and_count and this can
> return -ENOENT. Rather than check for a specific error, fix this by
> checking for any error
* H. Nikolaus Schaller [190920 09:19]:
> > Am 20.09.2019 um 10:55 schrieb Linus Walleij :
> > I suggest to go both way:
> > apply this oneliner and tag for stable so that GTA04 works
> > again.
> >
> > Then for the next kernel think about a possible more abitious
> > whitelist solution and after
On Fri, Sep 20, 2019 at 09:54:37PM +0800, Jia He wrote:
> When we tested pmdk unit test [1] vmmalloc_fork TEST1 in arm64 guest, there
> will be a double page fault in __copy_from_user_inatomic of cow_user_page.
>
> Below call trace is from arm64 do_page_fault for debugging purpose
> [
Attn:
This message is strictly for this mail ID owner.
My name is Curt Launer an Engineer and lives in Toronto, Canada.
When I was working with Australian Worldwide Exploration (AWE) Sydney,
Australia my company sent me to Brega Libya during Ghaddafi time.
We did the exploration and our
On 20.09.2019 16:21, Kirill A. Shutemov wrote:
> On Fri, Sep 20, 2019 at 03:29:07PM +0300, Cyrill Gorcunov wrote:
>> Currently there is a small gap between fetching pointer, calling
>> kvfree and assign its value to nil. In current callgraph it is
>> not a problem (since memcg_free_shrinker_maps
Hi all,
We would like to share a new data-race detector for the Linux kernel:
Kernel Concurrency Sanitizer (KCSAN) --
https://github.com/google/ktsan/wiki/KCSAN (Details:
https://github.com/google/ktsan/blob/kcsan/Documentation/dev-tools/kcsan.rst)
To those of you who we mentioned at LPC that
On 2019/9/20 20:54, Al Viro wrote:
> On Fri, Sep 20, 2019 at 01:45:33PM +0100, Al Viro wrote:
>> On Fri, Sep 20, 2019 at 08:21:53PM +0800, Xiaoming Ni wrote:
>>>
>>>
>>> On 2019/9/20 19:43, Al Viro wrote:
On Fri, Sep 20, 2019 at 02:54:38PM +0800, Xiaoming Ni wrote:
> Use kzalloc() to
On 20.09.2019 15:29, Cyrill Gorcunov wrote:
> Currently there is a small gap between fetching pointer, calling
> kvfree and assign its value to nil. In current callgraph it is
> not a problem (since memcg_free_shrinker_maps is running from
> memcg_alloc_shrinker_maps and mem_cgroup_css_free only)
The linux-next commit "libnvdimm/dax: Pick the right alignment default when
creating dax devices" causes powerpc failed to build with this config. Reverted
it fixed the issue.
ERROR: "hash__has_transparent_hugepage" [drivers/nvdimm/libnvdimm.ko] undefined!
ERROR: "radix__has_transparent_hugepage"
Hi Linus,
Normally soundwire updates go thru Greg (char) but this time around I
missed the bus to send him due to some stuff.
So with Greg's blessing here is the pull request for soundwire
subsystem. Please pull to receive these updates.
The following changes since commit
On Fri, Sep 20, 2019 at 03:37:08PM +0200, Rafał Miłecki wrote:
> Hardware or firmware instability may result in unusable wiphy. In such
> cases usually a hardware reset is needed. To allow a full recovery
> kernel has to indicate problem to the user space.
Why? Shouldn't the driver be able to
> From: Colin Ian King
>
> Currently the zero check on val to break out of a loop
> is a little obscure. Replace the val is zero and break check
> with a loop while value is non-zero.
>
> Signed-off-by: Colin Ian King
> ---
> drivers/net/wireless/mediatek/mt7601u/phy.c | 4 +---
> 1 file
Hi,
On 9/19/19 9:46 AM, Pavel Machek wrote:
On Wed 2019-09-18 08:18:59, Greg Kroah-Hartman wrote:
From: Hans de Goede
commit 61f7f7c8f978b1c0d80e43c83b7d110ca0496eb4 upstream.
Another day; another DSDT bug we need to workaround...
Since commit ca876c7483b6 ("gpiolib-acpi: make sure we
When we tested pmdk unit test vmmalloc_fork TEST1 in arm64 guest, there
will be a double page fault in __copy_from_user_inatomic of cow_user_page.
As told by Catalin: "On arm64 without hardware Access Flag, copying from
user will fail because the pte is old and cannot be marked young. So we
When we tested pmdk unit test [1] vmmalloc_fork TEST1 in arm64 guest, there
will be a double page fault in __copy_from_user_inatomic of cow_user_page.
Below call trace is from arm64 do_page_fault for debugging purpose
[ 110.016195] Call trace:
[ 110.016826] do_page_fault+0x5a4/0x690
[
We unconditionally set the HW_AFDBM capability and only enable it on
CPUs which really have the feature. But sometimes we need to know
whether this cpu has the capability of HW AF. So decouple AF from
DBM by new helper cpu_has_hw_af().
Reported-by: kbuild test robot
Suggested-by: Suzuki Poulose
On arm64 without hardware Access Flag, copying fromuser will fail because
the pte is old and cannot be marked young. So we always end up with zeroed
page after fork() + CoW for pfn mappings. we don't always have a
hardware-managed access flag on arm64.
Hence implement arch_faults_on_old_pte on
On 19/09/2019 23:03, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.3.1 release.
> There are 21 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses
From: Ricardo Ribalda Delgado
New control to pass to userspace the width/height of a pixel. Which is
needed for calibration and lens selection.
Reviewed-by: Philipp Zabel
Signed-off-by: Ricardo Ribalda Delgado
---
Documentation/media/uapi/v4l/ext-ctrls-image-source.rst | 9 +
1 file
From: Ricardo Ribalda Delgado
This control returns the unit cell size in nanometres. The struct provides
the width and the height in separated fields to take into consideration
asymmetric pixels and/or hardware binning.
This control is required for automatic calibration of sensors/cameras.
This type contains the width and the height of a rectangular area.
Signed-off-by: Ricardo Ribalda Delgado
---
drivers/media/v4l2-core/v4l2-ctrls.c | 21 ++
include/media/v4l2-ctrls.h | 41
include/uapi/linux/videodev2.h | 6
3 files
UNIT_CELL_SIZE is a control that represents the size of a cell (pixel).
We required a bit of boilerplate to add this control :)
- New way to init compount controls
- New control type
Thanks to Hans, Jacopo and Philipp for your help.
You might want to see the series at my github repository if
Currently compound controls do not have a simple way of initializing its
values. This results in ofuscated code with type_ops init.
This patch introduces a new field on the control with the default value
for the compound control that can be set with the brand new
v4l2_ctrl_new_std_compound
Function for initializing compound controls with a default value.
Suggested-by: Hans Verkuil
Signed-off-by: Ricardo Ribalda Delgado
---
Documentation/media/kapi/v4l2-controls.rst | 9 +
1 file changed, 9 insertions(+)
diff --git a/Documentation/media/kapi/v4l2-controls.rst
From: Ricardo Ribalda Delgado
A struct v4l2_area containing the width and the height of a rectangular
area.
Reviewed-by: Philipp Zabel
Signed-off-by: Ricardo Ribalda Delgado
---
Documentation/media/uapi/v4l/vidioc-queryctrl.rst | 6 ++
1 file changed, 6 insertions(+)
diff --git
From: Ricardo Ribalda Delgado
According to the product brief, the unit cell size is 1120 nanometers^2.
https://www.sony-semicon.co.jp/products_en/IS/sensor1/img/products/ProductBrief_IMX214_20150428.pdf
Signed-off-by: Ricardo Ribalda Delgado
---
drivers/media/i2c/imx214.c | 12
On Fri, Sep 20, 2019 at 3:49 PM syzbot
wrote:
>
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:e0bd8d79 usb-fuzzer: main usb gadget fuzzer driver
> git tree: https://github.com/google/kasan.git usb-fuzzer
> console output:
On Fri, Sep 20, 2019 at 10:21:23AM +0200, Dmitry Vyukov wrote:
> On Fri, Sep 20, 2019 at 10:03 AM Dmitry Vyukov wrote:
> >
> > On Fri, Sep 20, 2019 at 9:54 AM Dmitry Vyukov wrote:
> > > > On Thu, Sep 19, 2019 at 10:12 PM Paul E. McKenney
> > > > wrote:
> > > > >
> > > > > On Thu, Sep 19, 2019
Hello,
syzbot found the following crash on:
HEAD commit:e0bd8d79 usb-fuzzer: main usb gadget fuzzer driver
git tree: https://github.com/google/kasan.git usb-fuzzer
console output: https://syzkaller.appspot.com/x/log.txt?x=17cb825560
kernel config:
On 19/09/2019 23:03, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.14.146 release.
> There are 59 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses
Convert the Arm SMMU binding to DT schema.
The existing binding doc doesn't cover the number of variations of
compatible properties found in .dts files. "qcom,msm8998-smmu-v2" was
also missing, so add it.
SoCFPGA Stratix10 has a single clock defined which doesn't match the
binding. This issue
On 19/09/2019 23:01, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.2.17 release.
> There are 124 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses
On 19/09/2019 23:02, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.19.75 release.
> There are 79 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses
On 19/09/2019 23:03, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.9.194 release.
> There are 74 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses
On 19/09/2019 23:03, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.4.194 release.
> There are 56 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses
Hi,
On Wed, Sep 18, 2019 at 04:57:58PM -0700, Linus Torvalds wrote:
> On Wed, Sep 18, 2019 at 2:17 PM Ahmed S. Darwish wrote:
> >
> > Since Linux v3.17, getrandom(2) has been created as a new and more
> > secure interface for pseudorandom data requests. It attempted to
> > solve three problems,
On 9/19/19 3:03 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 5.3.1 release.
There are 21 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made
On 9/19/19 3:01 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 5.2.17 release.
There are 124 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made
On 20/09/2019 14:18, Qian Cai wrote:
On Fri, 2019-09-20 at 19:24 +0900, Masahiro Yamada wrote:
Hi Qian,
On Thu, Sep 19, 2019 at 10:06 PM Qian Cai wrote:
The commit 5489c8e0cf03 ("arm64: use asm-generic/dma-mapping.h") introduced a
kbuild warning,
scripts/Makefile.asm-generic:25: redundant
On Tue, Sep 17, 2019 at 10:42:01PM +0100, Russell King - ARM Linux admin wrote:
> On Tue, Sep 17, 2019 at 06:19:13PM +0100, Russell King - ARM Linux admin
> wrote:
> > whether you can get the link to come up at all. You might need to see
> > whether wiggling the RJ45 helps (I've had that sort of
On Fri, Sep 20, 2019 at 12:03:13AM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.9.194 release.
> There are 74 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me
On Fri, Sep 20, 2019 at 12:03:41AM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.4.194 release.
> There are 56 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me
On Fri, Sep 20, 2019 at 04:21:14PM +0300, Kirill A. Shutemov wrote:
> On Fri, Sep 20, 2019 at 03:29:07PM +0300, Cyrill Gorcunov wrote:
> > Currently there is a small gap between fetching pointer, calling
> > kvfree and assign its value to nil. In current callgraph it is
> > not a problem (since
On Wed, Sep 18, 2019 at 11:30 AM Markus Elfring wrote:
> From: Markus Elfring
> Date: Wed, 18 Sep 2019 11:20:48 +0200
>
> Simplify these function implementations by using a known wrapper function.
>
> This issue was detected by using the Coccinelle software.
>
> Signed-off-by: Markus Elfring
From: Rafał Miłecki
Hardware or firmware instability may result in unusable wiphy. In such
cases usually a hardware reset is needed. To allow a full recovery
kernel has to indicate problem to the user space.
This new nl80211 command lets user space known wiphy has crashed and has
been just
Hi Linus,
We've had a few arm64 fixes trickle in this week, so please can you pick
them up for -rc1? Nothing catastophic, but all things that should be
addressed.
Cheers,
Will
--->8
The following changes since commit e376897f424a1c807779a2635f62eb02d7e382f9:
arm64: remove __iounmap
On Fri, Sep 20, 2019 at 09:50:23AM +0200, Dmitry Vyukov wrote:
> On Thu, Sep 19, 2019 at 10:12 PM Paul E. McKenney wrote:
> >
> > On Thu, Sep 19, 2019 at 07:39:03PM +0200, Dmitry Vyukov wrote:
> > > On Thu, Sep 19, 2019 at 7:07 PM Paul E. McKenney
> > > wrote:
> > > >
> > > > On Wed, Sep 18,
Suleiman Souhlal writes:
> When CONFIG_KVMCLOCK_HOST_TIMEKEEPING is enabled, and the host
> supports it, update our timekeeping parameters to be the same as
> the host. This lets us have our time synchronized with the host's,
> even in the presence of host NTP or suspend.
>
> When enabled,
According to Tal Gilboa the only benefit from DIM comes from a driver
that uses it. So it doesn't make sense to make this symbol user visible,
instead all drivers that use it should select it (as is already the case
AFAICT).
Signed-off-by: Uwe Kleine-König
---
lib/Kconfig | 3 +--
1 file
On Tue, Sep 17, 2019 at 3:26 PM Paul Walmsley wrote:
>
>
> Just tested this on the SiFive HiFive Unleashed. Seems to work OK;
> however I did not stress-test it.
>
> Tested-by: Paul Walmsley # HiFive Unleashed
>
>
> - Paul
>
>
> # !cat
> cat /proc/interrupts
>CPU0 CPU1
[+cc Rafael]
On Fri, Sep 20, 2019 at 01:23:20PM +0200, Kai-Heng Feng wrote:
> On Mon, Sep 9, 2019 at 1:41 PM Bjorn Helgaas wrote:
> > > +bool pci_pr3_present(struct pci_dev *pdev)
> > > +{
> > > + struct pci_dev *parent_pdev = pci_upstream_bridge(pdev);
> > > + struct acpi_device
On 20/09/2019 13:54, Colin King wrote:
From: Colin Ian King
Currently the zero check on val to break out of a loop
is a little obscure. Replace the val is zero and break check
with a loop while value is non-zero.
Signed-off-by: Colin Ian King
---
On Fri, 20 Sep 2019 14:25:37 +0800
Kefeng Wang wrote:
> As said in commit f2c2cbcc35d4 ("powerpc: Use pr_warn instead of
> pr_warning"), removing pr_warning so all logging messages use a
> consistent _warn style. Let's do it.
Acked-by: Steven Rostedt (VMware)
-- Steve
>
> Cc: Steven Rostedt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi Linus,
Please pull powerpc updates for 5.4.
This is a bit late, partly due to me travelling, and partly due to a power
outage knocking out some of my test systems *while* I was travelling.
A few conflicts this time unfortunately. The key one
On Fri, Sep 20, 2019 at 03:29:07PM +0300, Cyrill Gorcunov wrote:
> Currently there is a small gap between fetching pointer, calling
> kvfree and assign its value to nil. In current callgraph it is
> not a problem (since memcg_free_shrinker_maps is running from
> memcg_alloc_shrinker_maps and
While touching seccomp code I realized that the struct seccomp_data
argument to secure_computing() seems to be unused by all current
callers. So let's remove it unless there is some subtlety I missed.
Note, I only tested this on x86.
Signed-off-by: Christian Brauner
Cc: Andy Lutomirski
Cc:
On Fri, 2019-09-20 at 19:24 +0900, Masahiro Yamada wrote:
> Hi Qian,
>
> On Thu, Sep 19, 2019 at 10:06 PM Qian Cai wrote:
> >
> > The commit 5489c8e0cf03 ("arm64: use asm-generic/dma-mapping.h") introduced
> > a
> > kbuild warning,
> >
> > scripts/Makefile.asm-generic:25: redundant generic-y
On Fri, Sep 20, 2019 at 03:23:58AM +0500, Alexander E. Patrakov wrote:
> OTOH, I thought that at least part of the real entropy, if it exists, comes
> from the interference of the CPU's memory accesses with the refresh cycles
> that are clocked from an independent oscillator.
That's not a valid
On Thu, Sep 19, 2019 at 08:50:15AM -0700, Linus Torvalds wrote:
> .. btw, instead of bad workarounds for a theoretical attack, here's
> something that should add actual *practical* real value: use the time
> of day (whether from an RTC device, or from ntp) to add noise to the
> random pool.
On Thu, Sep 19, 2019 at 08:20:57AM -0700, Linus Torvalds wrote:
> And unlike your theoretical state extension attack, I can point you to
> black hat presentations that literally talk about using the fact that
> we delay m,ixing in the input pull hash to know what's going on:
>
>
>
Since the commit ba2dd8a26baa ("powerpc/pseries/mm: call H_BLOCK_REMOVE"),
the call to H_BLOCK_REMOVE is always done if the feature is exhibited.
However, the hypervisor may not support all the block size for the hcall
H_BLOCK_REMOVE depending on the segment base page size and actual page
size.
Depending on the hardware and the hypervisor, the hcall H_BLOCK_REMOVE may
not be able to process all the page sizes for a segment base page size, as
reported by the TLB Invalidate Characteristics.
For each pair of base segment page size and actual page size, this
characteristic tells us the size
The PAPR document specifies the TLB Block Invalidate Characteristics which
tells for each pair of segment base page size, actual page size, the size
of the block the hcall H_BLOCK_REMOVE supports.
These characteristics are loaded at boot time in a new table hblkr_size.
The table is separate from
Hi,
Can this patch be accepted?
Thanks
Jin Yao
On 9/3/2019 10:03 AM, Jin Yao wrote:
This patch prints the stddev and hist for the cycles diff of
program block. It can help us to understand if the cycles
is noisy or not.
This patch is inspired by Andi Kleen's patch
On Fri, Sep 20, 2019 at 01:45:33PM +0100, Al Viro wrote:
> On Fri, Sep 20, 2019 at 08:21:53PM +0800, Xiaoming Ni wrote:
> >
> >
> > On 2019/9/20 19:43, Al Viro wrote:
> > > On Fri, Sep 20, 2019 at 02:54:38PM +0800, Xiaoming Ni wrote:
> > >> Use kzalloc() to allocate memory in jffs2_fill_super().
From: Colin Ian King
Currently the zero check on val to break out of a loop
is a little obscure. Replace the val is zero and break check
with a loop while value is non-zero.
Signed-off-by: Colin Ian King
---
drivers/net/wireless/mediatek/mt7601u/phy.c | 4 +---
1 file changed, 1
On 9/18/19 4:52 PM, Qais Yousef wrote:
> On 09/13/19 14:30, Dietmar Eggemann wrote:
>> On 9/4/19 4:40 PM, Qais Yousef wrote:
>>> On 09/04/19 07:25, Steven Rostedt wrote:
On Tue, 3 Sep 2019 11:33:29 +0100
Qais Yousef wrote:
[...]
>> On a big.LITTLE system (6 CPUs with [446 1024 1024
From: Markus Elfring
Date: Fri, 20 Sep 2019 14:44:06 +0200
Simplify this function implementation by using a known wrapper function.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
---
v2:
Jacek Anaszewski requested to split updates for two modules
Hi all,
Today's linux-next merge of the thermal tree got conflicts in:
Documentation/driver-api/thermal/index.rst
Documentation/driver-api/thermal/sysfs-api.rst
Documentation/driver-api/thermal/x86_pkg_temperature_thermal.rst
between commit:
eaf7b46083a7e34 ("docs: thermal: add it to
On Fri, Sep 20, 2019 at 08:21:53PM +0800, Xiaoming Ni wrote:
>
>
> On 2019/9/20 19:43, Al Viro wrote:
> > On Fri, Sep 20, 2019 at 02:54:38PM +0800, Xiaoming Ni wrote:
> >> Use kzalloc() to allocate memory in jffs2_fill_super().
> >> Freeing memory when jffs2_parse_options() fails will cause
> >>
On Fri, Sep 20, 2019 at 02:33:13PM +0200, Marek Szyprowski wrote:
> Hi Krzysztof,
>
>> +examples:
> >> + - |
> >> +#include
> > Does it really work? When I tried, it was failing... If you look up at
> > resulting DTS example it is wrong.
>
> In which way it was wrong? We checked and it
From: Markus Elfring
Date: Fri, 20 Sep 2019 14:30:31 +0200
Simplify this function implementation by using a known wrapper function.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
---
v2:
Jacek Anaszewski requested to split updates for two modules
Hi Krzysztof,
On 20.09.2019 14:26, Krzysztof Kozlowski wrote:
> On Fri, Sep 20, 2019 at 01:35:40PM +0200, Marek Szyprowski wrote:
>> From: Maciej Falkowski
>>
>> Convert Samsung I2S controller to newer dt-schema format.
>>
>> Signed-off-by: Maciej Falkowski
>> Signed-off-by: Marek Szyprowski
Hi Jacek,
On 18/07/2019 19:49, Jacek Anaszewski wrote:
On 7/18/19 3:31 PM, Jean-Jacques Hiblot wrote:
On 18/07/2019 14:24, Jacek Anaszewski wrote:
Hi Jean,
Thank you for the updated patch set.
I have some more comments below.
On 7/17/19 3:59 PM, Jean-Jacques Hiblot wrote:
+static bool
Currently there is a small gap between fetching pointer, calling
kvfree and assign its value to nil. In current callgraph it is
not a problem (since memcg_free_shrinker_maps is running from
memcg_alloc_shrinker_maps and mem_cgroup_css_free only) still
this looks suspicious and we can easily
On Fri, Sep 20, 2019 at 02:14:30PM +0200, Marek Szyprowski wrote:
> From: Maciej Falkowski
>
> Change representation of phandle array as then
> dt-schema counts number of its items properly.
>
> Signed-off-by: Maciej Falkowski
> Signed-off-by: Marek Szyprowski
> ---
>
On 9/20/19 13:35, Marek Szyprowski wrote:
> From: Maciej Falkowski
>
> Convert Samsung I2S controller to newer dt-schema format.
> .../devicetree/bindings/sound/samsung-i2s.txt | 84 ---
> .../bindings/sound/samsung-i2s.yaml | 135 ++
> 2 files changed, 135
Jacek
On 9/19/19 4:32 PM, Jacek Anaszewski wrote:
Dan,
On 9/19/19 3:07 AM, Dan Murphy wrote:
Jacek
On 9/18/19 4:27 PM, Jacek Anaszewski wrote:
Hi Dan,
I think Greg's guidance clarified everything nicely -
we will avoid sub-dirs in favour of prefixes
to *intensity and *max_intensity.
Yes
Most of the LEDs are powered by a voltage/current regulator. Describing it
in the device-tree makes it possible for the LED core to enable/disable it
when needed.
Signed-off-by: Jean-Jacques Hiblot
---
Documentation/devicetree/bindings/leds/common.txt | 6 ++
1 file changed, 6 insertions(+)
This series makes it possible for the LED core to manage the power supply
of a LED. It uses the regulator API to disable/enable the power if when the
LED is turned on/off.
This is especially useful in situations where the LED driver/controller is
not supplying the power.
Because updating a
A LED is usually powered by a voltage/current regulator. Let the LED core
know about it. This allows the LED core to turn on or off the power supply
as needed.
Signed-off-by: Jean-Jacques Hiblot
---
drivers/leds/led-class.c | 17 +++
drivers/leds/led-core.c | 65
Making led_set_brightness_sync() use led_set_brightness_nosleep() has 2
advantages:
- works for LED controllers that do not provide brightness_set_blocking()
- When the blocking callback is used, it uses the workqueue to update the
LED state, removing the need for mutual exclusion between
On Fri, Sep 20, 2019 at 01:35:40PM +0200, Marek Szyprowski wrote:
> From: Maciej Falkowski
>
> Convert Samsung I2S controller to newer dt-schema format.
>
> Signed-off-by: Maciej Falkowski
> Signed-off-by: Marek Szyprowski
> ---
> v3:
> - Removed quotation marks from strings in compatible
On 2019/9/20 19:43, Al Viro wrote:
> On Fri, Sep 20, 2019 at 02:54:38PM +0800, Xiaoming Ni wrote:
>> Use kzalloc() to allocate memory in jffs2_fill_super().
>> Freeing memory when jffs2_parse_options() fails will cause
>> use-after-free and double-free in jffs2_kill_sb()
>
> ... so we are not
From: Colin Ian King
The call to pinctrl_count_index_with_args checks for a -EINVAL return
however this function calls pinctrl_get_list_and_count and this can
return -ENOENT. Rather than check for a specific error, fix this by
checking for any error return to catch the -ENOENT case.
On Thu, Sep 19, 2019 at 05:03:18PM +0200, Thomas Gleixner wrote:
> #ifdef CONFIG_ARM64_ERRATUM_1463225
> @@ -97,19 +97,16 @@ static void el0_svc_common(struct pt_reg
>
> regs->orig_x0 = regs->regs[0];
> regs->syscallno = scno;
> + /* Set default error number */
> +
601 - 700 of 924 matches
Mail list logo
