Hi, Miroslav.
> On Oct 2, 2024, at 19:44, Miroslav Benes wrote:
>
> Hello,
>
> could you also include the selftests as discussed before, please?
>
> Miroslav
Should I include selftests in one patch?
Regards.
Wardenjohn.
On Thu 2024-10-03 16:06:59, zhang warden wrote:
> Hi,Miroslav.
>
> > could you also include the selftests as discussed before, please?
>
> Should I submit the selftests in one patch?
I would put it into a separate patch from the patch adding the
"stack_order" attribute.
You might split the sel
Hello,
On Sun, 29 Sep 2024, Wardenjohn wrote:
> As previous discussion, maintainers think that patch-level sysfs interface is
> the
> only acceptable way to maintain the information of the order that klp_patch
> is
> applied to the system.
>
> However, the previous patch introduce klp_ops int
As previous discussion, maintainers think that patch-level sysfs interface is
the
only acceptable way to maintain the information of the order that klp_patch is
applied to the system.
However, the previous patch introduce klp_ops into klp_func is a optimization
methods of the patch introducing
On 9/20/24 20:49, Artur Alves Cavalcante de Barros wrote:
On 9/20/24 4:10 AM, David Gow wrote:
On Fri, 20 Sept 2024 at 00:01, Shuah Khan wrote:
On 9/16/24 18:51, Artur Alves wrote:
Hi all,
This is part of a hackathon organized by LKCAMP[1], focused on writing
tests using KUnit. We reached o
On 9/20/24 12:10 PM, Shuah Khan wrote:
On 9/20/24 01:10, David Gow wrote:
On Fri, 20 Sept 2024 at 00:01, Shuah Khan
wrote:
On 9/16/24 18:51, Artur Alves wrote:
Hi all,
This is part of a hackathon organized by LKCAMP[1], focused on writing
tests using KUnit. We reached out a while ago asking
On 9/20/24 4:10 AM, David Gow wrote:
On Fri, 20 Sept 2024 at 00:01, Shuah Khan wrote:
On 9/16/24 18:51, Artur Alves wrote:
Hi all,
This is part of a hackathon organized by LKCAMP[1], focused on writing
tests using KUnit. We reached out a while ago asking for advice on what
would be a useful
On 9/20/24 01:10, David Gow wrote:
On Fri, 20 Sept 2024 at 00:01, Shuah Khan wrote:
On 9/16/24 18:51, Artur Alves wrote:
Hi all,
This is part of a hackathon organized by LKCAMP[1], focused on writing
tests using KUnit. We reached out a while ago asking for advice on what
would be a useful co
On Fri, 20 Sept 2024 at 00:01, Shuah Khan wrote:
>
> On 9/16/24 18:51, Artur Alves wrote:
> > Hi all,
> >
> > This is part of a hackathon organized by LKCAMP[1], focused on writing
> > tests using KUnit. We reached out a while ago asking for advice on what
> > would be a useful contribution[2] and
On 9/19/24 1:01 PM, Shuah Khan wrote:
On 9/16/24 18:51, Artur Alves wrote:
Hi all,
This is part of a hackathon organized by LKCAMP[1], focused on writing
tests using KUnit. We reached out a while ago asking for advice on what
would be a useful contribution[2] and ended up choosing data structur
On 9/16/24 18:51, Artur Alves wrote:
Hi all,
This is part of a hackathon organized by LKCAMP[1], focused on writing
tests using KUnit. We reached out a while ago asking for advice on what
would be a useful contribution[2] and ended up choosing data structures
that did not yet have tests.
This p
Hi all,
This is part of a hackathon organized by LKCAMP[1], focused on writing
tests using KUnit. We reached out a while ago asking for advice on what
would be a useful contribution[2] and ended up choosing data structures
that did not yet have tests.
This patch adds tests for the llist data str
Hi Maintainer,
I have update the patch base on your feedback, please help review again.
V3:
-Fix initial value;
-Remove unnecessary checks about mod->sects_attrs
-Check sysfs_creat_* return value as error code
-Reorder the reveral of successful operations before exiting
We will use the informati
Hi folks,
This is the third version of the patch to fix the softlockup in EDMM
iotcl()[1][2].
If we run an enclave equipped with large EPC(30G or greater on my platfrom)
on the Linux with kernel preemptions disabled(by configuring
"CONFIG_PREEMPT_NONE=y"), we will get the following softlockup wa
From: "Madhavan T. Venkataraman"
Reliable stacktracing requires that we identify when a stacktrace is
terminated early. We can do this by ensuring all tasks have a final
frame record at a known location on their task stack, and checking
that this is the final frame record in the chain.
All tasks
The BCM2711 has a designware USB controller that is commonly used
on the CM4 and RPi400. There is a desire to use thes machines with
a standard UEFI+ACPI stack as is being done with the normal RPi4.
This patch enables this by adding ACPI module boilerplate to the
existing dwc2 controller.
It shou
Hi,
Here is the last patch of the series which had minor problem in v2,
the rest of the patches are already applied by Krzysztof Kozlowski.
Changelog:
v3: - Added new optional reg property for emc-tables nodes in order to
fix dt_binding_check warning.
Please note that I will prepare
On Tue, 30 Mar 2021 09:17:19 -0500
David Lechner wrote:
> On 3/30/21 3:08 AM, Carlis wrote:
> > From: Xuezhi Zhang
> >
> > This adds a new module for the ST7789V controller with parameters
> > for the Waveshare 2inch LCD module.
> >
> > Signed-off-by: Xuezhi Zhang
> > ---
> > v2:change compat
nvmem: Change to unified property interface
Change from using device tree (Open Firmware) APIs to the unified
'fwnode' interface.
Change of_nvmem_cell_get() to fwnode_nvmem_cell_get(), and add a
wrapper for of_nvmem_cell_get().
Change of_nvmem_device_get() to fwnode_nvmem_device_get(). There
are
On 3/30/21 3:08 AM, Carlis wrote:
From: Xuezhi Zhang
This adds a new module for the ST7789V controller with parameters for
the Waveshare 2inch LCD module.
Signed-off-by: Xuezhi Zhang
---
v2:change compatible value.
v3:change author name.
---
MAINTAINERS| 8 +
drivers/
From: Xuezhi Zhang
This adds a new module for the ST7789V controller with parameters for
the Waveshare 2inch LCD module.
Signed-off-by: Xuezhi Zhang
---
v2:change compatible value.
v3:change author name.
---
MAINTAINERS| 8 +
drivers/gpu/drm/tiny/Kconfig | 14 ++
drive
Hello:
This patch was applied to netdev/net-next.git (refs/heads/master):
On Sun, 21 Mar 2021 22:48:48 +0900 you wrote:
> Abstract: would like to directly set dql.min_limit value inside a
> driver to improve BQL performances of a CAN USB driver.
>
> CAN packets have a small PDU: for classical CA
On Tue, 16 Feb 2021 10:03:50 -0500, Pavel Tatashin wrote:
> v3: - Sync with linux-next where arch_get_mappable_range() was
> introduced.
> v2: - Added test-by Tyler Hicks
> - Addressed comments from Anshuman Khandual: moved check under
> IS_ENABLED(CONFIG_RANDOMIZE_BASE),
Abstract: would like to directly set dql.min_limit value inside a
driver to improve BQL performances of a CAN USB driver.
CAN packets have a small PDU: for classical CAN maximum size is
roughly 16 bytes (8 for payload and 8 for arbitration, CRC and
others).
I am writing an CAN driver for an USB i
Changelog
v3
- Re-sending because it still has not landed in mainline.
- Sync with mainline
- Added Acked-by: Baoquan He
v2
- Added review-by's
- Sync with mainline
Allow to study performance shutdown via kexec reboot calls by having kmsg
log saved via pstor
This patchset is v3 of a previous version [1].
v2 -> v3:
- Coalesced all checks in one function (Marc's feedback)
- Allow sgi_ops on cpuif mismatch (to keep v4.1 doorbell
mechanism that works fine even if GIC CPUIF < v4.1)
v1 -> v2:
- Fixed vGIC behaviour accordi
Hi,
it took some time, but now we got the official ACPI id for the RX6110 RTC driver
from Seiko Epson.
regards,
Claudius
Johannes Hahn (1):
rtc: rx6110: add ACPI bindings to I2C
drivers/rtc/rtc-rx6110.c | 12
1 file changed, 12 insertions(+)
--
2.30.1
Hi,
This new patch replaces the path_is_under() check with
current_chrooted() as it is done with user namespaces. Indeed, it is
much more simple to check the current root instead of limiting access to
a subset of files.
The chroot system call is currently limited to be used by processes with
the
Hi Marcel (and linux bluetooth),
Here are a few suspend improvements based on user reports we saw on
ChromeOS and feedback from Hans de Goede on the mailing list.
I have tested this using our ChromeOS suspend/resume automated tests
(full SRHealth test coverage and some suspend resume stress tes
*Commit f21916ec4826 ("s390/vfio-ap: clean up vfio_ap resources when KVM
pointer invalidated") introduced a change that results in a circular
lockdep when a Secure Execution guest that is configured with
crypto devices is started. The problem resulted due to the fact that the
patch moved the settin
From: Alexandru Tachici
Currently AD7124-8 driver cannot use more than 8 IIO channels
because it was assigning the channel configurations bijectively
to channels specified in the device-tree. This is not possible
to do when using more than 8 channels as AD7124-8 has only 8
configuration registers
Hi,
This patch series gives the opportunity to users to not manually
configure the list of LSM enabled at boot but instead always rely on the
up-to-date list of existing LSMs. Indeed, CONFIG_LSM may never be
updated with a make oldconfig whereas users may select new LSMs over
time. With this pat
Hi Guido,
On Fri, 2021-02-19 at 10:38 +0100, Guido Günther wrote:
> Hi,
> On Wed, Dec 16, 2020 at 07:22:32PM +0100, Guido Günther wrote:
> > This allows us to shut down the mipi power domain on the imx8. The
> > alternative
> > would be to drop the dphy from the mipi power domain in the SOCs devi
Hi,
On Wed, Dec 16, 2020 at 07:22:32PM +0100, Guido Günther wrote:
> This allows us to shut down the mipi power domain on the imx8. The alternative
> would be to drop the dphy from the mipi power domain in the SOCs device tree
> and only have the DSI host controller visible there but since the PD i
This is for adding FITRIM ioctl functionality to exFAT filesystem.
To do that, add generic ioctl function and FITRIM handler.
Changelog
=
v2->v3:
- Remove unnecessary local variable
- Merge all changes to a single patch
v1->v2:
- Change variable declaration order as reverse tree style.
-
v3: - Sync with linux-next where arch_get_mappable_range() was
introduced.
v2: - Added test-by Tyler Hicks
- Addressed comments from Anshuman Khandual: moved check under
IS_ENABLED(CONFIG_RANDOMIZE_BASE), added
WARN_ON(start_linear_pa > end_linear_pa);
v2 at https://lore.kernel.org/lkml/20210122204038.3238-1-ggherdov...@suse.cz
Changes wrt v2:
- removed redundant "#ifdef CONFIG_ACPI_CPPC_LIB"
Giovanni Gherdovich (1):
x86,sched: On AMD EPYC set freq_max = max_boost in schedutil invariant
formula
drivers/cpufreq/acpi-cpufreq.c | 61 +++
Changelog
v3
- Added review-by Tyler
- Sync with mainline
v2
- Addressed Tyler Hicks comments
- added mutex_destroy()
- comment in lo_open()
- added lock around lo_disk
===
In our environment we are using systemd portable containers in
squashfs formats, convert them into loop device, a
Hi,
This series adds support for ARM SCMI Protocol based IIO Device.
This driver provides support for Accelerometer and Gyroscope sensor
using new SCMI Sensor Protocol defined by the upcoming SCMIv3.0 ARM
specification, which is available at
https://developer.arm.com/documentation/den0056/c/
Th
This set provides a platform standardized way to access PCI
config space. It does that via an Arm specific interface
exported by the firmware. The Arm specification this is
based on can be found here:
The Arm PCI Configuration Space Access Firmware Interface
https://developer.arm.com/documentation
With the ongoing work to add BQL to Socket CAN, I figured out that it
would be nice to have an easy way to mesure the latency.
And one easy way to do so it to check the round trip time of the
packet by doing the difference between the software rx timestamp and
the software tx timestamp.
rx timest
Add two sysfs nodes to the Intel MAX10 BMC driver: mac_address
and mac_count. The mac_address provides the first of a series
of sequential MAC addresses assigned to the FPGA card. The
mac_count indicates how many MAC addresses are assigned to the
card.
Changelog v2 -> v3:
- Updated Date and Kern
Hello,
This patch fixes I/O errors during BLKRRPART ioctl() behavior right
after format operation that changed logical block size of the block
device with a same file descriptor opened.
Testcase:
The following testcase is a case of NVMe namespace with the following
conditions:
- Current L
Post the regression fix in a standalone patch as Andrew suggested for
-stable branch better back porting. This is rebased on the latest
master branch of mainline kenrel, surely there's almost no change
comparing with v2.
https://lore.kernel.org/linux-mm/20201220082754.6900-1-...@redhat.com/
Tested
This allows us to shut down the mipi power domain on the imx8. The alternative
would be to drop the dphy from the mipi power domain in the SOCs device tree
and only have the DSI host controller visible there but since the PD is mostly
about the PHY that would defeat it's purpose.
This is basically
From: SeongJae Park
On a few of our systems, I found frequent 'unshare(CLONE_NEWNET)' calls
make the number of active slab objects including 'sock_inode_cache' type
rapidly and continuously increase. As a result, memory pressure occurs.
In more detail, I made an artificial reproducer that resem
This patch fixes object remain in the offline per-cpu quarantine as
describe below.
Free objects will get into per-cpu quarantine if enable generic KASAN.
If a cpu is offline and users use kmem_cache_destroy, kernel will detect
objects still remain in the offline per-cpu quarantine and report erro
IPQ6018 has the QPIC NAND controller of version 1.5.0, which
uses the BAM DMA. Add support for the QPIC BAM, QPIC NAND and
enable the same in the board DTS file.
[V3]:
- Rebased on v5.10-rc6
- Renamed the qpic bam dma node name from 'dma' to 'dma-controller'
- Update the de
Add new macro definition to "ingenic,sysost.h", exchange the original
ABI values of OST_CLK_PERCPU_TIMER and OST_CLK_GLOBAL_TIMER, prepare
for the upcoming new OST driver.
I'm sure that exchanging the ABI values of OST_CLK_PERCPU_TIMER and
OST_CLK_GLOBAL_TIMER will not affect the existing related
This patch add FriendlyArm ZeroPi support.
Wiki:
http://wiki.friendlyarm.com/wiki/index.php/ZeroPi
Schematic:
http://wiki.friendlyarm.com/wiki/images/7/71/ZeroPi_20190731_Schematic.pdf
v1:
- Remove the extra spaces in description text.
v2:
- Remove the ehci0 and ohci0 device nodes.
- Remove the
The polling mode workaround for the FU540-C000 on HiFive Unleashed A00
board was added earlier. The logic for this seems to work only in case
the interrupt property was missing/not added into the i2c0 device node.
Here we address this issue by identifying the SOC based on compatibility
string and
This is a resend of v3 as the the original, sent over 6 hours ago, is yet
to make it to LKML.
- Changes since v2:
* set status to PCI_ERS_RESULT_RECOVERED, in case of successful link
reset, if and only if the initial value of error status is
PCI_ERS_RESULT_DISCONNECT or PCI_ERS_RESULT_NO_A
- Changes since v2:
* set status to PCI_ERS_RESULT_RECOVERED, in case of successful link
reset, if and only if the initial value of error status is
PCI_ERS_RESULT_DISCONNECT or PCI_ERS_RESULT_NO_AER_DRIVER.
- Changes since v1:
* changed the commit message to clarify what broke post commi
Final (?) version of my "small improvements to ingenic-drm" patchset.
Most of the patches of V2 have been merged to drm-misc-next, except this
one which required some more work.
In the CRTC's .atomic_check callback, the size of the gamma LUT property
is now checked, so that only a complete 256-en
This patch is created and tested on top of mainline linux
commit 856deb866d16 ("Linux 5.9-rc5")
Reference log of "make dt_binding_check" is available here[1].
Just in case required the log of dt_binding_check without this patch
is available here[2]
[1] https://paste.ubuntu.com/p/d2bXwvpFz9/
[2]
Hi Sam,
On 27/8/20 10:59, Enric Balletbo i Serra wrote:
> The first 4 patches of the series version 2:
> - drm/bridge_connector: Set default status connected for eDP connectors
> - drm/bridge: ps8640: Get the EDID from eDP control
> - drm/bridge: ps8640: Return an error for incorrect attach
Hi,
On 15/09/2020 14:40, Enric Balletbo i Serra wrote:
> Hi Sam,
>
> On 27/8/20 10:59, Enric Balletbo i Serra wrote:
>> The first 4 patches of the series version 2:
>> - drm/bridge_connector: Set default status connected for eDP connectors
>> - drm/bridge: ps8640: Get the EDID from eDP contro
From: Mike Rapoport
Hi,
This is yet another attempt to enable SPARSEMEM on ARC.
I've boot tested it on nSIM with haps_hs_defconfig with highmem and
sparsemem enabled.
With sparsemem the kernel text becomes a bit smaller, but bss and data are
slightly increased:
$ size discontig/vmlinux sparse
The first 4 patches of the series version 2:
- drm/bridge_connector: Set default status connected for eDP connectors
- drm/bridge: ps8640: Get the EDID from eDP control
- drm/bridge: ps8640: Return an error for incorrect attach flags
- drm/bridge: ps8640: Print an error if VDO control fails
Add usb-typec detection support for the Intel LGM SoC based boards.
Original driver is not supporting usb detection on Intel LGM SoC based boards
then we debugged and fixed the issue, but before sending our patches Mr.Krzyszto
has sent the same kind of patches, so I have rebased over his latest pa
Hi Pablo,
> This patch is much smaller and if you confirm this is address the
> issue, then this is awesome.
Yes, I can confirm the updated patch does fix the kernel panic. I have retested
on the Pixel 4 XL with version 4.14.180. Please see the updated patchset v3.
Thanks,
Will
Will McVicker (
On Mon, 27 Jul 2020 22:17:33 +0800, Joakim Zhang wrote:
> This patch intends to implement intmux PM.
>
> ChangeLogs:
> V2->V3:
> 1. allocate u32 saved_reg for a per channel.
>
> V1->V2:
> 1. add more detailed commit message.
> 2. use u32 for 32bit HW registers.
> 3. fix kb
This patch intends to implement intmux PM.
ChangeLogs:
V2->V3:
1. allocate u32 saved_reg for a per channel.
V1->V2:
1. add more detailed commit message.
2. use u32 for 32bit HW registers.
3. fix kbuild failures.
4. move trivial functions into their respecti
On Fri, Jul 17, 2020 at 01:34:34PM +0200, Arnaud Ferraris wrote:
> Understood, sorry about that. Should I do a "clean" re-send for this one?
It's fine, please just remember this for future submissions.
signature.asc
Description: PGP signature
Le 17/07/2020 à 13:21, Mark Brown a écrit :
> On Fri, Jul 17, 2020 at 12:38:56PM +0200, Arnaud Ferraris wrote:
>> This patch fixes the automatic clock selection so it always selects
>> distinct input and output clocks.
>
> Please don't send new patches in reply to old ones, it buries things and
>
On Fri, Jul 17, 2020 at 12:38:56PM +0200, Arnaud Ferraris wrote:
> This patch fixes the automatic clock selection so it always selects
> distinct input and output clocks.
Please don't send new patches in reply to old ones, it buries things and
makes it hard to keep track of what the current versio
This patch fixes the automatic clock selection so it always selects
distinct input and output clocks.
v2 -> v3:
- Update code comment, fix formatting and add more detailed explanations
in commit message
v1 -> v2:
- compare clock indexes (and not the location in the clock table) to
make sure i
Hi linux-pm,
ChromeOS has a udev rule to chown the `power/wakeup` attribute so that
the power manager can modify it during runtime.
(https://source.chromium.org/chromiumos/chromiumos/codesearch/+/master:src/platform2/power_manager/udev/99-powerd-permissions.rules)
In our automated tests, we fo
On 7/6/20 6:18 PM, Chu Lin wrote:
> Per max6581, reg 4d and reg 4e is used for temperature read offset.
> This patch will let the user specify the temperature read offset for
> max6581. This patch is tested on max6581 and only applies to max6581.
>
Since this is a single patch, you don't need pat
Per max6581, reg 4d and reg 4e is used for temperature read offset.
This patch will let the user specify the temperature read offset for
max6581. This patch is tested on max6581 and only applies to max6581.
Testing:
echo 16250 > temp2_offset
cat temp2_offset
16250
echo 17500 > temp3_offset
cat te
The overall goal of this patch is to add tracepoints around mmap_lock
acquisition. This will let us collect latency histograms, so we can see
how long we block for in the contended case. Our goal is to collect this
data across all of production at Google, so low overhead is critical.
I'm sending t
An architecture protecting the guest memory against unauthorized host
access may want to enforce VIRTIO I/O device protection through the
use of VIRTIO_F_IOMMU_PLATFORM.
Let's give a chance to the architecture to accept or not devices
without VIRTIO_F_IOMMU_PLATFORM.
Pierre Morel (1):
s390: vir
Hello everyone,
Context
---
Here is my V3 of my patches that add the support for the Rockchip
RK3288w which is a revision of the RK3288. It is mostly the same SOC
except for, at least, one clock tree which is different.
This difference is only known by looking at the BSP kernel [1].
Currentl
Hi,
Just a "gentleman ping"
Regards,
Christophe.
On 27/04/2020 12:00, Christophe Roullier wrote:
> No new feature, just to simplify stm32 part to be easier to use.
> Add by default all Ethernet clocks in DT, and activate or not in function
> of phy mode, clock frequency, if property "st,ext-phy
Remove the explicit prefetch check when using vfio-ccw devices.
This check does not trigger in practice as all Linux channel programs
are intended to use prefetch.
Version 3 improves logging by including the UUID of the vfio device
that triggers the warning. A custom rate limit is used because
th
This series is against v5.4-rc3
I am posting "avalon-dma" update alone and going to post "avalon-test"
update as a follow-up or in the next round.
Changes since v2:
- avalon_dma_register() return value bug fixed;
- device_prep_slave_sg() does not crash dmaengine_prep_slave_single() now;
- kernel
Hi,
We have a new Atom Airmont core based product which does not support
RTC as persistent clock source.
Presently, platform ops get/set wallclock always use MC146818 RTC/CMOS
device to read & set time. This causes boot failure on our SOC with no
RTC. More specifically, it hangs in RTC driver's m
Reading /sys/class/leds//trigger returns all available LED triggers.
However, the size of this file is limited to PAGE_SIZE because of the
limitation for sysfs attribute.
Enabling LED CPU trigger on systems with thousands of CPUs easily hits
PAGE_SIZE limit, and makes it impossible to see all avai
Patch to support INT33FE ACPI pseudo-device on hardware with USB Micro-B
connector.
v4:
- Micro-B variant: Don't print error to the kernel log if i2c_acpi_new_device()
has returned -EPROBE_DEFER.
v3:
- Rename TypeB variant to Micro-B (we have only one such device for now and it
has Micro-B co
Patch to support INT33FE ACPI pseudo-device on hardware with USB Micro-B
connector.
v3:
- Rename TypeB variant to Micro-B (we have only one such device for now and it
has Micro-B connector)
- Rebase on current linus/master
- Remove empty lines and replace "TypeC" by "Type-C"
v2:
Instead of defi
Hi,
There is a new product which does not support RTC as persistent clock source.
Platform ops get/set wallclock are used to get/set timespec through kernel
timekeeping read/update_persistent_clock64() routines. Presently, get/set
wallclock ops always use MC146818A RTC/CMOS device to read & set
> Problem description:
>
> A node with Adaptec 6405 controller, latest BIOS V5.3-0[19204] A lot
> of disks attached to the controller. Simple test: running mkfs.ext4
> on many disks on the same controller in parallel (mkfs is not
> important here, any serious io load trigger
Problem description:
A node with Adaptec 6405 controller, latest BIOS V5.3-0[19204]
A lot of disks attached to the controller.
Simple test: running mkfs.ext4 on many disks on the same controller in
parallel (mkfs is not important here, any serious io load triggers controller
ab
On Wed, Aug 14, 2019 at 11:58:22AM -0400, Rich Felker wrote:
> On Wed, Aug 14, 2019 at 05:43:59PM +0200, Christian Brauner wrote:
> > Hey everyone,
> >
> > This patch adds support for waiting on the current process group by
> > specifying waitid(P_PGID, 0, ...) as discussed in [1]. The details why
On Wed, Aug 14, 2019 at 05:43:59PM +0200, Christian Brauner wrote:
> Hey everyone,
>
> This patch adds support for waiting on the current process group by
> specifying waitid(P_PGID, 0, ...) as discussed in [1]. The details why
> we need to do this are in the commit message of [PATCH 1/1] so I won
Hey everyone,
This patch adds support for waiting on the current process group by
specifying waitid(P_PGID, 0, ...) as discussed in [1]. The details why
we need to do this are in the commit message of [PATCH 1/1] so I won't
repeat them here.
I've picked this up since the thread has gone stale and
In this 3rd version of the patch series, I have compressed the patches
of the previous patch series into one patch. This was suggested by Christoph
Hellwig.
The suggestion was to remove the pte_lookup functions and use the g
et_user_pages* functions directly instead of the pte_lookup functions.
T
Changes in v3:
- add Multi-Arch: same to debian/control for linux-libc-dev
Changes in v2:
- forward $debarch from mkdebian to builddeb
- use dpkg-architecture -qDEB_HOST_MULTIARCH instead of $CC -dumpmachine
Cedric Hombourger (1):
builddeb: generate multi-arch friendly linux-libc-dev packa
v2 -> v3:
* patch 1-4: Abandoned
* patch 5:
- Eliminate "flags" (suggested by Uladzislau Rezki)
- Based on https://lkml.org/lkml/2019/6/6/455
and https://lkml.org/lkml/2019/7/3/661
v1 -> v2:
* patch 3: Rename __find_vmap_area to __search_va_in_busy_tree
instead of __search_va_fr
This patch is part of a split of the following patch:
https://lkml.org/lkml/2019/6/18/268
To fix Enric comments from https://lkml.org/lkml/2019/6/25/949
I extract it from the other serie to speed up acceptance because
other patches need it to be upstreamed.
Changes since v2:
- Use patch 1 from v1
Thank you for your feedback Wolfram. I have addressed your comments.
Concerning your questions:
"Why can't we use i2c_smbus_write_block_data()?"
i2c_smbus_write_block_data() does not allow me to pass the
requester_i2c_addr argument. Instead, it uses the
client->addr.
The client->addr in this dri
On Thu, Apr 11, 2019 at 12:29:43PM +, Leon Romanovsky wrote:
> On Wed, Apr 10, 2019 at 11:41:24AM -0400, jgli...@redhat.com wrote:
> > From: Jérôme Glisse
> >
> > Changes since v1/v2 are about rebase and better comments in the code.
> > Previous cover letter slightly updated.
> >
> >
> > This
On Wed, Apr 10, 2019 at 11:41:24AM -0400, jgli...@redhat.com wrote:
> From: Jérôme Glisse
>
> Changes since v1/v2 are about rebase and better comments in the code.
> Previous cover letter slightly updated.
>
>
> This patchset convert RDMA ODP to use HMM underneath this is motivated
> by stronger c
From: Jérôme Glisse
Changes since v1/v2 are about rebase and better comments in the code.
Previous cover letter slightly updated.
This patchset convert RDMA ODP to use HMM underneath this is motivated
by stronger code sharing for same feature (share virtual memory SVM or
Share Virtual Address S
On 3/14/19 2:06 AM, Jan Kara wrote:
> On Wed 13-03-19 19:21:37, Christopher Lameter wrote:
>> On Wed, 13 Mar 2019, Christoph Hellwig wrote:
>>
>>> On Wed, Mar 13, 2019 at 09:11:13AM +1100, Dave Chinner wrote:
On Tue, Mar 12, 2019 at 03:39:33AM -0700, Ira Weiny wrote:
> IMHO I don't think t
On 3/14/19 1:25 PM, William Kucharski wrote:
On Mar 14, 2019, at 7:30 AM, Jan Kara wrote:
Well I have some crash reports couple years old and they are not from QA
departments. So I'm pretty confident there are real users that use this in
production... and just reboot their machine in case it
> On Mar 14, 2019, at 7:30 AM, Jan Kara wrote:
>
> Well I have some crash reports couple years old and they are not from QA
> departments. So I'm pretty confident there are real users that use this in
> production... and just reboot their machine in case it crashes.
Do you know what the use c
On Thu 14-03-19 09:57:18, Jason Gunthorpe wrote:
> On Thu, Mar 14, 2019 at 10:03:45AM +0100, Jan Kara wrote:
> > On Wed 13-03-19 19:16:51, Christopher Lameter wrote:
> > > On Tue, 12 Mar 2019, Jerome Glisse wrote:
> > >
> > > > > > This has been discuss extensively already. GUP usage is now
> > >
On Thu, Mar 14, 2019 at 10:03:45AM +0100, Jan Kara wrote:
> On Wed 13-03-19 19:16:51, Christopher Lameter wrote:
> > On Tue, 12 Mar 2019, Jerome Glisse wrote:
> >
> > > > > This has been discuss extensively already. GUP usage is now
> > > > > widespread in
> > > > > multiple drivers, removing tha
On Wed 13-03-19 19:21:37, Christopher Lameter wrote:
> On Wed, 13 Mar 2019, Christoph Hellwig wrote:
>
> > On Wed, Mar 13, 2019 at 09:11:13AM +1100, Dave Chinner wrote:
> > > On Tue, Mar 12, 2019 at 03:39:33AM -0700, Ira Weiny wrote:
> > > > IMHO I don't think that the copy_file_range() is going t
1 - 100 of 233 matches
Mail list logo
