Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id E736CC433F5 for ; Wed, 1 Dec 2021 07:22:54 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1347168AbhLAH0O (ORCPT ); Wed, 1 Dec 2021 02:26:14 -0500 Received: from coyote.holtmann.net ([212.227.132.17]:39764 "EHLO mail.holtmann.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230360AbhLAH0N (ORCPT ); Wed, 1 Dec 2021 02:26:13 -0500 Received: from smtpclient.apple (p5b3d2e91.dip0.t-ipconnect.de [91.61.46.145]) by mail.holtmann.org (Postfix) with ESMTPSA id CAF0FCECDD; Wed, 1 Dec 2021 08:22:51 +0100 (CET) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.20.0.1.32\)) Subject: Re: [PATCH 01/15] skbuff: introduce skb_pull_data From: Marcel Holtmann In-Reply-To: <20211130182742.7537e212@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com> Date: Wed, 1 Dec 2021 08:22:51 +0100 Cc: Luiz Augusto von Dentz , "David S. Miller" , "linux-bluetooth@vger.kernel.org" , "open list:NETWORKING [GENERAL]" , Dan Carpenter , Luiz Augusto von Dentz Content-Transfer-Encoding: 7bit Message-Id: References: <20211201000215.1134831-1-luiz.dentz@gmail.com> <20211201000215.1134831-2-luiz.dentz@gmail.com> <20211130171105.64d6cf36@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com> <20211130182742.7537e212@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com> To: Jakub Kicinski X-Mailer: Apple Mail (2.3693.20.0.1.32) Precedence: bulk List-ID: X-Mailing-List: linux-bluetooth@vger.kernel.org Hi Jakub, >>> It doesn't take a data pointer, so not really analogous to >>> skb_put_data() and friends which come to mind. But I have >>> no better naming suggestions. You will need to respin, tho, >>> if you want us to apply these directly, the patches as posted >>> don't apply to either netdev tree. >> >> I cross posted it to net-dev just in case you guys had some strong >> opinions on introducing such a function, > > Someone else still may, I don't :) > >> it was in fact suggested by Dan but I also didn't find a better name >> so I went with it, if you guys prefer we can merge it in >> bluetooth-next first as usual. > > Going via bluetooth-next sounds good! if you are ok with this going via bluetooth-next, then I need some sort of ACK from you or Dave. Regards Marcel