search for: patchwork

...|Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED --- Comment #2 from Pablo Neira Ayuso <pablo at netfilter.org> --- There are already kernel patches for this: http://patchwork.ozlabs.org/patch/609733/ http://patchwork.ozlabs.org/patch/609734/ http://patchwork.ozlabs.org/patch/609735/ http://patchwork.ozlabs.org/patch/609736/ And userspace nft patches: http://patchwork.ozlabs.org/patch/611840/ http://patchwork.ozlabs.org/patch/611839/ http://patchwork.ozlabs.org/patch/6...

Hi all, The GlusterFS development team now uses Patchwork for managing patches. Both internal development patches and public submissions, and their status can be viewed at http://patches.gluster.com. Submitting a git formatted patch to gluster-devel at nongnu.org (with the word PATCH in the subject) will get the patch sucked into patchwork and its progres...

Hello everyone, I''ve asked the kernel.org admins to setup patchwork tracking for the btrfs mailing list. This is a pretty cool tool that tracks patches sent to the list and makes it easy to download and apply them. I''ll be the main consumer of this, but you can check out the interface at: http://patchwork.kernel.org/project/linux-btrfs/list/ -chris --...

...idia's help. I should note that the patches for this have been accepted into nouveau, Ben's just working on rebasing them on top of some of the display refactoring + other stuff he's been working on. So they should appear in drm-tip in the near future, but they're still available on patchwork for anyone who wants to try them: https://patchwork.freedesktop.org/series/78803/ (also needs https://patchwork.freedesktop.org/series/78915/ ) ANYWAY-the first question I had was whether anyone on here would be willing to help me with getting acks and/or reviews for some of the nouveau-relate...

Hi, I own a Yunto-Q 700 (made 2000 by online usv systems) and a Yunto-Q 1200 (made 2010). They both work with blazer_ser, but didn't shutdown. I straced the proprietary driver and found the ups expected the return time given with _5_ digits instead of 4, else the command was ignored by the ups. And the Yunto don't send rating/manufacturer informations. I don't want to commit this to

...ll issues around allocation - as I mentioned I think > we will need to improve accounting for that, > and maybe add pre-allocation. > But it's a great series of steps in the right direction! > So Acked-by: Michael S. Tsirkin <mst at redhat.com> > > > v4: https://patchwork.kernel.org/cover/11047717 > > v3: https://patchwork.kernel.org/cover/10970145 > > v2: https://patchwork.kernel.org/cover/10938743 > > v1: https://patchwork.kernel.org/cover/10885431 > > > > Below are the benchmarks step by step. I used iperf3 [1] modified with VSOCK &...

...16 with the exact same results. > >> > >> Anyone have an idea? The 3.18.x series runs without issue of course. > >> > > > > I think the APIC ID MISMATCH is an expected and ignorable error .. > see: > > > > https://patchwork.kernel.org/patch/9539933/ > <https://patchwork.kernel.org/patch/9539933/> > > > > I applied that patch and I am building a 4.9.16-23 right now, I 'll > > publish it when it finishes. Maybe with the error gone we can get a > > better error in...

https://bugzilla.netfilter.org/show_bug.cgi?id=1114 Bug ID: 1114 Summary: set: Can't add elements after flushing a full set with size description Product: nftables Version: unspecified Hardware: x86_64 OS: Ubuntu Status: NEW Severity: normal Priority: P5

mode_fixup function for encoder drivers became optional with patch http://patchwork.freedesktop.org/patch/msgid/1455106522-32307-1-git-send-email-palminha at synopsys.com This patch set nukes all the dummy mode_fixup implementations. (made on top of Daniel topic/drm-misc branch) Changes v1->v2: incorporated Daniel comments * added signed-off-by line to all patches * threadin...

mode_fixup function for encoder drivers became optional with patch http://patchwork.freedesktop.org/patch/msgid/1455106522-32307-1-git-send-email-palminha at synopsys.com This patch set nukes all the dummy mode_fixup implementations. (made on top of Daniel topic/drm-misc branch) Changes v1->v2: incorporated Daniel comments * added signed-off-by line to all patches * threadin...

Hi, Could CentOS kernel keepers apply following patch on current kernel? http://patchwork.ozlabs.org/patch/95785/ (Current as: 2.6.32-71.29.1.el6.x86_64) With the patch applied, and a ".local" kernel built, I get 30% higher throughput with vmxnet3 in my IP routing node, than when using e1000 "card" at the same. Without the patch, the TCP flow over vmxnet3 driver o...

