From: Yinbo Zhu
Add "fsl,ls1028a-esdhc" bindings for ls1028a eSDHC host controller
Signed-off-by: Yinbo Zhu
---
Change in v2:
as alphabetical order to update dt-bindings
update the commit information.
Documentation/devicetree/bindings/mmc/fsl-esdhc.txt | 1 +
FYI, we noticed the following commit (built with gcc-7):
commit: dea079527088cffccd014c815ecaf5b0f0506c59 ("[[repost]RFC PATCH]
mm/workingset : judge file page activity via timestamp")
url:
This syscall allows easy fileless execution, without calling chmod() first.
Thus, some security-related restrictions (like seccomp filters that deny
chmod +x) can by bypassed using memfd_create() if the policy author is
unaware of this.
Signed-off-by: Dima Krasner
Cc: linux...@kvack.org
Cc: Hugh
My name is Gavin. I want to get to know you better, if I may be so bold. I
consider myself an honest man, and I am currently looking for a relationship in
which I feel loved. Please tell me more about yourself, if you don't mind.
Gavin.
Use __maybe_unused for runtime PM related functions instead
of #if CONFIG_PM to simply the code.
Signed-off-by: Anson Huang
---
drivers/i2c/busses/i2c-imx.c | 11 +++
1 file changed, 3 insertions(+), 8 deletions(-)
diff --git a/drivers/i2c/busses/i2c-imx.c
On 5/4/19 8:05 PM, Dan Rue wrote:
On Sat, May 04, 2019 at 12:24:45PM +0200, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 5.0.13 release.
There are 32 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these
On Sat, May 04, 2019 at 12:24:45PM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.0.13 release.
> There are 32 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
BUG: KASAN: use-after-free in __list_add_valid+0xd4/0xe0 lib/list_debug.c:26
Read of size 8 at addr 8881ef61ae20 by task syz-executor.0/5996
CPU: 1 PID: 5996 Comm: syz-executor.0 Tainted: G C5.0.0+ #5
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1
On Sat, May 04, 2019 at 12:25:02PM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.19.40 release.
> There are 23 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 Mon, Apr 29, 2019 at 07:31:43PM +0200, Enrico Weigelt, metux IT consult
wrote:
Argh. Sorry, it seems your emails aren't making it into my inbox, only
my once-in-a-long-while-checked lkml folder. Sorry again.
> On 29.04.19 17:49, Serge E. Hallyn wrote:
>
> >> * all users are equal - no
Hi folks,
We observed deadlocks after enabling GICv4 and PCI passthrough on ARM64 virtual
machines, when not pinning VCPU to physical CPU.
We observed below warnings after enabling lockdep debug in kernel:
[ 362.847021] =
[ 362.855643]
A couple of ->i_link use-after-free fixes, regression fix for
wrong errno on absent device name in mount(2) (this cycle stuff) +
ancient UFS braino in large GID handling on Solaris UFS images (bogus
cut'n'paste from large UID handling; wrong field checked to decide
whether we should look
i.MX system controller watchdog can support pretimeout IRQ
via general SCU MU IRQ, it depends on IMX_SCU and driver MUST
be probed after SCU IPC ready, then enable corresponding SCU
IRQ group and register SCU IRQ notifier, when watchdog pretimeout
IRQ fires, SCU MU IRQ will be handled and watchdog
i.MX system controller watchdog has pretimeout function which
depends on i.MX SCU driver, so it should be a subnode of SCU.
Signed-off-by: Anson Huang
---
No change.
---
arch/arm64/boot/dts/freescale/imx8qxp.dtsi | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git
i.MX system controller watchdog depends on SCU driver to support
interrupt function, so it needs to be subnode of SCU node in DT,
binding doc should be moved to fsl,scu.txt as well.
Signed-off-by: Anson Huang
---
Changes since V2:
- no content change, just merge two dt-binding patches
Hi Suzuki,
On Fri, May 03, 2019 at 04:11:50PM +0100, Suzuki K Poulose wrote:
[...]
> Given that we now warn about OBSOLETE bindings, please could you fix
> the existing DTS in the kernel source tree to use the new binding ?
> Similarly for the replicator.
Yeah, will do. Thanks for reminding.
I am in the military unit here in Afghanistan, we have some amount of funds
that we want to move out of the country. My partners and I need a good partner
someone we can trust. It is risk free and legal. Reply to this email:
hornbeckmajordennis...@gmail.com
Regards,
Major Dennis Hornbeck.
On 5/4/19 3:24 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 5.0.13 release.
There are 32 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
CCing Oleg.
On Fri 03-05-19 22:28:00, Alexey Dobriyan wrote:
[...]
> add/remove: 0/0 grow/shrink: 8/68 up/down: 49/-1147 (-1098)
[...]
> --- a/include/linux/sched/signal.h
> +++ b/include/linux/sched/signal.h
> @@ -15,10 +15,10 @@
> */
>
> struct sighand_struct {
> - refcount_t
On 5/4/19 3:25 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.19.40 release.
There are 23 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
From: Omer Shpigelman
This patch fix a potential bug where a user's process has closed
unexpectedly without disabling the debug engines. In that case, the debug
engines might continue running but because the user's MMU mappings are
going away, we will get page fault errors.
This behavior is
This patch defines a new opcode in the DEBUG IOCTL that is used by the
user to notify the driver when the user wants to start or stop using the
debug and profile infrastructure of the device. i.e. set the device to
debug mode or to non-debug mode.
There are a couple of restrictions that this new
When a multi-descriptor DMA transfer is in progress, the "IRQ pending"
flag will apparently be set for that channel as soon as the last
descriptor loads, way before the IRQ actually happens. This behaviour
has been observed on the JZ4725B, but maybe other SoCs are affected.
In the case where
Use SPDX license notifier instead of plain text in the header.
Signed-off-by: Paul Cercueil
---
drivers/dma/dma-jz4780.c | 6 +-
1 file changed, 1 insertion(+), 5 deletions(-)
diff --git a/drivers/dma/dma-jz4780.c b/drivers/dma/dma-jz4780.c
index 9ce0a386225b..02075417c69f 100644
---
On Sat, May 4, 2019 at 1:12 PM Andy Lutomirski wrote:
>
> As an aside, is it even *possible* to get #BP from v8086 mode? On a quick
> SDM read, the INT3 instruction causes #GP if VM=1 and IOPL<3. And, if we
> allow vm86() to have IOPL=3, we should just remove that ability. It’s nuts.
Oh, and
On Sat, May 4, 2019 at 1:12 PM Andy Lutomirski wrote:
>
> As an aside, is it even *possible* to get #BP from v8086 mode? On a quick
> SDM read, the INT3 instruction causes #GP if VM=1 and IOPL<3. And, if we
> allow vm86() to have IOPL=3, we should just remove that ability. It’s nuts.
We've
> On May 4, 2019, at 11:59 AM, Linus Torvalds
> wrote:
>
> On Fri, May 3, 2019 at 10:08 PM Linus Torvalds
> wrote:
>>
>> I'll look at it tomorrow, but I think this actually makes unnecessary
>> changes.
>>
>> In particular, I think we could keep the existing entry code almost
>>
> @@ -5828,8 +5822,6 @@ void survey_timer_hdl(struct timer_list *t)
>
>
> exit_survey_timer_hdl:
> -
> - return;
> }
Are you sure that you compiled this code? I'm not sure that it is possible
to have a label without a subsequent statement.
julia
On Fri, May 3, 2019 at 10:08 PM Linus Torvalds
wrote:
>
> I'll look at it tomorrow, but I think this actually makes unnecessary changes.
>
> In particular, I think we could keep the existing entry code almost unchanged
> with this whole approach.
So here's what I *think* should work. Note that
Moved logical operator to previous line to get rid of checkpatch
warning.
Signed-off-by: Vatsala Narang
---
drivers/staging/rtl8723bs/core/rtw_mlme_ext.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/staging/rtl8723bs/core/rtw_mlme_ext.c
From: Igor Konopko
Currently L2P map size is calculated based on the total number of
available sectors, which is redundant, since it contains mapping for
overprovisioning as well (11% by default).
Change this size to the real capacity and thus reduce the memory
footprint significantly - with
Remove braces from single if statement to get rid of checkpatch warning.
Signed-off-by: Vatsala Narang
---
drivers/staging/rtl8723bs/core/rtw_mlme_ext.c | 12
1 file changed, 4 insertions(+), 8 deletions(-)
diff --git a/drivers/staging/rtl8723bs/core/rtw_mlme_ext.c
Swap the terms of comparisons whenever the constant comes first to get
rid of checkpatch warning.
Signed-off-by: Vatsala Narang
---
drivers/staging/rtl8723bs/core/rtw_mlme_ext.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/rtl8723bs/core/rtw_mlme_ext.c
Remove unnecessary parentheses after 'address-of' operator to get rid of
checkpatch warning.
Signed-off-by: Vatsala Narang
---
drivers/staging/rtl8723bs/core/rtw_mlme_ext.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git
stable-rc/linux-4.19.y boot: 128 boots: 0 failed, 123 passed with 4 offline, 1
untried/unknown (v4.19.39-24-gb0d6421bd855)
Full Boot Summary:
https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.19.y/kernel/v4.19.39-24-gb0d6421bd855/
Full Build Summary:
Replace NULL comparisons in the file to get rid of checkpatch warning.
Signed-off-by: Vatsala Narang
---
drivers/staging/rtl8723bs/core/rtw_mlme_ext.c | 32 +--
1 file changed, 16 insertions(+), 16 deletions(-)
diff --git a/drivers/staging/rtl8723bs/core/rtw_mlme_ext.c
To avoid style issues, remove multiple blank lines.
Signed-off-by: Vatsala Narang
---
drivers/staging/rtl8723bs/core/rtw_mlme_ext.c | 5 -
1 file changed, 5 deletions(-)
diff --git a/drivers/staging/rtl8723bs/core/rtw_mlme_ext.c
b/drivers/staging/rtl8723bs/core/rtw_mlme_ext.c
index
From: Igor Konopko
A line is left unsigned to the blocks lists in case pblk_gc_line
returns an error.
This moves the line back to be appropriate list, which can then be
picked up by the garbage collector.
Signed-off-by: Igor Konopko
Reviewed-by: Hans Holmberg
Reviewed-by: Javier González
From: Igor Konopko
Currently all the target instances are removed under global nvm_lock.
This was needed to ensure that nvm_dev struct will not be freed by
hot unplug event during target removal. However, current implementation
has some drawbacks, since the same lock is used when new nvme
Remove return in void function to get rid of checkpatch warning.
Signed-off-by: Vatsala Narang
---
drivers/staging/rtl8723bs/core/rtw_mlme_ext.c | 10 --
1 file changed, 10 deletions(-)
diff --git a/drivers/staging/rtl8723bs/core/rtw_mlme_ext.c
This series fix the following warnings:
-Remove multiple blank lines.
-Remove return in void function.
-Replace NULL comparison.
-Remove unnecessary parentheses.
-Remove braces from single if statement.
-Fix variable constant comparison.
-Move logical operator to previous line.
Vatsala Narang
stable-rc/linux-5.0.y boot: 136 boots: 0 failed, 130 passed with 4 offline, 2
untried/unknown (v5.0.12-33-gc6bd3efdcefd)
Full Boot Summary:
https://kernelci.org/boot/all/job/stable-rc/branch/linux-5.0.y/kernel/v5.0.12-33-gc6bd3efdcefd/
Full Build Summary:
I am in the military unit here in Afghanistan, we have some amount of funds
that we want to move out of the country. My partners and I need a good partner
someone we can trust. It is risk free and legal. Reply to this email:
hornbeckmajordennis...@gmail.com
Regards,
Major Dennis Hornbeck.
From: Colin Ian King
Currently hdev is being dereferenced when using macro hid_to_usb_dev
before hdev is being null checked, hence there is a potential null
pointer dereference. Fix this by only dereferencing hdev after it has
been null checked.
Fixes: 9614219e9310 ("HID: uclogic: Extract
On Wed, May 01, 2019 at 10:36:47PM +0200, Viktor Rosendahl wrote:
> This patch implements the feature that the trace file, e.g.
> /sys/kernel/debug/tracing/trace will receive notifications through
> the fsnotify framework when a new trace is available.
>
> This makes it possible to implement a
On Thu, May 02, 2019 at 04:04:06AM +0100, Al Viro wrote:
> On Wed, May 01, 2019 at 02:42:23PM +0800, Wenbin Zeng wrote:
> > The newly added evict callback shall be called by nsfs_evict(). Currently
> > only put() callback is called in nsfs_evict(), it is not able to release
> > all netns refcount,
01.05.2019 11:58, Ben Dooks пишет:
> On 24/04/2019 19:17, Dmitry Osipenko wrote:
>> 24.04.2019 19:23, Ben Dooks пишет:
>>> The tx_status callback does not report the state of the transfer
>>> beyond complete segments. This causes problems with users such as
>>> ALSA when applications want to know
From: Colin Ian King
Currently the shift of two enum ints by more than 31 places on
can result in undefined behaviour with 64 bit longs. Fix this by
casting the ints to unsigned long before the shift.
Addresses-Coverity: ("Bad shift operation")
Fixes: 3a379bbcea0a ("i3c: Add core I3C
On Sat, May 04, 2019 at 10:47:07PM +0800, Muchun Song wrote:
> Benjamin Herrenschmidt 于2019年5月2日周四 下午2:25写道：
>
> > > > The basic idea yes, the whole bool *locked is horrid though.
> > > > Wouldn't it
> > > > work to have a get_device_parent_locked that always returns with
> > > > the mutex held,
New race in x86_pmu_stop was introduced by replacing the
atomic __test_and_clear_bit of cpuc->active_mask by separate
test_bit and __clear_bit calls in following patch:
3966c3feca3f ("x86/perf/amd: Remove need to check "running" bit in NMI
handler")
The race causes panic for PEBS events with
From: Erik Bussing
Remove code duplication in byt_rt5640_codec_fixup
Signed-off-by: Erik Bussing
---
sound/soc/intel/boards/bytcr_rt5640.c | 64 ++-
1 file changed, 23 insertions(+), 41 deletions(-)
diff --git a/sound/soc/intel/boards/bytcr_rt5640.c
From: Jordy Ubink
The snprintf calls filling byt_rt5651_cpu_dai_name / byt_rt5651_cpu_dai_name
always fill them with the same string (ssp0-port" resp "rt5651-aif2"). So
instead of keeping these buffers around and making the cpu_dai_name /
codec_dai_name point to this, simply update the
From: Damian van Soelen
The snprintf calls filling cht_rt5645_cpu_dai_name / cht_rt5645_codec_aif_name
always fill them with the same string ("ssp0-port" resp "rt5645-aif2") so
instead of keeping these buffers around and making the cpu_dai_name /
codec_aif_name point to this, simply update the
From: Nariman Etemadi
in function snd_byt_rt5640_mc_probe and removed buffer yt_rt5640_codec_aif_name
& byt_rt5640_cpu_dai_name
Signed-off-by: Nariman Etemadi
---
sound/soc/intel/boards/bytcr_rt5640.c | 26 --
1 file changed, 4 insertions(+), 22 deletions(-)
diff
The commit d46eb14b735b ("fs: fsnotify: account fsnotify metadata to
kmemcg") added remote memcg charging for fanotify and inotify event
objects. The aim was to charge the memory to the listener who is
interested in the events but without triggering the OOM killer.
Otherwise there would be
Benjamin Herrenschmidt 于2019年5月2日周四 下午2:25写道：
> > > The basic idea yes, the whole bool *locked is horrid though.
> > > Wouldn't it
> > > work to have a get_device_parent_locked that always returns with
> > > the mutex held,
> > > or just move the mutex to the caller or something simpler like
On 5/4/19 11:38 PM, Minwoo Im wrote:
On 5/4/19 11:26 PM, Akinobu Mita wrote:
2019年5月4日(土) 19:04 Minwoo Im :
+ { NVME_REG_INTMS, "intms", 32 },
+ { NVME_REG_INTMC, "intmc", 32 },
+ { NVME_REG_CC, "cc", 32 },
+ { NVME_REG_CSTS,
On Sat, May 4, 2019 at 2:12 PM Alexandru Ardelean
wrote:
>
> On Sat, May 4, 2019 at 1:24 AM Melissa Wen wrote:
> >
> > This patchset solves readability issues in AD7150 code, such as clarify
> > register and mask definition, fashion improvement of mask uses, reduce
> > tedious operation and
On Sat, May 04, 2019 at 10:35:02AM -0400, Arnd Bergmann wrote:
> On Thu, May 2, 2019 at 1:23 PM Greg KH wrote:
> >
> > On Sat, Apr 27, 2019 at 11:04:58PM +0100, Dragan Cvetic wrote:
> > > Add char device interface per DT node present and support
> > > file operations:
> > > - open(),
> > > -
On 5/4/19 11:26 PM, Akinobu Mita wrote:
2019年5月4日(土) 19:04 Minwoo Im :
Hi, Akinobu,
Regardless to reply of the cover, few nits here.
On 5/2/19 5:59 PM, Akinobu Mita wrote:
+
+static const struct nvme_reg nvme_regs[] = {
+ { NVME_REG_CAP, "cap", 64 },
+ {
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Linus,
Please pull one more powerpc fix for 5.1:
The following changes since commit 7a3a4d763837d3aa654cd1059030950410c04d77:
powerpc/mm_iommu: Allow pinning large regions (2019-04-17 21:36:51 +1000)
are available in the git repository at:
2019年5月4日(土) 18:40 Minwoo Im :
>
> Hi Akinobu,
>
> On 5/4/19 1:20 PM, Akinobu Mita wrote:
> > 2019年5月3日(金) 21:20 Christoph Hellwig :
> >>
> >> On Fri, May 03, 2019 at 06:12:32AM -0600, Keith Busch wrote:
> >>> Could you actually explain how the rest is useful? I personally have
> >>> never
On 4/5/19 3:06 am, Guenter Roeck wrote:
On Fri, May 03, 2019 at 08:16:05AM +0100, Linus Walleij wrote:
On Fri, May 3, 2019 at 8:02 AM Greg Ungerer wrote:
I dug out some old ks8695 based hardware to try this out.
I had a lot of trouble getting anything modern working on it.
In the end I
On Thu, May 2, 2019 at 1:23 PM Greg KH wrote:
>
> On Sat, Apr 27, 2019 at 11:04:58PM +0100, Dragan Cvetic wrote:
> > Add char device interface per DT node present and support
> > file operations:
> > - open(),
> > - close(),
> > - unlocked_ioctl(),
> > - compat_ioctl().
>
> Why do you need
2019年5月4日(土) 19:04 Minwoo Im :
>
> Hi, Akinobu,
>
> Regardless to reply of the cover, few nits here.
>
> On 5/2/19 5:59 PM, Akinobu Mita wrote:
> > +
> > +static const struct nvme_reg nvme_regs[] = {
> > + { NVME_REG_CAP, "cap", 64 },
> > + { NVME_REG_VS,
On Fri, 2019-05-03 at 17:31 +0800, Hsin-Hsiung Wang wrote:
> From: Ran Bi
>
> This add support for the MediaTek MT6358 RTC. Driver using
> compatible data to store different RTC_WRTGR address offset.
>
> Signed-off-by: Ran Bi
> ---
> drivers/rtc/rtc-mt6397.c | 43
This fixes multiple things in the habanalabs debugfs code, in particular:
- mmu_write() was unnecessarily verbose, copying around between multiple
buffers
- mmu_write() could write a user-specified, unbounded amount of userspace
memory into a kernel buffer (out-of-bounds write)
-
On Sat, May 04, 2019 at 02:52:00PM +0200, Jiri Olsa wrote:
> Adding sysfs_update_groups function to update
> multiple groups.
>
> TODO:
>
> I'm not sure how to handle error path in here,
> currently it removes the whole updated group
> together with already existing (not updated)
> attributes.
On Sat, May 04, 2019 at 02:52:07PM +0200, Jiri Olsa wrote:
> Using the new pmu::update_attrs attribute group for default
> attributes - freeze_on_smi, allow_tsx_force_abort.
"And delete the unused merge_attr() function"
Nice work with this series, it looks sane to me!
greg k-h
On Sat, May 04, 2019 at 05:45:48AM -0400, Carmeli Tamir wrote:
> Changed file_system_type next field to list_head and refactored
> the code to use list.h functions.
What might be interesting is getting rid of this list and using an XArray
instead. This would be a more in-depth change; getting
Hi Jiri,
On Thu, May 02, 2019 at 04:44:04PM +0530, Jiri Kosina wrote:
> On Tue, 23 Apr 2019, Srinivas Pandruvada wrote:
>
> > +Jiri
> >
> > He is not copied.
>
> Could you please resubmit the final version, and CC linux-input@ and
> Benjamin Tissories as appropriate?
I just posted teo
This driver implements a slim layer to enable the ChromeOS
EC kernel stack (cros_ec) to communicate with ChromeOS EC
firmware running on the Intel Integrated Sensor Hub (ISH).
The driver registers a ChromeOS EC MFD device to connect
with cros_ec kernel stack (upper layer), and it registers a
On Sat, May 04, 2019 at 05:45:48AM -0400, Carmeli Tamir wrote:
> From: Tamir
>
> Changed file_system_type next field to list_head and refactored
> the code to use list.h functions.
... except that list_head is not a good match here. For one thing,
we never walk that thing backwards. For
On Sat 04-05-19 20:28:24, Zhiqiang Liu wrote:
> From: Kai Shen
>
> spinlock recursion happened when do LTP test:
> #!/bin/bash
> ./runltp -p -f hugetlb &
> ./runltp -p -f hugetlb &
> ./runltp -p -f hugetlb &
> ./runltp -p -f hugetlb &
> ./runltp -p -f hugetlb &
>
> The dtor returned by
Using the new pmu::update_attrs attribute group to
create detected events for x86_pmu.
Moving the topdown/memory/tsx attributes to separate
attribute groups with specific is_visible functions.
Signed-off-by: Jiri Olsa
---
arch/x86/events/core.c | 10 +
arch/x86/events/intel/core.c |
Nobody is using that.
Signed-off-by: Jiri Olsa
---
arch/x86/events/core.c | 3 ---
arch/x86/events/perf_event.h | 1 -
2 files changed, 4 deletions(-)
diff --git a/arch/x86/events/core.c b/arch/x86/events/core.c
index de1a924a4914..f2be5d2a62fe 100644
--- a/arch/x86/events/core.c
+++
Using the new pmu::update_attrs attribute group for
skylake specific format attributes.
Signed-off-by: Jiri Olsa
---
arch/x86/events/intel/core.c | 15 ++-
1 file changed, 10 insertions(+), 5 deletions(-)
diff --git a/arch/x86/events/intel/core.c b/arch/x86/events/intel/core.c
Adding attr_update attribute group into pmu, to allow
having multiple attribute groups for same group name.
This will allow us to update "events" or "format"
directories with attributes that depend on various
HW conditions.
For example having group_format_extra group that updates
"format"
Using the new pmu::update_attrs attribute group for default
attributes - freeze_on_smi, allow_tsx_force_abort.
Signed-off-by: Jiri Olsa
---
arch/x86/events/core.c | 34 --
arch/x86/events/intel/core.c | 9 +
arch/x86/events/perf_event.h | 3 ---
3
Using the new pmu::update_attrs attribute group for
"caps" directory.
Signed-off-by: Jiri Olsa
---
arch/x86/events/core.c | 8 ---
arch/x86/events/intel/core.c | 44
arch/x86/events/perf_event.h | 1 -
3 files changed, 34 insertions(+), 19
We dont need to pre-filter out unsupported base events,
we can just use its group's is_visible function to do this.
Signed-off-by: Jiri Olsa
---
arch/x86/events/core.c | 52 --
1 file changed, 14 insertions(+), 38 deletions(-)
diff --git
hi,
following up on [1], this patchset adds update attribute groups
to pmu and gets rid of the 'creative' attribute handling code.
In x86 pmu we mainly add attributes into following directories:
events, format, caps
so it seems like we could have just 3 attribute groups, but most of
the
Adding sysfs_update_groups function to update
multiple groups.
TODO:
I'm not sure how to handle error path in here,
currently it removes the whole updated group
together with already existing (not updated)
attributes.
Signed-off-by: Jiri Olsa
---
fs/sysfs/group.c | 43
From: Kai Shen
spinlock recursion happened when do LTP test:
#!/bin/bash
./runltp -p -f hugetlb &
./runltp -p -f hugetlb &
./runltp -p -f hugetlb &
./runltp -p -f hugetlb &
./runltp -p -f hugetlb &
The dtor returned by get_compound_page_dtor in __put_compound_page
may be the function of
Hello,
Kconfiglib (https://github.com/ulfalizer/Kconfiglib) now has a
Tkinter-based guiconfig.py in addition to the curses-based
menuconfig.py. It has been tested on Linux, Windows, and macOS.
See https://github.com/ulfalizer/Kconfiglib#menuconfig-interfaces for
a screenshot (with show-all mode
On Sat, May 04, 2019 at 07:54:46AM -0400, Michal Hocko wrote:
Hi Michal,
Thanks for having a look at the patch.
> On Sat 04-05-19 15:53:54, Bharath Vedartham wrote:
> > __thp_get_unmapped_area is only used in mm/huge_memory.c. Make it
> > static.
>
> Makes sense. Looks like an omission.
>
> >
On Fri 03-05-19 18:31:46, Andrea Arcangeli wrote:
> This reverts commit 2f0799a0ffc033bf3cc82d5032acc3ec633464c2.
>
> commit 2f0799a0ffc033bf3cc82d5032acc3ec633464c2 was rightfully applied
> to avoid the risk of a severe regression that was reported by the
> kernel test robot at the end of the
On Fri 03-05-19 18:31:45, Andrea Arcangeli wrote:
> This reverts commit 356ff8a9a78fb35d6482584d260c3754dcbdf669.
This should really provide some changelog. I would go with the
following.
"
Consolidation of the THP allocation flags at the same place was meant to
be a clean up to easier handle
On Sat, May 4, 2019 at 8:53 AM YueHaibing wrote:
> Remove duplicated include.
>
> Signed-off-by: YueHaibing
Patch applied, thanks!
Yours,
Linus Walleij
Aviso de seguridad:
Este mensaje es de nuestro centro de mensajería Web Admin a todos nuestros
propietarios de cuentas de correo electrónico. Estamos eliminando el acceso a
todos nuestros clientes de correo web. Su cuenta de correo electrónico se
actualizará a una nueva y mejorada interfaz de
On Fri, May 3, 2019 at 3:17 PM Dan Carpenter wrote:
> The devm_ioremap_resource() function doesn't retunr NULL, it returns
> error pointers.
>
> Fixes: ecc133c6da60 ("soc: ixp4xx: qmgr: Pass resources")
> Signed-off-by: Dan Carpenter
Good catch! Patch applied.
I will make sure this fix lands
On Sat, May 4, 2019 at 1:35 AM Douglas Anderson wrote:
> If I run the following on rk3288-veyron-minnie (a 2GB machine)
>
> cd /sys/bus/platform/drivers/dwmmc_rockchip
> for i in $(seq 1 3000); do
> echo "" $i
> echo ff0f.dwmmc > unbind
> sleep .5
>
On Sat 04-05-19 15:53:54, Bharath Vedartham wrote:
> __thp_get_unmapped_area is only used in mm/huge_memory.c. Make it
> static.
Makes sense. Looks like an omission.
> Tested by building and booting the kernel.
Testing by git grep __thp_get_unmapped_area would give you a better
picture. Build
Trampoline can only be enabled if there is only a single ops
attached to it. If there's only a single callback registered
to a function, and the ops has a trampoline registered for it,
then we can call the trampoline directly. This is very useful
for improving the performance of ftrace and
Aviso de seguridad:
Este mensaje es de nuestro centro de mensajería Web Admin a todos nuestros
propietarios de cuentas de correo electrónico. Estamos eliminando el acceso a
todos nuestros clientes de correo web. Su cuenta de correo electrónico se
actualizará a una nueva y mejorada interfaz de
Aviso de seguridad:
Este mensaje es de nuestro centro de mensajería Web Admin a todos nuestros
propietarios de cuentas de correo electrónico. Estamos eliminando el acceso a
todos nuestros clientes de correo web. Su cuenta de correo electrónico se
actualizará a una nueva y mejorada interfaz de
On Sat, May 4, 2019 at 1:24 AM Melissa Wen wrote:
>
> This patchset solves readability issues in AD7150 code, such as clarify
> register and mask definition, fashion improvement of mask uses, reduce
> tedious operation and useless comments.
>
Hey,
Two patches seem a bit noisy/un-needed.
The
Hi Kay-Liu,
On Thu, Apr 25, 2019 at 8:09 AM wrote:
>
> From: Kay-Liu
>
> The imx6sx's dts file defines five clocks for fec, the
> 'ahb'clock's value is IMX6SX_CLK_ENET_AHB, but in the
> i.MX6SX Reference Manual there is no such enet ahb clock,
> there is only one "enet clock" in the CCM_CCGR3
Hi Kay-Liu,
On Thu, Apr 25, 2019 at 8:14 AM wrote:
>
> From: Kay-Liu
>
> The imx6sx's dts file defines five clocks for fec, the
> 'ahb'clock's value is IMX6SX_CLK_ENET_AHB, but in the
> i.MX6SX Reference Manual there is no such enet ahb clock,
> there is only one "enet clock" in the CCM_CCGR3
On 02-05-19, 18:25, Sameer Pujar wrote:
> Audio DMA(ADMA) interface is a gateway in the AHUB for facilitating DMA
> transfers between memory and all of its clients. Currently the driver
> supports Tegra210 based platforms. This series adds support for Tegra186
> and Tegra194 based platforms and
1 - 100 of 219 matches
Mail list logo
