From: Tony Lindgren <tony@atomide.com>
To: Grazvydas Ignotas <notasas@gmail.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: multipath mux question
Date: Mon, 5 Jul 2010 16:10:22 +0300 [thread overview]
Message-ID: <20100705131020.GX15951@atomide.com> (raw)
In-Reply-To: <AANLkTinuFnpTyMJaMLLulio2hmGHKfL_6VkJogsV_nDa@mail.gmail.com>
* Grazvydas Ignotas <notasas@gmail.com> [100705 14:43]:
> On Mon, Jul 5, 2010 at 10:36 AM, Tony Lindgren <tony@atomide.com> wrote:
> >
> > We should just print a warning and return an error. Then we should
> > also start checking the return values for omap_mux_init_gpio
> > now that the code is converted over to use the new mux code.
>
> Hm, not sure about return checking, what omap2_mmc_mux() can do when
> it sees omap_mux_init_gpio failing because of that inevitable gpio126
> multipath error?
Heh, right :) I guess in that case omap2_mmc_mux should not do anything
and assume the board-*.c file has set up the muxing.
Regards,
Tony
prev parent reply other threads:[~2010-07-05 13:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-02 21:28 multipath mux question Grazvydas Ignotas
2010-07-05 7:36 ` Tony Lindgren
2010-07-05 11:49 ` Grazvydas Ignotas
2010-07-05 13:10 ` Tony Lindgren [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=20100705131020.GX15951@atomide.com \
--to=tony@atomide.com \
--cc=linux-omap@vger.kernel.org \
--cc=notasas@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).