On 15.07.2019 19:28, Andy Lutomirski wrote:
> On Mon, Jul 15, 2019 at 9:34 AM Andi Kleen wrote:
>>
>> Juergen Gross writes:
>>
>>> The long term plan has been to replace Xen PV guests by PVH. The first
>>> victim of that plan are now 32-bit PV guests, as those are used only
>>> rather seldom thes
UMWAIT and TPAUSE instructions use 32bit IA32_UMWAIT_CONTROL at MSR index
E1H to determines the maximum time in TSC-quanta that the processor can
reside in either C0.1 or C0.2.
This patch emulates MSR IA32_UMWAIT_CONTROL in guest and differentiate
IA32_UMWAIT_CONTROL between host and guest. The va
As the latest Intel 64 and IA-32 Architectures Software Developer's
Manual, UMWAIT and TPAUSE instructions cause a VM exit if the
RDTSC exiting and enable user wait and pause VM-execution
controls are both 1.
Because KVM never enable RDTSC exiting, the vm-exit for UMWAIT and TPAUSE
should never ha
UMONITOR, UMWAIT and TPAUSE are a set of user wait instructions.
This patch adds support for user wait instructions in KVM. Availability
of the user wait instructions is indicated by the presence of the CPUID
feature flag WAITPKG CPUID.0x07.0x0:ECX[5]. User wait instructions may
be executed at any
UMONITOR, UMWAIT and TPAUSE are a set of user wait instructions.
UMONITOR arms address monitoring hardware using an address. A store
to an address within the specified address range triggers the
monitoring hardware to wake up the processor waiting in umwait.
UMWAIT instructs the processor to ente
(+ Josh Poimboeuf)
On Tue, Jul 16, 2019 at 8:44 AM kbuild test robot wrote:
>
> tree:
> https://kernel.googlesource.com/pub/scm/linux/kernel/git/masahiroy/linux-kbuild.git
> kbuild
> head: 0ff0c3753e06c0420c80dac1b0187a442b372acb
> commit: 2eaf4e87ba258cc3f27e486cdf32d5ba76303c6f [5/19] kbu
>
> From: Bean Huo
>
> This patch is to change msleep() to usleep_range() based on
> Documentation/timers/timers-howto.txt. It suggests using
> usleep_range() for small msec(1ms - 20ms) since msleep()
> will often sleep longer than desired value.
>
> After changing, booting time will be 5ms-10m
trackpoint_detect() should be static inline while
CONFIG_MOUSE_PS2_TRACKPOINT is not set. otherwire,we
got building fails:
drivers/input/mouse/alps.o: In function `trackpoint_detect':
alps.c:(.text+0x8e00): multiple definition of `trackpoint_detect'
drivers/input/mouse/psmouse-base.o:psmouse-base.
On Tue, Jul 16, 2019 at 3:09 AM Pablo Neira Ayuso wrote:
>
> On Tue, Jul 16, 2019 at 02:56:09AM +0900, Masahiro Yamada wrote:
> > On Tue, Jul 16, 2019 at 2:33 AM Pablo Neira Ayuso
> > wrote:
> > >
> > > On Mon, Jul 15, 2019 at 07:28:04PM +0200, Laura Garcia wrote:
> > > > CC'ing netfilter.
> > >
Hi Masahiro,
On Tue, 16 Jul 2019 13:59:51 +0900 Masahiro Yamada
wrote:
>
> For the build error, I will fix it as follows for tomorrow's linux-next:
Thanks for the quick response.
--
Cheers,
Stephen Rothwell
pgpN0tCgezN6c.pgp
Description: OpenPGP digital signature
On 7/15/19 10:37 PM, Dmitry Osipenko wrote:
В Mon, 15 Jul 2019 21:37:09 -0700
Sowjanya Komatineni пишет:
On 7/15/19 8:50 PM, Dmitry Osipenko wrote:
16.07.2019 6:00, Sowjanya Komatineni пишет:
On 7/15/19 5:35 PM, Sowjanya Komatineni wrote:
On 7/14/19 2:41 PM, Dmitry Osipenko wrote:
13.07.
On Tue, 2019-07-16 at 08:06 +0200, Christoph Hellwig wrote:
>
> > /*
> > diff --git a/drivers/nvme/host/pci.c b/drivers/nvme/host/pci.c
> > index 54b35ea4af88..ab2358137419 100644
> > --- a/drivers/nvme/host/pci.c
> > +++ b/drivers/nvme/host/pci.c
> > @@ -2080,6 +2080,9 @@ static int nvme_setup_i
generic smp version of arch_futex_atomic_op_inuser() always returns -ENOSYS
Signed-off-by: Vasily Averin
---
include/asm-generic/futex.h | 21 +
1 file changed, 1 insertion(+), 20 deletions(-)
diff --git a/include/asm-generic/futex.h b/include/asm-generic/futex.h
index 8666f
On Tue, 2019-07-16 at 08:04 +0200, Christoph Hellwig wrote:
> >
> > + /*
> > +* If our IO queue size isn't the default, update the setting
> > +* in CC:IOSQES.
> > +*/
> > + if (ctrl->iosqes != NVME_NVM_IOSQES) {
> > + ctrl-
В Tue, 16 Jul 2019 08:37:01 +0300
Dmitry Osipenko пишет:
> В Mon, 15 Jul 2019 21:37:09 -0700
> Sowjanya Komatineni пишет:
>
> > On 7/15/19 8:50 PM, Dmitry Osipenko wrote:
> > > 16.07.2019 6:00, Sowjanya Komatineni пишет:
> > >> On 7/15/19 5:35 PM, Sowjanya Komatineni wrote:
> > >>> On
On 7/15/19 5:38 PM, Ralph Campbell wrote:
On 7/15/19 4:34 PM, John Hubbard wrote:
On 7/15/19 3:00 PM, Andrew Morton wrote:
On Tue, 9 Jul 2019 18:24:57 -0700 Ralph Campbell wrote:
mm/rmap.c | 1 +
1 file changed, 1 insertion(+)
--- a/mm/rmap.c~mm-hmm-fix-bad-subpage-pointer-in-try_to_un
On Mon, 15 Jul 2019, Linus Torvalds wrote:
> On Mon, Jul 15, 2019 at 1:00 AM Lee Jones wrote:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/lee/backlight.git
> > backlight-next-5.3
>
> Hmm. No such ref exists.
>
> I can see the "backlight-next" branch which has the right commit SHA1,
On 15.07.19 23:49, Lorenzo Bianconi wrote:
>> The LSM9DS1's accelerometer / gyroscope unit and it's magnetometer
>> (separately
>> supported in iio/magnetometer/st_magn*) are located on a separate i2c
>> addresses
>> on the bus.
>>
>> For the datasheet, see https://www.st.com/resource/en/datashee
On Tue, Jul 16, 2019 at 10:46:49AM +1000, Benjamin Herrenschmidt wrote:
> Based on reverse engineering and original patch by
>
> Paul Pawlowski
>
> This adds support for Apple weird implementation of NVME in their
> 2018 or later machines. It accounts for the twice-as-big SQ entries
> for the IO
> + /* Use default IOSQES. We'll update it later if needed */
> ctrl->ctrl_config |= NVME_CC_IOSQES | NVME_CC_IOCQES;
> ctrl->ctrl_config |= NVME_CC_ENABLE;
>
> @@ -2698,6 +2699,30 @@ int nvme_init_identify(struct nvme_ctrl *ctrl)
> ctrl->hmmin = le32_to_cpu(id->hmmi
On Tue, Jul 16, 2019 at 12:03 PM Stephen Rothwell wrote:
>
> Hi all,
>
> After merging the ntb tree, today's linux-next build (x86_64 allmodconfig)
> produced this warning:
>
> WARNING: could not open /home/sfr/next/next/drivers/ntb/ntb.c: No such file
> or directory
>
> The only thing I could se
On Tue, Jul 16, 2019 at 10:46:47AM +1000, Benjamin Herrenschmidt wrote:
> This will make it easier to handle variable queue entry sizes
> later. No functional change.
Looks good to me:
Reviewed-by: Christoph Hellwig
Use recently introduced devm_platform_ioremap_resource
helper which wraps platform_get_resource() and
devm_ioremap_resource() together. This helps produce much
cleaner code and remove local `struct resource` declaration.
Signed-off-by: Himanshu Jha
Signed-off-by: Julia Lawall
---
v2:
- added
Hi all,
Please do not add v5.4 material to your linux-next included branches
until after v5.3-rc1 has been released.
Changes since 20190715:
The kbuild tree gained a build failure for which I reverted 4 commits.
The pm tree lost its build failure.
The rdma tree gained a conflict against the
Hi Adrian,
On Mon, 15 Jul 2019 at 20:39, Adrian Hunter wrote:
>
> On 15/07/19 2:37 PM, Baolin Wang wrote:
> > Hi Adrian,
> >
> > On Mon, 15 Jul 2019 at 19:20, Adrian Hunter wrote:
> >>
> >> On 15/07/19 1:58 PM, Baolin Wang wrote:
> >>> In sdhci_runtime_resume_host() function, we will always do s
В Mon, 15 Jul 2019 21:37:09 -0700
Sowjanya Komatineni пишет:
> On 7/15/19 8:50 PM, Dmitry Osipenko wrote:
> > 16.07.2019 6:00, Sowjanya Komatineni пишет:
> >> On 7/15/19 5:35 PM, Sowjanya Komatineni wrote:
> >>> On 7/14/19 2:41 PM, Dmitry Osipenko wrote:
> 13.07.2019 8:54, Sowjanya Kom
Add check before assigning chip->ecc.read_page() and chip->ecc.write_page()
Signed-off-by: Naga Sureshkumar Relli
---
Changes in v18
- None
---
drivers/mtd/nand/raw/nand_micron.c | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/drivers/mtd/nand/raw/nand_micron.c
b/dri
Add driver for arm pl353 static memory controller nand interface.
This controller is used in Xilinx Zynq SoC for interfacing the
NAND flash memory.
Reviewed-by: Helmut Grohne
Signed-off-by: Naga Sureshkumar Relli
---
xilinx zynq TRM link:
https://www.xilinx.com/support/documentation/user_guides/
Introduced clock scaling using bitrate, preavious
calculations consider only the cycles per mb.
Also, clock scaling is now triggered before every
buffer being queued to the device. This helps in
deciding precise clock cycles required.
Signed-off-by: Aniket Masule
---
drivers/media/platform/qcom/
Present core assignment is static. Introduced load balancing
across the cores. Load on earch core is calculated and core
with minimum load is assigned to given instance.
Signed-off-by: Aniket Masule
---
drivers/media/platform/qcom/venus/helpers.c| 69 +++---
drivers/media
Current clock scaling calculations are same for vpu4 and
previous versions. For vpu4, Clock scaling calculations
are updated with cycles/mb. This helps in getting precise
clock required.
Signed-off-by: Aniket Masule
---
drivers/media/platform/qcom/venus/helpers.c | 91 +++
Add vpp cycles for different types of codec.
It indicates the cycles required by video hardware
to process each macroblock. Add vsp cycles, cycles
required by stream processor. Initialize the codec
data with core resources.
Signed-off-by: Aniket Masule
---
drivers/media/platform/qcom/venus/core.
In this patch series, clock scaling and core selection methods are
updated. Current clock scaling and core selection methods are same
for vpu4 and previous versions. Introducing load calculations using
vpp cycles, which indicates the cycles required by video hardware to
process each macroblock. Als
glink_ssr is used to signal a remote processor "A" about the stopping of
another remote processor "B", so that in the event that remote processor
B is ever booted again the fifos of the glink channel between A and B is
in a known state.
But if remote processor A receives this notification before B
Hi Stephen,
On Tue, Jul 16, 2019 at 1:31 PM Stephen Rothwell wrote:
>
> Hi all,
>
> After merging the kbuild tree, today's linux-next build (x86_64
> allnoconfig) failed like this:
>
> make[1]: *** No rule to make target 'modules.order', needed by
> 'autoksyms_recursive'. Stop.
>
> Starting wit
Change indentation to match parentheses. This complies with the Linux
kernel coding style and improves readability.
Signed-off-by: Benjamin Sherman
---
drivers/staging/vt6656/rxtx.c| 10 +-
drivers/staging/vt6656/usbpipe.c | 2 +-
2 files changed, 6 insertions(+), 6 deletions(-)
d
On Mon, 15 Jul 2019, Kelsey Skunberg wrote:
> Remove the following uncalled functions from include/linux/pci.h:
>
> pci_block_cfg_access()
> pci_block_cfg_access_in_atomic()
> pci_unblock_cfg_access()
>
> Functions were added in commit fb51ccbf217c ("PCI: Rework config
Hi Logan,
On Mon, 15 Jul 2019 21:46:42 -0600 Logan Gunthorpe wrote:
>
> I renamed the ntb.c file to core.c so we could add more files to build
> ntb.ko. See [1].
But that was last changed in June, so I assume that some change to the
build system has caused this warning to be produced now.
--
C
On 2019-07-15 21:30, Stanimir Varbanov wrote:
Hi,
On 7/2/19 5:46 PM, Aniket Masule wrote:
Present core assignment is static. Introduced load balancing
across the cores. Load on earch core is calculated and core
with minimum load is assigned to given instance.
Signed-off-by: Aniket Masule
---
Hi,
On 2019-07-15 21:28, Stanimir Varbanov wrote:
Hi,
On 7/2/19 5:46 PM, Aniket Masule wrote:
Introduced clock scaling using bitrate, preavious
calculations consider only the cycles per mb.
Also, clock scaling is now triggered before every
buffer being queued to the device. This helps in
decid
On 7/15/19 8:50 PM, Dmitry Osipenko wrote:
16.07.2019 6:00, Sowjanya Komatineni пишет:
On 7/15/19 5:35 PM, Sowjanya Komatineni wrote:
On 7/14/19 2:41 PM, Dmitry Osipenko wrote:
13.07.2019 8:54, Sowjanya Komatineni пишет:
On 6/29/19 8:10 AM, Dmitry Osipenko wrote:
28.06.2019 5:12, Sowjanya
The pull request you sent on Mon, 15 Jul 2019 23:37:03 +0200:
> git://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux.git i2c/for-5.3
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/273cbf61c3ddee9574ef1f4959b9bc6db5b24271
Thank you!
--
Deet-doot-dot, I am a bot.
h
The pull request you sent on Mon, 15 Jul 2019 14:27:02 -0500:
> git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git
> tags/pci-v5.3-changes
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/fb4da215ed92f564f7ca090bb81a199b0d6cab8a
Thank you!
--
Deet-doot-dot
The pull request you sent on Mon, 15 Jul 2019 21:49:33 +0200:
> ssh://g...@gitolite.kernel.org/pub/scm/linux/kernel/git/sre/linux-power-supply.git
> tags/for-v5.3
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/5fe7b600a116187e10317d83fb56922c4ef6b76d
Thank you!
--
The pull request you sent on Mon, 15 Jul 2019 08:48:35 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git tags/mfd-next-5.3
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/8de262531f5fbb7458463224a7587429800c24bf
Thank you!
--
Deet-doot-dot, I am a bo
The pull request you sent on Mon, 15 Jul 2019 15:26:22 +:
> git://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma.git tags/for-linus
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/2a3c389a0fde49b241430df806a34276568cfb29
Thank you!
--
Deet-doot-dot, I am a bot
On Mon, Jul 15, 2019 at 1:16 AM Oscar Salvador wrote:
>
> deactivate_section checks whether a section is early or not
> in order to either call free_map_bootmem() or depopulate_section_memmap().
> Being the former for sections added at boot time, and the latter for
> sections hotplugged.
>
> The p
Hi all,
After merging the kbuild tree, today's linux-next build (x86_64
allnoconfig) failed like this:
make[1]: *** No rule to make target 'modules.order', needed by
'autoksyms_recursive'. Stop.
Starting with commit
656c0ac3cb4b ("kbuild: modpost: read modules.order instead of
$(MODVERDIR)
On Sat, Jul 6, 2019 at 10:04 PM Andrew Morton wrote:
>
> On Fri, 5 Jul 2019 12:08:15 + Jason Gunthorpe wrote:
>
> > On Thu, Jul 04, 2019 at 04:29:55PM -0700, Dan Williams wrote:
> > > Guys, Andrew has kicked the subsection patches out of -mm because of
> > > the merge conflicts. Can we hold o
Hello Stephen,
Thanks for the review.
On 7/16/2019 4:14 AM, Stephen Boyd wrote:
Quoting Taniya Das (2019-05-12 20:44:46)
On 5/10/2019 11:24 PM, Stephen Boyd wrote:
diff --git a/drivers/clk/qcom/clk-rcg.h b/drivers/clk/qcom/clk-rcg.h
index 5562f38..e40e8f8 100644
--- a/drivers/clk/qcom/clk-rcg
Hello Stephen,
Thanks for your review.
On 7/16/2019 4:22 AM, Stephen Boyd wrote:
Quoting Taniya Das (2019-05-08 11:24:54)
diff --git a/drivers/clk/qcom/clk-rcg2.c b/drivers/clk/qcom/clk-rcg2.c
index 57dbac9..5bb6d45 100644
--- a/drivers/clk/qcom/clk-rcg2.c
+++ b/drivers/clk/qcom/clk-rcg2.c
@@
On Tue, Jul 16, 2019 at 11:13 AM Greg Kroah-Hartman
wrote:
>
> On Mon, Jul 15, 2019 at 11:48:27PM +0200, Rafael J. Wysocki wrote:
> > On Mon, Jul 15, 2019 at 11:44 PM Tri Vo wrote:
> > >
> > > Userspace can use wakeup_sources debugfs node to plot history of suspend
> > > blocking wakeup sources o
On 15.07.19 17:16, Andrew Cooper wrote:
There is a lot of infrastructure for functionality which is used
exclusively in __{save,restore}_processor_state() on the suspend/resume
path.
cr8 is an alias of APIC_TASKPRI, and APIC_TASKPRI is saved/restored by
lapic_{suspend,resume}(). Saving and rest
On 7/16/2019 12:04 AM, Sasha Levin wrote:
> ACPI_IORT lost it's explicit dependency on PCI in c6bb8f89fa6df
> ("ARM64/irqchip: Update ACPI_IORT symbol selection logic") where the
> author has relied on the general dependency of ACPI on PCI.
>
> However, that dependency was finally removed in 5d32a
It always returns 0 (success) and its return type should really be void.
Over that, many drivers have added error handling code based on its
return value, which is not required at all.
change its return type to void and update all the callers.
Signed-off-by: Viresh Kumar
---
V2->V3:
- Update bmi
ACPI_IORT lost it's explicit dependency on PCI in c6bb8f89fa6df
("ARM64/irqchip: Update ACPI_IORT symbol selection logic") where the
author has relied on the general dependency of ACPI on PCI.
However, that dependency was finally removed in 5d32a66541c4 ("PCI/ACPI:
Allow ACPI to be built without C
Hi Kamil,
On 19. 7. 15. 오후 9:04, Kamil Konieczny wrote:
> Add enable regulators to dev_pm_opp_set_regulators() and disable
> regulators to dev_pm_opp_put_regulators(). This prepares for
> converting exynos-bus devfreq driver to use dev_pm_opp_set_rate().
IMHO, it is not proper to mention the spec
On Mon, Jul 15, 2019 at 06:37:17PM -0500, Bjorn Helgaas wrote:
> On Mon, Jul 15, 2019 at 09:42:47PM +0200, Lukas Bulwahn wrote:
> > On Mon, 15 Jul 2019, Kelsey Skunberg wrote:
> >
> > > Remove the following uncalled functions from include/linux/pci.h:
> > >
> > > pci_block_cfg_access()
>
On 15.07.19 19:39, Andrew Cooper wrote:
On 15/07/2019 18:28, Andy Lutomirski wrote:
On Mon, Jul 15, 2019 at 9:34 AM Andi Kleen wrote:
Juergen Gross writes:
The long term plan has been to replace Xen PV guests by PVH. The first
victim of that plan are now 32-bit PV guests, as those are used
Hi Kamil,
Looks good to me. But, this patch has some issue.
I added the detailed reviews.
I recommend that you make the separate patches as following
in order to clarify the role of which apply the dev_pm_opp_* function.
First patch,
Need to consolidate the following two function into one functi
On 15.07.19 17:44, Boris Ostrovsky wrote:
diff --git a/arch/x86/xen/Makefile b/arch/x86/xen/Makefile
index 084de77a109e..d42737f31304 100644
--- a/arch/x86/xen/Makefile
+++ b/arch/x86/xen/Makefile
@@ -1,5 +1,5 @@
# SPDX-License-Identifier: GPL-2.0
-OBJECT_FILES_NON_STANDARD_xen-asm_$(BITS).o
16.07.2019 6:00, Sowjanya Komatineni пишет:
>
> On 7/15/19 5:35 PM, Sowjanya Komatineni wrote:
>>
>> On 7/14/19 2:41 PM, Dmitry Osipenko wrote:
>>> 13.07.2019 8:54, Sowjanya Komatineni пишет:
On 6/29/19 8:10 AM, Dmitry Osipenko wrote:
> 28.06.2019 5:12, Sowjanya Komatineni пишет:
>> T
> Caution: EXT Email
>
> On 15/07/2019 18:15:19+0800, Biwen Li wrote:
> > + device_init_wakeup(&pdev->dev, true);
> > + rtc->rtc_dev = devm_rtc_device_register(&pdev->dev, "ftm-alarm",
> > +
> &ftm_rtc_ops,
> > +
> THIS_MODULE);
>
> To be clear, I want you to not use devm_rtc_device_regis
On 2019-07-15 9:03 p.m., Stephen Rothwell wrote:
> Hi all,
>
> After merging the ntb tree, today's linux-next build (x86_64 allmodconfig)
> produced this warning:
>
> WARNING: could not open /home/sfr/next/next/drivers/ntb/ntb.c: No such file
> or directory
>
> The only thing I could see tha
Although we paid so many effort to settle down task on a particular
node, there are still chances for a task to leave it's preferred
node, that is by wakeup, numa swap migrations or load balance.
When we are using cpu cgroup in share way, since all the workloads
see all the cpus, it could be reall
On 7/15/19 8:00 PM, Sowjanya Komatineni wrote:
On 7/15/19 5:35 PM, Sowjanya Komatineni wrote:
On 7/14/19 2:41 PM, Dmitry Osipenko wrote:
13.07.2019 8:54, Sowjanya Komatineni пишет:
On 6/29/19 8:10 AM, Dmitry Osipenko wrote:
28.06.2019 5:12, Sowjanya Komatineni пишет:
This patch adds syst
This patch introduced numa execution time information, to imply the numa
efficiency.
By doing 'cat /sys/fs/cgroup/cpu/CGROUP_PATH/cpu.numa_stat', we see new
output line heading with 'exectime', like:
exectime 311900 407166
which means the tasks of this cgroup executed 311900 micro seconds on
n
By tracing numa page faults, we recognize tasks sharing the same page,
and try pack them together into a single numa group.
However when two task share lot's of cache pages while not much
anonymous pages, since numa balancing do not tracing cache page, they
have no chance to join into the same gro
This patch introduced numa locality statistic, which try to imply
the numa balancing efficiency per memory cgroup.
On numa balancing, we trace the local page accessing ratio of tasks,
which we call the locality.
By doing 'cat /sys/fs/cgroup/cpu/CGROUP_PATH/cpu.numa_stat', we
see output line headi
During our torturing on numa stuff, we found problems like:
* missing per-cgroup information about the per-node execution status
* missing per-cgroup information about the numa locality
That is when we have a cpu cgroup running with bunch of tasks, no good
way to tell how it's tasks are deali
In sched_copy_attr(), attr->size was fetched twice in get_user()
and copy_from_user().
If change it between two fetches may cause security problems
or unexpected behaivor.
We can apply the same pattern used in perf_copy_attr(). That
is, use value fetched first time to overwrite it after second fe
On Mon, Jul 15, 2019 at 1:00 AM Lee Jones wrote:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/lee/backlight.git
> backlight-next-5.3
Hmm. No such ref exists.
I can see the "backlight-next" branch which has the right commit SHA1,
but you normally do a signed tag, and I'd much rather merge
From: Anson Huang
According to i.MX8MM reference manual Rev.1, 03/2019:
SAI3_RXC pin's mux option #1 should be GPT1_CLK, NOT GPT1_CAPTURE2;
SAI3_TXFS pin's mux option #1 should be GPT1_CAPTURE2, NOT GPT1_CLK.
Fixes: c1c9d41319c3 ("dt-bindings: imx: Add pinctrl binding doc for imx8mm")
Signed-of
There are functions which increment a reference counter for a device node.
These functions belong to a programming interface for the management
of information from device trees.
The counter must be decremented after the last usage of a device node.
We find these functions by using the following scr
Hi all,
After merging the ntb tree, today's linux-next build (x86_64 allmodconfig)
produced this warning:
WARNING: could not open /home/sfr/next/next/drivers/ntb/ntb.c: No such file or
directory
The only thing I could see that might be relevant is commit
56dce8121e97 ("kbuild: split out *.mo
On 7/15/19 6:36 PM, Qian Cai wrote:
On Jul 15, 2019, at 8:22 PM, Yang Shi wrote:
On 7/15/19 2:23 PM, Qian Cai wrote:
On Fri, 2019-07-12 at 12:12 -0700, Yang Shi wrote:
Another possible lead is that without reverting the those commits below,
kdump
kernel would always also crash in shrin
On 7/15/19 5:35 PM, Sowjanya Komatineni wrote:
On 7/14/19 2:41 PM, Dmitry Osipenko wrote:
13.07.2019 8:54, Sowjanya Komatineni пишет:
On 6/29/19 8:10 AM, Dmitry Osipenko wrote:
28.06.2019 5:12, Sowjanya Komatineni пишет:
This patch adds system suspend and resume support for Tegra210
clocks
Hi,
On 07/15/19 at 12:59pm, Matthew Garrett wrote:
> From: Josh Boyer
>
> This option allows userspace to pass the RSDP address to the kernel, which
> makes it possible for a user to modify the workings of hardware . Reject
> the option when the kernel is locked down.
>
> Signed-off-by: Josh Bo
Hi,
On Mon, Jul 15, 2019 at 9:38 PM Sasha Levin wrote:
> From: Daniel Drake
>
> [ Upstream commit 604dc9170f2435d27da5039a3efd757dceadc684 ]
In my opinion this is not stable kernel material.
It alone does not solve a particular bug. It's part of a larger effort
to decrease usage of the 8254 PI
On Tue, Jul 16, 2019 at 07:50:02AM +0530, Hariprasad Kelam wrote:
> This patch removes NULL checks before calling kfree.
>
> fixes below issues reported by coccicheck
> net/sctp/sm_make_chunk.c:2586:3-8: WARNING: NULL check before some
> freeing functions is not needed.
> net/sctp/sm_make_chunk.c:
Hi Michal,
Thx for the comments :-)
On 2019/7/15 下午8:10, Michal Koutný wrote:
> Hello Yun.
>
> On Fri, Jul 12, 2019 at 06:10:24PM +0800, 王贇
> wrote:
>> Forgive me but I have no idea on how to combined this
>> with memory cgroup's locality hierarchical update...
>> parent memory cgroup do not
This patch removes NULL checks before calling kfree.
fixes below issues reported by coccicheck
net/sctp/sm_make_chunk.c:2586:3-8: WARNING: NULL check before some
freeing functions is not needed.
net/sctp/sm_make_chunk.c:2652:3-8: WARNING: NULL check before some
freeing functions is not needed.
net
Pablo
v2 has been sent
I made the following changes:
1. remove all unnecessary spaces in one go
2. revert bitmap_alloc ( since it's irrelevant to this subject)
3. chenge subject to "net/netfiler:remove unnecessary space"
thanks
Pablo Neira Ayuso 于2019年7月15日周一 下午4:27写道：
>
> On Wed, Jul 10, 201
On Mon, Jul 15, 2019 at 11:48:27PM +0200, Rafael J. Wysocki wrote:
> On Mon, Jul 15, 2019 at 11:44 PM Tri Vo wrote:
> >
> > Userspace can use wakeup_sources debugfs node to plot history of suspend
> > blocking wakeup sources over device's boot cycle. This information can
> > then be used (1) for p
On Mon, Jul 15, 2019 at 02:48:13PM -0700, Tri Vo wrote:
> > And I am guessing that you actually tested this all out, and it works
> > for you?
>
> Yes, I played around with wakelocks to make sure that wakeup source
> stats are added/updated/removed as expected.
Great!
> > Have you changed Androi
this patch removes extra spaces
Signed-off-by: yangxingwu
---
net/netfilter/ipset/ip_set_hash_gen.h | 2 +-
net/netfilter/ipset/ip_set_list_set.c | 2 +-
net/netfilter/ipvs/ip_vs_core.c| 2 +-
net/netfilter/ipvs/ip_vs_mh.c | 4 ++--
net/netfilter/ipvs/ip_vs_proto_tcp.c | 2 +
From: Sven Van Asbroeck Sent: Tuesday, July 16, 2019 5:05
AM
> The current fec driver allows the PHY to be reset via a gpio, specified in the
> devicetree. However, some PHYs need to be reset in a more complex way.
>
> To accommodate such PHYs, allow an optional reset controller in the fec
> dev
On 2019/7/15 13:38, Vasily Averin wrote:
> On 7/14/19 5:45 AM, Xiaoming Ni wrote:
>> On 2019/7/12 22:07, gre...@linuxfoundation.org wrote:
>>> On Fri, Jul 12, 2019 at 09:11:57PM +0800, Xiaoming Ni wrote:
On 2019/7/11 21:57, Vasily Averin wrote:
> On 7/11/19 4:55 AM, Nixiaoming wrote:
>
Hi, Weiyi:
On Mon, 2019-07-15 at 17:07 +0800, Weiyi Lu wrote:
> On Mon, 2019-07-15 at 16:07 +0800, CK Hu wrote:
> > Hi, Weiyi:
> >
> > On Mon, 2019-07-01 at 16:57 +0800, CK Hu wrote:
> > > Hi, Weiyi:
> > >
> > > On Thu, 2019-06-20 at 10:38 +0800, Weiyi Lu wrote:
> > > > Add power controller node
> On Jul 15, 2019, at 8:22 PM, Yang Shi wrote:
>
>
>
> On 7/15/19 2:23 PM, Qian Cai wrote:
>> On Fri, 2019-07-12 at 12:12 -0700, Yang Shi wrote:
Another possible lead is that without reverting the those commits below,
kdump
kernel would always also crash in shrink_slab_memcg()
ok
I will remove all unnecessary spaces and send the v2 patch
Thansk Pablo
Pablo Neira Ayuso 于2019年7月15日周一 下午4:27写道：
>
> On Wed, Jul 10, 2019 at 10:06:09AM +0200, Simon Horman wrote:
> > On Wed, Jul 10, 2019 at 03:45:52PM +0800, yangxingwu wrote:
> > > ---
> > > net/netfilter/ipvs/ip_vs_mh.c |
Reviewed-by: Sagi Grimberg
On 7/15/19 11:40 AM, Saravana Kannan wrote:
> Replying again because the previous email accidentally included HTML.
>
> Thanks for taking the time to reconsider the wording Frank. Your
> intention was clear to me in the first email too.
>
> A kernel command line option can also completely disable
Hi Bean,
On Mon, 2019-07-15 at 11:21 +, Bean Huo (beanhuo) wrote:
> From: Bean Huo
>
> This patch is to change msleep() to usleep_range() based on
> Documentation/timers/timers-howto.txt. It suggests using
> usleep_range() for small msec(1ms - 20ms) since msleep()
> will often sleep longer t
On Mon, Jul 15, 2019 at 1:16 AM Vincent Guittot
wrote:
>
> On Tue, 9 Jul 2019 at 21:03, Saravana Kannan wrote:
> >
> > On Tue, Jul 9, 2019 at 12:25 AM Vincent Guittot
> > wrote:
> > >
> > > On Sun, 7 Jul 2019 at 23:48, Saravana Kannan wrote:
> > > >
> > > > On Thu, Jul 4, 2019 at 12:12 AM Vince
> On Jul 15, 2019, at 4:30 PM, Andrew Cooper wrote:
>
> On 15/07/2019 19:17, Nadav Amit wrote:
>>> On Jul 15, 2019, at 8:16 AM, Andrew Cooper
>>> wrote:
>>>
>>> There is a lot of infrastructure for functionality which is used
>>> exclusively in __{save,restore}_processor_state() on the suspend
On Tue, 2019-07-16 at 10:46 +1000, Benjamin Herrenschmidt wrote:
> # Conflicts:
> # drivers/nvme/host/pci.c
> ---
Oops :-) You can strip that or should I resend ? I'll wait for
comments/reviews regardless.
Cheers,
Ben.
Based on reverse engineering and original patch by
Paul Pawlowski
This adds support for Apple weird implementation of NVME in their
2018 or later machines. It accounts for the twice-as-big SQ entries
for the IO queues, and the fact that only interrupt vector 0 appears
to function properly.
Sign
This will make it easier to handle variable queue entry sizes
later. No functional change.
Signed-off-by: Benjamin Herrenschmidt
# Conflicts:
# drivers/nvme/host/pci.c
---
drivers/nvme/host/pci.c | 30 +++---
1 file changed, 15 insertions(+), 15 deletions(-)
diff
On PCIe based NVME devices, this will retrieve the IO queue entry
size from the controller and use the "required" setting.
It should always be 6 (64 bytes) by spec. However some controllers
such as Apple's are not properly implementing the spec and require
the size to be 7 (128 bytes).
This prov
1 - 100 of 1645 matches
Mail list logo
