From: Paul Mundt <lethal@linux-sh.org>
To: Peter H?we <PeterHuewe@gmx.de>
Cc: linux-mips@linux-mips.org, linux-sh@vger.kernel.org,
linux-kernel@vger.kernel.org, David H?rdeman <david@hardeman.nu>,
Mauro Carvalho Chehab <mchehab@infradead.org>,
linuxppc-dev@ozlabs.org, linux-m68k@lists.linux-m68k.org,
linux-media@vger.kernel.org
Subject: Re: [PATCH] media/IR: Add missing include file to rc-map.c
Date: Fri, 14 May 2010 15:02:40 +0900 [thread overview]
Message-ID: <20100514060240.GD12002@linux-sh.org> (raw)
In-Reply-To: <201005112042.14889.PeterHuewe@gmx.de>
On Tue, May 11, 2010 at 08:42:14PM +0200, Peter H?we wrote:
> Am Mittwoch 05 Mai 2010 17:20:21 schrieb Peter H?we:
> > From: Peter Huewe <peterhuewe@gmx.de>
> >
> > This patch adds a missing include linux/delay.h to prevent
> > build failures[1-5]
> >
> > Signed-off-by: Peter Huewe <peterhuewe@gmx.de>
> > ---
> Any updates on this patch?
> Issue still exists with today's linux-next tree
>
You might want to send this to the linux-next list at least. If the
people who introduced the breakage are unresponsive (as often tends to be
the case with -next) it's still worth getting trivial fixes rolled in for
the interim. This change doesn't exist outside of -next and whatever tree
introduced it, so there's not much else anyone can do about it at
present.
next prev parent reply other threads:[~2010-05-14 6:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-05 15:20 [PATCH] media/IR: Add missing include file to rc-map.c Peter Hüwe
2010-05-11 18:42 ` Peter Hüwe
2010-05-14 6:02 ` Paul Mundt [this message]
2010-05-14 11:22 ` Peter Hüwe
2010-05-14 11:26 ` Peter Hüwe
2010-05-14 12:53 ` Stephen Rothwell
2010-05-16 1:54 ` Mauro Carvalho Chehab
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=20100514060240.GD12002@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=PeterHuewe@gmx.de \
--cc=david@hardeman.nu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-sh@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mchehab@infradead.org \
/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).