From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linus Walleij <linus.walleij@linaro.org>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Mugunthan V N <mugunthanvnm@ti.com>,
David Miller <davem@davemloft.net>,
netdev@vger.kernel.org
Subject: Re: linux-next: manual merge of the pinctrl tree with Linus' tree
Date: Mon, 17 Jun 2013 09:09:16 +0200 [thread overview]
Message-ID: <51BEB61C.3040904@linutronix.de> (raw)
In-Reply-To: <20130617161127.f202c6abe603c9ff8b30fc7c@canb.auug.org.au>
On 06/17/2013 08:11 AM, Stephen Rothwell wrote:
> Hi Linus,
Hi Stephen,
> I fixed it up (see below) and can carry the fix as necessary (no
> action is required).
The fix looks good.
Sebastian
next prev parent reply other threads:[~2013-06-17 7:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-17 6:11 linux-next: manual merge of the pinctrl tree with Linus' tree Stephen Rothwell
2013-06-17 6:11 ` Stephen Rothwell
2013-06-17 7:09 ` Sebastian Andrzej Siewior [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-12-13 4:02 linux-next: manual merge of the pinctrl tree with Linus'tree Stephen Rothwell
2013-12-13 4:01 linux-next: manual merge of the pinctrl tree with Linus' tree Stephen Rothwell
2013-08-29 7:17 Stephen Rothwell
2013-08-29 7:34 ` Linus Walleij
2013-08-29 7:45 ` Linus Walleij
2013-08-29 15:24 ` Sherman Yin
2013-08-29 17:20 ` Linus Walleij
2013-08-29 17:21 ` Linus Walleij
2012-10-12 3:30 Stephen Rothwell
2012-10-12 3:08 Stephen Rothwell
2012-10-12 3:01 Stephen Rothwell
2012-10-12 2:56 Stephen Rothwell
2012-05-28 3:08 Stephen Rothwell
2012-05-28 15:24 ` 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=51BEB61C.3040904@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=davem@davemloft.net \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mugunthanvnm@ti.com \
--cc=netdev@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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.