From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: Wim Van Sebroeck <wim@iguana.be>
Cc: linux-watchdog@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 0/3] watchdog: sunxi: Change compatible patterns
Date: Thu, 13 Mar 2014 12:15:58 +0100 [thread overview]
Message-ID: <20140313111558.GH2815@lukather> (raw)
In-Reply-To: <20140312180751.GC1484@spo001.leaseweb.com>
[-- Attachment #1: Type: text/plain, Size: 593 bytes --]
On Wed, Mar 12, 2014 at 07:07:51PM +0100, Wim Van Sebroeck wrote:
> > > I'm OK with the patches, but what is the preferred way to get them upstream?
> > > via watchdog tree or via arch/soc tree?
> >
> > Since it touches the machine restart code, I'd prefer to merge it
> > myself if it's ok?
>
> No Problem. You have my Acked-by.
Actually, I only have to keep together patches 2 and 3. Could you
merge the first one? I'll handle the two others.
Thanks!
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-03-13 11:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-07 21:29 [PATCH v2 0/3] watchdog: sunxi: Change compatible patterns Maxime Ripard
2014-02-07 21:29 ` [PATCH v2 1/3] watchdog: sunxi: Change compatibles Maxime Ripard
2014-02-07 21:29 ` [PATCH v2 2/3] ARM: sunxi: Add the new watchog compatibles to the reboot code Maxime Ripard
2014-02-07 21:29 ` [PATCH v2 3/3] ARM: sunxi: dt: Update the watchdog compatibles Maxime Ripard
2014-03-03 10:40 ` [PATCH v2 0/3] watchdog: sunxi: Change compatible patterns Maxime Ripard
2014-03-07 7:37 ` Wim Van Sebroeck
2014-03-11 20:54 ` Wim Van Sebroeck
2014-03-12 9:16 ` Maxime Ripard
2014-03-12 18:07 ` Wim Van Sebroeck
2014-03-13 11:15 ` Maxime Ripard [this message]
2014-03-15 8:37 ` Wim Van Sebroeck
2014-03-17 16:22 ` Maxime Ripard
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=20140313111558.GH2815@lukather \
--to=maxime.ripard@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=wim@iguana.be \
/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