...workarounds. > > > > > > Alex: do you know if there are remaining issues regarding that with amdgpu? > > > > There was an issue with hpd events not making it to the audio side > > when things were powered down that was fixed with this patch set: > > https://patchwork.freedesktop.org/patch/316793/ > > Those patches depended on a bunch of alsa changes as well which may > > have not been available in the distro used for a particular OEM > > program. > > FYI, the corresponding commit for ALSA part is destined for 5.4 > kernel: > >...

...ric variants exactly. Drop the local definitions and pull in > asm-generic/barrier.h instead. > This statement doesn't fit MIPS barriers variations. Moreover, there is a reason to extend that even more specific, at least for smp_store_release and smp_load_acquire, look into http://patchwork.linux-mips.org/patch/10506/ - Leonid.

...ric variants exactly. Drop the local definitions and pull in > asm-generic/barrier.h instead. > This statement doesn't fit MIPS barriers variations. Moreover, there is a reason to extend that even more specific, at least for smp_store_release and smp_load_acquire, look into http://patchwork.linux-mips.org/patch/10506/ - Leonid.

On Thu, 2018-09-06 at 17:43 -0400, Lyude Paul wrote: > Since we're about to use this in nouveau_backlight.c. Same thing as > DRM_WARN_ONCE, DRM_INFO_ONCE, etc... Can you redefine this in terms of the patches I submitted instead? https://lore.kernel.org/patchwork/patch/979598/ https://lore.kernel.org/patchwork/patch/979601/ > Signed-off-by: Lyude Paul <lyude at redhat.com> > Cc: Karol Herbst <kherbst at redhat.com> > --- > drivers/gpu/drm/nouveau/nouveau_drv.h | 8 ++++++++ > 1 file changed, 8 insertions(+) > > diff --gi...

...gt; > > > > > > > > > v3 -> v4: > > > > > > fix some issues > > > > > > > > > > > > v2 -> v3: > > > > > > This patches are splited from previous big patch: > > > > > > http://patchwork.ozlabs.org/patch/934673/ > > > > > > > > > > > > Tonghao Zhang (4): > > > > > > vhost: lock the vqs one by one > > > > > > net: vhost: replace magic number of lock annotation > > > > > > net: v...

...gt; > > > > > > > > > v3 -> v4: > > > > > > fix some issues > > > > > > > > > > > > v2 -> v3: > > > > > > This patches are splited from previous big patch: > > > > > > http://patchwork.ozlabs.org/patch/934673/ > > > > > > > > > > > > Tonghao Zhang (4): > > > > > > vhost: lock the vqs one by one > > > > > > net: vhost: replace magic number of lock annotation > > > > > > net: v...

...s on net-next > - added Stefan's R-b and Michael's A-b This doesn't solve all issues around allocation - as I mentioned I think we will need to improve accounting for that, and maybe add pre-allocation. But it's a great series of steps in the right direction! > v4: https://patchwork.kernel.org/cover/11047717 > v3: https://patchwork.kernel.org/cover/10970145 > v2: https://patchwork.kernel.org/cover/10938743 > v1: https://patchwork.kernel.org/cover/10885431 > > Below are the benchmarks step by step. I used iperf3 [1] modified with VSOCK > support. As Michael s...

...anges. While I was testing the v2 of this series I discovered an huge use of memory, so I added patch 1 to mitigate this issue. I put it in this series in order to better track the performance trends. v5: - rebased all patches on net-next - added Stefan's R-b and Michael's A-b v4: https://patchwork.kernel.org/cover/11047717 v3: https://patchwork.kernel.org/cover/10970145 v2: https://patchwork.kernel.org/cover/10938743 v1: https://patchwork.kernel.org/cover/10885431 Below are the benchmarks step by step. I used iperf3 [1] modified with VSOCK support. As Michael suggested in the v1, I booted h...

...anges. While I was testing the v2 of this series I discovered an huge use of memory, so I added patch 1 to mitigate this issue. I put it in this series in order to better track the performance trends. v5: - rebased all patches on net-next - added Stefan's R-b and Michael's A-b v4: https://patchwork.kernel.org/cover/11047717 v3: https://patchwork.kernel.org/cover/10970145 v2: https://patchwork.kernel.org/cover/10938743 v1: https://patchwork.kernel.org/cover/10885431 Below are the benchmarks step by step. I used iperf3 [1] modified with VSOCK support. As Michael suggested in the v1, I booted h...