linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Liam Breck <liam@networkimprov.net>,
	Sebastian Reichel <sre@kernel.org>, Takashi Iwai <tiwai@suse.de>,
	linux-pm@vger.kernel.org, Liam Breck <kernel@networkimprov.net>
Subject: Re: [PATCH v3] power: supply: bq24190_charger: Use extcon to determine ilimit, 5v boost
Date: Wed, 29 Mar 2017 09:38:06 -0700	[thread overview]
Message-ID: <20170329163806.GQ8575@atomide.com> (raw)
In-Reply-To: <5990b469-8c86-428e-428d-d2be77569dd3@redhat.com>

* Hans de Goede <hdegoede@redhat.com> [170329 02:36]:
> Hi,
> 
> On 29-03-17 10:21, Liam Breck wrote:
> > On Wed, Mar 29, 2017 at 12:34 AM, Hans de Goede <hdegoede@redhat.com> wrote:
> > > Hi,
> > > 
> > > On 29-03-17 03:12, Liam Breck wrote:
> > > > 
> > > > Sebastian, this patch needs some work, could you drop it from -next
> > > > and look for v4 from Hans?
> > > 
> > > 
> > > Nack.
> > > 
> > > Liam this whole dropping patches from -next business is not how
> > > things are normally done in kernel-land, please stop expecting it.
> > > 
> > > The whole dropping patches all the time thing means people don't have
> > > a stable base to base future patches on which is unworkable.
> > 
> > This was merged 3h after you posted it without acks from Tony or me.
> > So maybe asking for a do-over in this case isn't unreasonable :-)
> > Another of your patches has a replacement pending already. We'd both
> > benefit from a clean history wherever possible. And new-feature
> > patches should really simmer on the list for a little while.
> 
> When I posted my initial series you asked me to rebase it onto
> -next, which I agreed to as that is the normal way to do things.
> 
> All I'm asking of you is to do the same you've asked of me and
> base your patches on top of -next too.
> 
> Dropping patches out of -next is a rare thing and nothing something
> which we should do every other patch. This can all easily be
> fixed up with a follow-up patch without breaking bisectability
> or some-such.

Yeah agreed. Let's not start redoing branches if possible and
instead do incremental changes on top. Mistakes can happen, but
with multiple people patching the same code it's important to
have a branch we can all pull from.

> Actually having a follow-up patch to remove the 5v boost support
> is useful from a history pov as it documents why there is no 5v
> boost support in the extcon handling.

Yeah works for me.

Regards,

Tony

  reply	other threads:[~2017-03-29 16:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-23  8:32 [PATCH v3] power: supply: bq24190_charger: Use extcon to determine ilimit, 5v boost Hans de Goede
2017-03-23 11:16 ` Sebastian Reichel
2017-03-25  0:06 ` Liam Breck
2017-03-29  1:12 ` Liam Breck
2017-03-29  7:34   ` Hans de Goede
2017-03-29  8:21     ` Liam Breck
2017-03-29  9:34       ` Hans de Goede
2017-03-29 16:38         ` Tony Lindgren [this message]
2017-03-31 15:43     ` Hans de Goede

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=20170329163806.GQ8575@atomide.com \
    --to=tony@atomide.com \
    --cc=hdegoede@redhat.com \
    --cc=kernel@networkimprov.net \
    --cc=liam@networkimprov.net \
    --cc=linux-pm@vger.kernel.org \
    --cc=sre@kernel.org \
    --cc=tiwai@suse.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;
as well as URLs for NNTP newsgroup(s).