Received: by 2002:ac0:a5a7:0:0:0:0:0 with SMTP id m36-v6csp1429521imm; Thu, 19 Jul 2018 01:15:27 -0700 (PDT) X-Google-Smtp-Source: AAOMgpcPqE3PDJRA6cMtS7IDtFWWVveBpQaJUGryftyF/oYJxnOeXHWRS+Iyg3XbMzUGN4VQUtBY X-Received: by 2002:a63:c252:: with SMTP id l18-v6mr9053657pgg.76.1531988127739; Thu, 19 Jul 2018 01:15:27 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1531988127; cv=none; d=google.com; s=arc-20160816; b=LeLa429tA/Z25ygVm8Uroi323brDmQY6nGApeBgImacOtetetgSxo0CePBT3B6/0WW AR3wniW0t+QKPR/4cUUBWVUE5rMnrUh4+wriV4s7lwfWIOJa8G0eJhqpa/8rcy/Kk0gn UnLqRtiUTCqFK0dBUoqYeMHfJfp3Cbb+SYfW3tfSDSN1H7H+ZxMgCJDezHGiMoZXSK4T x9c+SiExzQGisbzTfg+7QuhE+GgmR2a4qQ7k3M3fBaE2iNG3xZN99iqJpQXKvQwqrh1o BhiSvh8Nm7VLs7/MAkc/1YCCniFW5BVdLm6lzdBrnD/nkZwHitRQ33w/cOmzOOGPwJtd Pd6w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :references:in-reply-to:mime-version:dkim-signature :arc-authentication-results; bh=bm1G+fUXII+2uTc5vTIF3YvFG/E6LMV8RgVIqKQehH0=; b=bTKUwAGKPTFCfqg08OmZv12Xpkf9kzMZTjLHS/MjXW2WPnwm/2rhpbjnCkH5uUgsrV i92OD2StwCYizEzGb4lp5pSyQ/J1eLKR0R+6OkqPHY8UDeo0LZCiJbk9R5O6fU8uFs4T tcDyv2I8ttfQBbQfTd3oOFzHt6RoUaNlpm4mehqjeqM3pUNoOS2HqcWz70Re9v1e+YEk yT2kLdpHMOrBrN/svao6XWmndEnnv3UeX9s/jyj+vm26BTD074/Pmp9CCTxa4wsuG4Lv vUByddpveLeO5arPpZ20Z4HEA93G/855hJjdc7bKYeeBgpKY0BNntAOE5crkouTyg/tm XGHw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@bgdev-pl.20150623.gappssmtp.com header.s=20150623 header.b=icra8ysF; 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 x130-v6si5900993pgx.207.2018.07.19.01.15.13; Thu, 19 Jul 2018 01:15:27 -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; dkim=pass header.i=@bgdev-pl.20150623.gappssmtp.com header.s=20150623 header.b=icra8ysF; 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 S1731556AbeGSI41 (ORCPT + 99 others); Thu, 19 Jul 2018 04:56:27 -0400 Received: from mail-io0-f179.google.com ([209.85.223.179]:33725 "EHLO mail-io0-f179.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1731465AbeGSI41 (ORCPT ); Thu, 19 Jul 2018 04:56:27 -0400 Received: by mail-io0-f179.google.com with SMTP id z20-v6so6383979iol.0 for ; Thu, 19 Jul 2018 01:14:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bgdev-pl.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=bm1G+fUXII+2uTc5vTIF3YvFG/E6LMV8RgVIqKQehH0=; b=icra8ysF6OCrRW+XpEbWMyUGZVmXKuBH5Yks/BypmKOHn5+oAVHw6E/yJCpQTU4Emy FjUx4H1dv5YSIiR8qzjM6UVNiPN4qy8A0U0cEe1TkFydZyYqPKGqUkn6H4pN3OUukxys 5ewtY5f6/Yy9FGdyZpYs8p/Hn+eRGGxnVZpJ+T4q+iGabaKUl0Plht6M7fxdpe9VQhYG a6k5QzR3LpGlEmXCuYBgGGE7DYqimGs7ckwVyTR30bv6ylCTWKtuTMMmig4WwbIj+T/l gZntuBHogQ/+PVIAZYNhr2QCurxs8yp9eM6t3+7t1cA5npx4z7TIYNkOVUfSS9P7ZJ2l 5qNw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=bm1G+fUXII+2uTc5vTIF3YvFG/E6LMV8RgVIqKQehH0=; b=f7EKoBtj1isUYgry72SATSRde06jlu80quzdqbI9v7EHXPhzJ5qisNE69opH+N6hEc KTDzpUPXkyDbFnhJBeHDytRWFoYr2CG/ZjAvFARW8JmeKTH3NhcLH3K6Od45yWW8j0M/ 9IRZmEnqRDqzyaenUfq35uLLWKxAMYfAcBEGgDQs/qBdqdxn1TUOrxNyS3lTb8HBohWR WBZV10J4WmH2T1GSRAGoGS6HrNE15ypveD34wcW+WgGc07ElsfdmmDVdeuHEUF0NU3io K87FH7Cpj8KqgosBH4p+iNLCqunsRE8GTeHq/Gj+TWvNksL/OSsVdrPmgAB8ADqG5TMg spHw== X-Gm-Message-State: AOUpUlEVtOak4FLz0ETQMwfbtb5cCXuaxdYLdMV1j+GZGQetR7EFdiVO S1+0LnrMQEj9fGv0oSGGtXP+tMdq2ce0q3nwDVDU/g== X-Received: by 2002:a6b:c844:: with SMTP id y65-v6mr7685708iof.187.1531988069852; Thu, 19 Jul 2018 01:14:29 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a5e:9402:0:0:0:0:0 with HTTP; Thu, 19 Jul 2018 01:14:29 -0700 (PDT) In-Reply-To: <20180718170352.GF12477@lunn.ch> References: <20180718161035.7005-1-brgl@bgdev.pl> <20180718161035.7005-6-brgl@bgdev.pl> <20180718164737.GE12477@lunn.ch> <20180718170352.GF12477@lunn.ch> From: Bartosz Golaszewski Date: Thu, 19 Jul 2018 10:14:29 +0200 Message-ID: Subject: Re: [PATCH 5/5] net: add MTD support to eth_platform_get_mac_address() To: Andrew Lunn Cc: Sekhar Nori , Kevin Hilman , Russell King , Grygorii Strashko , "David S . Miller" , Srinivas Kandagatla , Lukas Wunner , Rob Herring , Florian Fainelli , Dan Carpenter , Ivan Khoronzhuk , David Lechner , Greg Kroah-Hartman , Linux ARM , Linux Kernel Mailing List , linux-omap@vger.kernel.org, netdev@vger.kernel.org, Bartosz Golaszewski Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 2018-07-18 19:03 GMT+02:00 Andrew Lunn : >> >> +#ifdef CONFIG_MTD >> >> + /* NOTE: this should go away as soon as MTD gets nvmem support. */ >> >> + if (!addr) { >> >> + struct mtd_info *mtd; >> >> + int rv; >> >> + >> >> + mtd = get_mtd_device_nm("MAC-Address"); >> > >> > In order for this to go away, you need to keep backwards >> > compatibility. When using nvmem, you look for a cell called >> > "mac-address". Here you are looking for "MAC-Address". That is going >> > to make backwards compatibility harder. How do you plan to do it? >> > >> > Andrew >> >> I'm trying to adjust to already existing users. The only user of >> get_mtd_device_nm() who calls it to read the MAC address registers a >> partition called "MAC-Address". We can't change it since it's visible >> from user space. In the future we'd just have to have a list of >> supported string that we'd use to do the nvmem lookup. > > Why not have the nvmem cell called "MAC-Address"? When you add nvmem > support to MTD, i assume you are going to map each MTD partition to an > nvmem cell? Because all existing users of nvmem use "mac-address" as the name of this cell already. I guess we will need to live with both in this particular function. Bart