Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755047AbbGCLMo (ORCPT ); Fri, 3 Jul 2015 07:12:44 -0400 Received: from mga14.intel.com ([192.55.52.115]:57460 "EHLO mga14.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755090AbbGCLMe (ORCPT ); Fri, 3 Jul 2015 07:12:34 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.15,399,1432623600"; d="scan'208";a="757855494" Message-ID: <55966E1E.2090409@linux.intel.com> Date: Fri, 03 Jul 2015 14:12:30 +0300 From: Jarkko Sakkinen User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: Tejun Heo , Jason Gunthorpe CC: tpmdd-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org, peterhuewe@gmx.de, gregkh@linuxfoundation.org, Vivien Didelot , Guenter Roeck , NeilBrown , "Maliszewski, Richard L" Subject: Re: [PATCH v7 1/3] sysfs: added sysfs_link_entry_to_kobj() References: <1434993894-5911-1-git-send-email-jarkko.sakkinen@linux.intel.com> <1434993894-5911-2-git-send-email-jarkko.sakkinen@linux.intel.com> <20150622173039.GA3710@mtj.duckdns.org> <20150622175253.GA28080@obsidianresearch.com> <20150622180154.GC3710@mtj.duckdns.org> <20150623161932.GA20922@obsidianresearch.com> <20150702170407.GD30677@mtj.duckdns.org> In-Reply-To: <20150702170407.GD30677@mtj.duckdns.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1275 Lines: 34 On 07/02/2015 08:04 PM, Tejun Heo wrote: > Hello, Jason. > > On Tue, Jun 23, 2015 at 10:19:32AM -0600, Jason Gunthorpe wrote: >> The concept was to move the sysfs files to the natural location on the >> core's struct tpm.struct device and leave a symlink behind on the >> platform_device for compat. > > I see. The only problem I see is that this might get abused. Can you > clearly mark the function that it's not intended to be used in > anything new, e.g. by renaming it to sth like > __compat_only_sysfs_link_entry_to_kobj(). Great! We will do that. Thanks for taking time and understanding what we are dealing with. We are trying to fix all the bad behavior from TPM subsystem and bring up to the todays standards so that next gen TPM 2.0 devices will have a solid platform. >> We could also just move the sysfs file and ignore the compat symlink, >> but it is not clear to me if that is an OK UAPI break for sysfs? > > We shouldn't if it has actual chance of disturbing userland. > > Thanks. /Jarkko -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/