search for: lore

...e drivers to be filled with error message. However, the caller can easily overwrite the filled message. Instead of adding multiple "if (!extack->_msg)" checks before any NL_SET_ERR_MSG() call, which appears after call to the driver, let's add new macro to common code. [1] https://lore.kernel.org/all/Y9Irgrgf3uxOjwUm at unreal Signed-off-by: Leon Romanovsky <leonro at nvidia.com> --- Changelog: v2: * Removed () brackets around msg to fix compilation error. v1: https://lore.kernel.org/all/d4843760219f20367c27472f084bd8aa729cf321.1674995155.git.leon at kernel.org * Added sp...

...sing perftest-rdma, > especially (with a high rate of GPU memory access). If I got this patch series correctly, this is based on ODP (On Demand Paging). And a way also exists which is based on non-ODP. From the following links, this way is implemented on efa, irdma and mlx5. 1. iRDMA https://lore.kernel.org/all/20230217011425.498847-1-yanjun.zhu at intel.com/ 2. efa https://lore.kernel.org/lkml/20211007114018.GD2688930 at ziepe.ca/t/ 3. mlx5 https://lore.kernel.org/all/1608067636-98073-5-git-send-email-jianxin.xiong at intel.com/ Because these 2 methods are both implemented on mlx5, have...

On Thu, Jan 31, 2019 at 05:33:58PM +0100, Joerg Roedel wrote: > Hi, > > here is the next version of this patch-set. Previous > versions can be found here: > > V1: https://lore.kernel.org/lkml/20190110134433.15672-1-joro at 8bytes.org/ > > V2: https://lore.kernel.org/lkml/20190115132257.6426-1-joro at 8bytes.org/ > > V3: https://lore.kernel.org/lkml/20190123163049.24863-1-joro at 8bytes.org/ > > V4: https://lore.kernel.org/lkml/20190129084342.26030...

On Thu, Jan 31, 2019 at 05:33:58PM +0100, Joerg Roedel wrote: > Hi, > > here is the next version of this patch-set. Previous > versions can be found here: > > V1: https://lore.kernel.org/lkml/20190110134433.15672-1-joro at 8bytes.org/ > > V2: https://lore.kernel.org/lkml/20190115132257.6426-1-joro at 8bytes.org/ > > V3: https://lore.kernel.org/lkml/20190123163049.24863-1-joro at 8bytes.org/ > > V4: https://lore.kernel.org/lkml/20190129084342.26030...

This this definition: group { "puppettestgroup2": gid => 1235, ensure => present } user { "puppettestuser2": gid => "puppettestgroup2", uid => 1235, ensure => present } I see this: notice: Starting

...so on. > > > > > There are NOP for non-dma so passing the dma device is harmless. > > > > > > > > Yes, please. > > > > > > > > > I am not sure I got this fully. > > > > > > Are you mean this: > > > https://lore.kernel.org/all/20230214072704.126660-8-xuanzhuo at linux.alibaba.com/ > > > https://lore.kernel.org/all/20230214072704.126660-9-xuanzhuo at linux.alibaba.com/ > > > > > > Then the driver must do dma operation(map and sync) by these virtio_dma_* APIs. > > > No car...

Is there a way I can have "voice mail check" calls coming from my internal users automatically get to the right extension, without having the user enter their extension? I'm thinking that I could have the local SPA boxes translate, or have each user live in a context where the extension in question exists uniquely per user, but both of these seem kludgey. Thanks in advance for

...<jnixdorf-oss at avm.de> --- The corresponding kernel changes are in net-next.git as commit ddd1ad68826d ("net: bridge: Add netlink knobs for number / max learned FDB entries"). --- Changes in v5: - Removed the RFC status again, as the kernel changes landed. - Link to v4: https://lore.kernel.org/r/20230919-fdb_limit-v4-1-b4d2dc4df30f at avm.de Changes in v4: - Removed _entries from the names. (from review) - Removed the UAPI change, to be synced from linux separately by the maintainer. (from review) For local testing e.g. `make CCOPTS="-O2 -pipe -I${path_to_dev_...

...re NOP for non-dma so passing the dma device is harmless. > > > > > > > > > > Yes, please. > > > > > > > > > > > > I am not sure I got this fully. > > > > > > > > Are you mean this: > > > > https://lore.kernel.org/all/20230214072704.126660-8-xuanzhuo at linux.alibaba.com/ > > > > https://lore.kernel.org/all/20230214072704.126660-9-xuanzhuo at linux.alibaba.com/ > > > > > > > > Then the driver must do dma operation(map and sync) by these virtio_dma_* APIs. > &...

...ntly [1] but VT-d still implements its own DMA ops (conversion patches are on the list [2]). On Arm the arch Kconfig selects IOMMU_DMA, and I assume we'll have the same on X86 once Tom's work is complete. Until then I can add a "if X86" here for clarity. Thanks, Jean [1] https://lore.kernel.org/linux-iommu/20190613223901.9523-1-murphyt7 at tcd.ie/ [2] https://lore.kernel.org/linux-iommu/20191221150402.13868-1-murphyt7 at tcd.ie/

...ntly [1] but VT-d still implements its own DMA ops (conversion patches are on the list [2]). On Arm the arch Kconfig selects IOMMU_DMA, and I assume we'll have the same on X86 once Tom's work is complete. Until then I can add a "if X86" here for clarity. Thanks, Jean [1] https://lore.kernel.org/linux-iommu/20190613223901.9523-1-murphyt7 at tcd.ie/ [2] https://lore.kernel.org/linux-iommu/20191221150402.13868-1-murphyt7 at tcd.ie/

