Hi, Alessandro Zummo <[email protected]> writes:
> On Thu, 19 Dec 2013 17:34:09 +0100 > [email protected] (Arnaud Ebalard) wrote: > >> I never heard of *listed* RTC maintainer during all the review process >> on rtc-linux list (v0 sent in october); I dug the list archives and when >> this previously happened, someone else (e.g. Andrew Morton) was kind >> enough to handle the patches: > > Yes, Andrew usually pick those. I guess he should be put in the MAINTAINERS file then. Otherwise, get_maintainer.pl script can not do its job correctly and people end up thinking you should be the one handling those. > I do not maintain a separate tree due to most RTCs being specifit to a > subsytem. I do not understand: the chip is generic, i.e. this is not a RTC chip specific to a given SoC (like rtc-mv.c is for instance). Can you be more specific? >> http://www.spinics.net/lists/arm-kernel/msg292187.html > > Regarding your patch, please do not add entries to /proc. > Use sysfs if you need. Well, this is what is currently described in the documentation (Documentation/rtc.txt), in drivers/rtc/rtc-test.c driver and what many drivers do (AFAICT, 22/125). Additionally, I only provide some additional info for an existing file: the /proc entry is created by the drivers/rtc/class.c as soon as someone selects CONFIG_RTC_INTF_PROC. Do you want me to send a v7 w/ the .proc helper removed or leave things as they are and Ack the patch as is? Cheers, a+ -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
