From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) by mail.toke.dk (Postfix) with ESMTPS id 91196A590E8 for ; Mon, 4 Mar 2024 15:10:28 +0100 (CET) Authentication-Results: mail.toke.dk; dkim=pass (2048-bit key; unprotected) header.d=kernel.org header.i=@kernel.org header.a=rsa-sha256 header.s=k20201202 header.b=foYRdYyx Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by dfw.source.kernel.org (Postfix) with ESMTP id 1B89760F3A; Mon, 4 Mar 2024 14:10:27 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPS id AE089C433C7; Mon, 4 Mar 2024 14:10:26 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1709561426; bh=e3vwrozgYttFesjrkEkiWY1DOGCdGg097X1QMijHh14=; h=Subject:From:Date:References:In-Reply-To:To:Cc:From; b=foYRdYyxuUzzlnIK0ysZ+/h7LUP5HkwK3+MztotHFXqWWcsxXxuQL0fgW7QTDWLW1 JiE+/i9DxUhHjkBW0PbYjUDlGNTMNdkitPb1uftZ6yrBVA/XU7g80EDqeImTKoh9kH DzUYAyuDPYXw95glklTZ7nWh3xHQ5cKcg6jSvnh6lRpDi8tGN3hFi4PQsskNy7Bw7K 5HMm0o+gpW7U2Tj6iTX1tZTHlmFFJbE6MpZhcMfHL5WWuzkOfvO3kysX9ieU5Ght+C LSAsbtMHEny5mQc99MKLsZAMX0Lf9D+C0nVjZBbbXYZ4XdSJ84ZDBDSjaJN6eNu16+ 8bzq4osx4vG/A== Received: from aws-us-west-2-korg-oddjob-1.ci.codeaurora.org (localhost.localdomain [127.0.0.1]) by aws-us-west-2-korg-oddjob-1.ci.codeaurora.org (Postfix) with ESMTP id 90C7FC595C4; Mon, 4 Mar 2024 14:10:26 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit From: patchwork-bot+netdevbpf@kernel.org Message-Id: <170956142658.15074.12322285485014543685.git-patchwork-notify@kernel.org> Date: Mon, 04 Mar 2024 14:10:26 +0000 References: <20240303083225.1184165-1-yoong.siang.song@intel.com> In-Reply-To: <20240303083225.1184165-1-yoong.siang.song@intel.com> To: Song Yoong Siang Message-ID-Hash: AQCYZSSL4BG2CLB73AMQ5XPQRW7YSTF2 X-Message-ID-Hash: AQCYZSSL4BG2CLB73AMQ5XPQRW7YSTF2 X-MailFrom: patchwork-bot+netdevbpf@kernel.org X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header CC: jesse.brandeburg@intel.com, anthony.l.nguyen@intel.com, davem@davemloft.net, edumazet@google.com, kuba@kernel.org, pabeni@redhat.com, richardcochran@gmail.com, ast@kernel.org, daniel@iogearbox.net, hawk@kernel.org, john.fastabend@gmail.com, sdf@google.com, vinicius.gomes@intel.com, florian.bezdeka@siemens.com, andrii@kernel.org, eddyz87@gmail.com, mykolal@fb.com, martin.lau@linux.dev, song@kernel.org, yonghong.song@linux.dev, kpsingh@kernel.org, haoluo@google.com, jolsa@kernel.org, shuah@kernel.org, intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org, linux-kernel@vger.kernel.org, bpf@vger.kernel.org, linux-kselftest@vger.kernel.org, xdp-hints@xdp-project.net X-Mailman-Version: 3.3.9 Precedence: list Subject: [xdp-hints] Re: [PATCH iwl-next,v3 0/2] XDP Tx Hardware Timestamp for igc driver List-Id: XDP hardware hints design discussion Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: Hello: This series was applied to bpf/bpf-next.git (master) by Daniel Borkmann : On Sun, 3 Mar 2024 16:32:23 +0800 you wrote: > Implemented XDP transmit hardware timestamp metadata for igc driver. > > This patchset is tested with tools/testing/selftests/bpf/xdp_hw_metadata > on Intel ADL-S platform. Below are the test steps and results. > > Test Step 1: Run xdp_hw_metadata app > sudo ./xdp_hw_metadata > /dev/shm/result.log > > [...] Here is the summary with links: - [iwl-next,v3,1/2] selftests/bpf: xdp_hw_metadata reduce sleep interval https://git.kernel.org/bpf/bpf-next/c/01031fd47305 - [iwl-next,v3,2/2] igc: Add Tx hardware timestamp request for AF_XDP zero-copy packet (no matching commit) You are awesome, thank you! -- Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html