On Fri, Sep 4, 2020, at 14:26, Mason Loring Bliss wrote: > On Mon, Aug 31, 2020 at 05:28:58PM -0400, Jonathan Billings wrote: > > > This is pretty misleading. Isn't Stream just a collection of repos that > > offer pre-release packages for the next RHEL point release? It's not a > > midstream between Fedora and RHEL. > > Along those lines, if someone's

...mpbell at nvidia.com> --- This patch applies cleanly to Jason's Gunthorpe's hmm tree plus two patches I posted earlier. The first is queued in Ben Skegg's nouveau tree and the second is still pending review/not queued. [1] ("nouveau/hmm: map pages after migration") https://lore.kernel.org/linux-mm/20200304001339.8248-5-rcampbell at nvidia.com/ [2] ("nouveau/hmm: fix nouveau_dmem_chunk allocations") https://lore.kernel.org/lkml/20200421231107.30958-1-rcampbell at nvidia.com/ drivers/gpu/drm/nouveau/nouveau_dmem.c | 75 ++++++++++++++++++++++---- 1 file changed,...

...> > Can you point me to any specific example where this would be the case > for the core kernel symbols please? The most recent example that comes to mind was the thrash around __kernel_fpu_{begin,end} [1]. I referenced that when debating _GPL symbol policy with Jérôme [2]. [1]: https://lore.kernel.org/lkml/20190522100959.GA15390 at kroah.com/ [2]: https://lore.kernel.org/lkml/CAPcyv4gb+r==riKFXkVZ7gGdnKe62yBmZ7xOa4uBBByhnK9Tzg at mail.gmail.com/

Statically allocated array of pointed to hwmon_channel_info can be made const for safety. Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski at linaro.org> --- This depends on hwmon core patch: https://lore.kernel.org/all/20230406203103.3011503-2-krzysztof.kozlowski at linaro.org/ Therefore I propose this should also go via hwmon tree. Cc: Jean Delvare <jdelvare at suse.com> Cc: Guenter Roeck <linux at roeck-us.net> Cc: linux-hwmon at vger.kernel.org --- drivers/gpu/drm/i915/i915_hwmon....

...atch applies cleanly to Jason's Gunthorpe's hmm tree plus two >> patches I posted earlier. The first is queued in Ben Skegg's nouveau >> tree and the second is still pending review/not queued. >> [1] ("nouveau/hmm: map pages after migration") >> https://lore.kernel.org/linux-mm/20200304001339.8248-5-rcampbell at nvidia.com/ >> [2] ("nouveau/hmm: fix nouveau_dmem_chunk allocations") >> https://lore.kernel.org/lkml/20200421231107.30958-1-rcampbell at nvidia.com/ > > It would be best if it goes through Ben's tree if it doe...

...cv()' with valid >>> buffer. For SOCK_STREAM second 'recv()' must return data, because skbuff >>> must not be dropped, but for SOCK_SEQPACKET skbuff will be dropped by >>> kernel, and 'recv()' will return EAGAIN. >>> >>> Link to v1 on lore: >>> https://lore.kernel.org/netdev/c2d3e204-89d9-88e9-8a15-3fe027e56b4b at sberdevices.ru/ >>> >>> Link to v2 on lore: >>> https://lore.kernel.org/netdev/a7ab414b-5e41-c7b6-250b-e8401f335859 at sberdevices.ru/ >>> >>> Change log: >>> &...

...vious prototype for 'nv50_display_create' Another patch was sent in the meantime to mark the function static but that would just cause a different warning about an unused function. Fixes: 1cd97b5490c8 ("drm/nouveau/gr/tu102-: use sw_veid_bundle_init from firmware") Link: https://lore.kernel.org/all/CACO55tuaNOYphHyB9+ygi9AnXVuF49etsW7x2X5K5iEtFNAAyw at mail.gmail.com/ Link: https://lore.kernel.org/all/20230417210310.2443152-1-arnd at kernel.org/ Signed-off-by: Arnd Bergmann <arnd at arndb.de> --- I send this one back in April, and Lee Jones sent a similar patch in May. Pl...

...n patches are on the list [2]). On Arm the arch Kconfig selects >> IOMMU_DMA, and I assume we'll have the same on X86 once Tom's work is >> complete. Until then I can add a "if X86" here for clarity. >> >> Thanks, >> Jean >> >> [1] https://lore.kernel.org/linux-iommu/20190613223901.9523-1-murphyt7 at tcd.ie/ >> [2] https://lore.kernel.org/linux-iommu/20191221150402.13868-1-murphyt7 at tcd.ie/ > > What about others? E.g. PPC? That was the point I was getting at - while iommu-dma should build just fine for the likes of PPC, s...

...n patches are on the list [2]). On Arm the arch Kconfig selects >> IOMMU_DMA, and I assume we'll have the same on X86 once Tom's work is >> complete. Until then I can add a "if X86" here for clarity. >> >> Thanks, >> Jean >> >> [1] https://lore.kernel.org/linux-iommu/20190613223901.9523-1-murphyt7 at tcd.ie/ >> [2] https://lore.kernel.org/linux-iommu/20191221150402.13868-1-murphyt7 at tcd.ie/ > > What about others? E.g. PPC? That was the point I was getting at - while iommu-dma should build just fine for the likes of PPC, s...