All of lore.kernel.org
 help / color / mirror / Atom feed
From: SF Markus Elfring <elfring@users.sourceforge.net>
To: Dave Airlie <airlied@gmail.com>
Cc: Sean Paul <seanpaul@chromium.org>,
	Dan Carpenter <dan.carpenter@oracle.com>,
	Bhaktipriya Shridhar <bhaktipriya96@gmail.com>,
	kernel-janitors@vger.kernel.org,
	LKML <linux-kernel@vger.kernel.org>,
	dri-devel@lists.freedesktop.org,
	Julia Lawall <julia.lawall@lip6.fr>,
	Daniel Vetter <daniel.vetter@ffwll.ch>, Tejun Heo <tj@kernel.org>,
	Thierry Reding <treding@nvidia.com>
Subject: Re: GPU-DRM-QXL: Move three assignments in qxl_device_init()
Date: Fri, 23 Sep 2016 10:50:33 +0200	[thread overview]
Message-ID: <65f2917b-4264-01a3-2441-367d1e3a313b@users.sourceforge.net> (raw)
In-Reply-To: <CAPM=9twZjDec3dk0y5UN0HHx_pR-kiaf9+Q7n5E2_=v6TgQ=Lw@mail.gmail.com>

> Markus, please contact the list in advance in future before posting a bunch
> of patches that don't fix any problems.

I am trying to improve various open issues also in Linux source files.

Unfortunately, some of the proposed changes might not fit to your software
development attention at the moment.
How are the chances that corresponding change acceptance will evolve a bit more
after a while?

Regards,
Markus

WARNING: multiple messages have this Message-ID (diff)
From: SF Markus Elfring <elfring@users.sourceforge.net>
To: Dave Airlie <airlied@gmail.com>
Cc: Bhaktipriya Shridhar <bhaktipriya96@gmail.com>,
	kernel-janitors@vger.kernel.org,
	LKML <linux-kernel@vger.kernel.org>,
	dri-devel@lists.freedesktop.org,
	Julia Lawall <julia.lawall@lip6.fr>,
	Daniel Vetter <daniel.vetter@ffwll.ch>, Tejun Heo <tj@kernel.org>,
	Thierry Reding <treding@nvidia.com>,
	Dan Carpenter <dan.carpenter@oracle.com>
Subject: Re: GPU-DRM-QXL: Move three assignments in qxl_device_init()
Date: Fri, 23 Sep 2016 08:50:33 +0000	[thread overview]
Message-ID: <65f2917b-4264-01a3-2441-367d1e3a313b@users.sourceforge.net> (raw)
In-Reply-To: <CAPM=9twZjDec3dk0y5UN0HHx_pR-kiaf9+Q7n5E2_=v6TgQ=Lw@mail.gmail.com>

> Markus, please contact the list in advance in future before posting a bunch
> of patches that don't fix any problems.

I am trying to improve various open issues also in Linux source files.

Unfortunately, some of the proposed changes might not fit to your software
development attention at the moment.
How are the chances that corresponding change acceptance will evolve a bit more
after a while?

Regards,
Markus

WARNING: multiple messages have this Message-ID (diff)
From: SF Markus Elfring <elfring@users.sourceforge.net>
To: Dave Airlie <airlied@gmail.com>
Cc: Bhaktipriya Shridhar <bhaktipriya96@gmail.com>,
	kernel-janitors@vger.kernel.org,
	LKML <linux-kernel@vger.kernel.org>,
	dri-devel@lists.freedesktop.org,
	Julia Lawall <julia.lawall@lip6.fr>,
	Daniel Vetter <daniel.vetter@ffwll.ch>, Tejun Heo <tj@kernel.org>,
	Thierry Reding <treding@nvidia.com>,
	Dan Carpenter <dan.carpenter@oracle.com>
Subject: Re: GPU-DRM-QXL: Move three assignments in qxl_device_init()
Date: Fri, 23 Sep 2016 10:50:33 +0200	[thread overview]
Message-ID: <65f2917b-4264-01a3-2441-367d1e3a313b@users.sourceforge.net> (raw)
In-Reply-To: <CAPM=9twZjDec3dk0y5UN0HHx_pR-kiaf9+Q7n5E2_=v6TgQ=Lw@mail.gmail.com>

> Markus, please contact the list in advance in future before posting a bunch
> of patches that don't fix any problems.

I am trying to improve various open issues also in Linux source files.

Unfortunately, some of the proposed changes might not fit to your software
development attention at the moment.
How are the chances that corresponding change acceptance will evolve a bit more
after a while?

Regards,
Markus
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

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

Thread overview: 43+ 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:18 ` 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:20   ` SF Markus Elfring
2016-09-22  6:21 ` [PATCH 2/4] GPU-DRM-QXL: Move three assignments " SF Markus Elfring
2016-09-22  6:21   ` SF Markus Elfring
2016-09-22 10:09   ` Dan Carpenter
2016-09-22 10:09     ` Dan Carpenter
2016-09-22 13:11     ` SF Markus Elfring
2016-09-22 13:11       ` SF Markus Elfring
2016-09-22 15:46       ` Gerd Hoffmann
2016-09-22 15:46         ` Gerd Hoffmann
2016-09-22 15:46         ` Gerd Hoffmann
2016-09-22 17:16         ` SF Markus Elfring
2016-09-22 17:16           ` SF Markus Elfring
2016-09-22 20:24           ` Gerd Hoffmann
2016-09-22 20:24             ` Gerd Hoffmann
2016-09-22 20:24       ` Dan Carpenter
2016-09-22 20:24         ` Dan Carpenter
2016-09-22 20:24         ` Dan Carpenter
2016-09-23  7:25         ` Sean Paul
2016-09-23  7:25           ` Sean Paul
2016-09-23  7:25           ` Sean Paul
2016-09-23  7:53           ` Dave Airlie
2016-09-23  7:53             ` Dave Airlie
2016-09-23  8:50             ` SF Markus Elfring [this message]
2016-09-23  8:50               ` SF Markus Elfring
2016-09-23  8:50               ` SF Markus Elfring
2016-09-23 13:30               ` Emil Velikov
2016-09-23 13:30                 ` Emil Velikov
2016-09-23 14:23                 ` SF Markus Elfring
2016-09-23 14:23                   ` SF Markus Elfring
2016-09-23 14:23                   ` SF Markus Elfring
2016-09-23  8:42           ` SF Markus Elfring
2016-09-23  8:42             ` SF Markus Elfring
2016-09-23  8:42             ` SF Markus Elfring
2016-09-23  8:34         ` SF Markus Elfring
2016-09-23  8:34           ` SF Markus Elfring
2016-09-23  8:34           ` SF Markus Elfring
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:22   ` 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
2016-09-22  6:23   ` 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=65f2917b-4264-01a3-2441-367d1e3a313b@users.sourceforge.net \
    --to=elfring@users.sourceforge.net \
    --cc=airlied@gmail.com \
    --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=seanpaul@chromium.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 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.