From: Ingo Molnar <mingo@elte.hu>
To: Dmitri Vorobiev <dmitri.vorobiev@gmail.com>
Cc: tglx@linutronix.de, hpa@zytor.com, linux-kernel@vger.kernel.org
Subject: Re: x86: fix a couple of sparse warnings
Date: Mon, 28 Apr 2008 14:38:09 +0200 [thread overview]
Message-ID: <20080428123809.GD27997@elte.hu> (raw)
In-Reply-To: <1209338159-30095-1-git-send-email-dmitri.vorobiev@gmail.com>
* Dmitri Vorobiev <dmitri.vorobiev@gmail.com> wrote:
> Hi Ingo, Peter, Thomas,
>
> Here is a couple of patches that fix sparse warnings produced while
> compiling defconfig for i386:
thanks Dmitri, applied.
Ingo
next prev parent reply other threads:[~2008-04-28 12:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-27 23:15 x86: fix a couple of sparse warnings Dmitri Vorobiev
2008-04-27 23:15 ` [PATCH 1/2] x86: iommu_sac_force can become static Dmitri Vorobiev
2008-04-27 23:15 ` [PATCH 2/2] x86: add proper header for reboot_force Dmitri Vorobiev
2008-04-28 12:38 ` Ingo Molnar [this message]
2008-04-28 13:37 ` x86: fix a couple of sparse warnings Adrian Bunk
2008-04-28 13:43 ` Dmitri Vorobiev
2008-04-28 13:59 ` Adrian Bunk
2008-04-28 15:01 ` Ingo Molnar
2008-04-28 18:56 ` Adrian Bunk
2008-04-28 19:13 ` Sam Ravnborg
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=20080428123809.GD27997@elte.hu \
--to=mingo@elte.hu \
--cc=dmitri.vorobiev@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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