From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id D06C92561A7 for ; Sun, 12 Jul 2026 07:42:50 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1783842171; cv=none; b=Dh8YOZHtC7+NlHFNwSyJqm/Yl5InV+keAv8VvItsMUEYlbD3tCPpQKHbH4YlmZ7ixvieNrBq5SfT9cYeg5TzVGEPO39sYdFsk6+tNskajh3kqvk5FN9k6eABlMIIz8vKiUSmKqB8u5s7lI1gT/neX3qj0+ptO3WsnOchL1/g/3U= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1783842171; c=relaxed/simple; bh=v2vBDBbdB5yGyhLKo/TaqRBN9uKVnzDtEy7tEhLakXk=; h=From:To:Cc:In-Reply-To:References:Subject:Message-Id:Date: MIME-Version:Content-Type; b=DTsqEVOyw2v76tp52leq8dukYyJNvOPYj55PpnqtirE3/ZbeKfw5FolKpGGQmVGIBfouyi+f1ID9+s7PgwxhAAqarpo20dl39jNsRNf0SE6jelk7MCFoe+OdZDg2Xj7hNNNgT/UA2YZY7DVHLcAp5XEZG3iCZvoWlxgfoJZNm7M= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=BP/7GRhT; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="BP/7GRhT" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 342181F000E9; Sun, 12 Jul 2026 07:42:49 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1783842170; bh=L4+C/0TqRZQoPkG9QnfDmDheWThuMYOZJ0jnf7d8ur4=; h=From:To:Cc:In-Reply-To:References:Subject:Date; b=BP/7GRhTUBqz5aQoTx5Y/s+OkVyFLmM9+OnexNN3Ke7XRjQyoya5YyG2QzWOGreph Ur9JYLj8vhvfVJvETXxdpR6jHkoKfoMC8gy5WbljfGpItpHK1Lj2xdTDV9R9hYajtc D74iwoPJE0UFy3z2mmXGiWta7KjSZNMcb/2TV4P51tkEZ2WMhTNM5RiHjJ0Mr74Z8V qAGmY3hIY3h5svNNvK9TOmLbDwijtAzV5gxsxwwGcLc6kw+Uwgh3z1tS4yhU0i4ERv CwV1OXcYX/Vmuvfm1kDt0rmGZYRr36UahveNLMEs6VJTqJaGWEeK3Y/47z2o1BpTqL DVTV6KK/P7KFw== From: Srinivas Kandagatla To: Arnd Bergmann , Greg Kroah-Hartman , Wolfram Sang , Andi Shyti , Bartosz Golaszewski , Bartosz Golaszewski Cc: linux-kernel@vger.kernel.org In-Reply-To: <20260702-eeprom-move-to-nvmem-v2-1-327e1e5d1d95@oss.qualcomm.com> References: <20260702-eeprom-move-to-nvmem-v2-1-327e1e5d1d95@oss.qualcomm.com> Subject: Re: [PATCH v2] eeprom: move nvmem EEPROM drivers to drivers/nvmem/ Message-Id: <178384216881.1780728.10421703091684593571.b4-ty@kernel.org> Date: Sun, 12 Jul 2026 08:42:48 +0100 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit X-Mailer: b4 0.14.3 On Thu, 02 Jul 2026 11:24:37 +0200, Bartosz Golaszewski wrote: > For historical reasons EEPROM drivers have lived under > drivers/misc/eeprom/. Also for historical reasons changes to most of > them would go through the char-misc tree while some would be queued > through the I2C tree. Over the years some of them have also been > converted to using nvmem - the dedicated subsystem for non-volatile > memory - while get_maintainer.pl does not Cc the maintainer of nvmem on > patches changing them. > > [...] Applied, thanks! [1/1] eeprom: move nvmem EEPROM drivers to drivers/nvmem/ commit: addd9b7203a3dfb354fb3e4c117919032f719b46 Best regards, -- Srinivas Kandagatla