From: Rob Herring <robherring2@gmail.com>
To: Mark Brown <broonie@kernel.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux-ALSA <alsa-devel@alsa-project.org>,
Alexander Shiyan <shc_work@mail.ru>,
Liam Girdwood <lgirdwood@gmail.com>, Takashi Iwai <tiwai@suse.de>,
Timur Tabi <timur@tabi.org>, Rob Herring <robh+dt@kernel.org>,
Grant Likely <grant.likely@linaro.org>
Subject: Re: [PATCH] of: add empty of_find_node_by_path() for !OF
Date: Wed, 16 Apr 2014 11:10:15 -0500 [thread overview]
Message-ID: <CAL_JsqKPYiQpv8PDPsemSEuXJc_2Roqu-G3+8rV4dSHbXuHfDw@mail.gmail.com> (raw)
In-Reply-To: <20140416160352.GS12304@sirena.org.uk>
On Wed, Apr 16, 2014 at 11:03 AM, Mark Brown <broonie@kernel.org> wrote:
> On Wed, Apr 16, 2014 at 09:32:37AM -0500, Rob Herring wrote:
>> On Wed, Apr 16, 2014 at 9:25 AM, Mark Brown <broonie@kernel.org> wrote:
>
>> > Is there a branch I can pull into ASoC, or can I apply it there? This
>> > fixes a build failure introduced into there by some recent work.
>
>> I haven't pushed it out yet. You can take it and add my ack if you
>> want instead. Otherwise, I do plan to send fixes to Linus this week.
>
> OK, this is needed for new development so I'll apply it temporarily so I
> don't break my tree in -next and then discard it once Linus merges -
> sound sensible?
Yes. If this going to be a common pattern, a
of_get_machine_compatible() helper might be useful. Usually, any code
searching by path makes me suspicious.
Rob
next prev parent reply other threads:[~2014-04-16 16:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-16 6:49 [PATCH] of: add empty of_find_node_by_path() for !OF Alexander Shiyan
2014-04-16 12:26 ` Rob Herring
2014-04-16 14:25 ` Mark Brown
2014-04-16 14:32 ` Rob Herring
2014-04-16 16:03 ` Mark Brown
2014-04-16 16:10 ` Rob Herring [this message]
2014-04-16 17:15 ` Mark Brown
2014-04-16 17:39 ` Rob Herring
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=CAL_JsqKPYiQpv8PDPsemSEuXJc_2Roqu-G3+8rV4dSHbXuHfDw@mail.gmail.com \
--to=robherring2@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=grant.likely@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=robh+dt@kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=shc_work@mail.ru \
--cc=timur@tabi.org \
--cc=tiwai@suse.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.