linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: tj@kernel.org (Tejun Heo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/3] ahci: st: Add support for ST's SATA IP
Date: Wed, 19 Feb 2014 13:06:30 -0500	[thread overview]
Message-ID: <20140219180630.GN10134@htj.dyndns.org> (raw)
In-Reply-To: <20140219174041.GK10504@lee--X1>

On Wed, Feb 19, 2014 at 05:40:41PM +0000, Lee Jones wrote:
> Have you listened to a word I've said? Or have you managed to get your
> self all tangled up in what you _assumed_ was meant by the 3 words I
> mentioned about fairness at the very start of this conversation? Me
> thinks the latter might be true.

It wasn't only that.  Your mention of API compability later in the
thread or the notion of separate core and leaf developers were pretty
weird.  Things like

 "I was pertaining to the fact that requesting that a driver is
  converted to a non-existing API was wrong."

just don't make much sense.  That is a patchset which is pretty close
to completion and I'm asking people to converge on that.  That happens
regularly during development in the different layers.

I think what's fundamentally disturbing is this distinction between
what you're doing and what people working on the API are doing.  It's
not like the roles are bound by contracts and one party owes to the
other.  It seems that that's what leads you to think that asking your
driver updated for a pending patchset is unfair and the rest.

> Just because I don't contribute to your subsystem, it doesn't mean I
> don't contribute elsewhere.

Again, it's not about you being good and generously contributing.
It's about sharing of basic responsibility.  You say I'm not reading
what you're saying but what you're saying hasn't really changed since
the first post except for some weaseling.

> Here... let me help you down from that big horse! ;)

I'm surely doing some of that and thanks for helping me down but I do
hope you understand some of the points.

-- 
tejun

  reply	other threads:[~2014-02-19 18:06 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-17 12:56 [PATCH 1/3] ahci: st: Provide DT bindings for ST's SATA implementation Lee Jones
2014-02-17 12:56 ` [PATCH 2/3] ARM: DT: STi: Add DT node for ST's SATA device Lee Jones
2014-02-17 12:56 ` [PATCH 3/3] ahci: st: Add support for ST's SATA IP Lee Jones
2014-02-18 23:36   ` Tejun Heo
2014-02-19  8:30     ` Lee Jones
2014-02-19 14:04       ` Tejun Heo
2014-02-19 15:01         ` Lee Jones
2014-02-19 15:06           ` Tejun Heo
2014-02-19 15:23             ` Lee Jones
2014-02-19 15:36               ` Tejun Heo
2014-02-19 16:39                 ` Lee Jones
2014-02-19 17:00                   ` Tejun Heo
2014-02-19 17:24                     ` Lee Jones
2014-02-19 17:26                   ` Tejun Heo
2014-02-19 17:40                     ` Lee Jones
2014-02-19 18:06                       ` Tejun Heo [this message]
2014-02-19 11:54     ` Hans de Goede
2014-02-19 12:14       ` Lee Jones

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=20140219180630.GN10134@htj.dyndns.org \
    --to=tj@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).