mirror of https://lore.kernel.org/linux-amlogic/
 help / color / mirror / Atom feed
From: broonie@kernel.org (Mark Brown)
To: linus-amlogic@lists.infradead.org
Subject: [asoc:for-4.19 199/204] sound/soc//meson/axg-tdm-interface.c:225:8: error: implicit declaration of function 'clk_set_duty_cycle'; did you mean 'clk_set_rate'?
Date: Tue, 31 Jul 2018 15:02:22 +0100	[thread overview]
Message-ID: <20180731140222.GE5719@sirena.org.uk> (raw)
In-Reply-To: <1c2a42498ea90428fb6504414154fe3663258ed6.camel@baylibre.com>

On Tue, Jul 31, 2018 at 10:39:03AM +0200, Jerome Brunet wrote:

> The commit adding the duty-cycle feature in CCF is directly based on v4.18-rc1
> Do you plan on pulling this in your branch ? or wait for dependency to be sorted
> out during the merge window maybe ?

I'd like to but I'd rather have an explicit ack from the clock
maintainers that that's OK and ideally a signed tag.  Though it's taken
so long that at this point it's not going to be much worse than just
hoping it gets sorted out in mainline given the lack of branches, it's
not affecting common platforms.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-amlogic/attachments/20180731/894b30e5/attachment.sig>

  reply	other threads:[~2018-07-31 14:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <201807210204.l9GJCtSI%fengguang.wu@intel.com>
2018-07-20 18:40 ` Jerome Brunet
2018-07-31  8:39   ` Jerome Brunet
2018-07-31 14:02     ` Mark Brown [this message]
2018-07-31 22:16       ` Michael Turquette

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=20180731140222.GE5719@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=linus-amlogic@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

all inboxes | Powered by JetHome®