From: Mark Brown <broonie@kernel.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>,
backports@vger.kernel.org, Liam Girdwood <lgirdwood@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5/7] backports: add support for voltage / current regulator drivers
Date: Mon, 22 Apr 2013 14:11:01 +0100 [thread overview]
Message-ID: <20130422131101.GA17463@sirena.org.uk> (raw)
In-Reply-To: <1366043632.8361.33.camel@jlt4.sipsolutions.net>
On Mon, Apr 15, 2013 at 06:33:52PM +0200, Johannes Berg wrote:
> On Mon, 2013-04-15 at 17:26 +0100, Mark Brown wrote:
> > Please let's at least discuss the issues here, I'm not sure what this is
> > supposed to do but the analysis of the subsystem didn't seem complete.
> I wouldn't worry about it too much. For some reason (media drivers
> related?) Luis decided that it was worth including this in the backports
> project (see http://backports.wiki.kernel.org) and I am currently
> maintaining the git tree for that, at least while I was doing some
> refactoring.
> I do notice that it doesn't quite work, there are a lot of unresolved
> symbols :)
> If you think you'd be impacted by this because users demand support from
> you for the backport or whatever I can revert this (or probably just
> remove it from the copy list for now.) I don't really have an opinion on
> it, I'm doing this because I'm interested in one specific wireless
> driver.
Well, I'd much rather have a sane backport if we're going to have one -
whatever problem is being solved here it seems likely that someone else
will have the same need and if there's a general kernel project for this
(which preusmably has some overlap with LTSI?) it seems bad to have one
that people have to be warned away from using.
Given how big the misunderstandings in the cover letter for Luis' patch
were I'd be really concerned about seeing this going into anything
officialish without some discussion about what's going on.
next prev parent reply other threads:[~2013-04-22 13:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-13 14:13 [PATCH 0/7] backport: pending backlog Luis R. Rodriguez
2013-04-13 14:13 ` [PATCH 1/7] backports: add support for backport_srctree Luis R. Rodriguez
2013-04-13 20:55 ` Johannes Berg
2013-04-13 14:13 ` [PATCH 2/7] compat: add missing header includes for DMA backports Luis R. Rodriguez
2013-04-13 20:57 ` Johannes Berg
2013-04-13 14:13 ` [PATCH 3/7] compat: backport IORESOURCE_REG definition Luis R. Rodriguez
2013-04-13 20:57 ` Johannes Berg
2013-04-13 14:13 ` [PATCH 4/7] gentree.py: add support to explicitly disable a config Luis R. Rodriguez
2013-04-13 20:59 ` Johannes Berg
2013-04-13 14:13 ` [PATCH 5/7] backports: add support for voltage / current regulator drivers Luis R. Rodriguez
2013-04-13 21:01 ` Johannes Berg
2013-04-15 16:26 ` Mark Brown
2013-04-15 16:33 ` Johannes Berg
2013-04-22 13:11 ` Mark Brown [this message]
2013-04-23 6:18 ` Luis R. Rodriguez
2013-04-15 16:25 ` Mark Brown
2013-04-13 14:13 ` [PATCH 6/7] backports: add media subsystem drivers Luis R. Rodriguez
2013-04-13 21:02 ` Johannes Berg
2013-04-13 14:13 ` [PATCH 7/7] backports: add intel_ips support Luis R. Rodriguez
2013-04-13 21:03 ` Johannes Berg
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=20130422131101.GA17463@sirena.org.uk \
--to=broonie@kernel.org \
--cc=backports@vger.kernel.org \
--cc=johannes@sipsolutions.net \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@do-not-panic.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.