All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@the-dreams.de>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: ksummit <ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] Keeping reviews meaningful
Date: Wed, 17 Jul 2019 09:31:31 +0200	[thread overview]
Message-ID: <20190717073130.GA1021@kunai> (raw)
In-Reply-To: <bf269ea7-6a9c-25db-5b97-958d9e15bddd@infradead.org>

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


> > Right, if you commit it then you are responsible for it. It does not matter
> > whether you reviewed it yourself or relied on someone else review.
> 
> It's a bit amazing (and scary) that this is even being discussed (as though
> it's unknown) after these many years.

Guys, I am just trying to better cope with an amount of patches I can't
handle on my own currently.

My strategy to get more people involved is divide and conquer, e.g. look
for people willing to maintain a single driver. That makes the "trust
matrix" kind of complex. So, I still do think I can improve where to put
my always-too-limited efforts by documenting where I put it in the past.

I can keep track of that differently than a R-b tag, that is fine with
me.

I never had the intention of sneaking out of responsibility and I only
sign patches I am sure they are ready to be upstreamed. This discussion
exists because I want to keep this state.


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2019-07-17  7:31 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-06 14:27 [Ksummit-discuss] [MAINTAINERS SUMMIT] Keeping reviews meaningful Wolfram Sang
2019-07-06 16:52 ` Leon Romanovsky
2019-07-06 17:17   ` Wolfram Sang
2019-07-08 10:47     ` Jan Kara
2019-07-08 11:47       ` Wolfram Sang
2019-07-15 16:11     ` Mauro Carvalho Chehab
2019-07-08 11:21 ` Geert Uytterhoeven
2019-07-08 11:59   ` Wolfram Sang
2019-07-15 15:58     ` Mauro Carvalho Chehab
2019-07-15 17:00       ` Theodore Y. Ts'o
2019-07-15 17:11         ` Mauro Carvalho Chehab
2019-07-16 21:26         ` Wolfram Sang
2019-08-17 21:35         ` Paul Walmsley
2019-08-19  6:57           ` Jan Kara
2019-08-19  7:06             ` Jiri Kosina
2019-08-19  7:06             ` Julia Lawall
2019-08-19  8:04               ` Jan Kara
2019-08-19  8:13                 ` Julia Lawall
2019-08-20 10:22                   ` James Bottomley
2019-08-19  8:26             ` Thomas Gleixner
2019-08-19 16:16               ` Christian Brauner
2019-08-19 19:04                 ` Thomas Gleixner
2019-08-19 21:03                   ` Christian Brauner
2019-07-08 14:57   ` Mark Brown
2019-07-14  9:35 ` Jonathan Cameron
2019-07-14 10:13   ` Thomas Gleixner
2019-07-15  9:10     ` Rafael J. Wysocki
2019-07-16 21:16     ` Wolfram Sang
2019-07-16 21:57       ` Olof Johansson
2019-07-16 22:27         ` Thomas Gleixner
2019-07-17  3:59           ` Randy Dunlap
2019-07-17  7:31             ` Wolfram Sang [this message]
2019-07-17 16:05               ` Linus Walleij
2019-07-17 16:40                 ` Wolfram Sang

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=20190717073130.GA1021@kunai \
    --to=wsa@the-dreams.de \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=rdunlap@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 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.