From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: OMAP: Modified omap_mux_init_signal() to take in const char *
Date: Fri, 22 Oct 2010 10:21:20 -0700 [thread overview]
Message-ID: <20101022172120.GH9149@atomide.com> (raw)
In-Reply-To: <4CC09042.3000201@logicpd.com>
* Tim Nordell <tim.nordell@logicpd.com> [101021 12:02]:
> On 10/21/10 13:50, Tim Nordell wrote:
>
> It looks like by inspection that there could be a couple of things wrong
> with that patch however. Namely, on the comparison of muxname to
> m0_entry, if they have the same string up to mode0_len, such as
> "dss_data1" and "dss_data12" it'd match there prematurely as it'd stop
> comparing. Also, a minor display issue on the printk of the new muxname.
Good catch, it would be nice to get those fixed too. Got any patches
for those issues?
Regards,
Tony
prev parent reply other threads:[~2010-10-22 17:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-21 18:50 [PATCH] ARM: OMAP: Modified omap_mux_init_signal() to take in const char * Tim Nordell
2010-10-21 19:10 ` Tim Nordell
2010-10-22 17:21 ` 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=20101022172120.GH9149@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@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;
as well as URLs for NNTP newsgroup(s).