mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Lee Jones <lee.jones@linaro.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] regulator: First pull of MFD <-> Regulator IB (v3.16)
Date: Wed, 23 Apr 2014 19:13:50 +0100	[thread overview]
Message-ID: <20140423181350.GE12304@sirena.org.uk> (raw)
In-Reply-To: <20140423150047.GH6264@lee--X1>

[-- Attachment #1: Type: text/plain, Size: 2816 bytes --]

On Wed, Apr 23, 2014 at 04:00:47PM +0100, Lee Jones wrote:

> > Can you drop the last one please, I've already applied it?  I'd have
> > expected just the first two (or probably even just the second one).  If
> > you need it in your tree just grab the branch (or I can tag it if you
> > like).

> > I tend to apply these things early where they don't have dependencies
> > due to the large number of reposts for unrelated changes in the series
> > that tend to happen (and often several very similar serieses being in
> > flight at once); I frequently end up just deleting them unread.  Not
> > sure what the best way to handle this stuff is in general.

> I know that you due, which I think makes things easier for you, but
> more difficult for everyone else (author, other maintainers). Applying
> cross-subsystem patches also makes things difficult down the line.

It's not really my convenience here - it's about trying progress the
serieses and cut the amount of code that people are having to carry.

People were complaining about things getting stalled due to lack of
review but of course one of the reasons for that is that it seems that
the early bits of the series commonly need respins and there's frequent
delays too (probably compounded by the frequent respins).  That creates
a sense that these things are going nowhere slowly (or are just reposts
of already reviewed changes) which discourages spending time on them
until someone actively chases and then compounds the problem.

> Not sure what do do about the last patch now, as it has MFD changes
> which aren't in the MFD tree. All well and good if no one else touches
> that hunk for the remainder of the cycle, but if they do we're likely
> to have merge conflicts.

As I said above just pull the branch into MFD - like I say I can tag it
if you want, in fact I just pushed one:

  git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git tags/tps65090-reg-pdata-v3.16

That's what all the tiny topic branches are for, to make it easy to do
merges when needed - there shouldn't be any great difficulty here?

> > >  Documentation/devicetree/bindings/regulator/tps65090.txt |  4 ++++
> > >  drivers/mfd/tps65090.c                                   | 41 +++++++++++++++++++++++++----------------
> > >  drivers/power/tps65090-charger.c                         | 11 -----------
> > >  drivers/regulator/tps65090-regulator.c                   | 56 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> > >  include/linux/mfd/tps65090.h                             | 19 +++++++++++++++++++
> > >  5 files changed, 104 insertions(+), 27 deletions(-)

> > Your formatting for these still seems to be messing up.

> How so? Looks fine for me I think?

The lines are *way* over 80 columns, look to be formatted for about 130
or something.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2014-04-23 18:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-23 11:39 Lee Jones
2014-04-23 12:46 ` Mark Brown
2014-04-23 15:00   ` Lee Jones
2014-04-23 18:13     ` Mark Brown [this message]
2014-04-28  9:12 ` [GIT PULL v2] " Lee Jones
2014-04-29 17:04   ` Mark Brown

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=20140423181350.GE12304@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=lee.jones@linaro.org \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®