From: Linus Walleij <linus.walleij-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
To: John Crispin <blogic-p3rKhJxN3npAfugRpC6u6w@public.gmane.org>
Cc: Thomas Langer
<thomas.langer-th3ZBGNqt+7QT0dZR+AlfA@public.gmane.org>,
devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
Ralf Baechle <ralf-6z/3iImG2C8G8FEW9MqTrA@public.gmane.org>
Subject: Re: [PATCH 3/6] OF: pinctrl: MIPS: lantiq: adds support for FALCON SoC
Date: Sun, 19 Aug 2012 00:22:29 +0200 [thread overview]
Message-ID: <CACRpkdbWf=r1rfQ5Q_G=OSaPqF0iq43nDikz3+GdPReToC4wEw@mail.gmail.com> (raw)
In-Reply-To: <502C030D.1030604-p3rKhJxN3npAfugRpC6u6w@public.gmane.org>
On Wed, Aug 15, 2012 at 10:14 PM, John Crispin <blogic-p3rKhJxN3npAfugRpC6u6w@public.gmane.org> wrote:
> Is it ok if i have these pinctrl patches go upstream via the MIPS tree ?
Yes, go ahead.
Yours,
Linus Walleij
next prev parent reply other threads:[~2012-08-18 22:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-24 6:50 [PATCH 1/6] OF: pinctrl: MIPS: lantiq: implement lantiq/xway pinctrl support John Crispin
[not found] ` <1343112660-12245-1-git-send-email-blogic-p3rKhJxN3npAfugRpC6u6w@public.gmane.org>
2012-07-24 6:50 ` [PATCH 2/6] Document: devicetree: add OF documents for lantiq xway pinctrl John Crispin
2012-07-24 6:50 ` [PATCH 3/6] OF: pinctrl: MIPS: lantiq: adds support for FALCON SoC John Crispin
2012-07-27 23:23 ` Linus Walleij
2012-07-30 9:41 ` John Crispin
[not found] ` <CACRpkdYP8PdcnS2h_-+n9ZdBmMuBPUv9so9WsUyS-X5rMz1qsQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-08-15 20:14 ` John Crispin
[not found] ` <502C030D.1030604-p3rKhJxN3npAfugRpC6u6w@public.gmane.org>
2012-08-18 22:22 ` Linus Walleij [this message]
2012-07-24 6:50 ` [PATCH 4/6] Document: devicetree: add OF documents for lantiq falcon pinctrl John Crispin
2012-07-27 23:23 ` [PATCH 1/6] OF: pinctrl: MIPS: lantiq: implement lantiq/xway pinctrl support Linus Walleij
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='CACRpkdbWf=r1rfQ5Q_G=OSaPqF0iq43nDikz3+GdPReToC4wEw@mail.gmail.com' \
--to=linus.walleij-qsej5fyqhm4dnm+yrofe0a@public.gmane.org \
--cc=blogic-p3rKhJxN3npAfugRpC6u6w@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=ralf-6z/3iImG2C8G8FEW9MqTrA@public.gmane.org \
--cc=thomas.langer-th3ZBGNqt+7QT0dZR+AlfA@public.gmane.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).