> -Original Message-
> From: Rakesh Pillai
> Sent: Friday, July 24, 2020 11:51 AM
> To: 'Johannes Berg' ;
> 'ath...@lists.infradead.org'
> Cc: 'linux-wirel...@vger.kernel.org' ;
> 'linux-kernel@vger.kernel.org' ;
> 'kv...@codeaurora.org' ; 'da...@davemloft.net'
> ; 'k...@kernel.org' ;
On Sun, Jul 26, 2020 at 05:52:04PM +0200, Christoph Hellwig wrote:
> On Sun, Jul 26, 2020 at 08:49:28AM -0700, Linus Torvalds wrote:
> > On Sun, Jul 26, 2020 at 12:14 AM Christoph Hellwig wrote:
> > >
> > > Hi Al and Linus,
> > >
> > > currently a lot of the file system calls in the early in code
Le dim. 26 juil. 2020 à 18:15, Krzysztof Kozlowski a
écrit :
On Sun, Jul 26, 2020 at 06:12:27PM +0200, Paul Cercueil wrote:
Le dim. 26 juil. 2020 à 18:06, Krzysztof Kozlowski
a écrit
:
> On Sat, Jul 25, 2020 at 08:30:56PM +0200, Arnd Bergmann wrote:
> > On Sat, Jul 25, 2020 at
The following commit has been merged into the core/entry branch of tip:
Commit-ID: 543f5898d805e7e58bc5eadc20ed0a468368e7fd
Gitweb:
https://git.kernel.org/tip/543f5898d805e7e58bc5eadc20ed0a468368e7fd
Author:Thomas Gleixner
AuthorDate:Sun, 26 Jul 2020 18:14:43 +02:00
On Sun, Jul 26, 2020 at 06:12:27PM +0200, Paul Cercueil wrote:
>
>
> Le dim. 26 juil. 2020 à 18:06, Krzysztof Kozlowski a écrit
> :
> > On Sat, Jul 25, 2020 at 08:30:56PM +0200, Arnd Bergmann wrote:
> > > On Sat, Jul 25, 2020 at 2:17 PM Paul Cercueil
> > > wrote:
> > > > Le ven. 24 juil.
The ring buffer counter runs faster than hardware counter if the
period size in hw_param is larger than 240. Although the differce is
not much (around 2k frames), it causes false underrun in CRAS
sometimes because it's using 256 frames as period size in hw_param.
Using the hardware counter could
Le dim. 26 juil. 2020 à 18:06, Krzysztof Kozlowski a
écrit :
On Sat, Jul 25, 2020 at 08:30:56PM +0200, Arnd Bergmann wrote:
On Sat, Jul 25, 2020 at 2:17 PM Paul Cercueil
wrote:
> Le ven. 24 juil. 2020 à 17:54, Krzysztof Kozlowski
a
> écrit :
> > On Fri, Jul 24, 2020 at 05:50:06PM
On Sun, 26 Jul 2020 at 11:14, Mike Rapoport wrote:
>
> On Sat, Jul 25, 2020 at 06:16:48AM +0300, Jarkko Sakkinen wrote:
> > On Fri, Jul 24, 2020 at 11:27:46AM +0200, Ingo Molnar wrote:
> > >
> > > * Jarkko Sakkinen wrote:
> > >
> > > > Use text_alloc() and text_free() instead of module_alloc()
Le sam. 25 juil. 2020 à 20:30, Arnd Bergmann a écrit :
On Sat, Jul 25, 2020 at 2:17 PM Paul Cercueil
wrote:
Le ven. 24 juil. 2020 à 17:54, Krzysztof Kozlowski
a
écrit :
> On Fri, Jul 24, 2020 at 05:50:06PM +0200, Paul Cercueil wrote:
>> Le ven. 24 juil. 2020 à 17:33, Krzysztof
On Sat, Jul 25, 2020 at 08:30:56PM +0200, Arnd Bergmann wrote:
> On Sat, Jul 25, 2020 at 2:17 PM Paul Cercueil wrote:
> > Le ven. 24 juil. 2020 à 17:54, Krzysztof Kozlowski a
> > écrit :
> > > On Fri, Jul 24, 2020 at 05:50:06PM +0200, Paul Cercueil wrote:
> > >> Le ven. 24 juil. 2020 à 17:33,
Hello,
Documentation/filesystems/sharedsubtree.rst contains the following:
->mnt_flags
takes two more flags to indicate the propagation status of
the vfsmount. MNT_SHARE indicates that the vfsmount is a shared
vfsmount. MNT_UNCLONABLE
On 07/07, Chao Yu wrote:
> Don't let f2fs inner GC ruins original aging degree of segment.
>
> Signed-off-by: Chao Yu
> ---
> fs/f2fs/data.c| 2 +-
> fs/f2fs/f2fs.h| 5 +++--
> fs/f2fs/gc.c | 4 ++--
> fs/f2fs/segment.c | 55 ---
> 4
Fold the misaligned u64 workarounds into the main quotactl flow instead
of implementing a separate compat syscall handler.
Signed-off-by: Christoph Hellwig
---
arch/x86/entry/syscalls/syscall_32.tbl | 2 +-
fs/quota/Kconfig | 5 --
fs/quota/Makefile
Hi all,
the i386 ABI is a little special in that it uses less than natural
alignment for 64-bit integer types (u64 and s64), and a significant
amount of our compat handlers deals with just that. Unfortunately
there is no good way to check for this specific quirk at runtime,
similar how
Add a helper to check if the calling syscall needs a fixup for
non-natural 64-bit type alignment in the compat ABI. This will only
return true for i386 syscalls on x86_64.
Signed-off-by: Christoph Hellwig
---
arch/x86/include/asm/compat.h | 1 +
include/linux/compat.h| 9 +
2
lift the compat_s64 and compat_u64 definitions into common code using the
COMPAT_FOR_U64_ALIGNMENT symbol for the x86 special case.
Signed-off-by: Christoph Hellwig
---
arch/arm64/include/asm/compat.h | 2 --
arch/mips/include/asm/compat.h| 2 --
arch/parisc/include/asm/compat.h | 2 --
Always use so that we can move more declarations to
common code. In two of the three cases the asm include was in addition
to an existing one for anyway.
Signed-off-by: Christoph Hellwig
---
arch/arm64/include/asm/stat.h | 2 +-
arch/arm64/kernel/process.c | 1 -
arch/arm64/kernel/ptrace.c
On 07/07, Chao Yu wrote:
> Previous implementation of aligned pinfile allocation will:
> - allocate new segment on cold data log no matter whether last used
> segment is partially used or not, it makes IOs more random;
> - force concurrent cold data/GCed IO going into warm data area, it
> can make
…
> > Changes in v3:
> > - add missing '-' for patch rule in kmalloc/kzalloc call args
> > - selfcheck rule dropped from patchset
…
> All three applied. …
Will the software development discussion be continued by patches according to
previously mentioned ideas and remaining open issues?
The entries for JZ47xx SoCs and its drivers lacked MIPS mailing list.
Only MTD NAND driver pointed linux-mtd. Add linux-mips so the relevant
patches will get attention of MIPS developers.
Signed-off-by: Krzysztof Kozlowski
Acked-by: Paul Cercueil
---
Changes since v1:
1. Do not update DMA
The entry for MIPS Ingenic JZ4780 DMA driver is not up to date anymore.
Zubair Lutfullah Kakakhel's email bounces and no maintenance is
provided.
Suggested-by: Paul Cercueil
Signed-off-by: Krzysztof Kozlowski
---
Changes since v1:
1. New patch
---
MAINTAINERS | 5 -
1 file changed, 5
Hi Steven,
On Sat, Jul 25, 2020 at 05:09:14PM +0200, Oscar Carter wrote:
> Hi Steven,
>
> On Fri, Jul 24, 2020 at 02:34:57PM -0400, Steven Rostedt wrote:
> > On Fri, 24 Jul 2020 19:55:00 +0200
> > Oscar Carter wrote:
> >
> > > > Which one of the above is this patch set for?
> > >
> > > This
On Wed, Jul 01, 2020 at 03:02:06PM +0200, Johan Hovold wrote:
> On Sun, Jun 07, 2020 at 09:53:49PM +0530, Manivannan Sadhasivam wrote:
> > Add gpiochip support for Maxlinear/Exar USB to serial converter
> > for controlling the available gpios.
> >
> > Inspired from cp210x usb to serial converter
On Sun, Jul 26, 2020 at 08:49:28AM -0700, Linus Torvalds wrote:
> On Sun, Jul 26, 2020 at 12:14 AM Christoph Hellwig wrote:
> >
> > Hi Al and Linus,
> >
> > currently a lot of the file system calls in the early in code (and the
> > devtmpfs kthread) rely on the implicit set_fs(KERNEL_DS) during
On Sun, Jul 26, 2020 at 12:14 AM Christoph Hellwig wrote:
>
> Hi Al and Linus,
>
> currently a lot of the file system calls in the early in code (and the
> devtmpfs kthread) rely on the implicit set_fs(KERNEL_DS) during boot.
> This is one of the few last remaining places we need to deal with to
Hi,
Sorry for the late reply!
On Wed, Jul 01, 2020 at 12:34:33PM +0200, Johan Hovold wrote:
> On Sun, Jun 07, 2020 at 09:53:48PM +0530, Manivannan Sadhasivam wrote:
> > Add support for MaxLinear/Exar USB to Serial converters. This driver
> > only supports XR21V141X series but it can be extended
73] kvm: mmu:
> page_track: Fix RCU list API usage
> config: i386-randconfig-a006-20200726 (attached as .config)
> compiler: gcc-9 (Debian 9.3.0-14) 9.3.0
> reproduce (this is a W=1 build):
> git checkout 93d62a873f87bf69209a5c29d62b9497888de6d6
> # save the attach
Applied to nvme-5.9, thanks.
On Fri, Jul 24, 2020 at 12:33:51PM -0700, Keith Busch wrote:
> On Fri, Jul 24, 2020 at 11:25:17AM -0600, Logan Gunthorpe wrote:
> > + /*
> > +* The passthru NVMe driver may have a limit on the number of segments
> > +* which depends on the host's memory fragementation. To solve this,
> >
On Sun, 26 Jul 2020 07:50:54 -0700 Joe Perches wrote:
> On Sun, 2020-07-26 at 09:45 +0200, SeongJae Park wrote:
> > diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
> []
> > @@ -721,6 +721,7 @@ sub read_word_corrections {
> > my %deprecated_terms_fix;
> >
The LBR could be enabled on the guest if host perf supports LBR
(checked via x86_perf_get_lbr()) and the vcpu model is compatible
with the host one.
If LBR is disabled on the guest, the bits [0, 5] of the read-only
MSR_IA32_PERF_CAPABILITIES which tells about the record format
stored in the LBR
In addition to DEBUGCTLMSR_LBR, any KVM trap caused by LBR msrs access
will result in a creation of guest LBR event per-vcpu.
If the guest LBR event is scheduled on with the corresponding vcpu context,
KVM will pass-through all LBR records msrs to the guest. The LBR callstack
mechanism
The current vPMU only supports Architecture Version 2. According to
Intel SDM "17.4.7 Freezing LBR and Performance Counters on PMI", if
IA32_DEBUGCTL.Freeze_LBR_On_PMI = 1, the LBR is frozen on the virtual
PMI and the KVM would emulate to clear the LBR bit (bit 0) in
IA32_DEBUGCTL. Also, guest
The guest hypervisor may configure MSR_IA32_PERF_CAPABILITIES to unmask
some vmx-supported bits in vcpu->arch.perf_capabilities, and the requested
value could affect the exposure of features in the intel_pmu_refresh().
Refactoring its initialization path clears the way for the above usage.
The LBR feature would be enabled on the guest if:
- the KVM is enabled and the PMU is enabled and,
- the msr-based-feature IA32_PERF_CAPABILITIES is supporterd and,
- the supported returned value for lbr_fmt from this msr is not zero.
The LBR feature would be disabled on the guest if:
- the
When vcpu sets DEBUGCTLMSR_LBR in the MSR_IA32_DEBUGCTLMSR, the KVM handler
would create a guest LBR event which enables the callstack mode and none of
hardware counter is assigned. The host perf would schedule and enable this
event as usual but in an exclusive way.
The guest LBR event will be
Userspace could enable guest LBR feature when the exactly supported
LBR format value is initialized to the MSR_IA32_PERF_CAPABILITIES
and the LBR is also compatible with vPMU version and host cpu model.
Signed-off-by: Like Xu
---
arch/x86/kvm/vmx/capabilities.h | 9 -
SVM already has specific handlers of MSR_IA32_DEBUGCTLMSR in the
svm_get/set_msr, so the x86 common part can be safely moved to VMX.
Add vmx_supported_debugctl() to refactor the throwing logic of #GP.
Signed-off-by: Like Xu
---
arch/x86/kvm/vmx/capabilities.h | 5 +
arch/x86/kvm/vmx/vmx.c
The vPMU uses GUEST_LBR_IN_USE_IDX (bit 58) in 'pmu->pmc_in_use' to
indicate whether a guest LBR event is still needed by the vcpu. If the
vcpu no longer accesses LBR related registers within a scheduling time
slice, and the enable bit of LBR has been unset, vPMU will treat the
guest LBR event as
When the LBR records msrs has already been pass-through, there is no
need to call vmx_update_intercept_for_lbr_msrs() again and again, and
vice versa.
Signed-off-by: Like Xu
---
arch/x86/kvm/vmx/pmu_intel.c | 13 +
arch/x86/kvm/vmx/vmx.h | 3 +++
2 files changed, 16
It's reasonable to call vmx_set_intercept_for_msr() in other vmx-specific
files (e.g. pmu_intel.c), so expose it without semantic changes hopefully.
Signed-off-by: Like Xu
---
arch/x86/kvm/vmx/vmx.c | 4 ++--
arch/x86/kvm/vmx/vmx.h | 2 ++
2 files changed, 4 insertions(+), 2 deletions(-)
diff
Hi Paolo,
Please review this new version for the Kernel 5.9 release, and
Sean may not review them as he said in the previous email
https://lore.kernel.org/kvm/20200710162819.gf1...@linux.intel.com/
You may cherry-pick the perf patches "3cb9d5464c1c..e1ad1ac2deb8"
from the branch "tip/perf/core"
Hi Dan, and everybody,
Thank you for the patch.
On Sat, Jul 04, 2020 at 01:02:51PM -0700, Dan Williams wrote:
> Recent events have prompted a Linux position statement on inclusive
> terminology. Given that Linux maintains a coding-style and its own
> idiomatic set of terminology here is a
Thanks,
applied to nvme-5.8.
On Thu, Jun 25, 2020 at 06:52:10PM +0200, Wolfram Sang wrote:
> Missing this firmware is not fatal, my wifi card still works. Even more,
> I couldn't find any documentation what it is or where to get it. So, I
> don't think the users should be notified if it is missing. If you browse
> the net,
On Fri, Jul 24, 2020 at 02:24:32PM -0400, Qian Cai wrote:
> On Fri, Jun 19, 2020 at 05:17:47PM -0700, Matthew Wilcox wrote:
> > On Fri, Jun 19, 2020 at 05:17:50PM -0400, Qian Cai wrote:
> > > Running a syscall fuzzer by a normal user could trigger this,
> > >
> > > [55649.32][T515839]
On Fri, Jul 24, 2020 at 09:19:21PM +0530, Kanchan Joshi wrote:
> zone-append with bvec iov_iter gives WARN_ON, and returns -EINVAL.
> Add new helper to process such iov_iter and add pages in bio honoring
> zone-append specific constraints.
> This is used to enable zone-append with io-uring
On Fri, Jul 24, 2020 at 09:19:20PM +0530, Kanchan Joshi wrote:
> For zoned block device, opt in for zone-append by setting
> FMODE_ZONE_APPEND during open. Make direct IO submission path use
> IOCB_ZONE_APPEND to send bio with append op. Make direct IO completion
> return written-offset, in bytes,
> All three applied. …
Can the accepted software adjustment be seen by the interface
of a public development repository?
Regards,
Markus
Zone append is a protocol context that ha not business showing up
in a file system interface. The right interface is a generic way
to report the written offset for an append write for any kind of file.
So we should pick a better name like FMODE_REPORT_APPEND_OFFSET
(not that I particularly like
On Fri, Jul 24, 2020 at 09:19:18PM +0530, Kanchan Joshi wrote:
> From: SelvaKumar S
>
> kiocb->ki_complete(...,long ret2) - change ret2 to long long.
> This becomes handy to return 64bit written-offset with appending write.
> Change callers using ki_complete prototype.
There is no need for this
On Sun, Jul 26, 2020 at 10:10:52AM +0100, Matthew Wilcox (Oracle) wrote:
> If the filesystem has block size < page size and we end up calling
> iomap_page_create() in iomap_page_mkwrite_actor(), the uptodate bits
> would be zero, which causes us to skip writeback of blocks which are
> !uptodate in
On Sun, Jul 26, 2020 at 05:03:19PM +0200, Christoph Hellwig wrote:
> Hi Jens,
>
> this series contains a bunch of different BDI cleanups. The biggest item
> is to isolate block drivers from the BDI in preparation of changing the
> lifetime of the block device BDI in a follow up series.
Ooops,
From: Sivaprakash Murugesan
Convert QCOM pci bindings to YAML schema
Signed-off-by: Sivaprakash Murugesan
---
[v2]
- Referenced pci-bus.yaml
- removed duplicate properties already referenced by pci-bus.yaml
- Addressed comments from Rob
.../devicetree/bindings/pci/qcom,pcie.txt
Hi Vinod.
On Thu, Jul 23, 2020 at 10:04:39PM +0530, Vinod Koul wrote:
> Hi,
>
> This series adds driver and bindings for Lontium LT9611 bridge chip which
> takes MIPI DSI as input and HDMI as output.
>
> This chip can be found in 96boards RB3 platform [1] commonly called DB845c.
>
> [1]:
Ever since the switch to blk-mq, a lower device not used for VM
writeback will not be marked congested, so the check will never
trigger.
Signed-off-by: Christoph Hellwig
---
drivers/block/drbd/drbd_nl.c | 6 --
1 file changed, 6 deletions(-)
diff --git a/drivers/block/drbd/drbd_nl.c
This case isn't ever used.
Signed-off-by: Christoph Hellwig
Reviewed-by: Johannes Thumshirn
---
drivers/block/drbd/drbd_req.c | 4
include/linux/drbd.h | 1 -
2 files changed, 5 deletions(-)
diff --git a/drivers/block/drbd/drbd_req.c b/drivers/block/drbd/drbd_req.c
index
BDI_CAP_SYNCHRONOUS_IO is only checked in the swap code, and used to
decided if ->rw_page can be used on a block device. Just check up for
the method instead. The only complication is that zram needs a second
set of block_device_operations as it can switch between modes that
actually support
The last user of SB_I_MULTIROOT is disappeared with commit f2aedb713c28
("NFS: Add fs_context support.")
Signed-off-by: Christoph Hellwig
Reviewed-by: Johannes Thumshirn
---
fs/namei.c | 4 ++--
include/linux/fs.h | 1 -
2 files changed, 2 insertions(+), 3 deletions(-)
diff --git
Replace BDI_CAP_NO_ACCT_WB with a positive BDI_CAP_WRITEBACK_ACCT to
make the checks more obvious. Also remove the pointless
bdi_cap_account_writeback wrapper that just obsfucates the check.
Signed-off-by: Christoph Hellwig
---
fs/fuse/inode.c | 3 ++-
include/linux/backing-dev.h
Add two helpers macros to avoid boilerplate code for the queue sysfs
entries.
Signed-off-by: Christoph Hellwig
Reviewed-by: Johannes Thumshirn
---
block/blk-sysfs.c | 248 +++---
1 file changed, 58 insertions(+), 190 deletions(-)
diff --git
Replace the two negative flags that are always used together with a
single positive flag that indicates the writeback capability instead
of two related non-capabilities. Also remove the pointless wrappers
to just check the flag.
Signed-off-by: Christoph Hellwig
---
fs/9p/vfs_file.c
The raid5 and raid10 drivers currently update the read-ahead size,
but not the optimal I/O size on reshape. To prepare for deriving the
read-ahead size from the optimal I/O size make sure it is updated
as well.
Signed-off-by: Christoph Hellwig
---
drivers/md/raid10.c | 22
Set up a readahead size by default, as very few users have a good
reason to change it.
Signed-off-by: Christoph Hellwig
Acked-by: David Sterba [btrfs]
Acked-by: Richard Weinberger [ubifs, mtd]
---
block/blk-core.c | 1 -
drivers/mtd/mtdcore.c | 1 +
fs/9p/vfs_super.c | 4 ++--
The BDI_CAP_STABLE_WRITES is one of the few bits of information in the
backing_dev_info shared between the block drivers and the writeback code.
To help untangling the dependency replace it with a queue flag and a
superblock flag derived from it. This also helps with the case of e.g.
a file
There is no point in trying to call bdev_read_page if SWP_SYNCHRONOUS_IO
is not set, as the device won't support it.
Signed-off-by: Christoph Hellwig
---
mm/page_io.c | 18 ++
1 file changed, 10 insertions(+), 8 deletions(-)
diff --git a/mm/page_io.c b/mm/page_io.c
index
Generate the queue_sysfs_entry given that we have all the required
information for it, and rename the generated show and store methods
to match the other ones in the file.
Signed-off-by: Christoph Hellwig
Reviewed-by: Johannes Thumshirn
---
block/blk-sysfs.c | 31
On 7/24/20 7:06 AM, Vaishnav M A wrote:
> Attached is a patch for the mikroBUS driver which helps to
> instantiate an add-on board device on a mikrobus port by fetching
> the device identifier manifest binary from an EEPROM on-board
> the device. mikroBUS is an add-on board socket standard by
>
Hi Jens,
this series contains a bunch of different BDI cleanups. The biggest item
is to isolate block drivers from the BDI in preparation of changing the
lifetime of the block device BDI in a follow up series.
Changes since v2:
- fix a rw_page return value check
- fix up various changelogs
Just checking SB_I_CGROUPWB for cgroup writeback support is enough.
Either the file system allocates its own bdi (e.g. btrfs), in which case
it is known to support cgroup writeback, or the bdi comes from the block
layer, which always supports cgroup writeback.
Signed-off-by: Christoph Hellwig
Drivers shouldn't really mess with the readahead size, as that is a VM
concept. Instead set it based on the optimal I/O size by lifting the
algorithm from the md driver when registering the disk. Also set
bdi->io_pages there as well by applying the same scheme based on
max_sectors.
On Sun, Jul 26, 2020 at 07:50:12PM +0530, Aditya Jain wrote:
> Cleaning up messy multiline function declarations in hal_phy_cfg.h
>
> This patch is a continuation of patch "Clean up function declarations"
This should be merged with that patch, no reason to make it separate.
>
> Signed-off-by:
This adds full 802.1q VLAN support to the qca8k, allowing the use of
vlan_filtering and more complicated bridging setups than allowed by
basic port VLAN support.
Tested with a number of untagged ports with separate VLANs and then a
trunk port with all the VLANs tagged on it.
v2:
- Return
On Sun, 2020-07-26 at 09:45 +0200, SeongJae Park wrote:
> diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
[]
> @@ -721,6 +721,7 @@ sub read_word_corrections {
> my %deprecated_terms_fix;
> read_word_corrections($deprecated_terms_file, \%deprecated_terms_fix);
> my $deprecated_terms =
+Enric
Hello Alexandre,
Thanks for the series.
On Wed, 20 May 2020 at 05:27, Alexandre Courbot wrote:
>
> This series adds support for the encoder present on MT8183. It is very similar
> to the one in MT8173, but with different capabilities and using a new firmware
> interface (SCP, while
On Fri, Jul 24, 2020 at 09:14:26AM +0200, Juri Lelli wrote:
> Hi,
>
> On 07/07/20 00:04, Peng Liu wrote:
> > 'commit 840d719604b0 ("sched/deadline: Update rq_clock of later_rq when
> > pushing a task")'
> > introduced the update_rq_clock() to fix the "used-before-update" bug.
> >
> > 'commit
Hi Alexandre,
Last review on my side, this series looks mostly good.
On Mon, 13 Jul 2020 at 03:09, Alexandre Courbot wrote:
>
> Different chips have different supported bitrate ranges. Move the list
s/bitrate ranges/formats
> of supported formats to the platform data, and split the output and
Randy Dunlap a écrit :
Drop duplicated words in arch/powerpc/ header files.
How did you detect them ? Do you have some script for tgat, or you
just read all comments ?
Cc: Michael Ellerman
You say you Cc Michael, but in fact you don't ... Allthough he is the
powerpc maintainer
Adjust spacing in macro definitions to align them and improve
readbility
Signed-off-by: Aditya Jain
---
drivers/staging/rtl8723bs/include/hal_phy_cfg.h | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/staging/rtl8723bs/include/hal_phy_cfg.h
Clean up multiline function declartions in hal_phy_cfg.h
to improve code readablility
Signed-off-by: Aditya Jain
---
.../staging/rtl8723bs/include/hal_phy_cfg.h | 44 ---
1 file changed, 9 insertions(+), 35 deletions(-)
diff --git
Cleaning up messy multiline function declarations in hal_phy_cfg.h
This patch is a continuation of patch "Clean up function declarations"
Signed-off-by: Aditya Jain
---
.../staging/rtl8723bs/include/hal_phy_cfg.h | 56 ++-
1 file changed, 16 insertions(+), 40 deletions(-)
Fixing ERROR: "foo *bar" should be "foo *bar" in hal_phy_cfg.h
as reported by checkpatch.pl
Signed-off-by: Aditya Jain
---
.../staging/rtl8723bs/include/hal_phy_cfg.h| 18 +-
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git
Hi all,
The following series of patches fixes code style issues in
the file staging/drivers/rtl8723bs/include/hal_phy_cfg.h
Regards,
Aditya Jain
Em Thu, May 14, 2020 at 03:39:42PM -0500, Josh Poimboeuf escreveu:
> On Fri, Mar 08, 2019 at 10:17:47AM -0800, Davidlohr Bueso wrote:
> > On Thu, 07 Mar 2019, Arnaldo Carvalho de Melo wrote:
> > > You forgot to update tools/perf/Documentation/perf-bench.txt, and please
> > > take a look at
Quoting Alex Williamson (2020-07-26 14:30:52)
> On Sun, 26 Jul 2020 17:49:07 +1000
> Geoffrey McRae wrote:
>
> > Hi All,
> >
> > The commit 22540ca3d00d2990a4148a13b92209c3dc5422db causes a Windows KVM
> > guest running under QEMU with a VFIO passthrough GPU to randomly stall
> > when using
Add devicetree binding document for ADXRS290, a dual-axis MEMS gyroscope.
Reviewed-by: Rob Herring
Signed-off-by: Nishant Malpani
---
No changes in v4.
No changes in v3.
Changes in v2:
- use 'const' instead of 'enum' while setting the compatible string
since only a single item is
ADXRS290 is a high performance MEMS pitch and roll (dual-axis in-plane)
angular rate sensor (gyroscope) designed for use in stabilization
applications. It also features an internal temperature sensor and
programmable high-pass and low-pass filters.
Add support for ADXRS290 in direct-access mode
On 26/07/20 5:45 pm, Jonathan Cameron wrote:
On Fri, 24 Jul 2020 16:31:59 +0530
Nishant Malpani wrote:
ADXRS290 is a high performance MEMS pitch and roll (dual-axis in-plane)
angular rate sensor (gyroscope) designed for use in stabilization
applications. It also features an internal
Linus,
I was greatly confused and tried to confuse you.
Somehow I misunderstood your last version and didn't bother to read it
again until now.
Sorry for noise and thanks for your explanations.
Oleg.
On 07/25, Linus Torvalds wrote:
>
> On Sat, Jul 25, 2020 at 12:28 PM Oleg Nesterov wrote:
>
On 26/07/20 1:33 pm, Andy Shevchenko wrote:
On Fri, Jul 24, 2020 at 2:02 PM Nishant Malpani
wrote:
ADXRS290 is a high performance MEMS pitch and roll (dual-axis in-plane)
angular rate sensor (gyroscope) designed for use in stabilization
applications. It also features an internal temperature
The following commit has been merged into the core/entry branch of tip:
Commit-ID: aadfc2f957cb470a5a7e52cc41a2fa86e784bcd2
Gitweb:
https://git.kernel.org/tip/aadfc2f957cb470a5a7e52cc41a2fa86e784bcd2
Author:Ingo Molnar
AuthorDate:Sat, 25 Jul 2020 11:19:51 +02:00
Ingo Molnar writes:
> The noinstr attribute is to be specified before the return type in the
> same way 'inline' is used.
>
> Similar cases were recently fixed for x86, via:
>
> 7f6fa101dfac: ("x86: Correct noinstr qualifiers")
>
> These 2 cases were carried over by the new generic entry code.
Ingo Molnar writes:
> The __secure_computing() callback only exists on CONFIG_SECCOMP=y,
No. There is a stub function for the SECCOMP=n case.
> and on architectures that have CONFIG_HAVE_ARCH_SECCOMP_FILTER.
which is a prerequiste for converting over.
> Instead of complicating the #ifdef
> > +void i2c_free_slave_host_notify_device(struct i2c_client *client)
> > +{
> > + i2c_slave_unregister(client);
> > + kfree(client->dev.platform_data);
> > + i2c_unregister_device(client);
> > +}
> > +EXPORT_SYMBOL_GPL(i2c_free_slave_host_notify_device);
>
> Sidenote: With my recent
On Sat, Jul 25, 2020 at 11:45 PM Alexandre Courbot
wrote:
>
> On Thu, Jul 16, 2020 at 5:23 AM Ezequiel Garcia
> wrote:
> >
> > Now that slice invariant parameters have been moved,
> > the driver no longer needs this control, so drop it.
> >
> > Signed-off-by: Ezequiel Garcia
> > ---
> >
On 2020-07-26 23:32, Geoffrey McRae wrote:
On 2020-07-26 23:30, Alex Williamson wrote:
On Sun, 26 Jul 2020 17:49:07 +1000
Geoffrey McRae wrote:
Hi All,
The commit 22540ca3d00d2990a4148a13b92209c3dc5422db causes a Windows
KVM
guest running under QEMU with a VFIO passthrough GPU to
On 2020-07-26 23:30, Alex Williamson wrote:
On Sun, 26 Jul 2020 17:49:07 +1000
Geoffrey McRae wrote:
Hi All,
The commit 22540ca3d00d2990a4148a13b92209c3dc5422db causes a Windows
KVM
guest running under QEMU with a VFIO passthrough GPU to randomly stall
when using the GPU leading to the
On Sun, 26 Jul 2020 17:49:07 +1000
Geoffrey McRae wrote:
> Hi All,
>
> The commit 22540ca3d00d2990a4148a13b92209c3dc5422db causes a Windows KVM
> guest running under QEMU with a VFIO passthrough GPU to randomly stall
> when using the GPU leading to the guest assuming that the driver has
>
On 2020/7/26 19:21, Alexander A. Klimov wrote:
> Rationale:
> Reduces attack surface on kernel devs opening the links for MITM
> as HTTPS traffic is much harder to manipulate.
>
> Signed-off-by: Alexander A. Klimov
> ---
> Continuing my work started at 93431e0607e5 with unmaintained stuff
Change subject to:
RISC-V: KVM: kernel mmio read/write support
Also add 1-2 sentences of commit description.
On Fri, Jul 24, 2020 at 2:25 PM Yifei Jiang wrote:
>
> Signed-off-by: Yifei Jiang
> Signed-off-by: Mingwang Li
> ---
> arch/riscv/kvm/vcpu_exit.c | 38
301 - 400 of 609 matches
Mail list logo
