linux-watchdog.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gregory Fong <gregory@broadcom.com>
To: Gregory Fong <gregory.0xf0@gmail.com>
Cc: "robh+dt@kernel.org" <robh+dt@kernel.org>,
	"pawel.moll@arm.com" <pawel.moll@arm.com>,
	"mark.rutland@arm.com" <mark.rutland@arm.com>,
	"ijc+devicetree@hellion.org.uk" <ijc+devicetree@hellion.org.uk>,
	"galak@codeaurora.org" <galak@codeaurora.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"wim@iguana.be" <wim@iguana.be>,
	"linux-watchdog@vger.kernel.org" <linux-watchdog@vger.kernel.org>,
	bcm-kernel-feedback-list <bcm-kernel-feedback-list@broadcom.com>,
	Justin Chen <justinpopo6@gmail.com>
Subject: Re: [PATCH v2 2/2] watchdog: Watchdog driver for Broadcom Set-Top Box
Date: Thu, 27 Aug 2015 23:18:54 +0000	[thread overview]
Message-ID: <55DF9AFD.3060000@broadcom.com> (raw)
In-Reply-To: <55DF9AB6.4040104@broadcom.com>

Gah, sorry, my email client did something really weird.  Sorry for the
duplication, please don't reply to those.

-- 
Gregory

  reply	other threads:[~2015-08-27 23:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-27 22:53 [PATCH v2 0/2] watchdog: driver for BCM7038 and newer chips Justin Chen
2015-08-27 22:53 ` [PATCH v2 1/2] watchdog: bcm7038: add device tree binding documentation Justin Chen
2015-08-28  1:02   ` Guenter Roeck
2015-08-27 22:53 ` [PATCH v2 2/2] watchdog: Watchdog driver for Broadcom Set-Top Box Justin Chen
2015-08-28  1:01   ` Guenter Roeck
2015-08-27 23:17 ` Gregory Fong
2015-08-27 23:18   ` Gregory Fong [this message]
2015-08-27 23:17 ` [PATCH v2 1/2] watchdog: bcm7038: add device tree binding documentation Gregory Fong

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=55DF9AFD.3060000@broadcom.com \
    --to=gregory@broadcom.com \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=devicetree@vger.kernel.org \
    --cc=galak@codeaurora.org \
    --cc=gregory.0xf0@gmail.com \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=justinpopo6@gmail.com \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=pawel.moll@arm.com \
    --cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).