Received: by 10.223.176.46 with SMTP id f43csp879747wra; Wed, 24 Jan 2018 07:19:00 -0800 (PST) X-Google-Smtp-Source: AH8x2255vl6MGX9FSXi1T7dYOc3c9zkQt8av2GgzQ/eQDTILSv0INkiZSORgKdWyo7H/MOomVeNn X-Received: by 2002:a17:902:d688:: with SMTP id v8-v6mr8495420ply.302.1516807140064; Wed, 24 Jan 2018 07:19:00 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1516807140; cv=none; d=google.com; s=arc-20160816; b=VwHYTcLIrLXtnL95BJi9pnILXyXESIyoNGeTn414Tx5QlMWpGRNSvUNjEGuev8dD1m jewSkY/CTLjd5NPlU/tBAD7SuR8jz56I0KEE4KAoDvAv22pgjOHypVRjgx83HrYMyPOO 3FocRdpkIbipADF5YoiAFaoxzVaIUZq8Ax2Olw2w+bDlk/idgf2NajpFIwNDRz8nCKgp 6G7FS3j0yi2YtVvQID/d3OGuQSy4kSFtEw6syGIYHnmapdVU7iBVS9wiVqE6MFcZ2EJX Pmrf+ek0Hro34LRIVjY/WWy6cY/3qGFY5UKeMZ+LvwPem2+pGhJz0m95kCKBg3p9/l2l IICw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:arc-authentication-results; bh=nbCNtcfyKPcni6yZpBWmFilmrtyTypuE+pGv8lar6wg=; b=VUIpKYZvxuS6Mrn0qPe70JGS4Dat4BqxoKIcS2jCJ/gn31vySu26oJXvgOB7VZyCKK 20yzCwXMR3baycUfiQpwZfU+NFnHff1XxiW45IaNHVozfGmY7+Ap8wtsm5cdbwyZRvt/ +MB6YtxnxYOwK5Dm10vOoxYbLsuPPHfj+GMyU1Cw5LQJBQkOwLyumWdY/hNR4rcxV0fN w/zhR1+bN5bNAnqnl/DFsAUZwkZQxQiHPIY4dJuGBMyqOJI6cvya2AU1wo57WMrfSAZ1 2ku+1SkyAfvtIuzUXq2PZnwV1EWzttFHMPHmqiE+FGq99E9KCjoIMOVEICWzC+tH0+B8 zIog== 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 w1si257835pgt.182.2018.01.24.07.18.45; Wed, 24 Jan 2018 07:19:00 -0800 (PST) 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 S934143AbeAXPSI (ORCPT + 99 others); Wed, 24 Jan 2018 10:18:08 -0500 Received: from mail.ltec.ch ([95.143.48.181]:36018 "EHLO mail.ltec.ch" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934067AbeAXPSH (ORCPT ); Wed, 24 Jan 2018 10:18:07 -0500 Received: from nebula.ltec ([172.27.11.2] helo=[172.27.11.32]) by mail.ltec.ch with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.89) (envelope-from ) id 1eeMoP-00021E-9G; Wed, 24 Jan 2018 16:18:05 +0100 Subject: Re: nvmem: add driver for Microchip 24AA025E48 I2C eeprom / nodeID chip To: Andy Shevchenko Cc: Srinivas Kandagatla , Linux Kernel Mailing List , brgl@bgdev.pl References: From: Felix Brack Message-ID: <017877bf-5848-53c4-1f72-d630b3acaed4@ltec.ch> Date: Wed, 24 Jan 2018 16:18:04 +0100 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 24.01.2018 16:08, Andy Shevchenko wrote: > On Wed, Jan 24, 2018 at 4:23 PM, Felix Brack wrote: >> Hello, >> >> About three years ago I wrote a driver for Microchip's 24AA025E48 I2C >> eeprom/nodeID chip. At that time I placed the source files in >> drivers/misc/eeprom. I never posted the code. >> I now plan to rewrite the driver from scratch. Is it correct to place >> the source code in drivers/nvmem and is there a special mailing list to >> which the patch should be posted when ready? >> >> many thanks and kind regards, Felix > > Does the existing driver [1] work for you (if you add ID there)? > > [1]: at24 > Yes it does. Actually the driver I wrote 3 years ago is based on the at24 driver. Lot's of code in my driver originates directly from the at24 driver. -- regards Felix