From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934159AbeAXPSI (ORCPT ); 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 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 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