From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail.zeus03.de (zeus03.de [194.117.254.33]) (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 6E72C34404B for ; Thu, 18 Jun 2026 21:06:03 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=194.117.254.33 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1781816768; cv=none; b=oZXGn30aGjOyMuVtdu+c/7oVEiWW8si0CFjwhwHVNc7sPqvWMHNSOwZ1UDR768NaxNrupe9EDZsTFS9DspikyxC8o1KXOXZ0BmpvxbMAPutBmTK/xZdMFtvhUhfARsXsBM9v0+U0YAs0M/KD6HeSiKZlmKve+3D2XUJ9IchMuFo= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1781816768; c=relaxed/simple; bh=Io7ADHYXgXyX7t8ytl5Tdg4v74dm4i4Be5yxacSozTk=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=FSj/BNmI56H7MpZuDfPzsujPJOgSNu8Y3fbLQL30JlQiGjnEfAF7pwtuO4FwTu0/cvkvfxV2j0FCJ5/bcwM8vEE1vgId72bU/Y4uVI9tS5C2BVGVRKfN2xpBzId6/PiGWB3jm3KXQE7e5uIr+2QbLTSlEqjH4xVeIzdyHdZq1XI= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=sang-engineering.com; spf=pass smtp.mailfrom=sang-engineering.com; dkim=pass (2048-bit key) header.d=sang-engineering.com header.i=@sang-engineering.com header.b=WuoNPbyf; arc=none smtp.client-ip=194.117.254.33 Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=sang-engineering.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=sang-engineering.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=sang-engineering.com header.i=@sang-engineering.com header.b="WuoNPbyf" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= sang-engineering.com; h=date:from:to:cc:subject:message-id :references:mime-version:content-type:in-reply-to; s=k1; bh=Io7A DHYXgXyX7t8ytl5Tdg4v74dm4i4Be5yxacSozTk=; b=WuoNPbyfecJEnM11Og6W kdYnuyE0PeST0KDFF0lvYDxnoJY9n0xcIpTZD5755IqxtAyfNM7IzwDtWOOOLLhJ mshEhOObuBmEIzmr5hp1eApTznWFHRG5jFm/1pj0+3ZRDvGuYwVpLYTRcrGwg1gB 8cNCz/57qHvuJienvgWtT8X/mrfeb0NIIXxPW/RtbTK1bAj7QgesibkoqCSAlYo7 /23IbUpIgYSbiYQ6s4w4nEddp8aPOl3RYi4OepNOULK/QlEfUK30tsvdb0UIIsTP 1jkTdQRIJ9LspwERfIroJ2q2mzmMVqUK90jfeKJAu3BRsRI2djOfbAnPaNjB1x6S 1Q== Received: (qmail 704467 invoked from network); 18 Jun 2026 23:06:01 +0200 Received: by mail.zeus03.de with ESMTPSA (TLS_AES_256_GCM_SHA384 encrypted, authenticated); 18 Jun 2026 23:06:01 +0200 X-UD-Smtp-Session: l3s3148p1@cQ0gi41U4M8ujnsq Date: Thu, 18 Jun 2026 23:06:01 +0200 From: Wolfram Sang To: Bartosz Golaszewski Cc: Arnd Bergmann , Greg Kroah-Hartman , Srinivas Kandagatla , Andi Shyti , Bartosz Golaszewski , linux-kernel@vger.kernel.org Subject: Re: [PATCH] eeprom: move nvmem EEPROM drivers to drivers/nvmem/ Message-ID: References: <20260618-eeprom-move-to-nvmem-v1-1-21771f30efcc@oss.qualcomm.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="Ej252IKKCEMr/8YS" Content-Disposition: inline In-Reply-To: <20260618-eeprom-move-to-nvmem-v1-1-21771f30efcc@oss.qualcomm.com> --Ej252IKKCEMr/8YS Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jun 18, 2026 at 11:18:27AM +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. >=20 > Move the EEPROM drivers using nvmem under drivers/nvmem/ for > consistency of the review process and path upstream. >=20 > Signed-off-by: Bartosz Golaszewski I liked the idea since you first mentioned it. I think it makes way more sense using the nvmem tree than the other trees. Although, I happily did it for at24 all those years ;) Reviewed-by: Wolfram Sang --Ej252IKKCEMr/8YS Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEOZGx6rniZ1Gk92RdFA3kzBSgKbYFAmo0XbkACgkQFA3kzBSg Kbagug/9FMyCCrmhsjAnHmK1LboL9gwE4LkrQlkOKYdti+gnHal/NIGEKBstaioq VyOyVXLmQsKYmcjGWUEpWNYHYauFWUrs+qFniwk8xM82Fnq3/ucl1jWmP+So91oZ jOkVSUSZ++d5AAoa+oS+0ZsufRrDIRRQGzLIC9y0+W//kj+OBvkER036dcoL7qRc iH/UmLheOgldWhYMNgZwHWjknjBhMvtsAgnbwxeqtKSktE1h6DzSbE0fZjg774RS tJaVzjL6yA85oQXaF5y71hW9rCOlw4AU8JuKG907hLsfVDaTJfeqR9ThdrmqiKpC SnnYnxxWvTYqmvCZJr9n3KhS84WIQ8B6Pvc60volEnbo8gRwGSOxnhv3cDniiu5v +xbSvyTG4VzZ5ZHHHZc0m4cwBKcAwuEmLfqMy1gqFqJERBBkOchsVEunFC1kHu/2 0OexfvLR6O/f00JirqRCXqVvPXwHDw7ksXE6mP35aD3z+dKcnL81CZRifdahVa2X sJvJhipJ3vgEUPhjHrx6uioEFoW3mUkqpr7EgObMk+5B9l5BfxZx+yj82TlXhXWk 3sEWjsG9RydkVvGhqsAID8LJ13fV+jhhQHBkTwcfRTOXeSCtstS2GRbxX+KjfY0N M0CvUs/UpKHNntGch2T3V2W5Z1Sfl+7gaC950sBesEFDV7kav3s= =WGAX -----END PGP SIGNATURE----- --Ej252IKKCEMr/8YS--