Hi
Am 02.07.20 um 12:12 schrieb Thomas Zimmermann:
> Thanks!
>
> Am 02.07.20 um 10:54 schrieb Tian Tao:
>> code refactoring for hibmc_drv_vdac.c, no actual function changes.
>>
>> v2:
>> remove the debug message.
>>
>> v3:
>> embedding connector and encoder in struct hibmc_drm_private.
>>
>> Sign
Add documentation for SPI daisy chain driver.
Signed-off-by: Adrian Fiergolski
---
.../bindings/spi/spi-daisy_chain.txt | 56 +++
1 file changed, 56 insertions(+)
create mode 100644 Documentation/devicetree/bindings/spi/spi-daisy_chain.txt
diff --git a/Documentation/de
>
> From: Bean Huo
>
> fshcd_exec_dev_cmd() can send query request and NOP request, and it is
Typo ?
> confusing that ufshcd_add_query_upiu_trace() prints us the "query_send"
> string in the trace log. Change it and add NOP key message in the trace
> print according to the dev_cmd type.
>
>
Hi Stephen,
On 06-07-20, 17:55, Stephen Rothwell wrote:
> Hi all,
>
> Commit
>
> 09c6b5536361 ("dmaengine: fsl-edma: fix wrong tcd endianness for big-endian
> cpu")
>
> is missing a Signed-off-by from its author.
the sob line was in the patch but after the three dashes causing it to
strippe
On Thu, 2019-06-20 at 16:19 +0800, Haiyan Song wrote:
> Hi Laurent,
>
> I downloaded your script and run it on Intel 2s skylake platform with spf-v12
> patch
> serials.
>
> Here attached the output results of this script.
>
> The following comparison result is statistics from the script outputs
When generating debug dump, driver firstly collects all data in binary
form, and then performs per-feature formatting to human-readable if it
is supported.
For ethtool -d, this is roughly incorrect for two reasons. First of all,
drivers should always provide only original raw dumps to Ethtool with
MT6779 bus frabric provides TrustZone security support and data
protection to prevent slaves from being accessed by unexpected
masters.
The security violations are logged and sent to the processor for
further analysis or countermeasures.
Any occurrence of security violation would raise an interrup
These patch series introduce a MediaTek MT6779 devapc driver.
MT6779 bus frabric provides TrustZone security support and data
protection to prevent slaves from being accessed by unexpected
masters.
The security violations are logged and sent to the processor for
further analysis or countermeasures
Add bindings for MT6779 devapc.
Signed-off-by: Neal Liu
---
.../soc/mediatek/devapc/devapc-mt6779.yaml | 58
1 file changed, 58 insertions(+)
create mode 100644
Documentation/devicetree/bindings/soc/mediatek/devapc/devapc-mt6779.yaml
diff --git
a/Documentation/
On Mon, Jul 06, 2020 at 10:57:07AM +0200, Jürgen Groß wrote:
> On 06.07.20 10:41, Michal Kubecek wrote:
> > this patch - now in mainline as commit 13cbc0cd4a30 ("x86/entry/32: Fix
> > #MC and #DB wiring on x86_32") - seems to break i586 builds with
> > CONFIG_XEN_PV=y as xenpv_exc_nmi and xenpv_exc
Hi Jason,
On 7/3/2020 12:46 PM, Jason Wang wrote:
>
> On 2020/7/2 下午9:35, Kishon Vijay Abraham I wrote:
>> Hi Jason,
>>
>> On 7/2/2020 3:40 PM, Jason Wang wrote:
>>> On 2020/7/2 下午5:51, Michael S. Tsirkin wrote:
On Thu, Jul 02, 2020 at 01:51:21PM +0530, Kishon Vijay Abraham I wrote:
> Th
Re-enable modular build of DES crypto algorithm (no longer auto-enabled
since commit be01369859b8aa07 ("esp, ah: modernize the crypto algorithm
selections")).
Signed-off-by: Geert Uytterhoeven
---
To be combined with "m68k: defconfig: Update defconfigs for v5.8-rc1".
---
arch/m68k/configs/amiga_
On 7/4/20 1:26 PM, Liu Yi L wrote:
> IOMMUs that support nesting translation needs report the capability info
need to report
> to userspace, e.g. the format of first level/stage paging structures.
>
> This patch reports nesting info by DOMAIN_ATTR_NESTING. Caller can get
> nesting info after se
Hi Yi,
On 7/4/20 1:26 PM, Liu Yi L wrote:
> This patch refactors the vfio_iommu_type1_ioctl() to use switch instead of
> if-else, and each cmd got a helper function.
command
>
> Cc: Kevin Tian
> CC: Jacob Pan
> Cc: Alex Williamson
> Cc: Eric Auger
> Cc: Jean-Philippe Brucker
> Cc: Joerg Roed
On Thu, Jul 02, 2020 at 05:51:42PM +0200, Krzysztof Kozlowski wrote:
> The bindings required interrupts for all SoCs but actually only the PWM
> timer clocksource (for S3C/S5P SoCs) was using them. This PWM timer
> clocksource driver is not used on Exynos SoCs thus the interrupts can be
> marked a
The current code assumes that CPUs are evenly spread among
NUMA nodes. That is generally incorrect and leads to failure
on systems that have different NUMA topology.
Signed-off-by: Alexander Gordeev
---
tools/perf/bench/numa.c | 27 +--
1 file changed, 13 insertions(+), 1
Several benchmarks have names that do not correspond to
their configuration. Fix that and also some whitespace
inconsistencies.
Signed-off-by: Alexander Gordeev
---
tools/perf/bench/numa.c | 42 +-
1 file changed, 21 insertions(+), 21 deletions(-)
diff --
I will learn how to use KernelShark. Try to solve my problem,thanks
for your suggestion.
Talk about I solved a problem with hung task milliseconds：
the process get anon_vma read lock when it directly reclaims
memory, but other process down anon_vma write lock,
long time waiting for write lock u
Hi all,
Please, find couple of fixes to the tool. Note, I did not bother
fixing leaked memory allocated with numa_allocate_cpumask().
Alexander Gordeev (3):
perf bench numa: fix incorrect NUMA toplogy assumption
perf bench numa: fix benchmark names
perf bench numa: fix wrong benchmark confi
This update fixes a wrong number of processes for one
benchmark and consolidates two others in a unified way.
Signed-off-by: Alexander Gordeev
---
tools/perf/bench/numa.c | 7 +++
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/tools/perf/bench/numa.c b/tools/perf/bench/numa.c
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: dcb7fd82c75ee2d6e6f9d8cc71c52519ed52e258
commit: 80591e61a0f7e88deaada69844e4a31280c4a38f kbuild: tell sparse about the
$ARCH
date: 8 months ago
config: nios2-randconfig-s032-20200706 (attached as .config
Hello,
>From Mr. Asita Hussain
This message might meet you in utmost surprise.
I am a banker by profession in Burkina-Faso, West Africa and currently
holding the post of manager in account and auditing department in our
bank. I have the opportunity of transferring the left over funds ($
25.5 Millio
On 2020-06-26 19:11, Ezequiel Garcia wrote:
> The hardware only supports 4:2:2, 4:2:0 or 4:0:0 (monochrome),
> 8-bit or 10-bit depth content.
>
> Verify that the PPS refers to a supported bitstream, and refuse
This should be SPS not PPS, same for hantro patch.
> unsupported bitstreams by failing
Yu-Hsuan Hsu 於 2020年7月4日 週六 下午7:34寫道：
>
> Guenter Roeck 於 2020年7月4日 週六 上午3:28寫道：
> >
> > On Fri, Jul 3, 2020 at 12:11 PM Yu-Hsuan Hsu wrote:
> > >
> > > Guenter Roeck 於 2020年7月3日 週五 下午11:58寫道：
> > > >
> > > > On Fri, Jul 3, 2020 at 3:56 AM Enric Balletbo i Serra
> > > > wrote:
> > > > >
> > >
Hi Sandy,
Am Montag, 6. Juli 2020, 09:59:44 CEST schrieb Sandy Huang:
> don't mask possible_crtcs if remote-point is disabled.
>
> Signed-off-by: Sandy Huang
> ---
> drivers/gpu/drm/drm_of.c | 5 +
> 1 file changed, 5 insertions(+)
>
> diff --git a/drivers/gpu/drm/drm_of.c b/drivers/gpu/dr
Currently, the bitops test consists of two parts: one part is executed
during module load, the second part during module unload. This is
cumbersome for the user, as he has to perform two steps to execute all
tests, and is different from most (all?) other tests.
Merge the two parts, so both are exe
Paolo Bonzini writes:
> On 13/06/20 00:05, Thomas Gleixner wrote:
>>- KVM
>>
>> KVM is inconsistent as well. Patches have been posted, but they have
>> not yet been commented on or picked up by the KVM folks.
>
> Hi Thomas,
>
> which patches are these? I must have missed them, and
Below is the list of build error/warning regressions/improvements in
v5.8-rc4[1] compared to v5.7[2].
Summarized:
- build errors: +4/-4
- build warnings: +38/-41
JFYI, when comparing v5.8-rc4[1] to v5.8-rc3[3], the summaries are:
- build errors: +0/-0
- build warnings: +0/-4
Note that th
On Mon, Jul 6, 2020 at 11:20 AM Arnd Bergmann wrote:
>
> > Because of these reasons, I'm proposing a misc (not-device) driver that
> > supports
> > many Intel architectures (and families) to expose the information.
> > I understand your proposal to first enhance existing _device_ drivers, but I
>
From: He Zhe
commit 0688e64bc600 ("NFS: Allow signal interruption of NFS4ERR_DELAYed
operations")
introduces nfs4_delay_interruptible which also needs an _unsafe version to
avoid the following call trace for the same reason explained in
commit 416ad3c9c006 ("freezer: add unsafe versions of freez
On Wed, May 20, 2020 at 04:58:37PM +0800, Dinghao Liu wrote:
> pm_runtime_get_sync() increments the runtime PM usage counter even
> 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
> ---
> drive
On Fri, Jun 26, 2020 at 09:52:13PM +0800, Wei Yang wrote:
> No functional change, just improve the readability and prepare for
> following cleanup.
It's pretty much redundant. It doesn't provide any meaningful
readability improvement. Please drop the patch.
--
Kirill A. Shutemov
On Fri, Jun 26, 2020 at 09:52:15PM +0800, Wei Yang wrote:
> Page tables is moved on the base of PMD. This requires both source
> and destination range should meet the requirement.
>
> Current code works well since move_huge_pmd() and move_normal_pmd()
> would check old_addr and new_addr again. And
Hygon Family 18h(Dhyana) support RAPL in bit 14 of CPUID 0x8007 EDX,
and has MSRs RAPL_PWR_UNIT/CORE_ENERGY_STAT/PKG_ENERGY_STAT. So add Hygon
Dhyana Family 18h support for RAPL.
The output is available via the energy-pkg pseudo event:
$ perf stat -a -I 1000 --per-socket -e power/energy-pkg/
On Fri, Jun 26, 2020 at 09:52:12PM +0800, Wei Yang wrote:
> move_page_tables() tries to move page table by PMD or PTE.
>
> The root reason is if it tries to move PMD, both old and new range should be
> PMD aligned. But current code calculate old range and new range separately.
> This leads to some
Hi Guo,
On Sat, 4 Jul 2020 03:34:18 +
guo...@kernel.org wrote:
> From: Guo Ren
>
> This patch enables "kprobe & kretprobe" to work with ftrace
> interface. It utilized software breakpoint as single-step
> mechanism.
>
> Some instructions which can't be single-step executed must be
> simul
On 22.06.20 22:03, Andra Paraschiv wrote:
An enclave, before being started, has its resources set. One of its
resources is CPU.
The NE CPU pool is set for choosing CPUs for enclaves from it. Offline
the CPUs from the NE CPU pool during the pool setup and online them back
during the NE CPU poo
On Sun, Jul 05, 2020 at 11:18:36PM +0300, Nikolay Aleksandrov wrote:
> > > By the way, I can't verify at the moment, but I think we can drop that
> > > whole
> > > hunk altogether since skb_header_pointer() is used and it will simply
> > > return
> > > an error if there isn't enough data for nsrc
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: dcb7fd82c75ee2d6e6f9d8cc71c52519ed52e258
commit: 5456ffdee666c66e27ccc1006f9afe83ad9f powerpc/spufs: simplify spufs
core dumping
date: 9 weeks ago
config: powerpc64-randconfig-c003-20200706 (attached
On 22.06.20 22:03, Andra Paraschiv wrote:
Before setting the memory regions for the enclave, the enclave image
needs to be placed in memory. After the memory regions are set, this
memory cannot be used anymore by the VM, being carved out.
Add ioctl command logic to get the offset in enclave m
On Fri, Jun 26, 2020 at 09:42:06AM +0200, Johan Hovold wrote:
> On Fri, Jun 26, 2020 at 04:24:20AM +, Phu Luu wrote:
> > From: Brant Merryman
> >
> > CP210x hardware disables auto-RTS but leaves auto-CTS when
> > in hardware flow control mode and UART on cp210x hardware
> > is disabled. This
On Fri, Jul 3, 2020 at 10:43 PM Daniel Gutson wrote:
> After analyzing the intel-spi driver, I came up to these observations that
> led me conclude that it is not what I need to use:
>
> * Some SPI Controllers have 0x as their VID DID bytes in the PCI config
> space. This causes that the PC
On Mon, Jul 06, 2020 at 09:53:55AM +0200, Geert Uytterhoeven wrote:
> On Mon, Jul 6, 2020 at 9:22 AM Greg Kroah-Hartman
> wrote:
> > look at the USB spec for an example of these terms being used in this
> > way for many decades.
>
> And when does the "gadget" enter the show? ;-)
It doesn't, as t
- don't panic kernel if f2fs_get_node_page() fails in
f2fs_recover_inline_data() or f2fs_recover_inline_xattr();
- return error number of f2fs_truncate_blocks() to
f2fs_recover_inline_data()'s caller;
Signed-off-by: Chao Yu
---
fs/f2fs/f2fs.h | 4 ++--
fs/f2fs/inline.c | 19 --
2020-07-06 17:22 GMT+09:00, Ju Hyung Park :
> Hi Namjae.
Hi Juhyung,
>
> Looks like I ported this incorrectly from the previous sdFAT base.
>
> I'll fix, test again and send v2.
Okay:) Thanks!
>
> Thanks.
>
> On Thu, Jul 2, 2020 at 2:16 PM Namjae Jeon wrote:
>>
>> >
>> > if (((attr->ia_valid
On Fri, Jul 03, 2020 at 04:59:49PM -0400, Liang, Kan wrote:
> On 7/3/2020 3:50 PM, Peter Zijlstra wrote:
> > If I'm not mistaken, this correctly deals with LBR_FORMAT_INFO, so can't
> > we also use the intel_pmu_arch_lbr_read() function for that case?
>
> But the intel_pmu_arch_lbr_read() doesn't
Hi,
On 06/07/2020 00:08, Jonathan Marek wrote:
On 7/3/20 1:29 PM, Dmitry Baryshkov wrote:
On 03/07/2020 18:14, Dmitry Baryshkov wrote:
On 03/07/2020 18:08, Jonathan Marek wrote:
On 7/3/20 11:03 AM, Dmitry Baryshkov wrote:
On 30/06/2020 00:17, Jonathan Marek wrote:
This series adds the missi
On Mon, 6 Jul 2020 09:19:45 +0800
Jia He wrote:
Hi,
> Previously, numa_off is set to true unconditionally in dummy_numa_init(),
> even if there is a fake numa node.
>
> But acpi will translate node id to NUMA_NO_NODE(-1) in acpi_map_pxm_to_node()
> because it regards numa_off as turning off the
From: Bolarinwa Olayemi Saheed
On any failure pcie_capability_read_word() sets it's last parameter, *val
to 0. If pci_config_read_word() fails the *val is reset to 0. Any function
which check only for a frabricated ~0 which fail in this case.
Include a check on the return value of pcie_capabilit
From: Bolarinwa Olayemi Saheed
On failure pcie_capability_read_dword() sets it's last parameter,
val to 0.
However, with Patch 11/11, it is possible that val is set to ~0 on
failure. This would introduce a bug because (x & x) == (~0 & x).
This bug can be avoided if the return value of pcie_capab
From: Bolarinwa Olayemi Saheed
On failure pcie_capability_read_dword() sets it's last parameter,
val to 0.
However, with Patch 11/11, it is possible that val is set to ~0 on
failure. This would introduce a bug because (x & x) == (~0 & x).
This bug can be avoided if the return value of pcie_capab
From: Bolarinwa Olayemi Saheed
On failure pcie_capability_read_dword() sets it's last parameter, val
to 0. In which case (val & PCI_EXP_DEVCTL2_LTR_EN) evaluates to 0.
However, with Patch 10/10, it is possible that val is set to ~0 on
failure. This would introduce a bug because (x & x) == (~0 & x
On Sun, Jul 05, 2020 at 02:16:16PM +0800, qiang.zh...@windriver.com wrote:
> From: Zhang Qiang
>
> Add a missing spinlock protection to the add operation of the
> "audio->play_queue"
> in "f_audio_out_ep_complete" function.
That says _what_ you did, but not _why_ you did that. Why is a lock
ne
From: Bolarinwa Olayemi Saheed
On failure pcie_capability_read_dword() sets it's last parameter,
val to 0.
However, with Patch 11/11, it is possible that val is set to ~0 on
failure. This would introduce a bug because (x & x) == (~0 & x).
This bug can be avoided if the return value of pcie_capab
From: Bolarinwa Olayemi Saheed
The default case of the switch statement is redundant since
PCI_EXP_SLTCTL_PCC is only a single bit. pcie_capability_read_word()
currently causes "On" value to be set if it fails. Patch 11/11
changes the behaviour of pcie_capability_read_word() so on falure the
"Of
From: Bolarinwa Olayemi Saheed
On failure pcie_capability_read_dword() sets it's last parameter,
val to 0.
However, with Patch 11/11, it is possible that val is set to ~0 on
failure. This would introduce a bug because (x & x) == (~0 & x).
This bug can be avoided if the return value of pcie_capa
On Sun, Jul 05, 2020 at 11:53:27PM +0200, Kars Mulder wrote:
> The function quirks_param_set() takes as argument a const char* pointer
> to the new value of the usbcore.quirks parameter. It then casts this
> pointer to a non-const char* pointer and passes it to the strsep()
> function, which overwr
Hi Yi,
Please add a commit message: instead of returning a boolean for
DOMAIN_ATTR_NESTING, arm_smmu_domain_get_attr() returns a
iommu_nesting_info handle.
On 7/4/20 1:26 PM, Liu Yi L wrote:
> Cc: Will Deacon
> Cc: Robin Murphy
> Cc: Eric Auger
> Cc: Jean-Philippe Brucker
> Suggested-by: Jea
Yi,
On 7/4/20 1:26 PM, Liu Yi L wrote:
> This patch exports iommu nesting capability info to user space through
> VFIO. User space is expected to check this info for supported uAPIs (e.g.
> PASID alloc/free, bind page table, and cache invalidation) and the vendor
> specific format information for
On Mon, Jul 6, 2020 at 11:02 AM Sedat Dilek wrote:
>
> On Mon, Jul 6, 2020 at 10:43 AM Sedat Dilek wrote:
> >
> > On Mon, Jul 6, 2020 at 10:39 AM Peter Zijlstra wrote:
> > >
> > > On Mon, Jul 06, 2020 at 09:09:55AM +0200, Sedat Dilek wrote:
> > > > [ Please CC me I am not subscribed to this mail
On Mon, Jul 6, 2020 at 12:53 PM Geert Uytterhoeven wrote:
>
> Currently, the bitops test consists of two parts: one part is executed
> during module load, the second part during module unload. This is
> cumbersome for the user, as he has to perform two steps to execute all
> tests, and is differen
On Sun, Jul 05, 2020 at 11:44:57PM +0200, Alexander A. Klimov wrote:
> Rationale:
> Reduces attack surface on kernel devs opening the links for MITM
> as HTTPS traffic is much harder to manipulate.
>
> Deterministic algorithm:
> For each file:
> If not .svg:
> For each line:
> If doesn
On 07/03/20 14:09, Vincent Guittot wrote:
> I have run the perf bench sched pipe that have have already run
> previously with this v6 and the results are similar to my previous
> tests:
> The impact is -1.61% similarly to v2 which is better compared the
> original -3.66% without your patch
Thanks
On Sat, Mar 14, 2020 at 11:30:27AM +0800, Xiaowei Bao wrote:
> Add the PCIe EP multiple PF support for DWC and Layerscape, add
> the doorbell MSIX function for DWC, use list to manage the PF of
> one PCIe controller, and refactor the Layerscape EP driver due to
> some platforms difference.
>
> Xia
On 22.06.20 22:03, Andra Paraschiv wrote:
Another resource that is being set for an enclave is memory. User space
memory regions, that need to be backed by contiguous memory regions,
are associated with the enclave.
One solution for allocating / reserving contiguous memory regions, that
is us
Hello,
syzbot found the following crash on:
HEAD commit:7ae77150 Merge tag 'powerpc-5.8-1' of git://git.kernel.org..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=14180d3510
kernel config: https://syzkaller.appspot.com/x/.config?x=be4578b3f1083656
das
On Mon, 6 Jul 2020 11:29:21 +0100
Jonathan Cameron wrote:
> On Mon, 6 Jul 2020 09:19:45 +0800
> Jia He wrote:
>
> Hi,
>
> > Previously, numa_off is set to true unconditionally in dummy_numa_init(),
> > even if there is a fake numa node.
> >
> > But acpi will translate node id to NUMA_NO_NODE(
Hello,
syzbot found the following crash on:
HEAD commit:bdc48fa1 checkpatch/coding-style: deprecate 80-column warn..
git tree: net
console output: https://syzkaller.appspot.com/x/log.txt?x=12b3ffe210
kernel config: https://syzkaller.appspot.com/x/.config?x=129ea1e5950835e5
dashboar
Hello,
syzbot found the following crash on:
HEAD commit:719fdd32 afs: Fix storage of cell names
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=10e0f8a310
kernel config: https://syzkaller.appspot.com/x/.config?x=ce0957b53c175ac4
dashboard link: https://
Hello,
syzbot found the following crash on:
HEAD commit:7cc2a8ea Merge tag 'block-5.8-2020-07-01' of git://git.ker..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1744dc8310
kernel config: https://syzkaller.appspot.com/x/.config?x=183dd243398ba7ec
das
Hii Maintainers,
I recently came across this list of janatorial tasks
for starters on DRM subsystem [1]. One of the tasks is replacing
conventional dmesg macros (like dev_info(), dev_warn() and dev_err())
with DRM dmesg macros [2]. And I need your input whether the
conversions to DRM dmesg
While booting arm64 device dragonboard 410c the following kernel
warning noticed on
Linux version 5.8.0-rc3-next-20200706.
metadata:
git branch: master
git repo: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
git commit: 5680d14d59bddc8bcbc5badf00dbbd4374858497
git
Initially the thermal framework had a very simple notification
mechanism to send generic netlink messages to the userspace.
The notification function was never called from anywhere and the
corresponding dead code was removed. It was probably a first attempt
to introduce the netlink notification.
The generic netlink protocol is implemented but the different
notification functions are not yet connected to the core code.
These changes add the notification calls in the different
corresponding places.
Reviewed-by: Amit Kucheria
Signed-off-by: Daniel Lezcano
---
v4:
- Fixed missing st
On Wed, Jul 01, 2020 at 07:33:25PM +, Sasha Levin wrote:
> Hi
>
> [This is an automated email]
>
> This commit has been processed because it contains a -stable tag.
> The stable tag indicates that it's relevant for the following trees: all
>
> The bot has tested the following trees: v5.7.6,
The cdev, tz and governor list, as well as their respective locks are
statically defined in the thermal_core.c file.
In order to give a sane access to these list, like browsing all the
thermal zones or all the cooling devices, let's define a set of
helpers where we pass a callback as a parameter t
The next patch will introduce the generic netlink protocol to handle
events, sampling and command from the thermal framework. In order to
deal with the thermal zone, it uses its unique identifier to
characterize it in the message. Passing an integer is more efficient
than passing an entire string.
Hi everybody,
this patchset adds xterm like mouse reporting features to the console.
The linux virtual console has support for mouse reporting since 1994 or so,
but the kernel only supports the original X10/X11 style standard protocols.
To support more protocols these patches expand the kernel st
Add additional defines for mouse event types. The change of the value
of TIOCL_SELBUTTONMASK deserves a bit more explanation :
The old value of 15 uses the first 4 bits and sends them unchanged back
to userspace if requested by an application. But in fact only the first
two bits have ever been use
We need two values to store the status of mouse reporting, both need at
least two (vc_protocol_mouse) or three (vc_report_mouse) bits.
Signed-off-by: Tammo Block
---
include/linux/console_struct.h | 9 -
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git a/include/linux/console_s
The SRG protocol indicates a button release by appending a "m" to the
report. In this case the button number is not 3 (RELEASEEVENT) but
the number of the button that was released. As release events are only
reported for the first three buttons (LOWBUTTON_MASK), we need to store
the number on click
This enables userspace to enable one of the mouse protocols and choose
one of the new event types by escape sequences.
And don't forget to reset protocol value also if resetting vc.
Signed-off-by: Tammo Block
---
drivers/tty/vt/vt.c | 17 +++--
1 file changed, 15 insertions(+), 2 de
On Mon, 6 Jul 2020 at 12:55, Naresh Kamboju wrote:
>
> While booting arm64 device dragonboard 410c the following kernel
> warning noticed on
> Linux version 5.8.0-rc3-next-20200706.
>
> metadata:
> git branch: master
> git repo:
> https://git.kernel.org/pub/scm/
Hello,
syzbot found the following crash on:
HEAD commit:cd77006e Merge tag 'hyperv-fixes-signed' of git://git.kern..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=14ef775510
kernel config: https://syzkaller.appspot.com/x/.config?x=183dd243398ba7ec
das
The URXVT protocol easy, all data analog to the old X10.
Signed-off-by: Tammo Block
---
drivers/tty/vt/vt.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/tty/vt/vt.c b/drivers/tty/vt/vt.c
index 766983a848bb..5861e4c85c84 100644
--- a/drivers/tty/vt/vt.c
+++ b/drivers/tty/vt/vt.c
This patch adds a description of the kernel interface(s) used for vt
console mouse reporting and describes the protocols and bitmasks.
Signed-off-by: Tammo Block
---
.../admin-guide/console-mouse-reporting.rst | 88 +++
Documentation/admin-guide/index.rst | 1 +
2 fi
While booting qemu_arm64 and qemu_arm with Linux version 5.8.0-rc3-next-20200706
the kernel panic noticed due to kernel NULL pointer dereference.
metadata:
git branch: master
git repo: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
git commit
On Wed, May 20, 2020 at 04:47:56PM +0800, Dinghao Liu wrote:
> pm_runtime_get_sync() increments the runtime PM usage counter even
> 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
> ---
> drive
On Wed, May 20, 2020 at 05:02:53PM +0800, Dinghao Liu wrote:
> pm_runtime_get_sync() increments the runtime PM usage counter even
> 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
> ---
> drive
On Mon, Jul 06, 2020 at 08:07:46AM +0200, Jan Ziak wrote:
> On Sun, Jul 5, 2020 at 1:58 PM Greg KH wrote:
> > It also is a measurable increase over reading just a single file.
> > Here's my really really fast AMD system doing just one call to readfile
> > vs. one call sequence to open/read/close:
syzbot has found a reproducer for the following crash on:
HEAD commit:1ca0fafd tcp: md5: allow changing MD5 keys in all socket s..
git tree: net
console output: https://syzkaller.appspot.com/x/log.txt?x=15ec52b710
kernel config: https://syzkaller.appspot.com/x/.config?x=bf3aec367b9a
On 7/5/20 3:10 AM, Kees Cook wrote:
> On Sat, Jul 04, 2020 at 08:10:33PM -0400, Matthew Wilcox wrote:
>> Left-right tree makes no sense. It doesn't distinguish the rbtree from its
>> predecessor the avl tree. I don't think it's helpful to rename a standard
>> piece of computing terminology unless
Hi Alexandre,
> Am 05.07.2020 um 12:32 schrieb agrive...@deutnet.info:
>
> From: Alexandre GRIVEAUX
>
> Use brcm,bcm4329-fmac instead of brcm,bcm4330-fmac.
>
> Signed-off-by: Alexandre GRIVEAUX
> ---
> arch/mips/boot/dts/ingenic/ci20.dts | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions
On Thu, Apr 02, 2020 at 08:01:59PM +0530, Sriram Dash wrote:
[...]
> > So the patch itself is correct though the commit log has to be fixed. You
> > should
> > also check if all the endpoint controller drivers existing currently
> > provides
> > epc_features.
>
> At the moment, there is no iss
On Mon, Jul 06, 2020 at 08:07:46AM +0200, Jan Ziak wrote:
> On Sun, Jul 5, 2020 at 1:58 PM Greg KH wrote:
> >
> > On Sun, Jul 05, 2020 at 06:09:03AM +0200, Jan Ziak wrote:
> > > On Sun, Jul 5, 2020 at 5:27 AM Matthew Wilcox wrote:
> > > >
> > > > On Sun, Jul 05, 2020 at 05:18:58AM +0200, Jan Ziak
On Mon, Jul 6, 2020 at 1:02 AM Tomi Valkeinen wrote:
>
> Hi,
>
> On 03/07/2020 22:36, Sam Ravnborg wrote:
> > Hi Tomi.
> >
> > On Fri, Jul 03, 2020 at 10:17:29AM +0300, Tomi Valkeinen wrote:
> >> On 30/06/2020 21:26, Adam Ford wrote:
> >>> The drm/omap driver was fixed to correct an issue where us
On Sun, Jul 5, 2020 at 3:31 PM Sungbo Eo wrote:
>
> NXP PCA9570 is a 4-bit I2C GPO expander without interrupt functionality.
> Its ports are controlled only by a data byte without register address.
>
> Datasheet: https://www.nxp.com/docs/en/data-sheet/PCA9570.pdf
>
> Signed-off-by: Sungbo Eo
> --
On 22.06.20 22:03, Andra Paraschiv wrote:
After all the enclave resources are set, the enclave is ready for
beginning to run.
Add ioctl command logic for starting an enclave after all its resources,
memory regions and CPUs, have been set.
The enclave start information includes the local chan
Hi,
When I built an allmodconfig kernel for arm64, and boot that in qemu
guest I see the following issues:
[...]
[ 10.451561][T1] Testing tracer function: PASSED
[ 33.087895][T1] Testing dynamic ftrace: .. filter did not
filter .. FAILED!
[ 51.127094][T1] [ cut here
On 22.06.20 22:03, Andra Paraschiv wrote:
An enclave is associated with an fd that is returned after the enclave
creation logic is completed. This enclave fd is further used to setup
enclave resources. Once the enclave needs to be terminated, the enclave
fd is closed.
Add logic for enclave te
101 - 200 of 1314 matches
Mail list logo
