On Thu, Jan 21, 2021 at 09:52:51PM -0500, Thara Gopinath wrote:
> When bam dma is "controlled remotely", thus far clocks were not controlled
> from the Linux. In this scenario, Linux was disabling runtime pm in bam dma
> driver and not doing any clock management in suspend/resume hooks.
>
> With i
Hi all,
Today's linux-next merge of the notifications tree got conflicts in:
Documentation/security/keys/core.rst
samples/Kconfig
samples/watch_queue/watch_test.c
security/keys/Kconfig
between commit:
0c3f19da1229 ("watch_queue: Drop references to /dev/watch_queue")
from the keys tre
On Mon, Jan 18, 2021 at 4:42 AM Mark Brown wrote:
>
> On Mon, Jan 18, 2021 at 12:35:19PM +, Mark Brown wrote:
> > On Sat, Jan 16, 2021 at 08:25:36PM -0800, Alistair Francis wrote:
>
> > > +properties:
> > > + compatible:
> > > +enum:
> > > + - sy7636a-regulator
>
> > Compatible strin
On 1/21/21 5:42 PM, Miaohe Lin wrote:
> Hi:
> On 2021/1/22 3:00, Mike Kravetz wrote:
>> On 1/20/21 1:23 AM, Miaohe Lin wrote:
>>> The calculation 1U << (h->order + PAGE_SHIFT - 10) is actually equal to
>>> (PAGE_SHIFT << (h->order)) >> 10. So we can make it more readable by
>>> replace it with huge
On 22-01-21, 00:41, Dmitry Osipenko wrote:
> 21.01.2021 14:17, Viresh Kumar пишет:
> > @@ -1074,15 +1091,18 @@ int dev_pm_opp_set_rate(struct device *dev,
> > unsigned long target_freq)
> >
> > if (!ret) {
> > ret = _set_opp_bw(opp_table, opp, dev, false);
> > - if (!re
[Re: [PATCH 3/3] lib: support N as end of range in bitmap_parselist()] On
21/01/2021 (Thu 16:29) Yury Norov wrote:
> On Thu, Jan 21, 2021 at 2:34 PM Paul Gortmaker
> wrote:
> >
> > While this is done for all bitmaps, the original use case in mind was
> > for CPU masks and cpulist_parse(). Credi
Hi Troy,
On Mon, 18 Jan 2021, at 17:20, Troy Lee wrote:
> Add Aspeed AST2600 PWM/Fan tacho driver. AST2600 has 16 PWM channel and
> 16 FAN tacho channel.
>
> Changes since v2:
> - declare local function as static function
>
> Changes since v1:
> - fixed review comments
> - fixed double-looped
Mike Rapoport writes:
> > Signed-off-by: Roman Gushchin
>
> Reviewed-by: Mike Rapoport
I've seen a couple of spurious triggers of the WARN_ONCE() removed by this
patch. This happens on some ppc64le bare metal (powernv) server machines with
CONFIG_SWIOTLB=y and crashkernel=4G, as described in
[Re: [PATCH 1/3] lib: add "all" and "none" as valid ranges to
bitmap_parselist()] On 21/01/2021 (Thu 16:07) Yury Norov wrote:
> On Thu, Jan 21, 2021 at 2:34 PM Paul Gortmaker
> wrote:
> >
> > The use of "all" was originally RCU specific - I'd pushed it down to
> > being used for any CPU lists --
On 21-01-21, 23:26, Dmitry Osipenko wrote:
> 21.01.2021 14:17, Viresh Kumar пишет:
> > In order to avoid conditional statements at the caller site, this patch
> > updates _generic_set_opp_clk_only() to work for devices that don't
> > change frequency (like power domains, etc.). Return 0 if the clk
On Mon, 18 Jan 2021, at 17:20, Troy Lee wrote:
> We add binding for supporting a new AST2600 PWM/Fan hwmon driver.
>
> Changes since v2:
> - Fixed yamllint warnings/errors
>
> Changes since v1:
> - dt binding with DT schema format
>
> Signed-off-by: Troy Lee
> Reported-by: Rob Herring
> -
From: ❤️ Do you like my photos? Click here: http://bit.do/fMQVV?ud7m ❤️,
linux-kernel@vger.kernel.org, 436722671965
Subject: Backstage hero wants to help!
Message Body:
ihy5vra9
--
This e-mail was sent from the backstage hero contact form on RHS Jamboree
(https://rhsjamboree.org/wp)
Hi Krzysztof,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 9f29bd8b2e7132b409178d1367dae1813017bd0e
commit: 91687c1926bcd6b80d669375d57331b7bf80bf99 usb: phy: Enable compile
testing for some of drivers
date: 1
The mm-of-the-moment snapshot 2021-01-21-20-07 has been uploaded to
https://www.ozlabs.org/~akpm/mmotm/
mmotm-readme.txt says
README for mm-of-the-moment:
https://www.ozlabs.org/~akpm/mmotm/
This is a snapshot of my -mm patch queue. Uploaded at random hopefully
more than once a week.
You
On 1/5/21 10:57 PM, Yun Levi wrote:
Because of the missing export symbol for irq_chekc_status_bit,
Building arm_spe_pmu.ko is a failure on the modpost step.
Below is an error message I saw:
ERROR:modpost: "irq_check_status_bit" [drivers/perf/arm_spe_pmu.ko] undefined!
make[4]: *** [scripts/Makef
Hi Vincenzo,
I love your patch! Yet something to improve:
[auto build test ERROR on next-20210121]
[cannot apply to arm64/for-next/core arm/for-next soc/for-next xlnx/master
kvmarm/next linus/master hnaz-linux-mm/master v5.11-rc4 v5.11-rc3 v5.11-rc2
v5.11-rc4]
[If your patch is applied to the
On 1/22/2021 5:55 AM, Minchan Kim wrote:
> On Mon, Jan 18, 2021 at 03:26:42PM +0530, vji...@codeaurora.org wrote:
>> From: Vijayanand Jitta
>>
>> Add a kernel parameter stack_depot_disable to disable
>> stack depot. So that stack hash table doesn't consume
>> any memory when stack depot is disa
Changes in V6:
- Rebased patches to usb-testing.
- Renamed to PATCH series instead of RFC.
- Checking for fs_descriptors instead of ss_descriptors for determining the
endpoint count for a particular configuration.
- Re-ordered patch series to fix patch dependencies.
Changes in V5:
- Added
Some UDCs may have constraints on how many high bandwidth endpoints it can
support in a certain configuration. This API allows for the composite
driver to pass down the total number of endpoints to the UDC so it can verify
it has the required resources to support the configuration.
Signed-off-by:
Ensure that the USB gadget is able to support the configuration being
added based on the number of endpoints required from all interfaces. This
is for accounting for any bandwidth or space limitations.
Signed-off-by: Wesley Cheng
---
drivers/usb/gadget/configfs.c | 22 ++
1
Some devices have USB compositions which may require multiple endpoints
that support EP bursting. HW defined TX FIFO sizes may not always be
sufficient for these compositions. By utilizing flexible TX FIFO
allocation, this allows for endpoints to request the required FIFO depth to
achieve higher
Enable the flexible TX FIFO resize logic on SM8150. Using a larger TX FIFO
SZ can help account for situations when system latency is greater than the
USB bus transmission latency.
Signed-off-by: Wesley Cheng
---
arch/arm64/boot/dts/qcom/sm8150.dtsi | 1 +
1 file changed, 1 insertion(+)
diff --
On 1/22/2021 5:49 AM, Minchan Kim wrote:
> On Mon, Jan 18, 2021 at 03:26:41PM +0530, vji...@codeaurora.org wrote:
>> From: Yogesh Lal
>>
>> Use CONFIG_STACK_HASH_ORDER to configure STACK_HASH_SIZE.
>>
>> Aim is to have configurable value for STACK_HASH_SIZE,
>> so depend on use case one can co
On 13:07 Thu 21 Jan 2021, Randy Dunlap wrote:
On 1/21/21 6:30 AM, Bhaskar Chowdhury wrote:
s/Linus/Linux/
...how dare I?? :)
Signed-off-by: Bhaskar Chowdhury
Hi,
You missed a second occurrence of that a few lines later.
Indeed!
However, it is correct as is. It means the kernel tree
tha
Hello:
This patch was applied to netdev/net-next.git (refs/heads/master):
On Wed, 20 Jan 2021 20:43:03 +0100 you wrote:
> If the MII interface is used, the PHY is the clock master, thus don't
> set the clock rate. On Zynq-7000, this will prevent the following
> warning:
> macb e000b000.ethernet
On Thu, 14 Jan 2021 21:46:02 PST (-0800), wangkefeng.w...@huawei.com wrote:
Use the same implementation of initrd reserve to avoid duplication.
v3:
- split into four patches, suggested-by Palmer Dabbelt
v2:
- fix build error found by kernel test robot
Kefeng Wang (4):
initrd: Add the preproce
Fix the following coccicheck warnings:
./arch/x86/kvm/svm/nested.c:752:2-32: WARNING: Assignment of
0/1 to bool variable.
./arch/x86/kvm/svm/nested.c:545:1-31: WARNING: Assignment of
0/1 to bool variable.
Reported-by: Abaci Robot
Signed-off-by: Jiapeng Zhong
---
arch/x86/kvm/svm/nested.c | 4
On Thu, 21 Jan 2021 13:58:42 + Måns Rullgård wrote:
> > From: Arnd Bergmann
> >
> > The tango4 platform is getting removed, and this driver has no
> > other known users, so it can be removed.
> >
> > Cc: Marc Gonzalez
> > Cc: Mans Rullgard
> > Signed-off-by: Arnd Bergmann
>
> Acked-by: M
On Thu, Jan 21, 2021 at 09:58:03AM +0900, Changheun Lee wrote:
> bio size can grow up to 4GB when muli-page bvec is enabled.
> but sometimes it would lead to inefficient behaviors.
> in case of large chunk direct I/O, - 32MB chunk read in user space -
> all pages for 32MB would be merged to a bio s
Hi!
Syzkaller found this bug and it has a repro (below). I googled a similar
bug in 2019 which was fixed so this seems new.
The repro takes about a half a minute to produce the message, "grep
lock-classes /proc/lockdep_stats" reports 8177 of 8192, before running
the repro it is 702. It is a
Function current_gfp_context() is called after fast path. However, soon we
will add more constraints which will also limit zones based on context.
Move this call into fast path, and apply the correct constraints for all
allocations.
Also update .reclaim_idx based on value returned by current_gfp_c
PF_MEMALLOC_NOCMA is used ot guarantee that the allocator will not return
pages that might belong to CMA region. This is currently used for long
term gup to make sure that such pins are not going to be done on any CMA
pages.
When PF_MEMALLOC_NOCMA has been introduced we haven't realized that it is
It is still possible that we pin movable CMA pages if there are isolation
errors and cma_page_list stays empty when we check again.
Check for isolation errors, and return success only when there are no
isolation errors, and cma_page_list is empty after checking.
Because isolation errors are trans
In __get_user_pages_locked() i counts number of pages which should be
long, as long is used in all other places to contain number of pages, and
32-bit becomes increasingly small for handling page count proportional
values.
Signed-off-by: Pavel Tatashin
Acked-by: Michal Hocko
---
mm/gup.c | 2 +-
On some platforms ZERO_PAGE(0) might end-up in a movable zone. Do not
migrate zero page in gup during longterm pinning as migration of zero page
is not allowed.
For example, in x86 QEMU with 16G of memory and kernelcore=5G parameter, I
see the following:
Boot#1: zero_pfn 0x48a8d zero_pfn zone: Z
PF_MEMALLOC_PIN is only honored for CMA pages, extend
this flag to work for any allocations from ZONE_MOVABLE by removing
__GFP_MOVABLE from gfp_mask when this flag is passed in the current
context.
Add is_pinnable_page() to return true if page is in a pinnable page.
A pinnable page is not in ZONE
When pages are pinned they can be faulted in userland and migrated, and
they can be faulted right in kernel without migration.
In either case, the pinned pages must end-up being pinnable (not movable).
Add a new test to gup_test, to help verify that the gup/pup
(get_user_pages() / pin_user_pages(
When pages are longterm pinned, we must migrated them out of movable zone.
The function that migrates them has a hidden loop with goto. The loop is
to retry on isolation failures, and after successful migration.
Make this code better by moving this loop to the caller.
Signed-off-by: Pavel Tatashi
We should not pin pages in ZONE_MOVABLE. Currently, we do not pin only
movable CMA pages. Generalize the function that migrates CMA pages to
migrate all movable pages. Use is_pinnable_page() to check which
pages need to be migrated
Signed-off-by: Pavel Tatashin
Reviewed-by: John Hubbard
---
inc
In gup_test both gup_flags and test_flags use the same flags field.
This is broken.
Farther, in the actual gup_test.c all the passed gup_flags are erased and
unconditionally replaced with FOLL_WRITE.
Which means that test_flags are ignored, and code like this always
performs pin dump test:
155
Document the special handling of page pinning when ZONE_MOVABLE present.
Signed-off-by: Pavel Tatashin
Suggested-by: David Hildenbrand
Acked-by: Michal Hocko
---
Documentation/admin-guide/mm/memory-hotplug.rst | 9 +
1 file changed, 9 insertions(+)
diff --git a/Documentation/admin-gui
Hi Dmitry,
I love your patch! Perhaps something to improve:
[auto build test WARNING on tegra/for-next]
[also build test WARNING on v5.11-rc4 next-20210121]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as
When migration failure occurs, we still pin pages, which means
that we may pin CMA movable pages which should never be the case.
Instead return an error without pinning pages when migration failure
happens.
No need to retry migrating, because migrate_pages() already retries
10 times.
Signed-off-
When pages are isolated in check_and_migrate_movable_pages() we skip
compound number of pages at a time. However, as Jason noted, it is
not necessary correct that pages[i] corresponds to the pages that
we skipped. This is because it is possible that the addresses in
this range had split_huge_pmd()/
On 1/21/21 7:23 PM, Andrew Jeffery wrote:
> Randy found that with the following Kconfig settings we have duplicate
> definitions (e.g. __inittest()) in sdhci-of-aspeed due to competing
> module_init()/module_exit() calls from kunit and driver the itself.
>
> ```
> CONFIG_MMC_SDHCI_OF_ASPEED=m
> CO
Changelog
-
v7
- Added reviewed-by's
- Fixed a compile bug on non-mmu builds reported by robot
v6
Small update, but I wanted to send it out quicker, as it removes a
controversial patch and replaces it with something sane.
- Removed forcing FOLL_WRITE for longterm gup, instead added a p
In order not to fragment CMA the pinned pages are migrated. However,
they are migrated to ZONE_MOVABLE, which also should not have pinned pages.
Remove __GFP_MOVABLE, so pages can be migrated to zones where pinning
is allowed.
Signed-off-by: Pavel Tatashin
Reviewed-by: David Hildenbrand
Reviewe
From: Ricky Wu
v1:
make sure ASPM state sync with pcr->aspm_enabled
init value pcr->aspm_enabled
v2:
fixes conditions in v1 if-statement
v3:
more description for v1 and v2
Cc: sta...@vger.kernel.org
Signed-off-by: Ricky Wu
---
drivers/misc/cardreader/rtsx_pcr.c | 7 ++-
1 file changed, 6 i
On 1/21/21 3:27 PM, David Hildenbrand wrote:
> On 18.01.21 14:21, Anshuman Khandual wrote:
>>
>>
>> On 1/18/21 6:43 PM, Anshuman Khandual wrote:
>>> From: David Hildenbrand
>>>
>>> Right now, we only check against MAX_PHYSMEM_BITS - but turns out there
>>> are more restrictions of which memory
On 1/21/2021 12:13 AM, Jung Daehwan wrote:
> On Wed, Jan 20, 2021 at 11:44:05PM -0800, Wesley Cheng wrote:
>>
>>
>> On 1/20/2021 10:49 PM, Jung Daehwan wrote:
>>> Hi,
>>>
>>> On Thu, Jan 21, 2021 at 01:00:32AM +, Thinh Nguyen wrote:
Hi,
Daehwan Jung wrote:
> Sometimes dwc3
On Thu, Jan 21, 2021 at 05:19:56AM -0800, Tom Rix wrote:
>
> On 1/21/21 12:05 AM, Xu Yilun wrote:
> > On Wed, Jan 20, 2021 at 07:32:53AM -0800, Tom Rix wrote:
> >> On 1/19/21 6:34 PM, Xu Yilun wrote:
> >>> From: Matthew Gerlach
> >>>
> >>> This patch adds access tables to the MAX 10 BMC regmap. T
On Fri, 15 Jan 2021 15:49:48 PST (-0800), vitaly.w...@konsulko.com wrote:
Sometimes, especially in a production system we may not want to
use a "smart bootloader" like u-boot to load kernel, ramdisk and
device tree from a filesystem on eMMC, but rather load the kernel
from a NAND partition and ju
Randy found that with the following Kconfig settings we have duplicate
definitions (e.g. __inittest()) in sdhci-of-aspeed due to competing
module_init()/module_exit() calls from kunit and driver the itself.
```
CONFIG_MMC_SDHCI_OF_ASPEED=m
CONFIG_MMC_SDHCI_OF_ASPEED_TEST=y
```
Conditionally open-
On 2021/1/18 21:35, Peter Zijlstra wrote:
On Mon, Jan 18, 2021 at 09:05:06PM +0800, Like Xu wrote:
I guess this fix will silence the compiler error,
and v2 will be sent after the local 0day test passes.
I think there's also a problem where you don't assign a function at all.
Thank you!
I
Hi Atish,
First bad commit (maybe != root cause):
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 9f29bd8b2e7132b409178d1367dae1813017bd0e
commit: e557793799c5a8406afb08aa170509619f7eac36 RISC-V: Fix maximum allowed
phsyical memory for RV32
date: 6 da
On 01/22/21 at 09:22am, Dave Young wrote:
> Hi John,
>
> On 01/21/21 at 09:32am, john.p.donne...@oracle.com wrote:
> > On 11/22/20 9:47 PM, Dave Young wrote:
> > > Hi Guilherme,
> > > On 11/22/20 at 12:32pm, Guilherme Piccoli wrote:
> > > > Hi Dave and Kairui, thanks for your responses! OK, if tha
Clean up that CONFIG_RETPOLINE crud and replace the
indirect call x86_pmu.guest_get_msrs with static_call().
Suggested-by: Peter Zijlstra (Intel)
Reported-by: kernel test robot
Signed-off-by: Like Xu
---
arch/x86/events/core.c| 20
arch/x86/events/intel/core.c
On 22-01-21, 10:39, David Gibson wrote:
> No, it definitely will not work in general. It might kinda work in a
> few trivial cases, but it absolutely will not do the neccessary
> handling in some cases.
>
> > I
> > did inspect the output dtb (made by merging two overlays) using
> > fdtdump and it
On Fri, Jan 22, 2021 at 3:54 AM Jernej Škrabec wrote:
>
> Dne četrtek, 21. januar 2021 ob 18:08:36 CET je Hermann Lauer napisal(a):
> > BPi Pro needs TX and RX delay for Gbit to work reliable and avoid high
> > packet loss rates. The realtek phy driver overrides the settings of the
> > pull ups fo
On 22-01-21, 00:02, Dmitry Osipenko wrote:
> 21.01.2021 14:30, Viresh Kumar пишет:
> > @@ -1952,9 +1930,16 @@ void dev_pm_opp_put_regulators(struct opp_table
> > *opp_table)
> > for (i = opp_table->regulator_count - 1; i >= 0; i--)
> > regulator_put(opp_table->regulators[i]);
> >
The sizeof(u32) is hardcoded. It's better to use the config value in
regmap.
It increases the size of target object, but it's flexible when new mcp chip
need other val_bytes.
Signed-off-by: Su Yanjun
---
drivers/net/can/spi/mcp251xfd/mcp251xfd-core.c | 9 ++---
1 file changed, 6 insertions(
Recently i use mcp2518fd on 4.x kernel which multiple write is not
backported, regmap_raw_write will cause old kernel crash because the
tx buffer in driver is smaller then 2K. Use regmap_bulk_write instead
for compatibility.
Signed-off-by: Su Yanjun
---
drivers/net/can/spi/mcp251xfd/mcp251xfd-co
On 1/21/21 7:06 PM, Will Deacon wrote:
> On Wed, Jan 20, 2021 at 09:29:13PM -0800, Sudarshan Rajagopalan wrote:
>> memory_block_size_bytes() determines the memory hotplug granularity i.e the
>> amount of memory which can be hot added or hot removed from the kernel. The
>> generic value here bein
> -Original Message-
> From: Valentin Schneider [mailto:valentin.schnei...@arm.com]
> Sent: Friday, January 22, 2021 7:15 AM
> To: Song Bao Hua (Barry Song) ; Vincent Guittot
>
> Cc: Ingo Molnar ; Peter Zijlstra ;
> Dietmar Eggemann ; Morten Rasmussen
> ; linux-kernel ; Mel
> Gorman ; l
When bam dma is "controlled remotely", thus far clocks were not controlled
from the Linux. In this scenario, Linux was disabling runtime pm in bam dma
driver and not doing any clock management in suspend/resume hooks.
With introduction of crypto engine bam dma, the clock is a rpmh resource
that ca
On 2021/1/21 20:50, Robin Murphy wrote:
> On 2021-01-21 02:04, Leizhen (ThunderTown) wrote:
>>
>>
>> On 2021/1/20 23:02, Robin Murphy wrote:
>>> On 2021-01-19 01:59, Zhen Lei wrote:
This reverts commit 52f3fab0067d6fa9e99c1b7f63265dd48ca76046.
This problem has been fixed by anothe
On Mon, Jan 18, 2021 at 2:33 PM Alexander Lobakin wrote:
>
> Commit 9fd1ff5d2ac7 ("udp: Support UDP fraglist GRO/GSO.") actually
> not only added a support for fraglisted UDP GRO, but also tweaked
> some logics the way that non-fraglisted UDP GRO started to work for
> forwarding too.
> Commit 2e4e
Hi Vincenzo,
I love your patch! Perhaps something to improve:
[auto build test WARNING on next-20210121]
[cannot apply to arm64/for-next/core arm/for-next soc/for-next xlnx/master
kvmarm/next linus/master hnaz-linux-mm/master v5.11-rc4 v5.11-rc3 v5.11-rc2
v5.11-rc4]
[If your patch is applied
Hi Vincenzo,
I love your patch! Perhaps something to improve:
[auto build test WARNING on next-20210121]
[cannot apply to arm64/for-next/core arm/for-next soc/for-next xlnx/master
kvmarm/next linus/master hnaz-linux-mm/master v5.11-rc4 v5.11-rc3 v5.11-rc2
v5.11-rc4]
[If your patch is applied
On Thu, 2021-01-21 at 20:13 +0800, Nicolas Boichat wrote:
> On Thu, Jan 21, 2021 at 8:09 PM mtk15103 wrote:
> >
> > On Thu, 2021-01-21 at 16:55 +0800, Nicolas Boichat wrote:
> > > On Thu, Jan 21, 2021 at 3:52 PM Hailong Fan
> > > wrote:
> > > >
> > > > When flipping the polarity will be generate
The pull request you sent on Fri, 22 Jan 2021 09:29:02 +0900:
> git://github.com/openrisc/linux.git tags/for-linus
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/83d09ad4b950651a95d37697f1493c00d888d0db
Thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kern
Since thermal_notify_framework is no longer supported/implemented
remove the entry from sysfs-api.rst.
---
Documentation/driver-api/thermal/sysfs-api.rst | 12 +---
1 file changed, 1 insertion(+), 11 deletions(-)
diff --git a/Documentation/driver-api/thermal/sysfs-api.rst
b/Documentation
thermal_notify_framework just updates for a single trip point where as
thermal_zone_device_update does other bookkeeping like updating the
temperature of the thermal zone and setting the next trip point etc.
Replace thermal_notify_framework with thermal_zone_device_update as the
later is more thoro
thermal_notify_framework just updates for a single trip point where as
thermal_zone_device_update does other bookkeeping like updating the
temperature of the thermal zone and setting the next trip point. The only
driver that was using thermal_notify_framework was updated in the previous
patch to us
thermal_notify_framework just updates for a single trip point where as
thermal_zone_device_update does other bookkeeping like updating the
temperature of the thermal zone, running through the list of trip points
and setting the next trip point etc. Since the later is a more thorough
version of for
On Thu, Jan 21, 2021 at 08:32:35AM +0100, György Andrasek wrote:
> > This is basically a revert of commit 644592d32837 ("objtool: Fail the
> kernel build on fatal errors").
>
> > That change turned out to be more trouble than it's worth.
>
> ...I'm sorry, what? Fatal errors are normal for you peo
Thanks Max. Patch v3 looks good to me.
Reviewed-by: Abhishek Pandit-Subedi
On Thu, Jan 21, 2021 at 5:59 PM wrote:
>
> From: Max Chou
>
> By this change, it will enable WBS supported on the specific Realtek BT
> devices, such as RTL8822C and RTL8852A.
> In the future, it's able to maintain what
I find linux-mips.org too unreliable to rely on, so move to a place
I have proper control over.
Signed-off-by: Maciej W. Rozycki
---
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi,
My address is now . Please apply.
Maciej
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEgfGIKCQicRu6B1jhJ
Hi Arnd,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 9f29bd8b2e7132b409178d1367dae1813017bd0e
commit: 80fe7430c7085951d1246d83f638cc17e6c0be36 ALSA: add new 32-bit layout
for snd_pcm_mmap_status/control
date:
On Fri, 2021-01-22 at 05:25 +0900, Masahiro Yamada wrote:
> On Fri, Jan 22, 2021 at 2:17 AM Scott Branden
> wrote:
> >
> > Use python3 instead of python in diffconfig Shebang line.
> > python2 was sunset January 1, 2000 and environments do not need
> > to support python any more.
python2 was sun
On 2021/1/20 5:42, Jaegeuk Kim wrote:
On 01/16, Chao Yu wrote:
On 2021/1/15 22:59, Jaegeuk Kim wrote:
On 01/15, Chao Yu wrote:
On 2021/1/14 12:06, Jaegeuk Kim wrote:
On 01/14, Chao Yu wrote:
On 2021/1/13 23:41, Jaegeuk Kim wrote:
[58690.961685] F2FS-fs (vdb) : inject page get in f2fs_pageca
Object out is not released on path that no VMA instance found. The root
cause is jumping to an unexpected label on the error path.
Fixes: a47e788c2310 ("drm/i915/selftests: Exercise CS TLB invalidation")
Signed-off-by: Pan Bian
---
drivers/gpu/drm/i915/selftests/i915_gem_gtt.c | 2 +-
1 file cha
allnoconfig
x86_64 randconfig-a002-20210121
x86_64 randconfig-a003-20210121
x86_64 randconfig-a001-20210121
x86_64 randconfig-a005-20210121
x86_64 randconfig-a006-20210121
x86_64 randconfig-a004-20210121
i386
The default event list includes the most common events which are widely
used by users. But with -e option, the current perf only counts the events
assigned by -e option. Users may want to collect some extra events with
the default list. For this case, users have to manually add all the events
from
From: Max Chou
By this change, it will enable WBS supported on the specific Realtek BT
devices, such as RTL8822C and RTL8852A.
In the future, it's able to maintain what the Realtek devices support WBS
here.
Tested-by: Hilda Wu
Reviewed-by: Abhishek Pandit-Subedi
Signed-off-by: Max Chou
---
c
Hi:
On 2021/1/22 5:48, Nathan Chancellor wrote:
> Clang warns:
>
> mm/zswap.c:1271:6: warning: variable 'ret' is used uninitialized
> whenever 'if' condition is true [-Wsometimes-uninitialized]
> if (!entry->length) {
> ^~
> mm/zswap.c:1322:9: note: uninitialized us
Yep~
2021년 1월 22일 (금) 오전 10:46, Jaegeuk Kim 님이 작성:
>
> On 01/21, Daeho Jeong wrote:
> > From: Daeho Jeong
> >
> > We've added a new mount option "checkpoint=merge", which creates a
> > kernel daemon and makes it to merge concurrent checkpoint requests as
> > much as possible to eliminate redundan
On Thu, Jan 21, 2021 at 5:49 PM Sedat Dilek wrote:
>
> On Fri, Jan 22, 2021 at 2:43 AM Nick Desaulniers
> wrote:
> >
> > On Wed, Jan 20, 2021 at 6:03 PM Sedat Dilek wrote:
> > >
> > > On Mon, Jan 18, 2021 at 10:56 PM Bill Wendling wrote:
> > > >
> > > > On Mon, Jan 18, 2021 at 9:26 AM Sedat Dil
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 9f29bd8b2e7132b409178d1367dae1813017bd0e
commit: 3f50f132d8400e129fc9eb68b5020167ef80a244 bpf: Verifier, do explicit
ALU32 bounds tracking
date: 10 months ago
config: parisc-randconfig-r003-20210121
On Fri, Jan 22, 2021 at 2:44 AM Nick Desaulniers
wrote:
>
> On Thu, Jan 21, 2021 at 2:35 AM Sedat Dilek wrote:
> >
> > Thanks for v6.
> >
> > Small Changelog nits:
> > * Can you reverse-order the changelog - latest v6 first.
> > * v4: s/Makfile changes and se/Ma*k*efile changes and *u*se
> >
> >
On 1/21/2021 12:00 PM, Hillf Danton wrote:
On Wed, 20 Jan 2021 21:46:33 +0800 Oliver Sang wrote:
On Fri, Jan 15, 2021 at 03:24:32PM +0800, Hillf Danton wrote:
Thu, 14 Jan 2021 15:45:11 +0800
FYI, we noticed the following commit (built with gcc-9):
commit: d5bff968ea9cc005e632d9369c26cbd814
On Fri, Jan 22, 2021 at 2:43 AM Nick Desaulniers
wrote:
>
> On Wed, Jan 20, 2021 at 6:03 PM Sedat Dilek wrote:
> >
> > On Mon, Jan 18, 2021 at 10:56 PM Bill Wendling wrote:
> > >
> > > On Mon, Jan 18, 2021 at 9:26 AM Sedat Dilek wrote:
> > > >
> > > > On Mon, Jan 18, 2021 at 1:39 PM Sedat Dilek
On 01/21, Daeho Jeong wrote:
> From: Daeho Jeong
>
> We've added a new mount option "checkpoint=merge", which creates a
> kernel daemon and makes it to merge concurrent checkpoint requests as
> much as possible to eliminate redundant checkpoint issues. Plus, we
> can eliminate the sluggish issue
发件人: Uladzislau Rezki
发送时间: 2021年1月22日 4:26
收件人: Zhang, Qiang
抄送: Paul E. McKenney; r...@vger.kernel.org; linux-kernel@vger.kernel.org;
ure...@gmail.com
主题: Re: [PATCH] rcu: Release per-cpu krcp page cache when CPU going offline
>Hello, Qiang,
> On Thu,
Hi Arnaldo,
On 1/21/2021 9:02 PM, Arnaldo Carvalho de Melo wrote:
So if we just want to append the default list, we only need to set
detailed_run=1, then ideally perf-stat will print the default list.
But for now, there are no task-clock, context-switches, cpu-migrations,
page-faults, instru
On Thu, Jan 21, 2021 at 2:35 AM Sedat Dilek wrote:
>
> Thanks for v6.
>
> Small Changelog nits:
> * Can you reverse-order the changelog - latest v6 first.
> * v4: s/Makfile changes and se/Ma*k*efile changes and *u*se
>
> Can you add a hint to this "Clang-PGO" patch requiring Clang >= 12?
>
> Can y
On Fri, Jan 22, 2021 at 2:34 AM Nick Desaulniers
wrote:
>
> On Wed, Jan 20, 2021 at 6:21 PM Sedat Dilek wrote:
> >
> > Hi,
> >
> > When I looked through the code I wondered why we do not add a
> > "CONFIG_PGO_CLANG_PROFDATA" which can be helpful when doing the PGO
> > rebuild with a vmlinux.profd
On Wed, Jan 20, 2021 at 6:03 PM Sedat Dilek wrote:
>
> On Mon, Jan 18, 2021 at 10:56 PM Bill Wendling wrote:
> >
> > On Mon, Jan 18, 2021 at 9:26 AM Sedat Dilek wrote:
> > >
> > > On Mon, Jan 18, 2021 at 1:39 PM Sedat Dilek wrote:
> > > >
> > > > On Mon, Jan 18, 2021 at 3:32 AM Bill Wendling w
Hi:
On 2021/1/22 3:00, Mike Kravetz wrote:
> On 1/20/21 1:23 AM, Miaohe Lin wrote:
>> The calculation 1U << (h->order + PAGE_SHIFT - 10) is actually equal to
>> (PAGE_SHIFT << (h->order)) >> 10. So we can make it more readable by
>> replace it with huge_page_size(h) / SZ_1K.
>>
>> Signed-off-by: Mi
Hi Palmer,
First bad commit (maybe != root cause):
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 9f29bd8b2e7132b409178d1367dae1813017bd0e
commit: c2c81bb2f69138f902e1a58d3bef6ad97fb8a92c RISC-V: Fix the VDSO symbol
generaton for binutils-2.35+
date:
101 - 200 of 1499 matches
Mail list logo
