Message ID | 20240223163516.796606-1-michael.j.ruhl@intel.com |
---|---|
State | New |
Headers |
Return-Path: <linux-kernel+bounces-78735-ouuuleilei=gmail.com@vger.kernel.org> Delivered-To: ouuuleilei@gmail.com Received: by 2002:a05:7300:a81b:b0:108:e6aa:91d0 with SMTP id bq27csp700593dyb; Fri, 23 Feb 2024 08:38:22 -0800 (PST) X-Forwarded-Encrypted: i=3; AJvYcCXVii5e2dkpEQhATY2Cn7L1bYlyJuyq6WT0ZJ/HNGgunYyU0xO6nyIe5cSqACjhJWkZXKfO5P8DwoBgoARGX2RG4Ojn4w== X-Google-Smtp-Source: AGHT+IFZAy5Mr9BLgx75qm5ht2myiyrWMqDFOm85WPKHLxSBtD/Fzp9hSsuplfkfKZF1TBWl+4Zy X-Received: by 2002:a17:902:cec1:b0:1d9:f31c:d2f3 with SMTP id d1-20020a170902cec100b001d9f31cd2f3mr433430plg.51.1708706302191; Fri, 23 Feb 2024 08:38:22 -0800 (PST) ARC-Seal: i=2; a=rsa-sha256; t=1708706302; cv=pass; d=google.com; s=arc-20160816; b=dXQY8Rnb+59yeQnkT+r79I6GFiyHKPZEcEC0abwK5RM1zAoJOq1CsY7/ozZNzyiSRq pMXGB7Kw8TQfHI9YBxmm+jS+cc56aW2p2GGdouS/1O0a1ch85/iuHS3Z/K/ycyPyT6JQ ugdwWaeMoTErYL/S+AlVSqAHKxMilxhZzjbVaYioJEQNBT2iDmFe2CBv1ioH6GFfLeCK T3M5JIjbWfBvtljmB5zwd0BJRKmbSJZ97SO1NhpGoyfjKVBtgYuz8W4fgjiBt+1LlMXi Z/yqlBlKISY/gI9yV/qpdHMJ3oO9L0czNfQIjuJADcIWJ62aIVJt5V2F4Vcx7YBUpskw f63A== ARC-Message-Signature: i=2; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:mime-version:list-unsubscribe :list-subscribe:list-id:precedence:message-id:date:subject:cc:to :from:dkim-signature; bh=S5EJOGrgAm8aquG/Ab1nE0MaxS6rH0LCI6ijpwSDUSo=; fh=DeZ+4TrSaJ2WQ12PGxX9DEGARaHR24EoqAjUm1KSpqE=; b=pEd8kVZwnNQuMwT9nXb60eoAnXWOB5lagZQqDLeZ7ZuNPMlpbLeTfuHHLxx8eoyJX6 5OrpwgAINozBcE6LtN1+TtCsPqWaxWobfsKe2gVKYr/iKN5mRv7Jg/3xBxmoNDumt0QN swANlDWCfO9t3rXngxMCyszvj9v+FBgKmkyr7qb7cIzppvfCUL9qpbVacZD5pTKv95mC gotEAkI/KnYMBu3ximMzTQuOKA9bz34mqMJaJd2I3f6leDPouoyBUqgR7zBicg1FgbY1 PF+jI2E4JGZQSG1vToh9Xs8qahP7pQNP+ljlfOEEPQiU7sMVk27T7gkxlNKP68xLWAVD 2IFg==; dara=google.com ARC-Authentication-Results: i=2; mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=UL1yHmJr; arc=pass (i=1 spf=pass spfdomain=intel.com dkim=pass dkdomain=intel.com dmarc=pass fromdomain=intel.com); spf=pass (google.com: domain of linux-kernel+bounces-78735-ouuuleilei=gmail.com@vger.kernel.org designates 139.178.88.99 as permitted sender) smtp.mailfrom="linux-kernel+bounces-78735-ouuuleilei=gmail.com@vger.kernel.org"; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: from sv.mirrors.kernel.org (sv.mirrors.kernel.org. [139.178.88.99]) by mx.google.com with ESMTPS id m7-20020a170902db0700b001db4e1c8efcsi12686739plx.88.2024.02.23.08.38.22 for <ouuuleilei@gmail.com> (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 23 Feb 2024 08:38:22 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel+bounces-78735-ouuuleilei=gmail.com@vger.kernel.org designates 139.178.88.99 as permitted sender) client-ip=139.178.88.99; Authentication-Results: mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=UL1yHmJr; arc=pass (i=1 spf=pass spfdomain=intel.com dkim=pass dkdomain=intel.com dmarc=pass fromdomain=intel.com); spf=pass (google.com: domain of linux-kernel+bounces-78735-ouuuleilei=gmail.com@vger.kernel.org designates 139.178.88.99 as permitted sender) smtp.mailfrom="linux-kernel+bounces-78735-ouuuleilei=gmail.com@vger.kernel.org"; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: from smtp.subspace.kernel.org (wormhole.subspace.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by sv.mirrors.kernel.org (Postfix) with ESMTPS id C0BB9285425 for <ouuuleilei@gmail.com>; Fri, 23 Feb 2024 16:35:37 +0000 (UTC) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by smtp.subspace.kernel.org (Postfix) with ESMTP id 89BE484A43; Fri, 23 Feb 2024 16:35:29 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=intel.com header.i=@intel.com header.b="UL1yHmJr" Received: from mgamail.intel.com (mgamail.intel.com [192.198.163.15]) (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 F41E25B1E0 for <linux-kernel@vger.kernel.org>; Fri, 23 Feb 2024 16:35:24 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=192.198.163.15 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1708706126; cv=none; b=a0aZT5ZW+MM+oCaseRs+WrwkgNu0f8Knk1FY9Z/ZsTLadzeEkeHFipXHDpnrlPHvVP/fjPXkDXUKbWg5g3lmsQubGBSHxVRzqBWj0MCq0lLEYFGWQivM0ONowtu4iLbeMvubcytWx/xERmjqH+9+rVk0dlB7FRMmiZcn8P/I/eM= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1708706126; c=relaxed/simple; bh=N+xBnxQ1ExC9SLflSQYfvZ+wQb7LNsdhHsn3A2kmeH4=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=Eje+ElIZEJtPERYrSJJ5T0X5KNhpPPZFGqcnF5MGxSEiibs8AojQh7vfjHJG0ysVhaV42F+3wuT9SuRYm/EqVKqeOq8SqLuwFkhxv0himVqwdCyQvzr+8Fp9Sl2I8kaEMVjfsi15G+UtrJZlPPMNFYk0gtxV5Xcf+6iu0IODrlA= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=intel.com; spf=pass smtp.mailfrom=intel.com; dkim=pass (2048-bit key) header.d=intel.com header.i=@intel.com header.b=UL1yHmJr; arc=none smtp.client-ip=192.198.163.15 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=intel.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=intel.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1708706125; x=1740242125; h=from:to:cc:subject:date:message-id:mime-version: content-transfer-encoding; bh=N+xBnxQ1ExC9SLflSQYfvZ+wQb7LNsdhHsn3A2kmeH4=; b=UL1yHmJrnqyf98Sw1S+5kMUlW3k4HOxnQA8TKUmqq0k+LbEs2EnxZsWh q58JV8KHfcmXLRyFFL2eQChvgcf1h0bJbE2mYDwiF6xvyQxAnPvcwnFZU 1ywJvP257yTU+kzdtwSTQFVyV+0bLCGpuqDJHQV6mjy9AXhnl3trtWvwG /n9qojuA/fAx1cN2q311mvzkjKttxHHIxfuXww7TfZwrbfen5HETXZcT0 pWsDhFTUdhj+1xDrMDBrsUSFzsIG1qvucqY2QbjIGDErjSixiL6uo74j0 SmQByJUOvxqdNvc32mRUq9eEasj1wcRDpmHxnYrhAoSXUTnmM4e7WsFYc A==; X-IronPort-AV: E=McAfee;i="6600,9927,10993"; a="3189535" X-IronPort-AV: E=Sophos;i="6.06,180,1705392000"; d="scan'208";a="3189535" Received: from fmviesa006.fm.intel.com ([10.60.135.146]) by fmvoesa109.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 23 Feb 2024 08:35:24 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.06,180,1705392000"; d="scan'208";a="6168351" Received: from awvttdev-05.aw.intel.com ([10.228.212.156]) by fmviesa006-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 23 Feb 2024 08:35:23 -0800 From: "Michael J. Ruhl" <michael.j.ruhl@intel.com> To: linux@armlinux.org.uk, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, andriy.shevchenko@linux.intel.com Cc: "Michael J. Ruhl" <michael.j.ruhl@intel.com> Subject: [PATCH v2] clkdev: Update clkdev id usage to allow for longer names Date: Fri, 23 Feb 2024 11:35:16 -0500 Message-ID: <20240223163516.796606-1-michael.j.ruhl@intel.com> X-Mailer: git-send-email 2.41.0 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: <linux-kernel.vger.kernel.org> List-Subscribe: <mailto:linux-kernel+subscribe@vger.kernel.org> List-Unsubscribe: <mailto:linux-kernel+unsubscribe@vger.kernel.org> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-getmail-retrieved-from-mailbox: INBOX X-GMAIL-THRID: 1791708419287190590 X-GMAIL-MSGID: 1791708419287190590 |
Series |
[v2] clkdev: Update clkdev id usage to allow for longer names
|
|
Commit Message
Michael J. Ruhl
Feb. 23, 2024, 4:35 p.m. UTC
clkdev DEV ID information is limited to an array of 20 bytes
(MAX_DEV_ID). It is possible that the ID could be longer than
that. If so, the lookup will fail because the "real ID" will
not match the copied value.
For instance, generating a device name for the I2C Designware
module using the PCI ID can result in a name of:
i2c_designware.39424
clkdev_create() will store:
i2c_designware.3942
The stored name is one off and will not match correctly during probe.
Increase the size of the ID to allow for a longer name.
v2: Removed CON_ID update and added example to commit
Signed-off-by: Michael J. Ruhl <michael.j.ruhl@intel.com>
---
drivers/clk/clkdev.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Comments
On Fri, Feb 23, 2024 at 11:35:16AM -0500, Michael J. Ruhl wrote: > clkdev DEV ID information is limited to an array of 20 bytes > (MAX_DEV_ID). It is possible that the ID could be longer than > that. If so, the lookup will fail because the "real ID" will > not match the copied value. > > For instance, generating a device name for the I2C Designware > module using the PCI ID can result in a name of: > > i2c_designware.39424 > > clkdev_create() will store: > > i2c_designware.3942 > > The stored name is one off and will not match correctly during probe. > > Increase the size of the ID to allow for a longer name. > v2: Removed CON_ID update and added example to commit Usually we put changelog out of the commit messages... > Signed-off-by: Michael J. Ruhl <michael.j.ruhl@intel.com> > --- ..somewhere here. Also just noticed that you forgot CCF maintainers to be included. I'm suggesting to use my script [1] which harvests more or less adequate list of people and mailing lists to Cc email to. [1]: https://github.com/andy-shev/home-bin-tools/blob/master/ge2maintainer.sh
>-----Original Message----- >From: Andy Shevchenko <andriy.shevchenko@linux.intel.com> >Sent: Friday, February 23, 2024 12:43 PM >To: Ruhl, Michael J <michael.j.ruhl@intel.com> >Cc: linux@armlinux.org.uk; linux-arm-kernel@lists.infradead.org; linux- >kernel@vger.kernel.org >Subject: Re: [PATCH v2] clkdev: Update clkdev id usage to allow for longer >names > >On Fri, Feb 23, 2024 at 11:35:16AM -0500, Michael J. Ruhl wrote: >> clkdev DEV ID information is limited to an array of 20 bytes >> (MAX_DEV_ID). It is possible that the ID could be longer than >> that. If so, the lookup will fail because the "real ID" will >> not match the copied value. >> >> For instance, generating a device name for the I2C Designware >> module using the PCI ID can result in a name of: >> >> i2c_designware.39424 >> >> clkdev_create() will store: >> >> i2c_designware.3942 >> >> The stored name is one off and will not match correctly during probe. >> >> Increase the size of the ID to allow for a longer name. > >> v2: Removed CON_ID update and added example to commit > >Usually we put changelog out of the commit messages... Yeah, usually put it in the cover letter. I will remove. I see your script automatically does a cover page...will use that format int the future. >> Signed-off-by: Michael J. Ruhl <michael.j.ruhl@intel.com> >> --- > >...somewhere here. Ok. Will keep for future reference. >Also just noticed that you forgot CCF maintainers to be included. >I'm suggesting to use my script [1] which harvests more or less >adequate list of people and mailing lists to Cc email to. > >[1]: https://github.com/andy-shev/home-bin- >tools/blob/master/ge2maintainer.sh Using your script I got: To: "Michael J. Ruhl" <michael.j.ruhl@intel.com>, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Cc: Russell King <linux@armlinux.org.uk> My list (using get_maintainers.pl) is: linux@armlinux.org.uk linux-arm-kernel@lists.infradead.org linux-kernel@vger.kernel.org They appear to be the same.... I don't have the plain text part on Russel's email (linxu@armlinux.org.uk).. Is that what is missing? Not sure what CCF is? M > >-- >With Best Regards, >Andy Shevchenko >
On Fri, Feb 23, 2024 at 06:22:13PM +0000, Ruhl, Michael J wrote: > >From: Andy Shevchenko <andriy.shevchenko@linux.intel.com> > >Sent: Friday, February 23, 2024 12:43 PM > >On Fri, Feb 23, 2024 at 11:35:16AM -0500, Michael J. Ruhl wrote: .. > I will remove. Not remove, but move to the comments/changelog (after '---' line) > I see your script automatically does a cover page...will use that format int > the future. Only if there are more than a single patch. .. > >[1]: https://github.com/andy-shev/home-bin- > >tools/blob/master/ge2maintainer.sh > > Using your script I got: > > To: "Michael J. Ruhl" <michael.j.ruhl@intel.com>, > linux-arm-kernel@lists.infradead.org, > linux-kernel@vger.kernel.org > Cc: Russell King <linux@armlinux.org.uk> > > My list (using get_maintainers.pl) is: > > linux@armlinux.org.uk > linux-arm-kernel@lists.infradead.org > linux-kernel@vger.kernel.org > > They appear to be the same.... Ah, the Russel's email looked like a mailing list, that what confused me. > I don't have the plain text part on Russel's email (linxu@armlinux.org.uk)... Is that what is missing? Yes :-) But my script also uses a heuristics (which is not visible here) to add active developers of the code in question based on the git history. > Not sure what CCF is? Common Clock Framework (This is how it's advertised in MAINTAINERS)
On Fri, Feb 23, 2024 at 08:32:27PM +0200, Andy Shevchenko wrote: > On Fri, Feb 23, 2024 at 06:22:13PM +0000, Ruhl, Michael J wrote: > > >From: Andy Shevchenko <andriy.shevchenko@linux.intel.com> > > >Sent: Friday, February 23, 2024 12:43 PM > > >On Fri, Feb 23, 2024 at 11:35:16AM -0500, Michael J. Ruhl wrote: > > ... > > > I will remove. > > Not remove, but move to the comments/changelog (after '---' line) > > > I see your script automatically does a cover page...will use that format int > > the future. > > Only if there are more than a single patch. > > ... > > > >[1]: https://github.com/andy-shev/home-bin- > > >tools/blob/master/ge2maintainer.sh > > > > Using your script I got: > > > > To: "Michael J. Ruhl" <michael.j.ruhl@intel.com>, > > linux-arm-kernel@lists.infradead.org, > > linux-kernel@vger.kernel.org > > Cc: Russell King <linux@armlinux.org.uk> > > > > My list (using get_maintainers.pl) is: > > > > linux@armlinux.org.uk > > linux-arm-kernel@lists.infradead.org > > linux-kernel@vger.kernel.org > > > > They appear to be the same.... > > Ah, the Russel's email looked like a mailing list, that what confused me. Joe, I think you know that I'll pick up on your mis-spelling of my name... and I take that as an implicit right to call you something other than your proper name. :D Secondly, because the Cc contained my name, I fail to see how you can confuse that with a mailing list. Maybe your script that you mentioned strips the names from the email addresses, thereby adding to your confusion - and maybe that isn't such a good idea after all? I'm not the only one who uses linux@... There are six people in total listed in MAINTAINERS who have a linux@... email address there. > > I don't have the plain text part on Russel's email (linxu@armlinux.org.uk)... Is that what is missing? > > Yes :-) > But my script also uses a heuristics (which is not visible here) to add active > developers of the code in question based on the git history. The developers in question for this part of the code is me and not the CCF. Therefore, what has been done by the patch author is reasonable and no special scripts are necessary. While my main git server is offline, I'm happy for the CCF folk to pick this up, so: Reviewed-by: Russell King (Oracle) <rmk+kernel@armlinux.org.uk> Michael, please resubmit with my r-b line above, and include the CCF folk in that posting: Michael Turquette <mturquette@baylibre.com> Stephen Boyd <sboyd@kernel.org> linux-clk@vger.kernel.org Thanks!
>-----Original Message----- >From: Russell King <linux@armlinux.org.uk> >Sent: Friday, February 23, 2024 2:50 PM >To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>; Ruhl, Michael J ><michael.j.ruhl@intel.com> >Cc: linux-arm-kernel@lists.infradead.org; linux-kernel@vger.kernel.org >Subject: Re: [PATCH v2] clkdev: Update clkdev id usage to allow for longer >names > >On Fri, Feb 23, 2024 at 08:32:27PM +0200, Andy Shevchenko wrote: >> On Fri, Feb 23, 2024 at 06:22:13PM +0000, Ruhl, Michael J wrote: >> > >From: Andy Shevchenko <andriy.shevchenko@linux.intel.com> >> > >Sent: Friday, February 23, 2024 12:43 PM >> > >On Fri, Feb 23, 2024 at 11:35:16AM -0500, Michael J. Ruhl wrote: >> >> ... >> >> > I will remove. >> >> Not remove, but move to the comments/changelog (after '---' line) >> >> > I see your script automatically does a cover page...will use that format int >> > the future. >> >> Only if there are more than a single patch. >> >> ... >> >> > >[1]: https://github.com/andy-shev/home-bin- >> > >tools/blob/master/ge2maintainer.sh >> > >> > Using your script I got: >> > >> > To: "Michael J. Ruhl" <michael.j.ruhl@intel.com>, >> > linux-arm-kernel@lists.infradead.org, >> > linux-kernel@vger.kernel.org >> > Cc: Russell King <linux@armlinux.org.uk> >> > >> > My list (using get_maintainers.pl) is: >> > >> > linux@armlinux.org.uk >> > linux-arm-kernel@lists.infradead.org >> > linux-kernel@vger.kernel.org >> > >> > They appear to be the same.... >> >> Ah, the Russel's email looked like a mailing list, that what confused me. > >Joe, I think you know that I'll pick up on your mis-spelling of my >name... and I take that as an implicit right to call you something >other than your proper name. :D > >Secondly, because the Cc contained my name, I fail to see how you can >confuse that with a mailing list. Maybe your script that you mentioned >strips the names from the email addresses, thereby adding to your >confusion - and maybe that isn't such a good idea after all? I'm not >the only one who uses linux@... There are six people in total listed in >MAINTAINERS who have a linux@... email address there. 😊 Andy's script picked up your name for the CC... I stripped out all but the email text for my posting... so this is my fault.... > >> > I don't have the plain text part on Russel's email (linxu@armlinux.org.uk)... >Is that what is missing? >> >> Yes :-) >> But my script also uses a heuristics (which is not visible here) to add active >> developers of the code in question based on the git history. > >The developers in question for this part of the code is me and not the >CCF. Therefore, what has been done by the patch author is reasonable >and no special scripts are necessary. > >While my main git server is offline, I'm happy for the CCF folk >to pick this up, so: > >Reviewed-by: Russell King (Oracle) <rmk+kernel@armlinux.org.uk> > >Michael, please resubmit with my r-b line above, and include the CCF >folk in that posting: I will get the appropriate names listed and repost. Thank you! M >Michael Turquette <mturquette@baylibre.com> >Stephen Boyd <sboyd@kernel.org> >linux-clk@vger.kernel.org > >Thanks! > >-- >RMK's Patch system: https://www.armlinux.org.uk/developer/patches/ >FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!
On Fri, Feb 23, 2024 at 07:49:33PM +0000, Russell King (Oracle) wrote: > On Fri, Feb 23, 2024 at 08:32:27PM +0200, Andy Shevchenko wrote: > > On Fri, Feb 23, 2024 at 06:22:13PM +0000, Ruhl, Michael J wrote: > > > >From: Andy Shevchenko <andriy.shevchenko@linux.intel.com> > > > >Sent: Friday, February 23, 2024 12:43 PM > > > >On Fri, Feb 23, 2024 at 11:35:16AM -0500, Michael J. Ruhl wrote: .. > > > >[1]: https://github.com/andy-shev/home-bin- > > > >tools/blob/master/ge2maintainer.sh > > > > > > Using your script I got: > > > > > > To: "Michael J. Ruhl" <michael.j.ruhl@intel.com>, > > > linux-arm-kernel@lists.infradead.org, > > > linux-kernel@vger.kernel.org > > > Cc: Russell King <linux@armlinux.org.uk> > > > > > > My list (using get_maintainers.pl) is: > > > > > > linux@armlinux.org.uk > > > linux-arm-kernel@lists.infradead.org > > > linux-kernel@vger.kernel.org > > > > > > They appear to be the same.... > > > > Ah, the Russel's email looked like a mailing list, that what confused me. > > Joe, I think you know that I'll pick up on your mis-spelling of my > name... and I take that as an implicit right to call you something > other than your proper name. :D Since, Javier, you told me that, I now remember some rumors... :D > Secondly, because the Cc contained my name, I fail to see how you can > confuse that with a mailing list. Maybe your script that you mentioned > strips the names from the email addresses, thereby adding to your > confusion - and maybe that isn't such a good idea after all? It's other way around. My script uses full names. > I'm not the only one who uses linux@... There are six people in total listed > in MAINTAINERS who have a linux@... email address there. Yes, but you are the only one which pops up WRT this file. > > > I don't have the plain text part on Russel's email > > > (linxu@armlinux.org.uk)... Is that what is missing? > > > > Yes :-) > > But my script also uses a heuristics (which is not visible here) to add active > > developers of the code in question based on the git history. > > The developers in question for this part of the code is me and not the > CCF. Yes, get_maintainer.pl seems to return that. It's me who naively considered you as CCF maintainer. > Therefore, what has been done by the patch author is reasonable > and no special scripts are necessary. The scripts makes life easier and robust against changes.
diff --git a/drivers/clk/clkdev.c b/drivers/clk/clkdev.c index ee37d0be6877..9cd80522ca2d 100644 --- a/drivers/clk/clkdev.c +++ b/drivers/clk/clkdev.c @@ -144,7 +144,7 @@ void clkdev_add_table(struct clk_lookup *cl, size_t num) mutex_unlock(&clocks_mutex); } -#define MAX_DEV_ID 20 +#define MAX_DEV_ID 24 #define MAX_CON_ID 16 struct clk_lookup_alloc {