From: David Miller <davem@davemloft.net>
To: samuel@sortiz.org
Cc: bunk@stusta.de, akpm@osdl.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, ralf@linux-mips.org,
linux-mips@linux-mips.org, reiga@dspnet.fr.eu.org,
irda-users@lists.sourceforge.net
Subject: Re: [PATCH 2/2] [IrDA] Fix the AU1000 FIR dependencies
Date: Thu, 29 Jun 2006 17:03:40 -0700 (PDT) [thread overview]
Message-ID: <20060629.170340.55510056.davem@davemloft.net> (raw)
In-Reply-To: <20060630065607.GB4729@sortiz.org>
From: Samuel Ortiz <samuel@sortiz.org>
Date: Fri, 30 Jun 2006 09:56:07 +0300
> AU1000 FIR is broken, it should depend on SOC_AU1000.
>
> Spotted by Jean-Luc Leger.
>
> Signed-off-by: Adrian Bunk <bunk@stusta.de>
> Signed-off-by: Samuel Ortiz <samuel@sortiz.org>
Applied, thanks.
prev parent reply other threads:[~2006-06-30 0:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-29 15:41 [2.6 patch] fix the AU1000_FIR dependencies Adrian Bunk
2006-06-30 6:56 ` [PATCH 2/2] [IrDA] Fix the AU1000 FIR dependencies Samuel Ortiz
2006-06-30 0:03 ` David Miller [this message]
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=20060629.170340.55510056.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akpm@osdl.org \
--cc=bunk@stusta.de \
--cc=irda-users@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=netdev@vger.kernel.org \
--cc=ralf@linux-mips.org \
--cc=reiga@dspnet.fr.eu.org \
--cc=samuel@sortiz.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