From: Julia Lawall <julia.lawall@lip6.fr>
To: SF Markus Elfring <elfring@users.sourceforge.net>
Cc: linux-fbdev@vger.kernel.org,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
kernel-janitors@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
dri-devel@lists.freedesktop.org, "Andrew F. Davis" <afd@ti.com>,
Tomi Valkeinen <tomi.valkeinen@ti.com>,
Joe Perches <joe@perches.com>,
Arvind Yadav <arvind.yadav.cs@gmail.com>,
linux-omap@vger.kernel.org
Subject: Re: omapfb/dss: Delete an error message for a failed memory allocation in three functions
Date: Tue, 28 Nov 2017 09:26:00 +0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1711281025210.3443@hadrien> (raw)
In-Reply-To: <c504db1d-415a-9bd4-172c-b1c17dd3740f@users.sourceforge.net>
On Tue, 28 Nov 2017, SF Markus Elfring wrote:
> >>>> It seems that I got no responses so far for clarification requests
> >>>> according to the documentation in a direction I hoped for.
> >>>
> >>> That's because you are pretty unresponsive to direction.
> >>
> >> From which places did you get this impression?
> >
> > Perhaps from the text that you have written only four lines below.
> > All comments are dismissed as "the usual mixture of disagreements and acceptance".
>
> A mixture will always evolve.
>
> * Some acceptance might not need further considerations.
>
> * But the disagreements are remembered differently.
> They have got a potential for further improvements in some areas.
>
>
> > If you look at the patches sent by others, who learn from
> > the feedback provided to them,
>
> I am also learning to some degree continuously.
>
>
> > there are not so many responses on the disagreements side.
>
> How do you think about to look at the details for such an observation?
>
>
> > So the mixture is not usual.
>
> I find that it can be also a matter of statistics.
>
>
> > Since you send lots of patches on the same issues,
>
> Yes. - I am trying to fix some implementation details by the means
> of source code analysis and corresponding transformation.
> The patch count is still growing.
>
>
> > there should be no disagreements at all at this point.
>
> I got an other impression. The probability for disagreements is increasing
> in relation to the number of contributors to which I show change possibilities.
No. You should learn from the previous submissions what concerns people
have and address them up front.
julia
>
> There are also other open issues remaining which can get another
> solution somehow.
>
> Regards,
> Markus
> --
> To unsubscribe from this list: send the line "unsubscribe kernel-janitors" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2017-11-28 9:26 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-26 18:55 [PATCH] omapfb/dss: Delete an error message for a failed memory allocation in three functions SF Markus Elfring
2017-11-27 16:43 ` Andrew F. Davis
2017-11-27 17:27 ` SF Markus Elfring
2017-11-27 17:44 ` Ladislav Michl
2017-11-27 18:12 ` SF Markus Elfring
2017-11-27 18:56 ` Geert Uytterhoeven
2017-11-27 19:22 ` Ladislav Michl
2017-11-27 22:20 ` Ladislav Michl
2017-11-27 19:07 ` [PATCH] " Joe Perches
2017-11-27 21:33 ` Andrew F. Davis
2017-11-27 21:45 ` Ladislav Michl
2017-11-27 21:48 ` SF Markus Elfring
2017-11-28 1:45 ` Joe Perches
2017-11-28 7:41 ` SF Markus Elfring
2017-11-28 7:49 ` Julia Lawall
2017-11-28 8:49 ` SF Markus Elfring
2017-11-28 9:26 ` Julia Lawall [this message]
2017-11-28 9:56 ` SF Markus Elfring
2017-11-28 8:04 ` Joe Perches
2017-11-28 8:49 ` Ladislav Michl
2017-11-28 9:11 ` SF Markus Elfring
2017-11-28 9:28 ` Julia Lawall
2017-11-28 10:15 ` SF Markus Elfring
2017-11-28 10:23 ` Ladislav Michl
2017-11-28 10:50 ` SF Markus Elfring
2017-11-28 11:41 ` Ladislav Michl
2017-11-28 12:13 ` SF Markus Elfring
2017-11-28 17:50 ` Ladislav Michl
2017-11-28 18:09 ` SF Markus Elfring
2017-11-28 14:36 ` Joe Perches
2017-12-03 18:20 ` SF Markus Elfring
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=alpine.DEB.2.20.1711281025210.3443@hadrien \
--to=julia.lawall@lip6.fr \
--cc=afd@ti.com \
--cc=arvind.yadav.cs@gmail.com \
--cc=b.zolnierkie@samsung.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=elfring@users.sourceforge.net \
--cc=joe@perches.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=tomi.valkeinen@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox