linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: SF Markus Elfring <elfring@users.sourceforge.net>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: dri-devel@lists.freedesktop.org,
	"Bhaktipriya Shridhar" <bhaktipriya96@gmail.com>,
	"Daniel Vetter" <daniel.vetter@ffwll.ch>,
	"David Airlie" <airlied@linux.ie>,
	"Noralf Trønnes" <noralf@tronnes.org>,
	"Tejun Heo" <tj@kernel.org>,
	"Thierry Reding" <treding@nvidia.com>,
	LKML <linux-kernel@vger.kernel.org>,
	kernel-janitors@vger.kernel.org,
	"Julia Lawall" <julia.lawall@lip6.fr>
Subject: Re: GPU-DRM-QXL: Move three assignments in qxl_device_init()
Date: Fri, 23 Sep 2016 10:34:23 +0200	[thread overview]
Message-ID: <5a98e827-4ac1-ee6f-171b-02de97927a69@users.sourceforge.net> (raw)
In-Reply-To: <20160922202419.GP13620@mwanda>

>> Would you like to discuss the statistics for my failure (or success) rate
>> a bit more so that involved issues can be clarified in a constructive way?
> 
> It should be that you target 20 bug fixes for each new regression
> that you add.

How do you think about to clarify any concrete "regression" a bit more?


> There is no hope for improving the kernel

I have got an other impression. - I am trying to help also for this goal.


> because you are not even trying to fix 20 bugs,

Under which circumstances would you dare to acknowledge once more
that I improved anything for which you care about?


> only introducing them.

It's a pity that you interpret some of my contributions in this way.


> Once you fix 20 bugs, then you will be even and you can start sending
> cleanups again.  This is fair.

How much will the suggested software refactorings influence the kind of
error counter that you prefer so far?

Regards,
Markus

  parent reply	other threads:[~2016-09-23  8:35 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-22  6:18 [PATCH 0/4] GPU-DRM-QXL: Fine-tuning for three function implementations SF Markus Elfring
2016-09-22  6:20 ` [PATCH 1/4] GPU-DRM-QXL: Use kmalloc_array() in qxl_device_init() SF Markus Elfring
2016-09-22  6:21 ` [PATCH 2/4] GPU-DRM-QXL: Move three assignments " SF Markus Elfring
2016-09-22 10:09   ` Dan Carpenter
2016-09-22 13:11     ` SF Markus Elfring
2016-09-22 15:46       ` Gerd Hoffmann
2016-09-22 17:16         ` SF Markus Elfring
2016-09-22 20:24           ` Gerd Hoffmann
2016-09-22 20:24       ` Dan Carpenter
2016-09-23  7:25         ` Sean Paul
2016-09-23  7:53           ` Dave Airlie
2016-09-23  8:50             ` SF Markus Elfring
2016-09-23 13:30               ` Emil Velikov
2016-09-23 14:23                 ` SF Markus Elfring
2016-09-23  8:42           ` SF Markus Elfring
2016-09-23  8:34         ` SF Markus Elfring [this message]
2016-09-22  6:22 ` [PATCH 3/4] GPU-DRM-QXL: Improve a size determination in qxl_driver_load() SF Markus Elfring
2016-09-22  6:23 ` [PATCH 4/4] GPU-DRM-QXL: Adjust checks for null pointers in three functions 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=5a98e827-4ac1-ee6f-171b-02de97927a69@users.sourceforge.net \
    --to=elfring@users.sourceforge.net \
    --cc=airlied@linux.ie \
    --cc=bhaktipriya96@gmail.com \
    --cc=dan.carpenter@oracle.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=julia.lawall@lip6.fr \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=noralf@tronnes.org \
    --cc=tj@kernel.org \
    --cc=treding@nvidia.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;
as well as URLs for NNTP newsgroup(s).