On Mon 24-08-20 11:42:04, Andrew Morton wrote:
> On Mon, 24 Aug 2020 20:54:33 +0800 Alex Shi
> wrote:
>
> > The new version which bases on v5.9-rc2. The first 6 patches was picked into
> > linux-mm, and add patch 25-32 that do some further post optimization.
>
> 32 patches, version 18. That's
Quoting Bjorn Andersson (2020-08-24 09:42:12)
> On Fri 21 Aug 14:41 PDT 2020, Stephen Boyd wrote:
>
> > Quoting Sibi Sankar (2020-08-21 13:49:20)
> > > Add GENPD_FLAG_NO_SUSPEND/RESUME flags to instruct genpd to keep the
> > > status of the PM domain unaltered during suspend/resume respectively.
Hi,
I just sent a patch to fix the issue. The loop device would have
respected the configuration, but indeed the size of the underlying
block device was not set correctly, so reading back the size would
give the wrong result.
Thanks,
Martijn
On Mon, Aug 24, 2020 at 8:24 PM Martijn Coenen
On Mon, Aug 24, 2020 at 08:39:04PM -0600, Rob Herring wrote:
> On Mon, Aug 24, 2020 at 06:26:46PM +0200, Krzysztof Kozlowski wrote:
> > DTSes with new i.MX 8M SoCs use two compatibles so update the binding to
> > fix dtbs_check warnings like:
> >
> >
Hi Morimoto-san,
Other solution is create both snd_soc_find_dai_with_mutex()/without_mutex().
I'm not sure which style is best.
I don't know how complex it is to have a unified solution. But if we
can protect snd_soc_find_dai() itself, things would be simpler may be
in long term. Right now
On Tue, Aug 25, 2020 at 06:46:53AM +0200, Sascha Hauer wrote:
> On Mon, Aug 24, 2020 at 06:26:46PM +0200, Krzysztof Kozlowski wrote:
> > +oneOf:
> > + - items:
> > + - enum:
> > + - fsl,imx6q-ocotp
> > + - fsl,imx6sl-ocotp
> > + -
Hi Hillf,
I just tried the updated version and the system can boot up now.
It does mitigate the issue a lot but still couldn't get rid of it
thoroughly. It seems to me like the effect of Cong's patch.
Hillf Danton 于2020年8月25日周二 上午11:23写道：
>
>
> Hi Feng,
>
> On Tue, 25 Aug 2020 10:18:05 +0800
On Tue, Aug 25, 2020 at 08:33:04AM +0200, Thomas Richter wrote:
SNIP
> diff --git a/tools/perf/util/stat-display.c b/tools/perf/util/stat-display.c
> index 57d0706e1330..cbe836649f84 100644
> --- a/tools/perf/util/stat-display.c
> +++ b/tools/perf/util/stat-display.c
> @@ -117,12 +117,11 @@
Linux 5.9 introduced perf test case "Parse and process metrics" and
on s390 this test case always dumps core:
[root@t35lp67 perf]# ./perf test - -F 67
67: Parse and process metrics :
--- start ---
metric expr inst_retired.any / cpu_clk_unhalted.thread for IPC
On Mon, Aug 24, 2020 at 10:34 AM Arvind Sankar wrote:
>
> On Tue, Aug 25, 2020 at 12:57:22AM +0900, Masahiro Yamada wrote:
> >
> >
> > To prevent transformation from foo() into bar(),
> > there are two ways in Clang to do that;
> > -fno-builtin-foo, and -fno-builtin-bar.
> > There is only one in
On Wed, Aug 12, 2020 at 02:36:18PM -0600, Rob Herring wrote:
> Clean-up incorrect indentation, extra spaces, long lines, and missing
> EOF newline in schema files. Most of the clean-ups are for list
> indentation which should always be 2 spaces more than the preceding
> keyword.
>
> Found with
trace_printk is meant as a debugging tool, and should not be
compiled into production code without specific debug Kconfig
options enabled, or source code changes, as indicated by the
warning that shows up on boot if any trace_printk is called:
** NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE
Hello Peter,
On 25-08-20, 09:52, Peter Ujfalusi wrote:
> Hi Vinod,
>
> On 24/08/2020 11.47, Vinod Koul wrote:
> > Some complex dmaengine controllers have capability to program the
> > peripheral device, so pass on the peripheral configuration as part of
> > dma_slave_config
> >
> >
On Tue, Aug 25, 2020 at 02:37:04AM +, Xia, Hui wrote:
> >-Original Message-
> >From: Johan Hovold
> >Sent: 2020年8月24日 17:54
> >To: kernel test robot
> >Cc: Greg Kroah-Hartman ; kbuild-...@lists.01.org;
> >linux-kernel@vger.kernel.org
> >Subject: [kbuild-all] Re:
On Thu, 20 Aug 2020 at 21:06, Eddie James wrote:
>
>
> On 8/20/20 12:12 PM, Mark Brown wrote:
> > On Thu, Aug 20, 2020 at 12:02:23PM -0500, Eddie James wrote:
> >> From: Brad Bishop
> >>
> >> Use a clock divider tuned to a 200MHz FSI clock. Use of the previous
> >> divider at 200MHz results in
On Fri, Aug 21, 2020 at 09:58:19AM +0200, Christophe JAILLET wrote:
> The way 'spin_lock()' and 'spin_lock_irqsave()' are used is not consistent
> in this function.
>
> Use 'spin_lock_irqsave()' also here, as there is no guarantee that
> interruptions are disabled at that point, according to
On Mon, Aug 24, 2020 at 02:16:30PM -0700, Keith Busch wrote:
> On Mon, Aug 24, 2020 at 01:00:11PM -0700, Sagi Grimberg wrote:
> > > The way 'spin_lock()' and 'spin_lock_irqsave()' are used is not consistent
> > > in this function.
> > >
> > > Use 'spin_lock_irqsave()' also here, as there is no
On Mon, Aug 24, 2020 at 08:38:01PM -0600, Rob Herring wrote:
> On Mon, Aug 24, 2020 at 06:26:45PM +0200, Krzysztof Kozlowski wrote:
> > The i.MX 8 DTSes use two compatibles so update the binding to fix
> > dtbs_check warnings like:
> >
> > arch/arm64/boot/dts/freescale/imx8mn-evk.dt.yaml:
We have used callchain_node->hit to measure the hot level of one
stream. This patch calculates the sum of hits of total streams.
Thus in next patch, we can use following formula to report hot
percent for one stream.
hot percent = callchain_node->hit / sum of total hits
Signed-off-by: Jin Yao
This patch enables perf-diff with "--stream" option.
"--stream": Enable hot streams comparison
Now let's see examples.
perf record -b ... Generate perf.data.old with branch data
perf record -b ... Generate perf.data with branch data
perf diff --stream
[ Matched hot streams ]
hot
In previous patch, we have created an evsel_streams for one event,
and top N hottest streams will be saved in a stream array in
evsel_streams.
This patch compares total streams among two evsel_streams.
Once two streams are fully matched, they will be linked as
a pair. From the pair, we can know
Stream is the branch history which is aggregated by the branch
records from perf samples. Now we only support the callchain as
stream.
If the callchain entries of one stream are fully matched with
the callchain entries of another stream, we think two streams
are matched.
For example,
cycles:
We define the stream is the branch history which is aggregated by
the branch records from perf samples. For example, the callchains
aggregated from the branch records are considered as streams.
By browsing the hot stream, we can understand the hot code path.
Now we only support the callchain for
We show the streams separately. They are divided into different sections.
1. "Matched hot streams"
2. "Hot streams in old perf data only"
3. "Hot streams in new perf data only".
For each stream, we report the cycles and hot percent (hits%).
For example,
cycles: 2, hits: 4.08%
Sometimes, a small change in a hot function reducing the cycles of
this function, but the overall workload doesn't get faster. It is
interesting where the cycles are moved to.
What it would like is to diff before/after streams. The stream is the
branch history which is aggregated by the branch
In previous patch, we have created evsel_streams array
This patch returns the specified evsel_streams according to the
evsel_idx.
Signed-off-by: Jin Yao
---
v4:
- Rename the patch from 'perf util: Return per-event callchain
streams' to 'perf util: Get the evsel_streams by evsel_idx'
On Tue, 2020-08-25 at 00:01 -0700, Joe Perches wrote:
> On Tue, 2020-08-25 at 14:38 +0800, Jing Xiangfeng wrote:
> > The variable ret is being initialized with 'FAILED'. So we can remove
> > this assignement.
>
> If you are going to change the code at all,
> might as well try to improve it more
Looks like we might have to replace the IS_ENABLED with an ifdef to
cater for the 32-bit phys_addr_t and overzealous compilers.
On Tue, Aug 25, 2020 at 01:45:38PM +0800, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> master
> head:
On Tue, 2020-08-25 at 14:38 +0800, Jing Xiangfeng wrote:
> The variable ret is being initialized with 'FAILED'. So we can remove
> this assignement.
If you are going to change the code at all,
might as well try to improve it more by removing
the unnecessary out: label altogether.
Perhaps:
---
Fix variable set but not used compilation warning.
Fixes: 43b1bb4a9b3e ("clk: at91: clk-sam9x60-pll: re-factor to support plls
with multiple outputs")
Reported-by: kernel test robot
Signed-off-by: Claudiu Beznea
---
drivers/clk/at91/clk-sam9x60-pll.c | 3 +--
1 file changed, 1 insertion(+), 2
SAMA5D2 datasheet specifies on chapter 33.22.8 (PMC Clock Generator
Main Oscillator Register) that writing any value other than
0x37 on KEY field aborts the write operation. Use the key when
selecting main clock parent.
Fixes: 27cb1c2083373 ("clk: at91: rework main clk implementation")
Hi,
In this series I collected 2 patches send previously and add another that
fixes a compilation warning.
Changes in v2:
- add patches "clk: at91: remove the checking of parent_name" and
"clk: at91: clk-main: update key before writing AT91_CKGR_MOR" in the same
series and collect
There is no need to check parent_name variable while assigning it to
init.parent_names. parent_name variable is already checked at
the beginning of at91_clk_register_peripheral() function.
Fixes: 6114067e437eb ("clk: at91: add PMC peripheral clocks")
Signed-off-by: Claudiu Beznea
Reviewed-by:
On Tue, Aug 25, 2020 at 02:39:55PM +0800, Kai Heng Feng wrote:
> Hi Christoph,
>
> > On Aug 25, 2020, at 2:23 PM, Christoph Hellwig wrote:
> >
> > On Fri, Aug 21, 2020 at 08:32:20PM +0800, Kai-Heng Feng wrote:
> >> New Intel laptops with VMD cannot reach deeper power saving state,
> >> renders
On Tue, Aug 25, 2020 at 06:23:36AM +, Vaittinen, Matti wrote:
>
> Hello Krzysztof,
>
> On Mon, 2020-08-24 at 21:06 +0200, Krzysztof Kozlowski wrote:
> > The input clock and number of clock provider cells are not required
> > for
> > the PMIC to operate. They are needed only for the optional
On Tue, Aug 25, 2020 at 08:51:35AM +0200, Greg Kroah-Hartman wrote:
> On Mon, Aug 24, 2020 at 10:55:28AM +0200, Dmitry Vyukov wrote:
> > On Sun, Aug 23, 2020 at 12:57 PM Greg Kroah-Hartman
> > wrote:
> > >
> > > On Sun, Aug 23, 2020 at 12:31:03PM +0200, Dmitry Vyukov wrote:
> > > > On Sun, Aug
On Sat, Aug 22, 2020 at 10:52:54AM -0700, Rob Clark wrote:
> From: Rob Clark
>
> Now that it isn't causing problems to use dma_map/unmap, we can drop the
> hack of using dma_sync in certain cases.
Great to see! What did solve the problems?
On Tue, Aug 25, 2020 at 07:47:29AM +0100, Christoph Hellwig wrote:
> On Fri, Aug 21, 2020 at 06:27:04PM +0300, Tomer Samara wrote:
> > Remove BUG/BUG_ON from androind/ion
>
> Please just remove ion. It has been rejected and we have developed
> proper kernel subsystens to replace it. Don't waste
On Mon, Aug 24, 2020 at 10:55:28AM +0200, Dmitry Vyukov wrote:
> On Sun, Aug 23, 2020 at 12:57 PM Greg Kroah-Hartman
> wrote:
> >
> > On Sun, Aug 23, 2020 at 12:31:03PM +0200, Dmitry Vyukov wrote:
> > > On Sun, Aug 23, 2020 at 12:19 PM Greg Kroah-Hartman
> > > wrote:
> > > >
> > > > On Sun, Aug
Hello Krzysztof,
Just some questions - please ignore if I misunderstood the impact of
the change.
On Mon, 2020-08-24 at 21:06 +0200, Krzysztof Kozlowski wrote:
> Device tree schema expects regulator names to be lowercase. This
> fixes
> dtbs_check warnings like:
>
>
Hi Alexei,
On Mon, 24 Aug 2020 20:27:28 -0700 Alexei Starovoitov
wrote:
>
> I didn't receive the first email you've replied to.
> The build error is:
> "
> No libelf found
> make[5]: *** [Makefile:284: elfdep] Error 1
> "
> and build process stops because libelf is not found, right?
> That is
Hi Vinod,
On 24/08/2020 11.47, Vinod Koul wrote:
> Some complex dmaengine controllers have capability to program the
> peripheral device, so pass on the peripheral configuration as part of
> dma_slave_config
>
> Signed-off-by: Vinod Koul
> ---
> include/linux/dmaengine.h | 75
On Mon, Aug 24, 2020 at 05:56:53PM +0100, Mel Gorman wrote:
> On Mon, Aug 24, 2020 at 06:12:38PM +0200, Borislav Petkov wrote:
> >
> > > :) Right, this is what I'm doing right now. Some test job is queued on
> > > the test box, and it may needs some iterations of new patch. Hopefully we
> > >
On Tue, Aug 25, 2020 at 08:40:20AM +0200, Sascha Hauer wrote:
> On Mon, Aug 24, 2020 at 09:06:47PM +0200, Krzysztof Kozlowski wrote:
> > Driver requires different amount of clocks for different SoCs. Describe
> > these requirements properly to fix dtbs_check warnings like:
> >
> >
In the probe_acpi_namespace_devices function,when the physical
node of the acpi device is NULL,the unlock function is missing.
Add mutex_unlock(>physical_node_lock).
Reported-by: Dan Carpenter
Signed-off-by: FelixCuioc
---
drivers/iommu/intel/iommu.c | 1 +
1 file changed, 1 insertion(+)
diff
On Fri, Aug 21, 2020 at 06:27:04PM +0300, Tomer Samara wrote:
> Remove BUG/BUG_ON from androind/ion
Please just remove ion. It has been rejected and we have developed
proper kernel subsystens to replace it. Don't waste your time on it.
Hi Sameer
> > Other solution is create both snd_soc_find_dai_with_mutex()/without_mutex().
> > I'm not sure which style is best.
>
> I don't know how complex it is to have a unified solution. But if we
> can protect snd_soc_find_dai() itself, things would be simpler may be
> in long term.
Move the burst len fixup after setting the generic value for it. This
finally enables the fixup introduced by commit 137bd11090d8 ("dmaengine:
pl330: Align DMA memcpy operations to MFIFO width"), which otherwise was
overwritten by the generic value.
Reported-by: kernel test robot
Fixes:
On Tue, 25 Aug 2020 at 06:43, Viresh Kumar wrote:
>
> On 24-08-20, 17:08, Stephan Gerhold wrote:
> > On Mon, Aug 24, 2020 at 04:36:57PM +0200, Ulf Hansson wrote:
> > > That said, perhaps should rely on the consumer to deploy runtime PM
> > > support, but let the OPP core to set up the device
On Mon, 24 Aug 2020 at 22:20, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.19.142 release.
> There are 73 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.
>
>
Commit f45ec5ff16a75 ("userfaultfd: wp: support swap and page
migration") introduced support for tracking the uffd wp bit during page
migration. However the non-swap PTE variant was used to set the flag for
zone device private pages which are a type of swap page.
This leads to corruption of the
During memory migration a pte is temporarily replaced with a migration
swap pte. Some pte bits from the existing mapping such as the soft-dirty
and uffd write-protect bits are preserved by copying these to the
temporary migration swap pte.
However these bits are not stored at the same location
On Mon, Aug 24, 2020 at 09:06:47PM +0200, Krzysztof Kozlowski wrote:
> Driver requires different amount of clocks for different SoCs. Describe
> these requirements properly to fix dtbs_check warnings like:
>
> arch/arm64/boot/dts/freescale/imx8mm-beacon-kit.dt.yaml:
>
From: Qiwu Huang
Reports what type of wireless adapter connection is
currently active for the supply.
for example it can show if ADAPTER_PD capable source is attached.
Signed-off-by: Qiwu Huang
---
Documentation/ABI/testing/sysfs-class-power | 28 +
Hi Christoph,
> On Aug 25, 2020, at 2:23 PM, Christoph Hellwig wrote:
>
> On Fri, Aug 21, 2020 at 08:32:20PM +0800, Kai-Heng Feng wrote:
>> New Intel laptops with VMD cannot reach deeper power saving state,
>> renders very short battery time.
>
> So what about just disabling VMD given how
From: Qiwu Huang
This patchset aims to provide power supply properties about wireless/wired
charging.
"quick_charge_type" reports different types of quick charge based on the
charging power;
"tx_adapter" shows" the type of wireless charging adapter;
"signal_strength" shows the coupling level
From: Qiwu Huang
Interface to control wireless reverse charge.
Signed-off-by: Qiwu Huang
---
Documentation/ABI/testing/sysfs-class-power | 14 ++
drivers/power/supply/power_supply_sysfs.c | 1 +
include/linux/power_supply.h| 1 +
3 files changed, 16
From: Qiwu Huang
reports wireless signal strength.
The value show degree of coupling between tx and rx.
Signed-off-by: Qiwu Huang
---
Documentation/ABI/testing/sysfs-class-power | 22 +
drivers/power/supply/power_supply_sysfs.c | 1 +
include/linux/power_supply.h
From: Qiwu Huang
Reports the kind of quick charge type based on
different adapter power.
Signed-off-by: Qiwu Huang
---
Documentation/ABI/testing/sysfs-class-power | 21 ++
drivers/power/supply/power_supply_sysfs.c | 1 +
drivers/power/supply/qcom_smbb.c| 79
On Thu, 20 Aug 2020 at 16:12, Eddie James wrote:
>
> Mask the IRQ status to only the bits that the driver checks. This
> prevents excessive driver warnings when operating in slave mode
> when additional bits are set that the driver doesn't handle.
>
> Signed-off-by: Eddie James
> ---
>
On Mon, 24 Aug 2020 at 20:31, Xunlei Pang wrote:
>
> We've met problems that occasionally tasks with full cpumask
> (e.g. by putting it into a cpuset or setting to full affinity)
> were migrated to our isolated cpus in production environment.
>
> After some analysis, we found that it is due to
On 24.08.20 21:55:59, Joe Perches wrote:
> Use semicolons and braces.
>
> Signed-off-by: Joe Perches
> ---
> arch/alpha/kernel/pci_iommu.c | 8 +---
> arch/alpha/oprofile/op_model_ev4.c | 22 ++
> arch/alpha/oprofile/op_model_ev5.c | 8 +---
> 3 files changed,
The variable ret is being initialized with 'FAILED'. So we can remove
this assignement.
Signed-off-by: Jing Xiangfeng
---
drivers/scsi/megaraid/megaraid_sas_fusion.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/scsi/megaraid/megaraid_sas_fusion.c
On Mon, Aug 24, 2020 at 11:16:55AM -0700, Jakub Kicinski wrote:
> On Sun, 23 Aug 2020 13:50:42 +0530 Himadri Pandya wrote:
> > Initialize the buffer before passing it to usb_read_cmd() function(s) to
> > fix the uninit-was-stored issue in asix_read_cmd().
> >
> > Fixes: KMSAN: kernel-infoleak in
Fix a compile error on F32 and gcc version 10.1 on s390 in file
utils/stat-display.c. The error does not show up with make DEBUG=y.
In fact the issue shows up when using both compiler options
-O6 and -D_FORTIFY_SOURCE=2 (which are omitted with DEBUG=Y).
This is the offending call chain:
This patch fix following issue.
Controller slots blocked for devices with static_addr
but no init_dyn_addr may limit the number of I3C devices
on the bus which gets dynamic address in DAA. So
instead of attaching all the devices with static_addr,
now we only attach the devices which successfully
When radeon_kick_out_firmware_fb() fails, info should be
freed just like the subsequent error paths.
Fixes: 069ee21a82344 ("fbdev: Fix loading of module radeonfb on PowerMac")
Signed-off-by: Dinghao Liu
---
drivers/video/fbdev/aty/radeon_base.c | 2 +-
1 file changed, 1 insertion(+), 1
On 24-08-20, 22:02, Ionela Voinescu wrote:
> From: Valentin Schneider
>
> The passed cpumask arguments to arch_set_freq_scale() and
> arch_freq_counters_available() are only iterated over, so reflect this
> in the prototype. This also allows to pass system cpumasks like
> cpu_online_mask without
On 24-08-20, 22:02, Ionela Voinescu wrote:
> Now that the update of the FI scale factor is done in cpufreq core for
> selected functions - target(), target_index() and fast_switch(),
> we can provide feedback to the task scheduler and architecture code
> on whether cpufreq supports FI.
>
> For
Please ignore this patch.
Regards,
Parshuram Thombare
>-Original Message-
>From: Parshuram Thombare
>Sent: Tuesday, August 25, 2020 11:51 AM
>To: bbrezil...@kernel.org; vitor.soa...@synopsys.com
>Cc: Przemyslaw Gaj ; linux-...@lists.infradead.org; linux-
>ker...@vger.kernel.org; Milind
Hi Mike,
On Tue, Aug 25, 2020 at 12:21:03AM +, Mike Stunes wrote:
> Thanks for the new update! I still see the same FSGSBASE behavior on our
> platform.
>
> That is, APs come up offline; masking out either FSGSBASE or RDPID from the
> guest's CPUID results in all CPUs online.
>
> Is that
Hello Krzysztof,
On Mon, 2020-08-24 at 21:06 +0200, Krzysztof Kozlowski wrote:
> The input clock and number of clock provider cells are not required
> for
> the PMIC to operate. They are needed only for the optional bd718x7
> clock driver.
I have always found the DT bindings hard to do. I
On Fri, Aug 21, 2020 at 08:32:20PM +0800, Kai-Heng Feng wrote:
> New Intel laptops with VMD cannot reach deeper power saving state,
> renders very short battery time.
So what about just disabling VMD given how bloody pointless it is?
Hasn't anyone learned from the AHCI remapping debacle?
I'm
On Mon, Aug 24, 2020 at 06:12:38PM +0200, Borislav Petkov wrote:
> > -DEFINE_PER_CPU(struct mce, injectm);
> > +DEFINE_PER_CPU_ALIGNED(struct mce, injectm);
> > EXPORT_PER_CPU_SYMBOL_GPL(injectm);
>
> I don't think this is the right fix.
Agreed :) This is a debug patch, what we want is to root
This patch fixes the following issue.
Controller slots blocked for the devices with only static_addr
or init_dyn_addr may limit the number of I3C devices
on the bus which gets dynamic address in DAA. So
instead of attaching all the devices with static_addr,
now we only attach the devices which
On Mon, 2020-08-24 at 19:42 +0200, Rafael J. Wysocki wrote:
> From: "Rafael J. Wysocki"
>
> Make the energy_performance_preference policy attribute in sysfs
> always return the last EPP value written to it instead of the one
> currently in the HWP Request MSR to avoid possible confusion when
>
Since commit ("arm64/kvm: Add generic v8 KVM target"),
there is no negative number returned from kvm_target_cpu(). So it's
not needed to validate its return value in kvm_vcpu_preferred_target()
and this just drops the unnecessary check.
Signed-off-by: Gavin Shan
---
arch/arm64/kvm/guest.c | 3
The target CPU type is validated when KVM module is initialized.
However, we always have a valid target CPU type since commit
("arm64/kvm: Add generic v8 KVM target").
So it's unnecessary to validate the target CPU type at that time
and this just drops it.
Signed-off-by: Gavin Shan
---
On 8/24/20 10:22 PM, Jiri Olsa wrote:
> On Wed, Aug 12, 2020 at 08:27:08AM -0300, Arnaldo Carvalho de Melo wrote:
>> Em Wed, Jul 22, 2020 at 11:20:53AM +0200, Thomas Richter escreveu:
>>> Fix a compile error on F32 and gcc version 10.1 on s390 in file
>>> utils/stat-display.c. The error does not
Hi Eddy,
On Mon, 24 Aug 2020 16:41:58 +
"eddy...@trendmicro.com" wrote:
> > -Original Message-
> > From: Masami Hiramatsu
> > Sent: Monday, August 24, 2020 11:54 PM
> > To: Eddy Wu (RD-TW)
> > Cc: Peter Zijlstra ; linux-kernel@vger.kernel.org;
> > x...@kernel.org; David S. Miller
On Fri, Aug 21, 2020 at 09:52:00AM +, Robin Gong wrote:
> On 2020/08/20 14:52 Sascha Hauer wrote:
> > On Wed, Aug 19, 2020 at 01:08:29PM +0200, Lars-Peter Clausen wrote:
> > > > For the first option, which is potentially more performant, we have
> > > > to leave the atomic PCM context and we
While running LTP tracing ftrace-stress-test kernel on x86_64 got panic on
stable rc 4.19 branch. I have checked this kernel panic has been happening from
the beginning of 4.19 release. I will run git bisect starting from
4.18 and get back to you
on this email thread.
steps to reproduce:
# Boot
On 24-08-20, 22:02, Ionela Voinescu wrote:
> To properly scale its per-entity load-tracking signals, the task scheduler
> needs to be given a frequency scale factor, i.e. some image of the current
> frequency the CPU is running at. Currently, this scale can be computed
> either by using counters
Hello,
syzbot found the following issue on:
HEAD commit:da2968ff Merge tag 'pci-v5.9-fixes-1' of git://git.kernel...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=153afba690
kernel config: https://syzkaller.appspot.com/x/.config?x=a0437fdd630bee11
Hello,
syzbot found the following issue on:
HEAD commit:da2968ff Merge tag 'pci-v5.9-fixes-1' of git://git.kernel...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=159763ce90
kernel config: https://syzkaller.appspot.com/x/.config?x=bb68b9e8a8cc842f
On Fri, 21 Aug 2020, Will Deacon wrote:
> On Sun, Aug 02, 2020 at 08:53:20AM +0200, Lukas Bulwahn wrote:
> > Commit e86d1aa8b60f ("iommu/arm-smmu: Move Arm SMMU drivers into their own
> > subdirectory") moved drivers/iommu/qcom_iommu.c to
> > drivers/iommu/arm/arm-smmu/qcom_iommu.c amongst
1201 - 1286 of 1286 matches
Mail list logo
