On Fri, 2020-11-20 at 23:39 +0100, Alexandre Belloni wrote: > On 20/11/2020 21:11:06+0100, Johannes Berg wrote: > > From: Johannes Berg <johannes.berg@xxxxxxxxx> > > > > There's no real reason it should be disabled, and at least we can > > use it for development & testing with the RTC test driver. > > > > However, two devices are missing a HAS_IOMEM dependency, so add > > that to avoid build failures from e.g. allyesconfig. > > > > Signed-off-by: Johannes Berg <johannes.berg@xxxxxxxxx> > Acked-by: Alexandre Belloni <alexandre.belloni@xxxxxxxxxxx> > > > --- > > Would there be objection to taking this through the linux-um tree? > > I have a couple of patches that depend on it as well, to add > > suspend/resume support with a pseudo-RTC to wake up from it. > > I'm fine with that. Thanks. I think I spoke too quickly here though; I realize now that it's probably better if you just merge it through whatever RTC tree you have. Some of the code I was working on has "depends on RTC_CLASS", but then it obviously doesn't matter what tree it goes through, it doesn't have any conflicts, and things will just fall into place whenever all patches are merged, regardless through which tree. For my local experimentation etc. it doesn't matter, I can just carry this. I apologize for not thinking this through properly yesterday, but now think it's better if it just goes through the normal route. Thanks, johannes
