This patch series adds watchdog timer driver and respective yaml schemas
for watchdog timer on Intel Lightning Mountain SoC.
This patch series is rebased and tested on mainline linux kernel 5.7:
base-commit: 3d77e6a8804a ("Linux 5.7")
tags: v5.7
Dilip Kota (2):
dt-bindings: watchdog: intel:
Add YAML schemas for the watchdog timer on Intel Lightning
Mountain SoC.
Signed-off-by: Dilip Kota
---
.../bindings/watchdog/intel,lgm-gptc-wdt.yaml | 75 ++
1 file changed, 75 insertions(+)
create mode 100644
On Intel Lightning Mountain SoC, General Purpose Timer Counter(GPTC)
programmable as clocksource, real time clock or watchdog timer.
This driver configures GPTC as Watchdog timer and triggers reset signal
to CPU on timeout.
Signed-off-by: Dilip Kota
---
drivers/watchdog/Kconfig |
On Sun, Jun 07, 2020 at 10:41:56PM +, Rodolfo C. Villordo wrote:
> Multiple line over 80 characters fixes by splitting in multiple lines.
> Warning found by checkpatch.pl
I doubt that checkpatch.pl can catch the real problems there:
* Hungarian Notation Sucks. Really.
* so does CamelCase,
rc is initialized to -ENIVAL but that's never used. Drop it.
Fixes: 5f1f79bbc9e2 ("virtio-mem: Paravirtualized memory hotplug")
Reported-by: kernel test robot
Signed-off-by: Michael S. Tsirkin
---
drivers/virtio/virtio_mem.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
On Sun, Jun 07, 2020 at 10:24:14PM +0200, Pavel Machek wrote:
> On Fri 2020-06-05 19:33:28, Andrzej Pietrasiewicz wrote:
> > Userspace might want to implement a policy to temporarily disregard input
> > from certain devices.
>
> Wow, you certainly cc a lot of lists.
>
> > An example use case is
On 17.04.20 01:45, Deep Shah wrote:
Thomas Hellstrom will be handing over VMware's maintainership of these
interfaces to Deep Shah.
Signed-off-by: Deep Shah
Acked-by: Thomas Hellstrom
Pushed to xen/tip.git for-linus-5.8
Juergen
pm_runtime_get_sync() increments the runtime PM usage counter even
when it returns an error code. Thus a pairing decrement is needed on
the error handling path to keep the counter balanced.
Signed-off-by: Dinghao Liu
---
Changelog:
v2: - Fix the imbalance in vsp1_device_get().
Use
On Sun, Jun 07, 2020 at 10:41:56PM +, Rodolfo C. Villordo wrote:
> Multiple line over 80 characters fixes by splitting in multiple lines.
> Warning found by checkpatch.pl
>
> Signed-off-by: Rodolfo C. Villordo
> ---
> drivers/staging/vt6655/rxtx.c | 225 --
>
Thank you for your comment.
> >> Can you split this patch into two? (Don't set VOL_DIRTY on -ENOTEMPTY and
> >> Setting EXFAT_SB_DIRTY is
> >> merged into exfat_set_vol_flag). I need to check the second one more.
> >
> > Can't do that.
> >
> > exfat_set_vol_flag() is called when rmdir processing
On Mon, Jun 8, 2020 at 10:30 AM Guenter Roeck wrote:
>
> Hi,
>
> On Fri, Jun 05, 2020 at 10:39:55AM +0300, Denis Efremov wrote:
> > Allow user to use alternative implementations of compression tools,
> > such as pigz, pbzip2, pxz. For example, multi-threaded tools to
> > speed up the build:
> > $
On Sun, 31 May 2020, Greg Thelen wrote:
> Since v4.19 commit b0dedc49a2da ("mm/vmscan.c: iterate only over charged
> shrinkers during memcg shrink_slab()") a memcg aware shrinker is only
> called when the per-memcg per-node shrinker_map indicates that the
> shrinker may have objects to release to
Reviewed-by: Sagi Grimberg
> On Jun 7, 2020, at 11:16 PM, Laurent Pinchart
> wrote:
>
> I forgot to mention, I think the subject line should be
>
> drm/rcar-du: Make DRM_RCAR_WRITEBACK depend on DRM_RCAR_DU
>
> Could you please let me know if you're OK with these two small changes ?
Yes, I am fine with those.
Increase length of bios_to_linux_keycode to 2 bytes to allow for a new
keycode 0x, this silences the following messages being logged at
startup on a Dell Inspiron 5593
dell_wmi: firmware scancode 0x48 maps to unrecognized keycode 0x
dell_wmi: firmware scancode 0x50 maps to unrecognized
add new backlight events with a type of 0x0010 and a code of 0x57 / 0x58,
add a new keymap type table 0x0012 for keycode of 0xe035 from the Fn-lock
key
extend bios_to_linux_keycode to 2 bytes to allow for a new keycode 0x
Y Paritcher (3):
platform/x86: dell-wmi: add new backlight events
Ignore events with a type of 0x0010 and a code of 0x57 / 0x58,
this silences the following messages being logged on a
Dell Inspiron 5593:
dell_wmi: Unknown key with type 0x0010 and code 0x0057 pressed
dell_wmi: Unknown key with type 0x0010 and code 0x0058 pressed
Signed-off-by: Y Paritcher
---
Ignore events with a type of 0x0012 and a code of 0xe035,
this silences the following messages being logged when
pressing the Fn-lock key on a Dell Inspiron 5593:
dell_wmi: Unknown WMI event type 0x12
dell_wmi: Unknown key with type 0x0012 and code 0xe035 pressed
Signed-off-by: Y Paritcher
---
On Sun, Jun 07, 2020 at 12:08:40PM -0700, Paul E. McKenney wrote:
> On Sun, Jun 07, 2020 at 06:23:40AM +1000, Stephen Rothwell wrote:
> > Hi all,
> >
> > On Mon, 6 Apr 2020 16:29:50 +0530 Amol Grover wrote:
> > >
> > > exceptions may be traversed using list_for_each_entry_rcu()
> > > outside of
On Thu, 28 May 2020, Alex Shi wrote:
> This is a new version which bases on linux-next
>
> Johannes Weiner has suggested:
> "So here is a crazy idea that may be worth exploring:
>
> Right now, pgdat->lru_lock protects both PageLRU *and* the lruvec's
> linked list.
>
> Can we make PageLRU
On Mon, Jun 08, 2020 at 09:02:53AM +0800, kernel test robot wrote:
> From: kernel test robot
>
> drivers/pinctrl/pinctrl-mcp23s08_spi.c:129:1-3: WARNING: PTR_ERR_OR_ZERO can
> be used
>
>
> Use PTR_ERR_OR_ZERO rather than if(IS_ERR(...)) + PTR_ERR
>
> Generated by:
> On May 20, 2020, at 18:18, Kai-Heng Feng wrote:
>
> USB2 devices with LPM enabled may interrupt the system suspend:
> [ 932.510475] usb 1-7: usb suspend, wakeup 0
> [ 932.510549] hub 1-0:1.0: hub_suspend
> [ 932.510581] usb usb1: bus suspend, wakeup 0
> [ 932.510590] xhci_hcd
On 2020/6/7 下午10:11, Michael S. Tsirkin wrote:
Everyone's using buf APIs, no need for head based ones anymore.
Signed-off-by: Michael S. Tsirkin
---
drivers/vhost/vhost.c | 36
drivers/vhost/vhost.h | 12
2 files changed, 8 insertions(+),
> On May 7, 2020, at 18:35, Mathias Nyman wrote:
>
> On 7.5.2020 11.21, Greg Kroah-Hartman wrote:
>> On Thu, May 07, 2020 at 03:58:36PM +0800, Kai-Heng Feng wrote:
>>>
>>>
On May 7, 2020, at 15:31, Greg Kroah-Hartman
wrote:
On Thu, May 07, 2020 at 03:15:01PM +0800,
> On May 5, 2020, at 01:16, Kai-Heng Feng wrote:
>
> Etron EJ168 USB 3.0 Host Controller stops working after S3, if it was
> runtime suspended previously:
> [ 370.080359] pci :02:00.0: can't change power state from D3cold to D0
> (config space inaccessible)
> [ 370.080477] xhci_hcd
From:
The affiliate office of the:
*International Monetary Fund,
*International Fund Regulatory Board,
*Capital Flight Fund Regulation,
Reliance Bank Limited
London EC3R 8EB,
United Kingdom
Sub: Payment approval of GBP£3,150,000.00/
Good day, this is a comprehensive summary as to what have
> On May 6, 2020, at 18:28, Kai-Heng Feng wrote:
>
> On HP 800 G4 DM, if HDMI cable isn't plugged before boot, the HDMI port
> becomes useless and never responds to cable hotplugging:
> [3.031904] [drm:lspcon_init [i915]] *ERROR* Failed to probe lspcon
> [3.031945] [drm:intel_ddi_init
On Sat, Jun 6, 2020 at 2:29 PM Andy Shevchenko
wrote:
>
>
>
> On Saturday, June 6, 2020, Jonathan Cameron wrote:
>>
>> On Thu, 4 Jun 2020 21:44:44 -0500
>> Navid Emamdoost wrote:
>>
>> > Calling pm_runtime_get_sync increments the counter even in case of
>> > failure, causing incorrect ref
Now the __iommu_map() and __iommu_map_sg() are used only in iommu.c
file, so mark them as static.
Signed-off-by: Baolin Wang
---
drivers/iommu/iommu.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/drivers/iommu/iommu.c b/drivers/iommu/iommu.c
index
Now the ARM page tables are always allocated by GFP_ATOMIC parameter,
but the iommu_ops->map() function has been added a gfp_t parameter by
commit 781ca2de89ba ("iommu: Add gfp parameter to iommu_ops::map"),
thus io_pgtable_ops->map() should use the gfp parameter passed from
iommu_ops->map() to
Hi,
The first patch masks some functions as static, and the second patch
changes to use the gfp parameter from iommu_ops->map() to allocate
ARM page pages. Any comments are welcome. Thanks.
Baolin Wang (2):
iommu: Mark __iommu_map/__iommu_map_sg as static
iommu: Add gfp parameter to
Yes, this is for security key destruction.
AFAIK, discard will unmap the data block and, after done it,
we can read either zero data or garbage data from that block depending
on eMMC/UFS.
In a view point of read data, it might be the same with zeroing the data block.
However, since we can even
On 2020/6/7 下午9:57, Michael S. Tsirkin wrote:
On Fri, Jun 05, 2020 at 11:40:17AM +0800, Jason Wang wrote:
On 2020/6/4 下午4:59, Michael S. Tsirkin wrote:
On Wed, Jun 03, 2020 at 03:27:39PM +0800, Jason Wang wrote:
On 2020/6/2 下午9:06, Michael S. Tsirkin wrote:
With this patch applied, new and
hsfreqrange should be chosen based on the calculated mbps which
is closer to the default bit rate and within the range as per
table[1]. But current calculation always selects first value which
is greater than or equal to the calculated mbps which may lead
to chosing a wrong range in some cases.
Hi Linus,
This should be the final feature pull for drm for rc1. This tree has
been in next for a couple of weeks, but Rob missed an arm32 build
issue, so I was awaiting the tree with a patch reverted. The tree was
also based on an 5.7-rc5 tree so I didn't want to futz around with
backmerging
>
> The vsp1_probe() function has a struct vsp1_device whose dev field is
> populated by the time it needs to call pm_runtime_get_sync() and
> pm_runtime_get_put(), so I think you can use vsp1_device_get() and
> vsp1_device_put() as drop-in replacements without changing the
> parameters to these
On 2020/6/7 下午9:51, Michael S. Tsirkin wrote:
On Fri, Jun 05, 2020 at 04:54:17PM +0800, Jason Wang wrote:
On 2020/6/2 下午3:08, Jason Wang wrote:
+static const struct pci_device_id vp_vdpa_id_table[] = {
+ { PCI_DEVICE(PCI_VENDOR_ID_REDHAT_QUMRANET, PCI_ANY_ID) },
+ { 0 }
+};
This looks
On Mon, Jun 08, 2020 at 09:56:16AM +0800, Kefeng Wang wrote:
>
> On 2020/6/8 3:00, Paul E. McKenney wrote:
> > On Fri, Jun 05, 2020 at 05:19:14PM -0700, Paul E. McKenney wrote:
> > > On Sat, Jun 06, 2020 at 07:07:10AM +0800, kernel test robot wrote:
> > > > tree:
> > > >
Hi Qian,
I forgot to mention, I think the subject line should be
drm/rcar-du: Make DRM_RCAR_WRITEBACK depend on DRM_RCAR_DU
Could you please let me know if you're OK with these two small changes ?
On Mon, Jun 08, 2020 at 06:14:43AM +0300, Laurent Pinchart wrote:
> On Sun, Jun 07, 2020 at
Hey Linus,
This are the fixes from last week for the stuff merged in the merge
window. It got a bunch of nouveau fixes for HDA audio on some new
GPUs, some i915 and some amdpgu fixes.
I've got another pull request with Rob's msm next stuff in it I'll
send along after this, it was in -next all
Hi Qian,
Thank you for the patch.
On Sun, Jun 07, 2020 at 10:53:40PM -0400, Qian Cai wrote:
> There is no need to select DRM_RCAR_WRITEBACK if DRM=n which just make
s/DRM=n/DRM_RCAR_DU=n/ here.
> the generated .config a bit ugly.
>
> # ARM devices
> #
> # end of ARM devices
>
>
Hi Dianghao,
On Mon, Jun 08, 2020 at 11:03:26AM +0800, dinghao@zju.edu.cn wrote:
> Hi Laurent,
>
> > > I wonder how many bugs we have today, and how many bugs will keep
> > > appearing in the future, due to this historical design mistake :-(
>
> Good question. It's hard to say if this is a
Hi Laurent,
> >
> > I wonder how many bugs we have today, and how many bugs will keep
> > appearing in the future, due to this historical design mistake :-(
> >
Good question. It's hard to say if this is a design mistake (some use
of this API does not check its return value and expects it
On 2020/6/8 5:17, Jaegeuk Kim wrote:
> On 06/05, Chao Yu wrote:
>> 71.07% 0.01% kworker/u256:1+ [kernel.kallsyms] [k] wb_writeback
>> |
>> --71.06%--wb_writeback
>>|
>>|--68.96%--__writeback_inodes_wb
>>
Hi, Bjorn
On 2020/6/6 上午7:19, Bjorn Helgaas wrote:
On Thu, Jun 04, 2020 at 09:33:07PM +0800, Zhangfei Gao wrote:
On 2020/6/2 上午1:41, Bjorn Helgaas wrote:
On Thu, May 28, 2020 at 09:33:44AM +0200, Joerg Roedel wrote:
On Wed, May 27, 2020 at 01:18:42PM -0500, Bjorn Helgaas wrote:
Is this
Hi Alim,
On 6/8/2020 8:15 AM, Alim Akhtar wrote:
>
>
>> -Original Message-
>> From: Martin K. Petersen
>> Sent: 03 June 2020 08:02
>> To: r...@kernel.org; Alim Akhtar
>> Cc: Martin K . Petersen ; k...@kernel.org;
> linux-
>> samsung-...@vger.kernel.org; avri.alt...@wdc.com;
>>
There is no need to select DRM_RCAR_WRITEBACK if DRM=n which just make
the generated .config a bit ugly.
# ARM devices
#
# end of ARM devices
CONFIG_DRM_RCAR_WRITEBACK=y
#
# Frame buffer Devices
Let DRM_RCAR_WRITEBACK depend on DRM_RCAR_DU instead.
Signed-off-by: Qian Cai
---
Hi Laurent,
> -Original Message-
> From: Laurent Pinchart
> Sent: Sunday, June 7, 2020 7:10 AM
> To: Vishal Sagar
> Cc: Hyun Kwon ; mche...@kernel.org;
> robh...@kernel.org; mark.rutl...@arm.com; Michal Simek
> ; linux-me...@vger.kernel.org;
> devicet...@vger.kernel.org;
This patch adds another way to attach bio flags to node writes.
Description: Give a way to attach REQ_META|FUA to node writes
given temperature-based bits. Now the bits indicate:
* REQ_META | REQ_FUA |
*5 |4 | 3 |2 |
On 2020/6/6 2:15, Denis Efremov wrote:
> Use kfree() instead of kvfree() to free sbi in
> f2fs_fill_super() because the memory is allocated with
> kzalloc() in the function.
Could you fix them in one patch?
In addition, we need to fix them in f2fs_put_super() as well.
Thanks,
>
> Fixes:
Currently arm64 personality syscall uses wrapper __arm64_sys_personality
to redirect to __arm64_sys_arm64_personality, it's easily confused,
Whereas using an normal hook arch_check_personality() can reject
additional settings like this for special case of different architectures.
This makes code
Hi Prakhar,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on arm64/for-next/core]
[also build test ERROR on powerpc/next soc/for-next v5.7 next-20200605]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also
On 2020/6/6 2:15, Denis Efremov wrote:
> Use kfree() instead of kvfree() to free super in
> read_raw_super_block() because the memory is allocated with
> kzalloc() in the function.
>
> Fixes: 5222595d093e ("f2fs: use kvmalloc, if kmalloc is failed")
> Signed-off-by: Denis Efremov
Reviewed-by:
On 2020/6/5 12:27, Daeho Jeong wrote:
> From: Daeho Jeong
>
> Added a new ioctl to send discard commands to whole data area of
> a regular file for security reason.
I guess this interface is introduced for security key destruction, if I'm
right, however, IIRC, discard(erase) semantics in
> -Original Message-
> From: Martin K. Petersen
> Sent: 03 June 2020 08:02
> To: r...@kernel.org; Alim Akhtar
> Cc: Martin K . Petersen ; k...@kernel.org;
linux-
> samsung-...@vger.kernel.org; avri.alt...@wdc.com;
> stanley@mediatek.com; linux-s...@vger.kernel.org; linux-arm-
>
> On Jun 7, 2020, at 10:02 PM, Laurent Pinchart
> wrote:
>
> How about depending on DRM_RCAR_DU instead, as DRM_RCAR_WRITEBACK is
> used to select compilation of rcar_du_writeback.c that is part of the
> rcar-du driver ?
Sure. I’ll send a v2.
Hi Prakhar,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on arm64/for-next/core]
[also build test WARNING on powerpc/next soc/for-next v5.7 next-20200605]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: af7b4801030c07637840191c69eb666917e4135d
commit: 9227942383307f97fa6992416f73af4a23ef972c phy: intel-lgm-emmc: Add
support for eMMC PHY
date: 5 months ago
config: x86_64-randconfig-a011-20200607 (attached
On 2020/6/5 7:50, Jaegeuk Kim wrote:
> This adds more IOs to attach flags.
>
> Fixes: d58f2f658159 ("f2fs: add node_io_flag for bio flags likewise
> data_io_flag")
> Signed-off-by: Jaegeuk Kim
Reviewed-by: Chao Yu
Thanks,
On 2020/6/5 7:50, Jaegeuk Kim wrote:
> This patch adds another way to attach bio flags to node writes.
>
> Description: Give a way to attach REQ_META|FUA to node writes
>given temperature-based bits. Now the bits indicate:
>* REQ_META | REQ_FUA
Excerpts from David Rientjes's message of June 7, 2020 8:57 pm:
> Thanks for trying it out, Alex. Would you mind sending your .config and
> command line? I assume either mem_encrypt=on or
> CONFIG_AMD_MEM_ENCRYPT_ACTIVE_BY_DEFAULT is enabled.
>
> Could you also give this a try?
>
> diff
> >
> > I would argue that setting the current process exe file check should just
> > be reduced to a "can you ptrace a children" check.
> > Here's why: any process can masquerade into another executable with ptrace.
> > One can fork a child, ptrace it, have the child execve("target_exe"), then
On Sun, Jun 07, 2020 at 12:48:53PM -0700, Linus Torvalds wrote:
> Rasmus, say the word and I'll mark you for authorship on the first one.
>
> Comments? Can you find something else wrong here, or some other fixup to do?
>
> Al, any reaction?
It's correct, but this
> + if (mask & (mode ^
Hi Qian,
Thank you for the patch.
On Sun, Jun 07, 2020 at 09:48:18PM -0400, Qian Cai wrote:
> There is no need to select DRM_RCAR_WRITEBACK if DRM=n which just make
> the generated .config a bit ugly.
>
> # ARM devices
> #
> # end of ARM devices
>
> CONFIG_DRM_RCAR_WRITEBACK=y
>
> #
> #
Hi,
On Mon, May 11, 2020 at 01:21:49PM +0900, Masahiro Yamada wrote:
> I think all the warnings have been fixed by now. Make it a fatal error.
>
Not entirely. With this patch in the tree, I get:
Building sparc64:allmodconfig ... failed
--
Error log:
error: the following would cause
On Mon, Jun 08, 2020 at 04:54:57AM +0300, Laurent Pinchart wrote:
> Hi Dinghao,
>
> Thank you for the patch.
>
> On Sat, May 23, 2020 at 07:54:26PM +0800, Dinghao Liu wrote:
> > pm_runtime_get_sync() increments the runtime PM usage counter even
> > when it returns an error code. Thus a pairing
Hi Dinghao,
Thank you for the patch.
On Sat, May 23, 2020 at 07:54:26PM +0800, Dinghao Liu wrote:
> pm_runtime_get_sync() increments the runtime PM usage counter even
> when it returns an error code. Thus a pairing decrement is needed on
> the error handling path to keep the counter balanced.
I
/scm/linux/kernel/git/arm64/linux.git
for-next/core
config: arm64-randconfig-r012-20200607 (attached as .config)
compiler: clang version 11.0.0 (https://github.com/llvm/llvm-project
e429cffd4f228f70c1d9df0e5d77c08590dd9766)
reproduce (this is a W=1 build):
wget
https
> -Original Message-
> From: linux-fpga-ow...@vger.kernel.org
> On Behalf Of t...@redhat.com
> Sent: Sunday, June 7, 2020 5:03 AM
> To: m...@kernel.org
> Cc: linux-f...@vger.kernel.org; linux-kernel@vger.kernel.org; Tom Rix
>
> Subject: [PATCH 1/1] fpga: dfl: Fix dead store
>
Thanks
On 2020/6/8 09:48, Keyur Patel wrote:
> ./ocfs2/mmap.c:65: bebongs ==> belonging
>
> Signed-off-by: Keyur Patel
Reviewed-by: Joseph Qi
> ---
> fs/ocfs2/mmap.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/ocfs2/mmap.c b/fs/ocfs2/mmap.c
> index
Fix to return negative error code -ENOMEM with the use of
ERR_PTR from dpu_encoder_init.
Fixes: 25fdd5933e4c ("drm/msm: Add SDM845 DPU support")
Signed-off-by: Chen Tao
---
drivers/gpu/drm/msm/disp/dpu1/dpu_encoder.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Hi Dinghao,
> From: Dinghao Liu, Sent: Sunday, June 7, 2020 6:32 PM
>
> pm_runtime_get_sync() increments the runtime PM usage counter even
> the call returns an error code. Thus a corresponding decrement is
> needed on the error handling path to keep the counter balanced.
>
> Signed-off-by:
./ocfs2/mmap.c:65: bebongs ==> belonging
Signed-off-by: Keyur Patel
---
fs/ocfs2/mmap.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/ocfs2/mmap.c b/fs/ocfs2/mmap.c
index 3a44e461828a..39a77e903fdf 100644
--- a/fs/ocfs2/mmap.c
+++ b/fs/ocfs2/mmap.c
@@ -62,7 +62,7 @@
There is no need to select DRM_RCAR_WRITEBACK if DRM=n which just make
the generated .config a bit ugly.
# ARM devices
#
# end of ARM devices
CONFIG_DRM_RCAR_WRITEBACK=y
#
# Frame buffer Devices
Signed-off-by: Qian Cai
---
drivers/gpu/drm/rcar-du/Kconfig | 1 +
1 file changed, 1
On 2020/6/8 06:07, Keyur Patel wrote:
> ./ocfs2/mmap.c:65: bebongs ==> belongs
>
This should be updated with your new change.
Thanks,
Joseph
> Signed-off-by: Keyur Patel
> ---
> fs/ocfs2/mmap.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/ocfs2/mmap.c
On 2020/5/14 21:02, Peter Zijlstra wrote:
> On Fri, May 08, 2020 at 08:34:57PM +0800, Aaron Lu wrote:
>> With this said, I realized a workaround for the issue described above:
>> when the core went from 'compatible mode'(step 1-3) to 'incompatible
>> mode'(step 4), reset all root level sched
On 2020/6/3 6:38, Mauro Carvalho Chehab wrote:
> As reported by Sphinx:
>
> Documentation/filesystems/f2fs.rst:229: WARNING: Malformed table.
> Text in column margin in table line 126.
>
> ==
>
>
In blkdev_get() we call __blkdev_get() to do some internal jobs and if
there is some errors in __blkdev_get(), the bdput() is called which
means we have released the refcount of the bdev (actually the refcount of
the bdev inode). This means we cannot access bdev after that point. But
acctually
On Sun, Jun 7, 2020 at 5:04 AM Michael S. Tsirkin wrote:
>
> On Fri, Jun 05, 2020 at 10:28:42AM +0900, David Stevens wrote:
> > On Fri, Jun 5, 2020 at 4:05 AM Michael S. Tsirkin wrote:
> > >
> > > On Tue, May 26, 2020 at 07:58:09PM +0900, David Stevens wrote:
> > > > This change adds a new
On 2020/6/7 03:08, Tom Seewald wrote:
> After commit 12abc5ee7873 ("tcp: add tcp_sock_set_nodelay") and
> commit c488aeadcbd0 ("tcp: add tcp_sock_set_user_timeout"), building the
> kernel with OCFS2_FS=y but without INET=y causes it to fail with:
>
> ld: fs/ocfs2/cluster/tcp.o: in function
Hi,
On Fri, Jun 05, 2020 at 10:39:55AM +0300, Denis Efremov wrote:
> Allow user to use alternative implementations of compression tools,
> such as pigz, pbzip2, pxz. For example, multi-threaded tools to
> speed up the build:
> $ make GZIP=pigz BZIP2=pbzip2
>
> Variables _GZIP, _BZIP2, _LZOP are
在 2020/6/5 22:37, Jan Kara 写道:
No need for braces here after you remove bdput(). With this fixed, feel
free to add:
Reviewed-by: Jan Kara
Thanks, I will fix it in v4.
Jason
在 2020/6/5 19:05, Sedat Dilek 写道:
On Fri, Jun 5, 2020 at 12:23 PM Jason Yan wrote:
In blkdev_get() we call __blkdev_get() to do some internal jobs and if
there is some errors in __blkdev_get(), the bdput() is called which
means we have released the refcount of the bdev (actually the
On Sun, 07 Jun 2020 18:02:44 -0700 Joe Perches wrote:
> On Mon, 2020-06-08 at 00:40 +, Yann Collet wrote:
> > Hi Vasily
> >
> >
> > If I do understand the discussion, the question is about usage of `&`
> > instead of `&&`,
> > and the speculation that it might be an error.
> >
> > It's
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: cf0c97f148e9e50aa5a7ddd1984a604dd2bde4af
commit: 0f04a81784fe3ddc00cae74c517265b3ddb8825c pinctrl: mcp23s08: Split to
three parts: core, I²C, SPI
date: 8 weeks ago
config: parisc-randconfig-c021-20200607
From: kernel test robot
drivers/pinctrl/pinctrl-mcp23s08_spi.c:129:1-3: WARNING: PTR_ERR_OR_ZERO can be
used
Use PTR_ERR_OR_ZERO rather than if(IS_ERR(...)) + PTR_ERR
Generated by: scripts/coccinelle/api/ptr_ret.cocci
Fixes: 0f04a81784fe ("pinctrl: mcp23s08: Split to three parts: core,
On Mon, 2020-06-08 at 00:40 +, Yann Collet wrote:
> Hi Vasily
>
>
> If I do understand the discussion, the question is about usage of `&` instead
> of `&&`,
> and the speculation that it might be an error.
>
> It's not an error. Unfortunately, explaining the reasoning behind this
>
A sequence counter write side critical section must be protected by some
form of locking to serialize writers. A plain seqcount_t does not
contain the information of which lock must be held when entering a write
side critical section.
Use the new seqcount_spinlock_t data type, which allows to
A sequence counter write side critical section must be protected by some
form of locking to serialize writers. A plain seqcount_t does not
contain the information of which lock must be held when entering a write
side critical section.
Use the new seqcount_spinlock_t data type, which allows to
A sequence counter write side critical section must be protected by some
form of locking to serialize writers. A plain seqcount_t does not
contain the information of which lock must be held when entering a write
side critical section.
Use the new seqcount_raw_spinlock_t data type, which allows to
A sequence counter write side critical section must be protected by some
form of locking to serialize writers. A plain seqcount_t does not
contain the information of which lock must be held when entering a write
side critical section.
Use the new seqcount_spinlock_t data type, which allows to
A sequence counter write side critical section must be protected by some
form of locking to serialize writers. A plain seqcount_t does not
contain the information of which lock must be held when entering a write
side critical section.
Use the new seqcount_raw_spinlock_t data type, which allows to
A sequence counter write side critical section must be protected by some
form of locking to serialize writers. A plain seqcount_t does not
contain the information of which lock must be held when entering a write
side critical section.
Use the new seqcount_spinlock_t data type, which allows to
A sequence counter write side critical section must be protected by some
form of locking to serialize writers. A plain seqcount_t does not
contain the information of which lock must be held when entering a write
side critical section.
Use the new seqcount_spinlock_t data type, which allows to
A sequence counter write side critical section must be protected by some
form of locking to serialize writers. A plain seqcount_t does not
contain the information of which lock must be held when entering a write
side critical section.
Use the new seqcount_spinlock_t data type, which allows to
A sequence counter write side critical section must be protected by some
form of locking to serialize writers. A plain seqcount_t does not
contain the information of which lock must be held when entering a write
side critical section.
Use the new seqcount_rwlock_t data type, which allows to
Hi,
This is v2 of the seqlock patch series:
[PATCH v1 00/25] seqlock: Extend seqcount API with associated locks
https://lore.kernel.org/lkml/20200519214547.352050-1-a.darw...@linutronix.de
Patches 1=>3 of this v2 series add documentation for the existing
seqlock.h datatypes and APIs.
A sequence counter write side critical section must be protected by some
form of locking to serialize writers. A plain seqcount_t does not
contain the information of which lock must be held when entering a write
side critical section.
Use the new seqcount_spinlock_t data type, which allows to
When building without CONFIG_CHELSIO_TLS_DEVICE a build error occurs:
drivers/net/ethernet/chelsio/cxgb4/cxgb4_uld.c:666:13: error:
‘cxgb4_uld_in_use’ defined but not used [-Werror=unused-function]
666 | static bool cxgb4_uld_in_use(struct adapter *adap)
| ^~~~
A sequence counter write side critical section must be protected by some
form of locking to serialize writers. A plain seqcount_t does not
contain the information of which lock must be held when entering a write
side critical section.
Use the new seqcount_spinlock_t data type, which allows to
1 - 100 of 439 matches
Mail list logo
