Received: by 2002:ac0:a582:0:0:0:0:0 with SMTP id m2-v6csp4227935imm; Mon, 15 Oct 2018 11:06:58 -0700 (PDT) X-Google-Smtp-Source: ACcGV63RitWRH9Ia93GjqkQDffqgdZDP9lRfXHiZQAP1Wvov0gx3izS4QYUL5tq3DMs4CB2EoLVU X-Received: by 2002:a62:9fc4:: with SMTP id v65-v6mr18730138pfk.130.1539626818086; Mon, 15 Oct 2018 11:06:58 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1539626818; cv=none; d=google.com; s=arc-20160816; b=N7LY3XHCnDfBu76VOUtD20i6ZXgmGN6ayx592NUMHWnLSiIr9UsYwiuFr++yCIbecW r449OkJAtZ7VKfezfHBIkoYYaIEOgwyjQ2F4eaKbdRAbaBhAJmvrQAsXyvUUxkcARrLT zQXSO17/HWNP92txIecaQ981gR5o3L1qxPaSzgdv8O+PpDaYbGUQzJNoSTIhvcIN1vnd V3Co397vB+LFm/4VY8xFXwYTazgLdxzpdV/baZQvAH7VWx9H/p1i43OA90jRIQD76q+C TssaDrTBA7WLTLJ8bfkjDIjjAZYXhnSAfT7y7fSjg8ccV8yk/Ux0yHZKEkVBzc+Rzg0Q VrLA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:to:references:message-id :content-transfer-encoding:cc:date:in-reply-to:from:subject :mime-version; bh=o6qEwatTrGg2RIAKafZkA+iArOYweQo5vWE8eerBDfQ=; b=EKLvPIuliovbBk9oAHBbnsI+gAxmymBZcbdJRPAc+A3DsuWOOlYi/QuOTwTdkgSktN IvpZAZ+ZxF568w6P1u2BBPm+cg2awA92ex6Ar6AehKurg81MUyMkLO4RERbgLNL/3Bj9 GJH/tmZYAppIinOP1xPjkYp+HqIjsrkII4f+n0W7o9TS6NnbTp5NSxEjkQUF8tx/qlPx 3DYiZI8IT/l3HvrUJfXKZzkE2o0IbUpvslzvnGPxG5vatfI2bit+0KwB0kz95mGHyLJi fT6bkcqAnKKVMXWlmh7f9Q9q4D65ASr5E6xSgbiiUUZjAMzsM5KBC85weZOdJ+NO8E8Z eKJA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id e184-v6si11895502pfa.206.2018.10.15.11.06.41; Mon, 15 Oct 2018 11:06:58 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726825AbeJPBwX convert rfc822-to-8bit (ORCPT + 99 others); Mon, 15 Oct 2018 21:52:23 -0400 Received: from coyote.holtmann.net ([212.227.132.17]:42489 "EHLO mail.holtmann.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726585AbeJPBwW (ORCPT ); Mon, 15 Oct 2018 21:52:22 -0400 Received: from marcel-macbook.fritz.box (p4FF9F655.dip0.t-ipconnect.de [79.249.246.85]) by mail.holtmann.org (Postfix) with ESMTPSA id 55638CF361; Mon, 15 Oct 2018 20:13:24 +0200 (CEST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 12.0 \(3445.100.39\)) Subject: Re: [PATCH v4 1/2] Bluetooth: Add device_get_bd_address() From: Marcel Holtmann In-Reply-To: <20181004173338.GL22824@google.com> Date: Mon, 15 Oct 2018 20:06:02 +0200 Cc: Sinan Kaya , Balakrishna Godavarthi , Greg Kroah-Hartman , "Rafael J . Wysocki" , Sakari Ailus , Marcin Wojtas , Andy Shevchenko Andy Shevchenko , Johan Hedberg , LKML , Bluez mailing list , Loic Poulain , Brian Norris Content-Transfer-Encoding: 8BIT Message-Id: <9B742DB5-F584-4A47-A04B-4F72EB17519C@holtmann.org> References: <20180927004810.124185-1-mka@chromium.org> <20180927004810.124185-2-mka@chromium.org> <20180927171305.GG22824@google.com> <20181004173338.GL22824@google.com> To: Matthias Kaehlcke X-Mailer: Apple Mail (2.3445.100.39) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Matthias, >>>> void bt_sock_reclassify_lock(struct sock *sk, int proto); >>>> >>>> +int device_get_bd_address(struct device *dev, bdaddr_t *bd_addr); >>> >>> Maybe change the API name to start with bt_ and get rid of device_? >> >> device_ indicates that we get the BD_ADDR for a 'struct device' and >> not for e.g. a 'struct fwnode_handle'. >> >> Anyway with this version of the patch fwnode_get_bd_address() has been >> scrapped and it might never be introduced again, so I'm open to change >> the name to bt_ if there is a general preference for it. > > Marcel, can you live with this being added to the Bluetooth code base > instead of property? Also if you'd prefer the function to be named > bt_get_bd_address() let me know. explain to me again why this is useful? I am failing to see the benefit if this is not part of the property.h API. Regards Marcel