From: Linus Torvalds <torvalds@linux-foundation.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Samuel Ortiz <sameo@linux.intel.com>,
Tony Lindgren <tony@atomide.com>,
Santosh Shilimkar <santosh.shilimkar@ti.com>,
Balaji T K <balajitk@ti.com>, Rajendra Nayak <rnayak@ti.com>
Subject: Re: linux-next: origin tree build warnings
Date: Thu, 31 Dec 2009 17:32:11 -0800 (PST) [thread overview]
Message-ID: <alpine.LFD.2.00.0912311731130.3630@localhost.localdomain> (raw)
In-Reply-To: <20100101122259.394d5b19.sfr@canb.auug.org.au>
On Fri, 1 Jan 2010, Stephen Rothwell wrote:
>
> I have built drivers/mfd/twl4030-irq.o the same way as before but after
> applying your patch and the warnings are fixed. I do not have the
> hardware and so cannot do a runtime test.
Ok, committed as "Reported-and-compile-tested-by:" you.
Somebody should probably test it on real hardware, but I doubt the patch
makes anything worse, and it _probably_ makes things better.
Linus
next prev parent reply other threads:[~2010-01-01 1:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-01 0:42 linux-next: origin tree build warnings Stephen Rothwell
2010-01-01 0:50 ` Linus Torvalds
2010-01-01 1:22 ` Stephen Rothwell
2010-01-01 1:32 ` Linus Torvalds [this message]
2010-01-01 1:50 ` Stephen Rothwell
2010-01-02 9:32 ` Shilimkar, Santosh
2010-01-04 13:51 ` Samuel Ortiz
-- strict thread matches above, loose matches on Subject: below --
2009-04-29 4:44 Stephen Rothwell
2009-04-29 7:52 ` Andrew Morton
2009-04-29 15:38 ` Tyler Hicks
2008-12-29 0:35 Stephen Rothwell
2008-12-29 4:01 ` David Miller
2008-12-29 4:17 ` Stephen Rothwell
2008-12-29 4:21 ` David Miller
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=alpine.LFD.2.00.0912311731130.3630@localhost.localdomain \
--to=torvalds@linux-foundation.org \
--cc=balajitk@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rnayak@ti.com \
--cc=sameo@linux.intel.com \
--cc=santosh.shilimkar@ti.com \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
--cc=tony@atomide.com \
/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