From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752151AbdAYSTb (ORCPT ); Wed, 25 Jan 2017 13:19:31 -0500 Received: from shards.monkeyblade.net ([184.105.139.130]:57186 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751513AbdAYSTa (ORCPT ); Wed, 25 Jan 2017 13:19:30 -0500 Date: Wed, 25 Jan 2017 13:19:28 -0500 (EST) Message-Id: <20170125.131928.1293307938933551620.davem@davemloft.net> To: daniel@iogearbox.net Cc: ast@kernel.org, netdev@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH net-next 0/3] BPF tracepoints From: David Miller In-Reply-To: References: X-Mailer: Mew version 6.7 on Emacs 24.5 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.5.12 (shards.monkeyblade.net [149.20.54.216]); Wed, 25 Jan 2017 09:20:26 -0800 (PST) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Daniel Borkmann Date: Wed, 25 Jan 2017 02:28:15 +0100 > This set adds tracepoints to BPF for better introspection and > debugging. The first two patches are prerequisite for the actual > third patch that adds the tracepoints. I think the first two are > small and straight forward enough that they could ideally go via > net-next, but I'm also open to other suggestions on how to route > them in case that's not applicable (it would reduce potential > merge conflicts on BPF side, though). For details, please see > individual patches. Looks great, series applied, thanks Daniel.