linux-um archives
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Alexandre Belloni <alexandre.belloni@bootlin.com>
Cc: linux-rtc@vger.kernel.org,
	Alessandro Zummo <a.zummo@towertech.it>,
	linux-um@lists.infradead.org
Subject: Re: [PATCH] rtc: enable RTC framework on ARCH=um
Date: Sat, 21 Nov 2020 10:51:43 +0100	[thread overview]
Message-ID: <229d3b5d615c858345a8b84454099eefd64581ce.camel@sipsolutions.net> (raw)
In-Reply-To: <20201120223914.GD348979@piout.net>

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@intel.com>
> > 
> > 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@intel.com>
> Acked-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
> 
> > ---
> > 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


_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um


  reply	other threads:[~2020-11-21  9:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-20 20:11 [PATCH] rtc: enable RTC framework on ARCH=um Johannes Berg
2020-11-20 22:39 ` Alexandre Belloni
2020-11-21  9:51   ` Johannes Berg [this message]
2020-12-03 22:41 ` Alexandre Belloni

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=229d3b5d615c858345a8b84454099eefd64581ce.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=a.zummo@towertech.it \
    --cc=alexandre.belloni@bootlin.com \
    --cc=linux-rtc@vger.kernel.org \
    --cc=linux-um@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox