All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: "Luis R. Rodriguez" <mcgrof@kernel.org>,
	Ingo Molnar <mingo@redhat.com>, "H . Peter Anvin" <hpa@zytor.com>,
	linux-kernel@vger.kernel.org, x86@kernel.org
Subject: Re: [PATCH v2 1/1] x86/rtc: Allocate interrupt for platform device
Date: Wed, 18 Jan 2017 18:48:37 +0200	[thread overview]
Message-ID: <1484758117.2133.213.camel@linux.intel.com> (raw)
In-Reply-To: <1484756950.2133.211.camel@linux.intel.com>

On Wed, 2017-01-18 at 18:29 +0200, Andy Shevchenko wrote:
> On Wed, 2017-01-18 at 11:24 +0100, Thomas Gleixner wrote:

> Another variant is to use just a separate callback on arch_initcall().
> It would be closer to current solution.

I will go this way and just create
arch/x86/platform/intel-mid/device_libs/platform_mrfld_rtc.c
in a similar way how it's done for watchdog.

> If you have something better to try, please tell, I would test it.

-- 
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy

      reply	other threads:[~2017-01-18 16:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-16 17:23 [PATCH v2 1/1] x86/rtc: Allocate interrupt for platform device Andy Shevchenko
2017-01-16 19:04 ` Luis R. Rodriguez
2017-01-16 19:21   ` Andy Shevchenko
2017-01-16 21:00     ` Thomas Gleixner
2017-01-16 22:44       ` Andy Shevchenko
2017-01-17  8:25         ` Thomas Gleixner
2017-01-17 13:40       ` Andy Shevchenko
2017-01-18 10:24         ` Thomas Gleixner
2017-01-18 10:56           ` Andy Shevchenko
2017-01-18 11:02             ` Thomas Gleixner
2017-01-18 11:54               ` Andy Shevchenko
2017-01-18 16:29           ` Andy Shevchenko
2017-01-18 16:48             ` Andy Shevchenko [this message]

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=1484758117.2133.213.camel@linux.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcgrof@kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.