Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933360AbdDEKKq (ORCPT ); Wed, 5 Apr 2017 06:10:46 -0400 Received: from wolverine02.qualcomm.com ([199.106.114.251]:11940 "EHLO wolverine02.qualcomm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932586AbdDEKJv (ORCPT ); Wed, 5 Apr 2017 06:09:51 -0400 X-IronPort-AV: E=Sophos;i="5.36,278,1486454400"; d="scan'208";a="371562216" X-IronPort-AV: E=McAfee;i="5800,7501,8488"; a="1341434151" X-MGA-submission: =?us-ascii?q?MDFfhHgA6S07ZvPJnf+OtRVu1eOEA6Xiw3JJEF?= =?us-ascii?q?cs6KtPZYJKFYSgMxDf+wPWxabCEulbgK1EHtuTk6/aepTyblDDINxkk2?= =?us-ascii?q?dqrMW2pTRPLwtbdcpy/IpLolWzhIfYIi8fojzEqRjoChZBldkWDRV2dm?= =?us-ascii?q?cN?= From: Kalle Valo To: Alban CC: ath9k-devel , John Crispin , Rob Herring , Mark Rutland , "linux-wireless@vger.kernel.org" , "netdev@vger.kernel.org" , "devicetree@vger.kernel.org" , "linux-kernel@vger.kernel.org" Subject: Re: [PATCH 1/7] Documentation: dt: net: Update the ath9k binding for SoC devices Thread-Topic: [PATCH 1/7] Documentation: dt: net: Update the ath9k binding for SoC devices Thread-Index: AQHSnD2lhqkpNgKCEkmUuDCXvGsZNg== Date: Wed, 5 Apr 2017 10:09:44 +0000 Message-ID: <87tw63i2s7.fsf@kamboji.qca.qualcomm.com> References: <1489439116-4233-1-git-send-email-albeu@free.fr> In-Reply-To: <1489439116-4233-1-git-send-email-albeu@free.fr> (Alban's message of "Mon, 13 Mar 2017 22:05:09 +0100") Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-messagesentrepresentingtype: 1 x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [10.251.52.12] Content-Type: text/plain; charset="iso-8859-1" MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by mail.home.local id v35ABB8S015483 Content-Length: 702 Lines: 20 Alban writes: > The current binding only cover PCI devices so extend it for SoC devices. > > Most SoC platforms use an MTD partition for the calibration data > instead of an EEPROM. The qca,no-eeprom property was added to allow > loading the EEPROM content using firmware loading. This new binding > replace this hack with NVMEM cells, so we also mark the qca,no-eeprom > property as deprecated in case anyone ever used it. A patchset like this should definitely have a cover letter and explain the backround and reasoning for this patchset. Currently I'm just guessing. > Signed-off-by: Alban Please use your full name both in From and S-o-b lines. -- Kalle Valo