From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Paul Mundt <lethal@linux-sh.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Peter Huewe <peterhuewe@gmx.de>,
Ian Lartey <ian@opensource.wolfsonmicro.com>,
Dimitris Papastamos <dp@opensource.wolfsonmicro.com>,
Samuel Ortiz <sameo@linux.intel.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mfd/wm831x-irq: Convert to new irq_chip functions and fix build failure
Date: Fri, 10 Dec 2010 18:24:55 +0000 [thread overview]
Message-ID: <20101210182455.GJ3200@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <20101210174843.GB3750@linux-sh.org>
On Sat, Dec 11, 2010 at 02:48:43AM +0900, Paul Mundt wrote:
> I have no intention of dropping the select from SH, but I'm not going to
> insist that these drivers have the deprecated dependency if we're a) not
> really using them and b) there's a reasonable expectation that they'll
> basically be taken care of in .38 anyways.
That's unfortunate, I'm a bit concerned about support for users picking
up the kernel and using it to build products.
Samuel, would you be OK with cherry picking the relevant commits to the
Wolfson drivers back into .37? I'm especially concerned about WM8994
here - I'd really not like to see a kernel version go out where that
doesn't work.
> I haven't been following the progress in -next, but now that you've
> pointed it out I'll give it a look. It's less effort to just fix up the
> remaining users than it is to audit API dependencies for all of them at
> least.
Probably slightly more in that you can't just blindly add the dependency
when you see the problem but yeah.
next prev parent reply other threads:[~2010-12-10 18:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-09 23:34 [PATCH] mfd/wm831x-irq: Convert to new irq_chip functions and fix build failure Peter Huewe
[not found] ` <12ABA93B-6923-4AF7-BF34-E070BE72A8E2@opensource.wolfsonmicro.com>
2010-12-10 1:39 ` Thomas Gleixner
2010-12-10 5:07 ` Paul Mundt
2010-12-10 12:14 ` Mark Brown
2010-12-10 15:43 ` Paul Mundt
2010-12-10 17:01 ` Paul Mundt
2010-12-10 17:32 ` Mark Brown
2010-12-10 17:24 ` Mark Brown
2010-12-10 17:48 ` Paul Mundt
2010-12-10 18:24 ` Mark Brown [this message]
2010-12-11 1:59 ` Paul Mundt
2010-12-20 0:29 ` Samuel Ortiz
2010-12-10 7:55 ` Peter Hüwe
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=20101210182455.GJ3200@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=dp@opensource.wolfsonmicro.com \
--cc=ian@opensource.wolfsonmicro.com \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterhuewe@gmx.de \
--cc=sameo@linux.intel.com \
--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