All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Liam Breck <liam@networkimprov.net>
Cc: Sebastian Reichel <sre@kernel.org>,
	linux-pm@vger.kernel.org, Tony Lindgren <tony@atomide.com>,
	Liam Breck <kernel@networkimprov.net>
Subject: Re: [PATCH v3 2/4] power: bq24190_charger: Clean up extcon code
Date: Mon, 3 Apr 2017 08:53:37 +0200	[thread overview]
Message-ID: <857a9dd7-8ed3-0afe-d1e2-2420928263aa@redhat.com> (raw)
In-Reply-To: <CAKvHMgQ6gJ822W_hXO8jGAq_vr4L8NaFJpNHA5sKYJ+kTRtQgg@mail.gmail.com>

Hi,

On 03-04-17 00:03, Liam Breck wrote:

<snip>

> Could you adjust your tone to be more collaborative and less cutting?

I'm sorry if I sounded a bit cutting.

I've tried nothing but to be collaborative and work with you
until now, but this patch introduces several changes I already
mentioned were not a good idea in your review of my original
patch and IMHO do nothing to improve the code.

> You only have this code for the Atom device because I designed and
> built hardware with this part and hired Mark to write the driver from
> scratch. I'd like a little goodwill in exchange!

And here we get to the root of the problem, that you keep claiming
ownership of the driver because you paid Mark to write it,
this is not how the Linux kernel works. Yes you paid Mark to write
a driver and in return you get an entire kernel. You no less own
the bq24190_charger driver then other people own other parts of
the kernel.

Your remarks against Sebastian that he MUST wait for your ack
before merging anything are quite frankly completely out of line
and I have been on the verge of saying something about this
several times already but I decided to stay quiet (until now).

So yes I apologize for my tone getting a bit cutting as I never
want that, but TBH I've found the way you're claiming to be
THE authority on the bq24190_charger driver and have been behaving
if everyone needs to do exactly as you say when it comes to that
driver quite off-putting / abrasive.

As for me "only having this code for the Atom devices", it would
have likely taken me way less time to knock out a new driver
(like I've done for the fuel-gauge) then all the coordination with
you is costing me...

> And also gratitude
> for taking time to fix two of your patches.

I reviewed and acked the first fix, which is my way of saying
thank you. As for this set of fixes, I never asked for those
and I think they are a bad idea.

> I expect discussion of charger patches with an experienced kernel
> contributor to look like these threads:
>
> https://patchwork.kernel.org/project/linux-pm/list/?submitter=109&state=*&q=bq24190_charger%3A+Use+PM+runtime+autosuspend&archive=both

So do I and usually conversations I take place in look like that
...

Regards,

Hans

  reply	other threads:[~2017-04-03  6:53 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-01 20:25 [PATCH v3 0/4] BQ24190 charger fixes Liam Breck
2017-04-01 20:25 ` [PATCH v3 1/4] power: bq24190_charger: Limit over/under voltage fault logging Liam Breck
2017-04-01 20:25 ` [PATCH v3 2/4] power: bq24190_charger: Clean up extcon code Liam Breck
2017-04-02 12:27   ` Hans de Goede
2017-04-02 22:03     ` Liam Breck
2017-04-03  6:53       ` Hans de Goede [this message]
2017-04-03  8:17         ` Hans de Goede
2017-04-03 21:40         ` Liam Breck
2017-04-01 20:25 ` [PATCH v3 3/4] power: bq24190_charger: Uniform pm_runtime_get() failure handling Liam Breck
2017-04-01 20:25 ` [PATCH v3 4/4] power: bq24190_charger: Delay before polling reset flag Liam Breck
2017-04-02 12:29   ` Hans de Goede
2017-04-02 20:16     ` Liam Breck
2017-04-02 20:35       ` Hans de Goede
2017-04-04  4:36         ` Liam Breck

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=857a9dd7-8ed3-0afe-d1e2-2420928263aa@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=kernel@networkimprov.net \
    --cc=liam@networkimprov.net \
    --cc=linux-pm@vger.kernel.org \
    --cc=sre@kernel.org \
    --cc=tony@atomide.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.