From: Wim Van Sebroeck <wim@iguana.be>
To: Guenter Roeck <guenter@roeck-us.net>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Aaron Sierra <asierra@xes-inc.com>,
Samuel Ortiz <sameo@linux.intel.com>,
Randy Dunlap <rdunlap@xenotime.net>,
linux-watchdog@vger.kernel.org, Jean Delvare <khali@linux-fr.org>
Subject: Re: linux-next: manual merge of the watchdog tree with the mfd tree
Date: Wed, 23 May 2012 07:44:30 +0200 [thread overview]
Message-ID: <20120523054430.GH3074@spo001.leaseweb.com> (raw)
In-Reply-To: <6.2.5.6.2.20120522153050.0284ee38@roeck-us.net>
Hi Sam,
Since %04llx with a typecast to u64 is the way to go (Thanks Stephen and Randy)...
> How do we make sure that Randy's patch makes it upstream ? The iTCO
> patch is currently in Sam's tree.
Can you carry Randy's patch/fix (since it fixes the change introduced by the iTCO_wdt mfd patch)?
If not then I will apply the patch later on once the iTCO_wdt mfd patch is mainstream.
Kind regards,
Wim.
next prev parent reply other threads:[~2012-05-23 5:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-18 5:23 linux-next: manual merge of the watchdog tree with the mfd tree Stephen Rothwell
2012-05-18 8:32 ` Wim Van Sebroeck
2012-05-19 1:20 ` Guenter Roeck
2012-05-22 16:35 ` Wim Van Sebroeck
2012-05-22 22:37 ` Guenter Roeck
2012-05-22 22:46 ` Stephen Rothwell
2012-05-23 5:44 ` Wim Van Sebroeck [this message]
2012-05-23 14:26 ` Samuel Ortiz
2012-05-23 14:55 ` Wim Van Sebroeck
-- strict thread matches above, loose matches on Subject: below --
2013-02-08 1:52 Stephen Rothwell
2013-02-08 11:36 ` Wim Van Sebroeck
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=20120523054430.GH3074@spo001.leaseweb.com \
--to=wim@iguana.be \
--cc=asierra@xes-inc.com \
--cc=guenter@roeck-us.net \
--cc=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=sameo@linux.intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox