All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: linux-can@vger.kernel.org
Subject: Re: [PATCH v3 1/2] can: mcp251xfd: mcp251xfd_probe(): try to get crystal clock rate from property
Date: Thu, 22 Jul 2021 21:52:54 +0300	[thread overview]
Message-ID: <YPm+hkutsbtsTNlB@smile.fi.intel.com> (raw)
In-Reply-To: <20210706101421.ukdgfo3eyoijblbu@pengutronix.de>

On Tue, Jul 06, 2021 at 12:14:21PM +0200, Marc Kleine-Budde wrote:
> On 06.07.2021 13:10:59, Andy Shevchenko wrote:
> > On Mon, May 31, 2021 at 01:09:41PM +0300, Andy Shevchenko wrote:
> > > On Mon, May 31, 2021 at 10:44:43AM +0200, Marc Kleine-Budde wrote:
> > > > From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> > > > 
> > > > In some configurations, mainly ACPI-based, the clock frequency of the
> > > > device is supplied by very well established 'clock-frequency'
> > > > property. Hence, try to get it from the property at last if no other
> > > > providers are available.
> > 
> > Is this series missed merge window?
> > I never saw it in Linux Next and nor in vanilla...
> 
> Yes, I missed the merge window. Will send a pull request after -rc1
> (when net-next is open again).

Still no sign of them anywhere. Please, proceed with them!

-- 
With Best Regards,
Andy Shevchenko



      reply	other threads:[~2021-07-22 18:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-31  8:44 [PATCH v3 1/2] can: mcp251xfd: mcp251xfd_probe(): try to get crystal clock rate from property Marc Kleine-Budde
2021-05-31  8:44 ` [PATCH v3 2/2] can: mcp251xfd: Fix header block to clarify independence from OF Marc Kleine-Budde
2021-05-31 10:09 ` [PATCH v3 1/2] can: mcp251xfd: mcp251xfd_probe(): try to get crystal clock rate from property Andy Shevchenko
2021-07-06 10:10   ` Andy Shevchenko
2021-07-06 10:14     ` Marc Kleine-Budde
2021-07-22 18:52       ` 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=YPm+hkutsbtsTNlB@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=linux-can@vger.kernel.org \
    --cc=mkl@pengutronix.de \
    /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.