tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 9ebcfadb0610322ac537dd7aa5d9cbc2b2894c68
commit: 0e4a459f56c32d3e52ae69a4b447db2f48a65f44 tracing: Remove unnecessary
DEBUG_FS dependency
date: 7 months ago
config: powerpc-randconfig-m031-20200629
From: Vladimir Oltean
Date: Sun, 28 Jun 2020 17:49:35 +0300
> Fixes sparse warning:
>
> Function parameter or member 'pbuflen' not described in 'packing'
>
> Fixes: 554aae35007e ("lib: Add support for generic packing operations")
> Signed-off-by: Vladimir Oltean
> ---
> Hi David, since the
From: Horatiu Vultur
Date: Sun, 28 Jun 2020 15:45:16 +0200
> The following sparse warnings are fixed:
> net/bridge/br_mrp.c:106:18: warning: incorrect type in assignment (different
> base types)
> net/bridge/br_mrp.c:106:18:expected unsigned short [usertype]
> net/bridge/br_mrp.c:106:18:
On 20-06-26 07:19:56, Pawel Laszczak wrote:
> Hi Felipe,
>
> >
> >Hi,
> >
> >Pawel Laszczak writes:
> >> This patch introduce new Cadence USBSS DRD driver to linux kernel.
> >>
> >> The Cadence USBSS DRD Controller is a highly configurable IP Core which
> >> can be instantiated as Dual-Role
From: Luo bin
Date: Sun, 28 Jun 2020 20:36:19 +0800
> patch #1: support to set and get pause params with
> "ethtool -A/a" cmd
> patch #2: support to set and get irq coalesce params with
> "ethtool -C/c" cmd
> patch #3: support to do self test with "ethtool -t" cmd
> patch #4:
Fixes: 9fe55eea7e4b ("Fix race when checking i_size on direct i/o read").
This commit caused ext4 direct I/O read error when the read size is not
alignment with block size.
Then, I will use a test to explain the error.
(1) Make the file that is not alignment with block size:
$dd
On Mon, 2020-06-29 at 11:12 +0800, Pkshih wrote:
> On Sun, 2020-06-28 at 19:51 -0700, j...@perches.com wrote:
> > On 2020-06-28 19:09, Pkshih wrote:
> > > On Sun, 2020-06-28 at 03:17 -0700, Joe Perches wrote:
> > >
> > > Use 'rtlwifi:' as subject title prefix is enough, likes
> > > rtlwifi: Use
With legacy PM, drivers themselves were responsible for managing the
device's power states and takes care of register states.
After upgrading to the generic structure, PCI core will take care of
required tasks and drivers should do only device-specific operations.
The driver was invoking PCI
With legacy PM, drivers themselves were responsible for managing the
device's power states and takes care of register states.
After upgrading to the generic structure, PCI core will take care of
required tasks and drivers should do only device-specific operations.
The driver was invoking PCI
Linux Kernel Mentee: Remove Legacy Power Management.
The purpose of this patch series is to remove legacy power management callbacks
from amd ethernet drivers.
The callbacks performing suspend() and resume() operations are still calling
pci_save_state(), pci_set_power_state(), etc. and handling
Excerpts from Linus Torvalds's message of June 28, 2020 3:39 pm:
> On Fri, Jun 26, 2020 at 8:43 AM Peter Zijlstra wrote:
>>
>> I ended up with something like the below.. but it is too warm to think
>> properly.
>>
>> I don't particularly like WQ_FLAG_PAGEWAITERS, but I liked open-coding
>> all
From: Randy Dunlap
sound/soc/soc-io.c was merged into sound/soc/soc-component.c, so fixup
the Documentation to use the updated file name.
Error: Cannot open file ../sound/soc/soc-io.c
WARNING: kernel-doc '../scripts/kernel-doc -rst -enable-lineno
../sound/soc/soc-io.c' failed with return code
Add performance monitor unit DT node in SiFive Fu540 soc-specific DT
file. This pmu node passes the dtbs_check verification.
Signed-off-by: Zong Li
---
arch/riscv/boot/dts/sifive/fu540-c000.dtsi | 13 +
1 file changed, 13 insertions(+)
diff --git
This patch set adds raw event support on RISC-V. In addition, we
introduce the DT mechanism to make our perf more generic and common.
Currently, we set the hardware events by writing the mhpmeventN CSRs, it
would raise an illegal instruction exception and trap into m-mode to
emulate event
Add device tree bindings for performance monitor unit. And it passes the
dt_binding_check verification.
Signed-off-by: Zong Li
---
.../devicetree/bindings/riscv/pmu.yaml| 59 +++
1 file changed, 59 insertions(+)
create mode 100644
The hpmcounter CSRs are used for perf to read the value of monitoring
hardware events.
Signed-off-by: Zong Li
---
arch/riscv/include/asm/csr.h | 58
1 file changed, 58 insertions(+)
diff --git a/arch/riscv/include/asm/csr.h b/arch/riscv/include/asm/csr.h
Add support for raw events and hardware cache events. Currently, we set
the events by writing the mhpmeventN CSRs, it would raise an illegal
instruction exception and trap into m-mode to emulate event selector
CSRs access. It doesn't make sense because we shouldn't write the
m-mode CSRs in s-mode,
We only one instance of riscv_pmu now, and use DT file to describe the
platform-specific information, so drop the dependency and menu of
RISCV_BASE_PMU.
Signed-off-by: Zong Li
---
arch/riscv/Kconfig | 13 -
arch/riscv/include/asm/perf_event.h | 2 --
Each architecture is responsible for mapping generic hardware and cache
events to their own specific encoding of hardware events. For each
architecture, it also have to distinguish the defination of hardware
events of different platforms of each vendor. We use DT file to describe
platform-specific
On Sun, 2020-06-28 at 19:51 -0700, j...@perches.com wrote:
> On 2020-06-28 19:09, Pkshih wrote:
> > On Sun, 2020-06-28 at 03:17 -0700, Joe Perches wrote:
> >
> > Use 'rtlwifi:' as subject title prefix is enough, likes
> > rtlwifi: Use const in swing_table declarations
>
> We disagree.
>
> I
> -Original Message-
> From: linux-fpga-ow...@vger.kernel.org
> On Behalf Of Xu Yilun
> Sent: Monday, June 29, 2020 10:19 AM
> To: t...@redhat.com
> Cc: m...@kernel.org; linux-f...@vger.kernel.org; linux-
> ker...@vger.kernel.org; Wu, Hao ;
> matthew.gerl...@linux.intel.com
> Subject: Re:
From: Randy Dunlap
Fix spelling of the 'langid' function argument in the kernel-doc
notation to quieten a kernel-doc warning.
../drivers/usb/gadget/usbstring.c:77: warning: Function parameter or member
'langid' not described in 'usb_validate_langid'
../drivers/usb/gadget/usbstring.c:77:
> Subject: Re: [PATCH] xen: introduce xen_vring_use_dma
>
> On Thu, Jun 25, 2020 at 10:31:27AM -0700, Stefano Stabellini wrote:
> > On Wed, 24 Jun 2020, Michael S. Tsirkin wrote:
> > > On Wed, Jun 24, 2020 at 02:53:54PM -0700, Stefano Stabellini wrote:
> > > > On Wed, 24 Jun 2020, Michael S.
> Subject: Re: [PATCH] xen: introduce xen_vring_use_dma
>
> On Wed, 24 Jun 2020, Michael S. Tsirkin wrote:
> > On Wed, Jun 24, 2020 at 02:53:54PM -0700, Stefano Stabellini wrote:
> > > On Wed, 24 Jun 2020, Michael S. Tsirkin wrote:
> > > > On Wed, Jun 24, 2020 at 10:59:47AM -0700, Stefano
Add a binding for the Tegra20-based Acer Iconia Tab A500 tablet device.
Acked-by: Rob Herring
Signed-off-by: Dmitry Osipenko
---
Documentation/devicetree/bindings/arm/tegra.yaml | 3 +++
1 file changed, 3 insertions(+)
diff --git a/Documentation/devicetree/bindings/arm/tegra.yaml
There are few hardware variants of NVIDIA Tegra30-based Nexus 7 device:
1. WiFi-only (named Grouper)
2. GSM (named Tilapia)
3. Using Maxim PMIC (E1565 board ID)
4. Using Ti PMIC (PM269 board ID)
This patch adds device-trees for known and tested variants.
Link:
Hello,
This series introduces upstream kernel support for Acer Iconia Tab A500
and ASUS Google Nexus 7 tablet devices. Please review and apply, thanks
in advance.
Changelog:
v10:- Rebased on a recent linux-next which got some device-tree changes:
- Renamed sdhci@ DT nodes to mmc@
Add device-tree for Acer Iconia Tab A500, which is NVIDIA Tegra20-based
tablet device.
Signed-off-by: Dmitry Osipenko
---
arch/arm/boot/dts/Makefile|1 +
.../boot/dts/tegra20-acer-a500-picasso.dts| 1438 +
2 files changed, 1439 insertions(+)
create
Add a binding for the Tegra30-based ASUS Google Nexus 7 tablet device.
Acked-by: Rob Herring
Signed-off-by: Dmitry Osipenko
---
Documentation/devicetree/bindings/arm/tegra.yaml | 7 +++
1 file changed, 7 insertions(+)
diff --git a/Documentation/devicetree/bindings/arm/tegra.yaml
Enable several very useful options and drivers for hardware that is found
on Nexus 7 and Acer A500 tablet devices. Please note that some drivers may
require firmware files extracted from original Android image.
Link: https://github.com/grate-driver/linux-firmware
Link:
Acer is a hardware and electronics corporation, specializing in advanced
electronics technology. Acer's products include desktop PCs, laptop PCs,
tablets, servers, displays, storage devices, virtual reality devices,
smartphones and peripherals. Their web site is http://www.acer.com/.
Acked-by:
From: Randy Dunlap
Fix kernel-doc warnings in :
../include/linux/usb.h:713: warning: Function parameter or member
'use_generic_driver' not described in 'usb_device'
../include/linux/usb.h:1253: warning: Function parameter or member 'match' not
described in 'usb_device_driver'
From: Xiaowei Bao
Add the DSPI flash nodes into fsl-ls1028a-qds.dts
Signed-off-by: Xiaowei Bao
Signed-off-by: Zhao Qiang
---
Changes for v2
- correct commit msg
arch/arm64/boot/dts/freescale/fsl-ls1028a-qds.dts | 85 +++
1 file changed, 85 insertions(+)
diff --git
From: "Steven Rostedt (VMware)"
After a discussion with the new time algorithm to have nested events still
have proper time keeping but required using local64_t atomic operations.
Mathieu was concerned about the performance this would have on 32 bit
machines, as in most cases, atomic 64 bit
From: "Steven Rostedt (VMware)"
Instead of calling out the absolute test for each time to check if the
ring buffer wants absolute time stamps for all its recording, incorporate it
with the add_timestamp field and turn it into flags for faster processing
between wanting a absolute tag and needing
From: "Steven Rostedt (VMware)"
Up until now, if an event is interrupted while it is recorded by an
interrupt, and that interrupt records events, the time of those events will
all be the same. This is because events only record the delta of the time
since the previous event (or beginning of a
V1 of this patch set can be found here:
https://lore.kernel.org/r/20200627010041.517736...@goodmis.org
Changes since V1 patch set:
- Fixed white space issues (kernel test robot)
- Fixed change log algorithm to match the code (Masami Hiramatsu)
- Removed next_write useless code. (Masami
On 2020-06-28 19:09, Pkshih wrote:
On Sun, 2020-06-28 at 03:17 -0700, Joe Perches wrote:
Use 'rtlwifi:' as subject title prefix is enough, likes
rtlwifi: Use const in swing_table declarations
We disagree.
I like knowing what content is changed via patch subject lines
as there are 3 rtlwifi
> From: Anson Huang
> Sent: Friday, June 26, 2020 5:14 AM
>
> The i.MX SCU soc driver depends on SCU firmware driver, so it has to use
> platform driver model for proper defer probe operation, since it has no device
> binding in DT file, a simple platform device is created together inside the
>
Hi Mark,
> From: Mark Brown, Sent: Saturday, June 27, 2020 12:14 AM
>
> On Fri, Jun 26, 2020 at 06:32:21PM +0900, Yoshihiro Shimoda wrote:
> > Note that this is possible to happen when the regulator-fixed driver
> > turns the vmmc and vqmmc off by firmware like PSCI while the system
> > is
On Sat, Jun 27, 2020 at 04:55:07AM +, Long Li wrote:
> Environment using the slub allocator, 1G memory in my ARM32.
> kmalloc(1024, GFP_HIGHUSER) can allocate memory normally,
> kmalloc(64*1024, GFP_HIGHUSER) will cause a memory leak, because
> alloc_pages returns highmem physical pages, but
Hi Mark,
> From: Mark Brown, Sent: Friday, June 26, 2020 11:39 PM
>
> On Fri, Jun 26, 2020 at 06:32:20PM +0900, Yoshihiro Shimoda wrote:
>
> > +static int reg_is_enabled(struct regulator_dev *rdev)
> > +{
> > + struct fixed_voltage_data *priv = rdev_get_drvdata(rdev);
> > +
> > + return
Hi Marc,
On 6/23/20 12:28 AM, Marc Zyngier wrote:
> Booting a recent kernel on a rk3399-based system (nanopc-t4),
> equipped with a recent u-boot and ATF results in the following:
>
> [5.607431] Unable to handle kernel NULL pointer dereference at virtual
> address 01e4
> [
NVIDIA's Tegra194 SoC uses two ARM MMU-500s together to interleave
IOVA accesses across them.
Add NVIDIA implementation for dual ARM MMU-500s and add new compatible
string for Tegra194 SoC SMMU topology.
Signed-off-by: Krishna Reddy
---
MAINTAINERS | 2 +
Add global/context fault hooks to allow NVIDIA SMMU implementation
handle faults across multiple SMMUs.
Signed-off-by: Krishna Reddy
---
drivers/iommu/arm-smmu-nvidia.c | 101 +++-
drivers/iommu/arm-smmu.c| 17 +-
drivers/iommu/arm-smmu.h| 3 +
Changes in v7:
Incorporated the review feedback from Nicolin Chen, Robin Murphy and Thierry
Reding.
Rebased and validated patches on top of
git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu.git next
v6- https://lkml.org/lkml/2020/6/4/1018
v5 - https://lkml.org/lkml/2020/5/21/1114
v4 -
Add binding for NVIDIA's Tegra194 SoC SMMU topology that is based
on ARM MMU-500.
Signed-off-by: Krishna Reddy
---
Documentation/devicetree/bindings/iommu/arm,smmu.yaml | 5 +
1 file changed, 5 insertions(+)
diff --git a/Documentation/devicetree/bindings/iommu/arm,smmu.yaml
I think maybe we don't have to select them all. It is now possible for
FPGA DFL boards to work without FME or AFU, providing limited
functionality. It is possible designers trim the bitstream for their
purpose, and also need a smaller driver set.
I think we may add "default FPGA_DFL" for
Since 'tcfp_burst' with TICK factor, driver side always need to recover
it to the original value, this patch moves the generic calculation and
recover to the 'burst' original value before offloading to device driver.
Signed-off-by: Po Liu
Signed-off-by: Vladimir Oltean
---
Hi Linus:
This push fixes two race conditions, one in padata and one in
af_alg.
The following changes since commit 819966c06b759022e9932f328284314d9272b9f3:
crypto: drbg - always try to free Jitter RNG instance (2020-06-15 17:38:54
+1000)
are available in the Git repository at:
Hi Josh, will you please have a look at this patchset?
There might be another way to set SHT_PROGBITS of section .orc_lookup by
writing section headers when orc_unwind and orc_unwind_ip tables are writen. It
might be as follows:
diff --git a/tools/objtool/orc_gen.c b/tools/objtool/orc_gen.c
On 26-06-20, 09:24, Quentin Perret wrote:
> On Friday 26 Jun 2020 at 09:21:42 (+0530), Viresh Kumar wrote:
> > The locking around governors handling isn't adequate currently. The list
> > of governors should never be traversed without locking in place. Also we
> > must make sure the governor isn't
Hi Mark,
> From: Mark Brown, Sent: Friday, June 26, 2020 11:30 PM
>
> On Fri, Jun 26, 2020 at 06:32:19PM +0900, Yoshihiro Shimoda wrote:
>
> > The regulator-fixed driver is possible to be off by firmware
> > like PSCI while the system is suspended. If a consumer could get
> > such a condition
On Sun, 2020-06-28 at 03:17 -0700, Joe Perches wrote:
Use 'rtlwifi:' as subject title prefix is enough, likes
rtlwifi: Use const in swing_table declarations
> Reduce data usage about 1KB by using const.
>
> Signed-off-by: Joe Perches
> ---
> .../net/wireless/realtek/rtlwifi/rtl8188ee/dm.c
On 26-06-20, 16:57, Quentin Perret wrote:
> On Friday 26 Jun 2020 at 09:21:44 (+0530), Viresh Kumar wrote:
> > index e798a1193bdf..93c6399c1a42 100644
> > --- a/drivers/cpufreq/cpufreq.c
> > +++ b/drivers/cpufreq/cpufreq.c
> > @@ -50,6 +50,9 @@ static LIST_HEAD(cpufreq_governor_list);
> > #define
Current police action must set 'rate' and 'burst'. 'mtu' parameter
set the max frame size and could be set alone without 'rate' and 'burst'
in some situation. Offloading to hardware for example, 'mtu' could limit
the flow max frame size.
Signed-off-by: Po Liu
---
v1->v2 changes:
- fix the print
On 26-06-20, 10:05, Krzysztof Kozlowski wrote:
> Fix dtschema validator warnings like:
> l2-cache: $nodename:0: 'l2-cache' does not match
> '^(cache-controller|cpu)(@[0-9a-f,]+)*$'
>
> Signed-off-by: Krzysztof Kozlowski
> ---
> arch/arm/boot/dts/spear13xx.dtsi | 2 +-
> 1 file changed, 1
Change the double quotes to single quotes in fprintf message to make it
more readable.
Signed-off-by: Po Liu
---
v1->v2 changes:
- Patch new added
tc/m_police.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/tc/m_police.c b/tc/m_police.c
index a5bc20c0..7eb47f8e
Hi Qiangming:
Do you have the specific timing cost data about the "continuous mode"?
Is it better than the default multi-write mode(one message by one
message) ?I need to know if this patch is very necessary.
On Fri, 2020-06-19 at 16:06 +0800, Qiangming Xia wrote:
> From: "qiangming.xia"
On Thu, Jun 25, 2020 at 11:57 PM Lee Jones wrote:
>
> On Thu, 25 Jun 2020, Masahiro Yamada wrote:
>
> > On Thu, Jun 25, 2020 at 3:16 AM Lee Jones wrote:
> > >
> > > On Thu, 25 Jun 2020, Masahiro Yamada wrote:
> > >
> > > > On Tue, Jun 23, 2020 at 9:24 PM Lee Jones wrote:
> > > > >
> > > > > On
On 2020-06-26 15:31, Peter Xu wrote:
This is a preparation patch to move page fault accountings into the general
code in handle_mm_fault(). This includes both the per task flt_maj/flt_min
counters, and the major/minor page fault perf events. To do this, the pt_regs
pointer is passed into
Hi,
On Sat, 2020-06-27 at 14:28 +0200, Markus Elfring wrote:
> Hello,
>
> A source code analysis approach by the means of the semantic patch language
> (Coccinelle software) pointed an implementation detail out for further
> development considerations.
>
> The functions “mtu3_gadget_ep_set_halt”
Hi Sameer
> dpcm_end_walk_at_be() stops the graph walk when first BE is found for
> the given FE component. In a component model we may want to connect
> multiple DAIs from different components. A new flag is introduced in
> 'snd_soc_card', which when set allows DAI/component chaining. Later
>
Hi Sylwester,
On 6/25/20 12:11 AM, Sylwester Nawrocki wrote:
> Hi All,
>
> On 24.06.2020 12:32, Lukasz Luba wrote:
>> I had issues with devfreq governor which wasn't called by devfreq
>> workqueue. The old DELAYED vs DEFERRED work discussions and my patches
>> for it [1]. If the CPU which
On 2020/6/24 15:54, Vinod Koul wrote:
On 09-06-20, 09:14, Sugar Zhang wrote:
There is no reason to limit the performance on the 'NO-FLUSHP' SoCs,
cuz these platforms are just that the 'FLUSHP' instruction is broken.
Lets not use terms like cuz... 'because' is perfect term :)
It can
Hi Sameer
> PCM devices are created for dai links with 'no-pcm' flag as '0'.
> Such DAI links have CPU component which implement pcm_construct()
> and pcm_destruct() callbacks. Based on this, current patch exposes
> a helper function to identify such components and populate 'no_pcm'
> flag for
On 2020-06-28 16:01, Matias Bjørling wrote:
> + /* This may take a while, so be nice to others */
> + cond_resched();
> +
> + return submit_bio_wait();
A cond_resched() call before a submit_bio_wait() call? I think it's the
first time that I see this. Is that call really necessary?
Hi,
Sorry for late reply because of my perfornal issue. I count not check the email.
On 6/26/20 8:22 PM, Bartlomiej Zolnierkiewicz wrote:
>
> On 6/25/20 2:12 PM, Kamil Konieczny wrote:
>> On 25.06.2020 14:02, Lukasz Luba wrote:
>>>
>>>
>>> On 6/25/20 12:30 PM, Kamil Konieczny wrote:
Hi
On Sun, Jun 28, 2020 at 06:34:46PM +0800, Baolin Wang wrote:
> Move the sg table allocation and free into the init_request() and
> exit_request(), instead of allocating sg table when queuing requests,
> which can benefit the IO performance.
If you want to pre-allocate something per-request, you
Hi Sameer
> The simple-card driver supports multiple CPU and single Codec entries
> for DPCM DAI links. In some cases it is required to have multiple
> CPU/Codecs. Currently parsing logic for DPCM link loops over all
> children of DAI link but assumes that there is a single Codec entry.
> When
Free buf before returning to avoid memory leak.
Signed-off-by: Gaurav Singh
---
scripts/insert-sys-cert.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/scripts/insert-sys-cert.c b/scripts/insert-sys-cert.c
index 8902836c2342..22d99a8faca9 100644
--- a/scripts/insert-sys-cert.c
+++
When adding first socket to nbd, if nsock's allocation failed, the data
structure member "config->socks" was reallocated, but the data structure
member "config->num_connections" was not updated. A memory leak will occur
then because the function "nbd_config_put" will free "config->socks" only
when
Hi all,
Today's linux-next merge of the drm-misc tree got conflicts in:
drivers/gpu/drm/nouveau/dispnv04/crtc.c
drivers/gpu/drm/nouveau/dispnv04/overlay.c
drivers/gpu/drm/nouveau/dispnv50/base507c.c
drivers/gpu/drm/nouveau/dispnv50/wndw.c
drivers/gpu/drm/nouveau/nouveau_dmem.c
Hi Mike,
On 17/6/20 10:33 pm, Greg Ungerer wrote:
Hi Mike,
On 17/6/20 4:53 pm, Mike Rapoport wrote:
From: Mike Rapoport
The m68k nommu setup code didn't register the beginning of the physical
memory with memblock because it was anyway occupied by the kernel. However,
commit fa3354e4ea39
Hi Sameer
> CPU/Codec in DPCM DAI links are connected as CPU<->Dummy and Dummy<->Codec.
> Though mostly CPU won't use/require 'mclk-fs' property, looping over
> 'np' (current child node in a DAI link) can help in cases where multiple
> Codecs are defined. This further helps to get rid of
On 2020/06/29 8:01, Matias Bjorling wrote:
> The NVMe Zoned Namespace Command Set adds support for associating
> data to a zone through the Zone Descriptor Extension feature.
>
> To allow user-space to associate data to a zone, add support through
> the BLKSETDESCZONE ioctl. The ioctl requires
Hi Sameer
> simple-audio-card,dai-link@xxx {
> format = "i2s";
> bitclock-master=<>;
> frame-master=<>;
>
> cpu1: cpu@0 {
> ...
> };
>
> codec@0 {
> ...
> };
>
> ...
> };
>
> In above case CPU is expected to be configured as a
On 6/29/20 8:37 AM, Lai Jiangshan wrote:
> On Mon, Jun 29, 2020 at 8:13 AM Bob Liu wrote:
>>
>> On 6/28/20 11:54 PM, Lai Jiangshan wrote:
>>> On Thu, Jun 11, 2020 at 6:29 PM Bob Liu wrote:
Current code always set 'Unbound && max_active == 1' workqueues to ordered
implicitly, while
On Wed, Jun 17, 2020 at 12:02 PM Masahiro Yamada wrote:
>
> The conversion is done. No more user of '---help---'.
>
> Cc: Ulf Magnusson
> Signed-off-by: Masahiro Yamada
Applied to linux-kbuild.
> ---
>
> scripts/checkkconfigsymbols.py | 2 +-
> scripts/kconfig/lexer.l| 2 +-
> 2
On 2020/06/29 8:01, Matias Bjorling wrote:
> The NVMe Zoned Namespace Command Set adds support for associating
> data to a zone through the Zone Descriptor Extension feature.
>
> The Zone Descriptor Extension size is fixed to a multiple of 64
> bytes. A value of zero communicates the feature is
Hi Stephen,
> -Original Message-
> From: Stephen Hemminger
> Sent: 2020年6月29日 4:16
> To: Po Liu
> Cc: dsah...@gmail.com; linux-kernel@vger.kernel.org;
> net...@vger.kernel.org; da...@davemloft.net; j...@mojatatu.com;
> v...@buslov.dev; Claudiu Manoil ; Vladimir
> Oltean ; Alexandru
Hi Sameer
Thank you for your patch
# I guess there was ML registering magic until v3 ?
# This is 1st time for me to get this patch series...
> The "prefix" can be defined in DAI link node or it can be specified as
> part of the component node itself. Currently "sound-name-prefix" defined
> in
On Mon, Jun 29, 2020 at 8:13 AM Bob Liu wrote:
>
> On 6/28/20 11:54 PM, Lai Jiangshan wrote:
> > On Thu, Jun 11, 2020 at 6:29 PM Bob Liu wrote:
> >>
> >> Current code always set 'Unbound && max_active == 1' workqueues to ordered
> >> implicitly, while this may be not an expected behaviour for
On Sat, Jun 27, 2020 at 09:09:09AM -0400, Mikulas Patocka wrote:
>
>
> On Sat, 27 Jun 2020, Dave Chinner wrote:
>
> > On Fri, Jun 26, 2020 at 11:02:19AM -0400, Mikulas Patocka wrote:
> > > Hi
> > >
> > > I suggest to join memalloc_noio and memalloc_nofs into just one flag that
> > > prevents
Hi K,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on staging/staging-testing]
[also build test WARNING on v5.8-rc2 next-20200626]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use as
On Sat, June 27, 2020 12:56 AM, Uwe Kleine-König wrote:
> On Fri, Jun 26, 2020 at 01:17:29PM +, Roy Im wrote:
> > > On Fri, June 26, 2020 3:19 PM, Uwe Kleine-König wrote:
> > > Hello,
> > > from the PWM POV I'm happy now. Just a few minor comments that I noticed
> > > while checking the PWM
On 6/28/20 11:54 PM, Lai Jiangshan wrote:
> On Thu, Jun 11, 2020 at 6:29 PM Bob Liu wrote:
>>
>> Current code always set 'Unbound && max_active == 1' workqueues to ordered
>> implicitly, while this may be not an expected behaviour for some use cases.
>>
>> E.g some scsi and iscsi
On Sun, 28 Jun 2020 18:28:42 -0400
Steven Rostedt wrote:
> You create a bpf event just like you create any other event. When a bpf
> program that uses a bpf_trace_printk() is loaded, you can enable that
> event from within the kernel. Yes, there's internal interfaces to
> enabled and disable
On Tue, May 19, 2020 at 2:36 PM Sasha Levin wrote:
>
> Hi Daniel,
>
> On Tue, May 19, 2020 at 09:21:15PM +0200, Daniel Vetter wrote:
> >Hi Sasha
> >
> >So obviously great that Microsoft is trying to upstream all this, and
> >very much welcome and all that.
> >
> >But I guess there's a bunch of
Hello,
Here are some minor fixes for perf tools regarding *SEC_PER*SEC macro usage,
found while reading the code.
Patch 1 replaces a macro with a more suitable one (same value, different
name).
Patch 2 converts some hardcoded values (which seem appropriate IMHO) with
their
The values of interval and timeout are in msecs as documented in the
-I and --timeout options.
Use MSEC_PER_SEC instead USEC_PER_MSEC to convert to struct timespec.
Both macros have the same value 1000L (see tools/include/linux/time64.h).
No functional change intended.
builtin-stat.c: typecast macro to u64
see commit ea9eb1f456a0 ("perf stat: Fix duration_time value for higher
intervals")
No functional change intended.
Signed-off-by: Emmanouil Maroudas
---
tools/perf/builtin-record.c | 2 +-
tools/perf/builtin-stat.c | 4 ++--
The NVMe Zoned Namespace Command Set adds support for associating
data to a zone through the Zone Descriptor Extension feature.
The Zone Descriptor Extension size is fixed to a multiple of 64
bytes. A value of zero communicates the feature is not available.
A value larger than zero communites the
Hi,
This patchset adds support for the Zone Descriptor Extension feature
that is defined in the NVMe Zoned Namespace Command Set.
The feature adds support for associating data to a zone that is in
the Empty state. Upon successful completion, the specified zone
transitions to the Closed state and
The NVMe Zoned Namespace Command Set adds support for associating
data to a zone through the Zone Descriptor Extension feature.
To allow user-space to associate data to a zone, add support through
the BLKSETDESCZONE ioctl. The ioctl requires that it is issued to
a zoned block device, and that it
From: Alexander Usyskin
It's not needed to set driver to NULL in mei_cl_device_remove()
which is bus_type remove() handler as this is done anyway
in __device_release_driver().
Actually this is causing an endless loop in driver_detach()
on ubuntu patched kernel, while removing (rmmod) the
On Sat, 27 Jun 2020 at 07:04, Ralph Campbell wrote:
>
> If system memory is migrated to device private memory and no GPU MMU
> page table entry exists, the GPU will fault and call hmm_range_fault()
> to get the PFN for the page. Since the .dev_private_owner pointer in
> struct hmm_range is not
On Sun, 28 Jun 2020 15:02:09 -0700
Alexei Starovoitov wrote:
> >
> > Then do a bpf trace event and enable it when a bpf_trace_printk() is
> > loaded. It will work the same for your users.
>
> I'm not sure I follow. How that would preserve the expectation
> to see the output in
On Sat, Jun 27, 2020 at 09:48:21AM -0300, Arnaldo Carvalho de Melo wrote:
> Em Fri, Jun 26, 2020 at 02:57:59PM -0700, Andi Kleen escreveu:
> > > The name could be a metric or an event, the logic for each is quite
> >
> > I would say collisions are unlikely. Event names follow quite structured
> >
Well, we had a big merge window, and we have a fairly big rc3 here
too. The calm period for rc2 is clearly over.
That said, I don't think there's anything _particularly_ scary in
here, and the size of this rc is probably simply a direct result of
the fact that 5.8 is a big release. It's too early
1 - 100 of 364 matches
Mail list logo
