From: Mike Rapoport <mike@compulab.co.il>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org
Subject: Re: [PATCH 0/8] Omap mux changes for v2.6.33 merge window (Series short description)
Date: Thu, 26 Nov 2009 13:20:25 +0200 [thread overview]
Message-ID: <4B0E6479.50608@compulab.co.il> (raw)
In-Reply-To: <20091126002038.GH4348@atomide.com>
Tony,
Tony Lindgren wrote:
> * Tony Lindgren <tony@atomide.com> [091125 16:17]:
>> Hi all,
>>
>> Here are some omap mux updates for review. These
>> are intended for the v2.6.33 merge window.
>
> Forgot to edit the subject :)
>
> Also, these patches are available in the mux branch
> of the linux-omap tree for easy testing.
After all the discussions we had, what would be preferable way to define the
board mux configuration? The omap_board_mux array or a calls for
omap_mux_init_signal?
> Regards,
>
> Tony
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
Sincerely yours,
Mike.
WARNING: multiple messages have this Message-ID (diff)
From: mike@compulab.co.il (Mike Rapoport)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/8] Omap mux changes for v2.6.33 merge window (Series short description)
Date: Thu, 26 Nov 2009 13:20:25 +0200 [thread overview]
Message-ID: <4B0E6479.50608@compulab.co.il> (raw)
In-Reply-To: <20091126002038.GH4348@atomide.com>
Tony,
Tony Lindgren wrote:
> * Tony Lindgren <tony@atomide.com> [091125 16:17]:
>> Hi all,
>>
>> Here are some omap mux updates for review. These
>> are intended for the v2.6.33 merge window.
>
> Forgot to edit the subject :)
>
> Also, these patches are available in the mux branch
> of the linux-omap tree for easy testing.
After all the discussions we had, what would be preferable way to define the
board mux configuration? The omap_board_mux array or a calls for
omap_mux_init_signal?
> Regards,
>
> Tony
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo at vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2009-11-26 11:20 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-26 0:18 [PATCH 0/8] Series short description Tony Lindgren
2009-11-26 0:18 ` Tony Lindgren
2009-11-26 0:18 ` [PATCH 1/8] omap2: mux: intoduce omap_mux_{read,write} Tony Lindgren
2009-11-26 0:18 ` Tony Lindgren
2009-11-29 10:03 ` Shilimkar, Santosh
2009-11-29 10:03 ` Shilimkar, Santosh
2009-11-30 18:54 ` Tony Lindgren
2009-11-30 18:54 ` Tony Lindgren
2009-11-26 0:19 ` [PATCH 2/8] omap: mux: Add new style pin multiplexing code for omap3 Tony Lindgren
2009-11-26 0:19 ` Tony Lindgren
2009-11-26 0:19 ` [PATCH 3/8] omap: mux: Add new style pin multiplexing data for 34xx Tony Lindgren
2009-11-26 0:19 ` Tony Lindgren
2009-11-26 0:19 ` [PATCH 4/8] omap: mux: Add new style init functions to omap3 board-*.c files Tony Lindgren
2009-11-26 0:19 ` Tony Lindgren
2009-11-26 0:19 ` [PATCH 5/8] omap: mux: Add debugfs support for new mux code Tony Lindgren
2009-11-26 0:19 ` Tony Lindgren
2009-11-26 0:19 ` [PATCH 6/8] omap: Split i2c platform init for mach-omap1 and mach-omap2 Tony Lindgren
2009-11-26 0:19 ` Tony Lindgren
2009-11-27 17:44 ` Tony Lindgren
2009-11-27 17:44 ` Tony Lindgren
2009-11-26 0:20 ` [PATCH 7/8] omap: mux: Replace omap_cfg_reg() with new style signal or gpio functions Tony Lindgren
2009-11-26 0:20 ` Tony Lindgren
2009-11-26 0:20 ` [PATCH 8/8] omap: mux: Remove old mux code for 34xx Tony Lindgren
2009-11-26 0:20 ` Tony Lindgren
2009-11-26 0:20 ` [PATCH 0/8] Omap mux changes for v2.6.33 merge window (Series short description) Tony Lindgren
2009-11-26 0:20 ` Tony Lindgren
2009-11-26 11:20 ` Mike Rapoport [this message]
2009-11-26 11:20 ` Mike Rapoport
2009-11-26 18:15 ` Tony Lindgren
2009-11-26 18:15 ` Tony Lindgren
2009-11-27 16:16 ` Tony Lindgren
2009-11-27 16:16 ` Tony Lindgren
2009-11-26 6:44 ` [PATCH 0/8] Series short description Hemanth V
2009-11-26 6:44 ` Hemanth V
2009-11-26 8:27 ` Tony Lindgren
2009-11-26 8:27 ` Tony Lindgren
2009-11-29 10:03 ` Shilimkar, Santosh
2009-11-29 10:03 ` Shilimkar, Santosh
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=4B0E6479.50608@compulab.co.il \
--to=mike@compulab.co.il \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.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 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.