On Tue 16-02-21 14:30:15, Mike Kravetz wrote:
[...]
> However, this is an 'opt in' feature. So, I would not expect anyone who
> carefully plans the size of their hugetlb pool to enable such a feature.
> If there is a use case where hugetlb pages are used in a non-essential
> application, this
On Tue 16-02-21 13:53:12, David Rientjes wrote:
> On Tue, 16 Feb 2021, Michal Hocko wrote:
[...]
> > Overall, I am not really happy about this feature even when above is
> > fixed, but let's hear more the actual problem first.
>
> Shouldn't this behavior be possible as an oomd plugin instead,
On Tue, Feb 16, 2021 at 09:36:01PM -0500, Lyude Paul wrote:
> On Tue, 2021-02-16 at 20:08 +0200, Imre Deak wrote:
> > Hi,
> >
> > thanks for respinning this patchset, some comments below.
> >
> > On Fri, Feb 12, 2021 at 01:50:53PM -0500, Lyude Paul wrote:
> > > From: Tejas Upadhyay
> > >
> > >
The WARN_ON() argument is a condition, not an error message. So this
code will print a stack trace but will not print the warning message.
Fix that and also change it to only WARN_ONCE().
Fixes: 4ddb74165ae5 ("bpf: Extract nullable reg type conversion into a helper
function")
Signed-off-by: Dan
Hi Chaiwei,
On Wed, 17 Feb 2021 at 07:40, ChiaWei Wang wrote:
>
> Hi All,
>
> Do you have update on this patch series?
> Aspeed has subsequent LPC module upstream plan.
> We hope that the following patches can be on the basis of the fixed LPC
> layout.
Andrew has expressed his support for your
Hi All,
Do you have update on this patch series?
Aspeed has subsequent LPC module upstream plan.
We hope that the following patches can be on the basis of the fixed LPC layout.
Thanks.
Chiawei
> -Original Message-
> From: Andrew Jeffery
> Sent: Wednesday, January 27, 2021 8:25 AM
> To:
From: Mircea Caprioru
The AD5673R/AD5677R are low power, 16-channel, 12-/16-bit buffered voltage
output digital-to-analog converters (DACs). They include a 2.5 V internal
reference (enabled by default).
These devices are very similar to AD5674R/AD5679R, except that they
have an i2c interface.
Following a recent update to the IIO buffer infrastructure, this change
adds a basic example on how to access an IIO buffer via the new mmap()
interface.
The ioctl() for the high-speed mode needs to be enabled right from the
start, before setting any parameters via sysfs (length, enable, etc), to
From: Lars-Peter Clausen
Add support for the new mmap interface to IIO DMA buffer. This interface
allows to directly map the backing memory of a block to userspace. This is
especially advantageous for high-speed devices where the extra copy from
kernel space to userspace of the data incurs a
The type of the 'size' parameter in the block struct is size_t which is
64 bit wide on 64 bit archs.
When the mmap interface gets introduced, we will use a 32 bit field in the
block descriptor for the block size, which will cause some compiler-checks
to fail.
32 bits (4 GB) block sizes should be
A part of the logic in the iio_dma_buffer_exit() is required for the change
to add mmap support to IIO buffers.
This change splits the logic into a separate function, which will be
re-used later.
Signed-off-by: Alexandru Ardelean
---
drivers/iio/buffer/industrialio-buffer-dma.c | 45
This change takes the comment from the commit that introduces the IIO
high-speed buffer API, and formats it into rst format.
Signed-off-by: Alexandru Ardelean
---
Documentation/iio/iio_high_speed_buffers.rst | 100 +++
Documentation/iio/index.rst | 2 +
From: Lars-Peter Clausen
Add the necessary infrastructure to the IIO core to support an mmap based
interface to access the capture data.
The advantage of the mmap based interface compared to the read() based
interface is that it avoids an extra copy of the data between kernel and
userspace.
Changelog v3 -> v4:
*
https://lore.kernel.org/linux-iio/20210215143234.3248-5-alexandru.ardel...@analog.com/T/
* added patch 'iio: buffer-dma: reduce the type of block.size to u32'
- resolves error on 64 bit archs; 32 bit block size should be enough
* in patch 'iio: buffer-dma: Add mmap
This makes a few changes, notably:
- Removes the mutex primitive as it is not needed in the file
operation path. The read path had multiple spinlock acquisitions
with state changes that don't appear safe to reordering,
specifically around forced aborts.
- Removes multiple
This is a more typical pattern for having the platform specific drivers
store their own data around the generic driver data.
Signed-off-by: William A. Kennington III
---
drivers/char/ipmi/kcs_bmc.c | 40 +++---
drivers/char/ipmi/kcs_bmc.h | 13 +-
The generic kcs_bmc code shouldn't need to store data on behalf of the
platform specific driver that initializes it. Instead, have the platform
specific driver allocate memory and call a generic initialization
routine.
Signed-off-by: William A. Kennington III
---
drivers/char/ipmi/kcs_bmc.c
The generic kcs_bmc code doesn't care about how byte reads / writes are
implemented. This pushes that logic to the device specific handlers, so
that kcs_bmc doesn't need to understand registers and how to read
or write them.
Signed-off-by: William A. Kennington III
---
Platforms specific IRQ handles repeat the same logic, calling a
sub-handler in the kcs_bmc generic code that should just conform to the
irqhandler callback.
Signed-off-by: William A. Kennington III
---
drivers/char/ipmi/kcs_bmc.c | 10 +-
drivers/char/ipmi/kcs_bmc.h | 3
Greg Kroah-Hartman writes:
> On Tue, Feb 16, 2021 at 05:05:14PM +0100, Maciej Kwapulinski wrote:
>> --- /dev/null
>> +++ b/drivers/misc/gna/gna_driver.c
>> @@ -0,0 +1,65 @@
>> +// SPDX-License-Identifier: GPL-2.0-only
>> +// Copyright(c) 2017-2021 Intel Corporation
>> +
>> +#define pr_fmt(fmt)
Shuah Khan writes:
> On 2/16/21 12:53 AM, Felix Fietkau wrote:
>>
>> On 2021-02-16 08:03, Kalle Valo wrote:
>>> Shuah Khan wrote:
>>>
ath_tx_process_buffer() references ieee80211_find_sta_by_ifaddr()
return pointer (sta) outside null check. Fix it by moving the code
block under
On Tue, Feb 16, 2021 at 10:02 PM Jonathan Cameron wrote:
>
> On Mon, 15 Feb 2021 16:32:29 +0200
> Alexandru Ardelean wrote:
>
>
> Hi Alex,
>
> I'm a little nervous about adding the userspace interface used in this
> series, but it seems reasonable and as you say below, is close to what
> Analog
On Wed, Feb 17, 2021 at 11:07:14AM +0800, Ming Lei wrote:
> Do you think it is correct for ioctl(BLKRRPART) to always drop/re-add
> partition device node?
Yes, that is what it is designed to do. The only reason to call this
ioctl is when userspace software has written new partition table
On Tue, Feb 16, 2021 at 07:50:49PM +, Min Li wrote:
> >
> > Yes, that line.
> >
> > The documentation should tell you how to do that, as per my patch bot:
> >
> > - This looks like a new version of a previously submitted patch, but you
> > did not list below the --- line any changes from
On Wed, Feb 17, 2021 at 8:07 AM Selvakumar Elangovan
wrote:>
> Removed an unnecessary blank line before closing brace reported by
> checkpatch.pl
>
> Signed-off-by: Selvakumar Elangovan
> ---
> drivers/staging/mt7621-pci/pci-mt7621.c | 1 -
> 1 file changed, 1 deletion(-)
Reviewed-by: Sergio
Removed an unnecessary blank line before closing brace reported by
checkpatch.pl
Signed-off-by: Selvakumar Elangovan
---
drivers/staging/mt7621-pci/pci-mt7621.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/staging/mt7621-pci/pci-mt7621.c
b/drivers/staging/mt7621-pci/pci-mt7621.c
On Wed, Feb 17, 2021 at 6:33 AM Nathan Chancellor wrote:
>
> When using AMD's Optimizing C/C++ Compiler (AOCC), the build fails due
> to a # character in the version string, which is interpreted as a
> comment:
>
> $ make CC=clang defconfig init/main.o
> include/config/auto.conf.cmd:1374: ***
Hi Selvakumar,
On Wed, Feb 17, 2021 at 7:53 AM Selvakumar Elangovan
wrote:
>
> Removed an unecessary blank line before closing brace reported by
> checkpatch.pl
Typo:
s/unecessary/unnecessary/g
>
> Signed-off-by: Selvakumar Elangovan
> ---
> drivers/staging/mt7621-pci/pci-mt7621.c | 1 -
>
Hi upstream committee,
Please consider to merge this patch which resolved VP8 hardware encoding GPU
hang critical issue on Gen9 sku, and there is no performance regression on this
fix.
Best Regards,
Cooper
-Original Message-
From: kernel test robot
Sent: Monday, February 8, 2021
From: Menglong Dong
The bit mask for MSG_* seems a little confused here. Replace it
with BIT() to make it clear to understand.
Signed-off-by: Menglong Dong
---
v4:
- CC netdev
v3:
- move changelog here
v2:
- use BIT() instead of BIT_MASK()
---
include/linux/socket.h | 71
Removed an unecessary blank line before closing brace reported by
checkpatch.pl
Signed-off-by: Selvakumar Elangovan
---
drivers/staging/mt7621-pci/pci-mt7621.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/staging/mt7621-pci/pci-mt7621.c
b/drivers/staging/mt7621-pci/pci-mt7621.c
On Tue, Feb 16, 2021 at 04:25:20PM -0800, Si-Wei Liu wrote:
>
> > > The saved mvq->avail_idx will be used to recreate hardware virtq object
> > > and
> > > the used index in create_virtqueue(), once status DRIVER_OK is set. I
> > > suspect we should pass the index to mvq->used_idx in
> > >
Added the entries for all the files added as a part of driver support for
DCC(Data Capture and Compare).
Signed-off-by: Souradeep Chowdhury
---
MAINTAINERS | 8
1 file changed, 8 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 546aa66..f0d208a 100644
--- a/MAINTAINERS
+++
Add the DCC(Data Capture and Compare) device tree node entry along with
the addresses for register regions.
Signed-off-by: Souradeep Chowdhury
---
arch/arm64/boot/dts/qcom/sm8150.dtsi | 7 +++
1 file changed, 7 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/sm8150.dtsi
The DCC is a DMA Engine designed to capture and store data
during system crash or software triggers.The DCC operates
based on link list entries which provides it with data and
addresses and the function it needs to perform.These functions
are read,write and loop.Added the basic driver in this
The DCC is a DMA engine designed to store register values either in
case of a system crash or in case of software triggers manually done
by the user.Using DCC hardware and the sysfs interface of the driver
the user can exploit various functionalities of DCC.The user can specify
the register
Added the sysfs variables to expose the user space functionalities
like DCC enable,disable,configure addresses and software triggers.
Also added the necessary methods along with the same.
Signed-off-by: Souradeep Chowdhury
---
drivers/soc/qcom/dcc.c | 519
DCC(Data Capture and Compare) is a DMA engine designed for debugging
purposes.In case of a system
crash or manual software triggers by the user the DCC hardware stores the value
at the register
addresses which can be used for debugging purposes.The DCC driver provides the
user with sysfs
Documentation for Data Capture and Compare(DCC) device tree bindings
in yaml format.
Signed-off-by: Souradeep Chowdhury
---
.../devicetree/bindings/arm/msm/qcom,dcc.yaml | 49 ++
1 file changed, 49 insertions(+)
create mode 100644
Hi Vlastimil,
On 1/13/2021 9:35 PM, Vlastimil Babka wrote:
> On 1/12/21 10:21 AM, Faiyaz Mohammed wrote:
>> Reading the sys slab alloc_calls, free_calls returns the available object
>> owners, but the size of this file is limited to PAGE_SIZE
>> because of the limitation of sysfs attributes, it
On 16/02/2021 22:22, Dario Binacchi wrote:
> The fdd property of the tilcdc_panel_info structure must set the reqdly
> bit field (bit 12 to 19) of the raster control register. The previous
> statement set the least significant bit instead.
>
> Signed-off-by: Dario Binacchi
>
> ---
>
>
On 17.02.2021 03:13, Yang Shi wrote:
> Use per memcg's nr_deferred for memcg aware shrinkers. The shrinker's
> nr_deferred
> will be used in the following cases:
> 1. Non memcg aware shrinkers
> 2. !CONFIG_MEMCG
> 3. memcg is disabled by boot parameter
>
> Signed-off-by: Yang Shi
Hello Dan,
On 2/17/21 4:55 AM, Dan Williams wrote:
One small comment on patch5, otherwise looks good.
I take it back, patch5 looks good. I was going to ask about the return
value removal for dax_bus_remove(), but that would need struct
bus_type to change prototypes.
Changing struct
On Tue, Feb 16, 2021 at 7:15 PM Dmitry Vyukov wrote:
> > On Tue, Feb 16, 2021 at 06:50:20PM +0100, Jason A. Donenfeld wrote:
> > > On Tue, Feb 16, 2021 at 6:46 PM Jason A. Donenfeld
> > > wrote:
> > > > On Tue, Feb 16, 2021 at 6:28 PM Catalin Marinas
> > > > wrote:
> > > > > > hlist_add_head
On 17.02.2021 03:13, Yang Shi wrote:
> Currently the number of deferred objects are per shrinker, but some slabs,
> for example,
> vfs inode/dentry cache are per memcg, this would result in poor isolation
> among memcgs.
>
> The deferred objects typically are generated by __GFP_NOFS
Hi Matthew,
On 1/12/2021 5:52 PM, Matthew Wilcox wrote:
> On Tue, Jan 12, 2021 at 02:51:27PM +0530, Faiyaz Mohammed wrote:
>> @@ -5180,6 +5187,7 @@ static int any_slab_objects(struct kmem_cache *s)
>>
>> struct slab_attribute {
>> struct attribute attr;
>> +struct bin_attribute
On 17.02.2021 03:13, Yang Shi wrote:
> Using kvfree_rcu() to free the old shrinker_maps instead of call_rcu().
> We don't have to define a dedicated callback for call_rcu() anymore.
>
> Signed-off-by: Yang Shi
Acked-by: Kirill Tkhai
> ---
> mm/vmscan.c | 7 +--
> 1 file changed, 1
On Tue, Feb 16, 2021 at 10:59:51PM -0500, Sean Behan wrote:
> ---
> drivers/staging/emxx_udc/emxx_udc.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/drivers/staging/emxx_udc/emxx_udc.c
> b/drivers/staging/emxx_udc/emxx_udc.c
> index 3536c03ff523..741147a4f0fe 100644
> ---
Hi Luc,
First bad commit (maybe != root cause):
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: f40ddce88593482919761f74910f42f4b84c004b
commit: e5fc436f06eef54ef512ea55a9db8eb9f2e76959 sparse: use static inline for
__chk_{user,io}_ptr()
date: 6
From: Vincent Cheng
Code clean-up.
Signed-off-by: Vincent Cheng
---
drivers/ptp/ptp_clockmatrix.c | 5 +
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/drivers/ptp/ptp_clockmatrix.c b/drivers/ptp/ptp_clockmatrix.c
index 241bff0..dc42c36 100644
---
From: Vincent Cheng
This series fixes a race condition that may result in the output clock
not aligned to internal 1 PPS clock.
Part of device initialization is to align the rising edge of output
clocks to the internal rising edge of the 1 PPS clock. If the system
APLL and DPLL are not locked
From: Vincent Cheng
When enabling output using PTP_CLK_REQ_PEROUT, need to align the output
clock to the internal 1 PPS clock.
Signed-off-by: Vincent Cheng
Acked-by: Richard Cochran
---
drivers/ptp/ptp_clockmatrix.c | 16 +---
1 file changed, 13 insertions(+), 3 deletions(-)
From: Vincent Cheng
Code clean-up.
* Remove unnecessary \n termination from dev_*() messages.
* Remove 'char *fmt' to define strings to stay within 80 column
limit. Not needed since coding guidelines increased to
100 columns limit.
Keeping format in place allows static code checkers to
On 2/17/21 2:39 PM, Namjae Jeon wrote:
Hi Hyeongseok,
Do you have any other opinion about this?
I also think this patch should be combined with the 2/2 patch.
If you agree, I'll merge these as one.
Yep, Agreed. Please do that:)
Thanks!
Thank you for the opinion.
I sent out v3.
From: Vincent Cheng
Code clean-up.
* Remove blank line between variable declarations.
* Remove blank line between:
err = blah(...)
if (err)
...
* Remove unnecessary blank line before/after loop constructs.
Signed-off-by: Vincent Cheng
---
This is for adding FITRIM ioctl functionality to exFAT filesystem.
To do that, add generic ioctl function and FITRIM handler.
Changelog
=
v2->v3:
- Remove unnecessary local variable
- Merge all changes to a single patch
v1->v2:
- Change variable declaration order as reverse tree style.
-
Add FITRIM ioctl to enable discarding unused blocks while mounted.
As current exFAT doesn't have generic ioctl handler, add empty ioctl
function first, and add FITRIM handler.
Signed-off-by: Hyeongseok Kim
---
fs/exfat/balloc.c | 81 +
From: Vincent Cheng
Part of the device initialization aligns the rising edge of the output
clock to the internal 1 PPS clock. If the system APLL and DPLL is not
locked, then the alignment will fail and there will be a fixed offset
between the internal 1 PPS clock and the output clock.
After
From: Vincent Cheng
Removed unused header declarations.
Signed-off-by: Vincent Cheng
---
drivers/ptp/ptp_clockmatrix.h | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/ptp/ptp_clockmatrix.h b/drivers/ptp/ptp_clockmatrix.h
index 0233236..fb32327 100644
---
From: Vincent Cheng
Code clean-up.
Signed-off-by: Vincent Cheng
---
drivers/ptp/ptp_clockmatrix.c | 18 --
1 file changed, 8 insertions(+), 10 deletions(-)
diff --git a/drivers/ptp/ptp_clockmatrix.c b/drivers/ptp/ptp_clockmatrix.c
index dc42c36..75463c2 100644
---
On 17/02/21 7:46 am, Adrian Hunter wrote:
> On 17/02/21 7:22 am, DooHyun Hwang wrote:
>> This makes to handle read errors faster by not retrying
>> multiple block read(CMD18) errors with single block reads(CMD17).
>>
>> On some bad SD Cards that have problem with read operations,
>> it is not
Hi Thara,
On 16-02-21, 19:00, Thara Gopinath wrote:
> This is a fix for a regression observed on db845 platforms with 5.7-rc11
> kernel. On these platforms running stress tests with 5.11-rc7 kernel
> causes big cpus to overheat and ultimately shutdown the system due to
> hitting critical
freq_qos_update_request() returns 1 if the effective constraint value
has changed, 0 if the effective constraint value has not changed, or a
negative error code on failures.
The frequency constraints for CPUs can be set by different parts of the
kernel. If the maximum frequency constraint set by
The commit 36b238d57172 ("psi: Optimize switching tasks inside shared
cgroups") only update cgroups whose state actually changes during a
task switch only in task preempt case, not in task sleep case.
We actually don't need to clear and set TSK_ONCPU state for common cgroups
of next and prev task
On 17/02/21 7:22 am, DooHyun Hwang wrote:
> This makes to handle read errors faster by not retrying
> multiple block read(CMD18) errors with single block reads(CMD17).
>
> On some bad SD Cards that have problem with read operations,
> it is not helpful to retry multiple block read errors with
>
Segher Boessenkool writes:
> Hi!
>
> On Tue, Feb 16, 2021 at 08:36:02PM +1100, Michael Ellerman wrote:
>> Feng Tang writes:
>> > {standard input}:577: Error: unsupported relocation against base
>> > {standard input}:580: Error: unsupported relocation against base
>> > {standard input}:583:
On Tue, Feb 16, 2021 at 09:21:14PM -0800, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit:dcc0b490 Merge tag 'powerpc-5.11-8' of git://git.kernel.or..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=1316c614d0
>
2021-02-17 9:33 GMT+09:00, Hyeongseok Kim :
> On 2/17/21 9:17 AM, Chaitanya Kulkarni wrote:
>> On 2/16/21 16:13, Hyeongseok Kim wrote:
>>> Sorry, I don't understand exactly.
>>> You're saying that these 2 patch should be merged to a single patch?
>>> Would it be better?
>> I think so unless there
Add an optional property to not retry multiple block read error
with several single block reads.
This property makes to handle read errors faster by not retrying
multiple block read errors with single block reads.
Signed-off-by: DooHyun Hwang
---
This makes to handle read errors faster by not retrying
multiple block read(CMD18) errors with single block reads(CMD17).
On some bad SD Cards that have problem with read operations,
it is not helpful to retry multiple block read errors with
several single block reads, and it is delayed to treat
Add an optional property to not retry multiple block read error
with several single block reads.
DooHyun Hwang (2):
dt-bindings: mmc: Add no-single-read-retry property
mmc: core: Add no single read retries
Documentation/devicetree/bindings/mmc/mmc-controller.yaml | 6 ++
+Frank, Rob, devicetree list
On 2/16/21 9:35 AM, Michal Simek wrote:
> Hi,
>
> I have a question about expectations when pinctrl setting is applied. In
> DTS all nodes are described in the order available in DT.
>
> uart-default {
> mux {
> ...
> };
>
> conf {
>
Add an optional property to not retry multiple block read error
with several single block reads.
This property makes to handle read errors faster by not retrying
multiple block read errors with single block reads.
Signed-off-by: DooHyun Hwang
---
This makes to handle read errors faster by not retrying
multiple block read(CMD18) errors with single block reads(CMD17).
On some bad SD Cards that have problem with read operations,
it is not helpful to retry multiple block read errors with
several single block reads, and it is delayed to treat
Add an optional property to not retry multiple block read error
with several single block reads.
DooHyun Hwang (2):
dt-bindings: mmc: Add no-single-read-retry property
mmc: core: Add no single read retries
Documentation/devicetree/bindings/mmc/mmc-controller.yaml | 6 ++
Hello,
syzbot found the following issue on:
HEAD commit:dcc0b490 Merge tag 'powerpc-5.11-8' of git://git.kernel.or..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1316c614d0
kernel config: https://syzkaller.appspot.com/x/.config?x=a2fbb1a71525e1d5
On Wed, Feb 17, 2021 at 1:28 AM Johannes Weiner wrote:
>
> On Tue, Feb 16, 2021 at 11:59:01AM -0500, Johannes Weiner wrote:
> > Hello Muchun,
> >
> > On Sat, Feb 13, 2021 at 01:01:59AM +0800, Muchun Song wrote:
> > > The swap charges the actual number of swap entries on cgroup v2.
> > > If a swap
On Wed, Feb 17, 2021 at 12:59 AM Johannes Weiner wrote:
>
> Hello Muchun,
>
> On Sat, Feb 13, 2021 at 01:01:59AM +0800, Muchun Song wrote:
> > The swap charges the actual number of swap entries on cgroup v2.
> > If a swap cache page is charged successful, and then we uncharge
> > the swap
Hello Johannes,
在 2021/2/17 上午4:00, Johannes Weiner 写道:
> Hello Chengming,
>
> This patch looks useful to me. A couple of comments below:
>
> On Tue, Feb 09, 2021 at 03:14:13PM +0800, Chengming Zhou wrote:
>> The commit 36b238d57172 ("psi: Optimize switching tasks inside shared
>> cgroups") only
Hi all,
Today's linux-next merge of the tip tree got a conflict in:
arch/x86/platform/intel-mid/device_libs/platform_bt.c
between commit:
4590d98f5a4f ("sfi: Remove framework for deprecated firmware")
from the pm tree and commit:
bdb154f074a6 ("x86/platform/intel-mid: Convert comma to
Hi Arnd,
On 12/2/21 8:05 pm, Arnd Bergmann wrote:
On Fri, Feb 12, 2021 at 6:48 AM kernel test robot wrote:
FYI, the error/warning still remains.
| ^~~~
arch/m68k/68000/dragen2.c: In function 'init_dragen2':
arch/m68k/68000/dragen2.c:73:16: error:
On 16-02-21, 15:10, Jonathan Marek wrote:
> There is not "nothing to do" when the opp is the same. The frequency can
> be different from opp->rate.
I am sorry but I am not sure what are you trying to fix here and what exactly is
broken here. Can you provide a usecase for your platform where this
On 16-02-21, 16:42, Vinod Koul wrote:
> Add the CPUfreq compatible for SM8350 SoC along with note for using the
> specific compatible for SoCs
>
> Signed-off-by: Vinod Koul
> ---
> Documentation/devicetree/bindings/cpufreq/cpufreq-qcom-hw.txt | 4 +++-
> 1 file changed, 3 insertions(+), 1
On Mon, Feb 15, 2021 at 11:42 PM Luis Henriques wrote:
>
> Nicolas Boichat reported an issue when trying to use the copy_file_range
> syscall on a tracefs file. It failed silently because the file content is
> generated on-the-fly (reporting a size of zero) and copy_file_range needs
> to know in
On Tue, Feb 16, 2021 at 9:42 PM Alex Ghiti wrote:
>
> Hi Dmitry,
>
> Le 2/16/21 à 6:25 AM, Dmitry Vyukov a écrit :
> > On Tue, Feb 16, 2021 at 12:17 PM Dmitry Vyukov wrote:
> >>
> >> On Fri, Jan 29, 2021 at 9:11 AM Dmitry Vyukov wrote:
> I was fixing KASAN support for my sv48 patchset so I
powerpc allmodconfig
powerpc allnoconfig
x86_64 randconfig-a003-20210216
x86_64 randconfig-a002-20210216
x86_64 randconfig-a004-20210216
x86_64 randconfig-a001-20210216
x86_64
allyesconfig
powerpc allmodconfig
powerpc allnoconfig
i386 randconfig-a003-20210216
i386 randconfig-a005-20210216
i386 randconfig-a002-20210216
i386 randconfig-a006
Hi Russ,
On Tue, Feb 16, 2021 at 09:46:53AM -0800, Russ Weight wrote:
> I believe all of the dependencies have been accepted now.
>
> - Russ
Sorry for dropping the ball on this, I'll get to this ASAP after -rc1 is
tagged.
>
> On 2/15/21 6:56 AM, Tom Rix wrote:
> > Russ, Moritz
> >
> > This
On 17-02-21, 00:24, Ionela Voinescu wrote:
> I think it could be merged in patch 1/2 as it's part of enabling the use
> of multiple sources of information for FIE. Up to you!
Sure.
> > static void amu_fie_setup(const struct cpumask *cpus)
> > {
> > - bool invariant;
> > int cpu;
> >
>
The Ethernet MAC and PHY are usually major consumers of power on boards
which may not be able to fully power off (those with no PMIC). Powering
down the MAC and internal PHY saves power while these boards are "off".
Reviewed-by: Chen-Yu Tsai
Signed-off-by: Samuel Holland
---
This is a deinitialization function that always returned zero, and that
return value was always ignored. Have it return void instead.
Reviewed-by: Chen-Yu Tsai
Signed-off-by: Samuel Holland
---
drivers/net/ethernet/stmicro/stmmac/dwmac-sun8i.c | 5 ++---
1 file changed, 2 insertions(+), 3
Use the appropriate function instead of reimplementing it,
and update the error message to match the code.
Reviewed-by: Chen-Yu Tsai
Signed-off-by: Samuel Holland
---
drivers/net/ethernet/stmicro/stmmac/dwmac-sun8i.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git
These patches clean up some things I noticed while fixing suspend/resume
behavior. The first four are minor code improvements. The last one adds
a shutdown hook to minimize power consumption on boards without a PMIC.
Changes v1 to v2:
- Note the assumption of exclusive reset controller access
Adjust the spacing and use an explicit "return 0" in the success path
to make the function easier to parse.
Reviewed-by: Chen-Yu Tsai
Signed-off-by: Samuel Holland
---
drivers/net/ethernet/stmicro/stmmac/dwmac-sun8i.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git
sun8i_dwmac_unpower_internal_phy already checks if the PHY is powered,
so there is no need to do it again here.
Reviewed-by: Chen-Yu Tsai
Signed-off-by: Samuel Holland
---
drivers/net/ethernet/stmicro/stmmac/dwmac-sun8i.c | 6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git
It's often useful in debug scenarios to see what the hardware has dumped
out. As it stands today, any device error will result in the payload not
being copied out, so there is no way to triage commands which weren't
expected to fail (and sometimes the payload may have that information).
The
---
drivers/staging/emxx_udc/emxx_udc.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/staging/emxx_udc/emxx_udc.c
b/drivers/staging/emxx_udc/emxx_udc.c
index 3536c03ff523..741147a4f0fe 100644
--- a/drivers/staging/emxx_udc/emxx_udc.c
+++ b/drivers/staging/emxx_udc/emxx_udc.c
@@
Add initial set of formal commands beyond basic identify and command
enumeration.
Signed-off-by: Ben Widawsky
Reviewed-by: Dan Williams
Reviewed-by: Jonathan Cameron (v2)
---
drivers/cxl/mem.c| 9 +
include/uapi/linux/cxl_mem.h | 5 +
2 files changed, 14 insertions(+)
CXL devices identified by the memory-device class code must implement
the Device Command Interface (described in 8.2.9 of the CXL 2.0 spec).
While the driver already maintains a list of commands it supports, there
is still a need to be able to distinguish between commands that the
driver knows
Cc: Dan Williams
Cc: Vishal Verma
Cc: Ira Weiny
Cc: Alison Schofield
Signed-off-by: Ben Widawsky
---
MAINTAINERS | 11 +++
1 file changed, 11 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 6eff4f720c72..93c8694a8f04 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -,6
1 - 100 of 927 matches
Mail list logo
