From: Doug Ledford <dledford@redhat.com>
To: Richard Weinberger <richard.weinberger@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Zhang Rui <rui.zhang@intel.com>,
LKML <linux-kernel@vger.kernel.org>,
Linux PM list <linux-pm@vger.kernel.org>
Subject: Re: [GIT PULL] Thermal management updates for v5.4-rc1
Date: Fri, 27 Sep 2019 15:57:28 -0400 [thread overview]
Message-ID: <7689df508569921295851c83bbb6f5fcd2e3f90f.camel@redhat.com> (raw)
In-Reply-To: <CAFLxGvxm77O7JnVeHjk8xMfAO2_5+PxV7QDkihL5q+86Q1xz6Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1340 bytes --]
On Fri, 2019-09-27 at 21:52 +0200, Richard Weinberger wrote:
> On Fri, Sep 27, 2019 at 9:30 PM Doug Ledford <dledford@redhat.com>
> wrote:
> > Because there are literally thousands of developers working on
> > kernel
> > bits here and there, and you're swatting this particular fly one
> > developer at a time.
>
> I strongly disagree. One of the golden rules of kernel development is,
> read what Linus writes. Especially during the merge window.
>
> Thanks,
> //richard
Developers come and go. Your argument is temporally flawed. A
developer might start working on the tree, read everything during a
merge window, and not catch one of Linus' rebase rants prior to
committing a rebase felony of their own.
Besides, I don't think this rule of yours is all that universal. If
Linus is off on a thread about arm64 device tree brokenness and someone
does a rebase and he rants about it, I'm very likely to miss that rant.
I read what I reasonably deem to be relevant to me and my work, or
sometimes additional stuff that just jumps out at me. But I never
learned to speed read so I don't even try to read it all and wouldn't
agree to a rule that says I have to.
--
Doug Ledford <dledford@redhat.com>
GPG KeyID: B826A3330E572FDD
Fingerprint = AE6B 1BDA 122B 23B4 265B 1274 B826 A333 0E57 2FDD
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-09-27 19:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-27 13:08 Zhang Rui
2019-09-27 18:34 ` Linus Torvalds
2019-09-27 19:29 ` Doug Ledford
2019-09-27 19:41 ` Linus Torvalds
2019-09-27 19:52 ` Doug Ledford
2019-09-27 19:52 ` Richard Weinberger
2019-09-27 19:57 ` Doug Ledford [this message]
2019-09-30 13:09 ` Jonathan Corbet
2019-09-30 13:09 ` Jonathan Corbet
2019-09-28 14:00 ` Zhang Rui
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=7689df508569921295851c83bbb6f5fcd2e3f90f.camel@redhat.com \
--to=dledford@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=richard.weinberger@gmail.com \
--cc=rui.zhang@intel.com \
--cc=torvalds@linux-foundation.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®