From: Paul Bolle <pebolle@tiscali.nl>
To: John Crispin <blogic@openwrt.org>, Ralf Baechle <ralf@linux-mips.org>
Cc: Valentin Rothberg <valentinrothberg@gmail.com>,
linux-mips@linux-mips.org, linux-kernel@vger.kernel.org
Subject: Re: MIPS: ralink: CONFIG_SOC_MT7621?
Date: Mon, 12 Jan 2015 13:35:53 +0100 [thread overview]
Message-ID: <1421066153.22660.64.camel@x220> (raw)
In-Reply-To: <1414406687.28499.17.camel@x220>
John,
On Mon, 2014-10-27 at 11:44 +0100, Paul Bolle wrote:
> Your commit 715f2e581856 ("MIPS: ralink: cleanup early_printk") landed
> in today's linux-next (ie, next-20141027). It adds two checks for
> CONFIG_SOC_MT7621. The patch to add Kconfig symbol SOC_MT7621 is still
> pending (see http://patchwork.linux-mips.org/patch/8033/ ).
>
> Obviously, until that patch lands these two checks will always evaluate
> to false.
These useless checks have now made it into v3.19-rc1 and later. What's
the current status of the patch I quoted above?
Thanks,
Paul Bolle
prev parent reply other threads:[~2015-01-12 12:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-27 10:44 MIPS: ralink: CONFIG_SOC_MT7621? Paul Bolle
2015-01-12 12:35 ` Paul Bolle [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=1421066153.22660.64.camel@x220 \
--to=pebolle@tiscali.nl \
--cc=blogic@openwrt.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.org \
--cc=valentinrothberg@gmail.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