From: SF Markus Elfring <elfring@users.sourceforge.net>
To: Julia Lawall <julia.lawall@lip6.fr>,
linux-omap@vger.kernel.org, linux-fbdev@vger.kernel.org,
dri-devel@lists.freedesktop.org
Cc: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
kernel-janitors@vger.kernel.org,
LKML <linux-kernel@vger.kernel.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>
Subject: Re: omapfb/dss: Delete an error message for a failed memory allocation in three functions
Date: Tue, 28 Nov 2017 09:56:25 +0000 [thread overview]
Message-ID: <62306606-9e30-d33d-d059-07fdcdbaae92@users.sourceforge.net> (raw)
In-Reply-To: <alpine.DEB.2.20.1711281025210.3443@hadrien>
>> 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.
The concerns can vary as contributors and changes are different.
How would you like to “address” the data structure for a default allocation
failure report finally?
Regards,
Markus
WARNING: multiple messages have this Message-ID (diff)
From: SF Markus Elfring <elfring@users.sourceforge.net>
To: Julia Lawall <julia.lawall@lip6.fr>,
linux-omap@vger.kernel.org, linux-fbdev@vger.kernel.org,
dri-devel@lists.freedesktop.org
Cc: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
kernel-janitors@vger.kernel.org,
LKML <linux-kernel@vger.kernel.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>
Subject: Re: omapfb/dss: Delete an error message for a failed memory allocation in three functions
Date: Tue, 28 Nov 2017 10:56:25 +0100 [thread overview]
Message-ID: <62306606-9e30-d33d-d059-07fdcdbaae92@users.sourceforge.net> (raw)
In-Reply-To: <alpine.DEB.2.20.1711281025210.3443@hadrien>
>> 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.
The concerns can vary as contributors and changes are different.
How would you like to “address” the data structure for a default allocation
failure report finally?
Regards,
Markus
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
WARNING: multiple messages have this Message-ID (diff)
From: SF Markus Elfring <elfring@users.sourceforge.net>
To: Julia Lawall <julia.lawall@lip6.fr>,
linux-omap@vger.kernel.org, linux-fbdev@vger.kernel.org,
dri-devel@lists.freedesktop.org
Cc: Joe Perches <joe@perches.com>, "Andrew F. Davis" <afd@ti.com>,
Arvind Yadav <arvind.yadav.cs@gmail.com>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
Tomi Valkeinen <tomi.valkeinen@ti.com>,
LKML <linux-kernel@vger.kernel.org>,
kernel-janitors@vger.kernel.org
Subject: Re: omapfb/dss: Delete an error message for a failed memory allocation in three functions
Date: Tue, 28 Nov 2017 10:56:25 +0100 [thread overview]
Message-ID: <62306606-9e30-d33d-d059-07fdcdbaae92@users.sourceforge.net> (raw)
In-Reply-To: <alpine.DEB.2.20.1711281025210.3443@hadrien>
>> 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.
The concerns can vary as contributors and changes are different.
How would you like to “address” the data structure for a default allocation
failure report finally?
Regards,
Markus
next prev parent reply other threads:[~2017-11-28 9:56 UTC|newest]
Thread overview: 80+ 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-26 18:55 ` SF Markus Elfring
2017-11-26 18:55 ` SF Markus Elfring
2017-11-27 16:43 ` Andrew F. Davis
2017-11-27 16:43 ` Andrew F. Davis
2017-11-27 16:43 ` Andrew F. Davis
2017-11-27 17:27 ` SF Markus Elfring
2017-11-27 17:27 ` SF Markus Elfring
2017-11-27 17:27 ` SF Markus Elfring
2017-11-27 17:44 ` Ladislav Michl
2017-11-27 17:44 ` Ladislav Michl
2017-11-27 17:44 ` Ladislav Michl
2017-11-27 18:12 ` SF Markus Elfring
2017-11-27 18:12 ` SF Markus Elfring
2017-11-27 18:12 ` SF Markus Elfring
2017-11-27 18:56 ` Geert Uytterhoeven
2017-11-27 18:56 ` Geert Uytterhoeven
2017-11-27 18:56 ` Geert Uytterhoeven
2017-11-27 19:22 ` Ladislav Michl
2017-11-27 19:22 ` Ladislav Michl
2017-11-27 22:20 ` Ladislav Michl
2017-11-27 22:20 ` Ladislav Michl
2017-11-27 19:07 ` [PATCH] " Joe Perches
2017-11-27 19:07 ` Joe Perches
2017-11-27 21:33 ` Andrew F. Davis
2017-11-27 21:33 ` Andrew F. Davis
2017-11-27 21:33 ` Andrew F. Davis
2017-11-27 21:45 ` Ladislav Michl
2017-11-27 21:45 ` Ladislav Michl
2017-11-27 21:48 ` SF Markus Elfring
2017-11-27 21:48 ` SF Markus Elfring
2017-11-27 21:48 ` SF Markus Elfring
2017-11-27 21:48 ` SF Markus Elfring
2017-11-28 1:45 ` Joe Perches
2017-11-28 1:45 ` Joe Perches
2017-11-28 1:45 ` Joe Perches
2017-11-28 7:41 ` SF Markus Elfring
2017-11-28 7:41 ` SF Markus Elfring
2017-11-28 7:41 ` SF Markus Elfring
2017-11-28 7:49 ` Julia Lawall
2017-11-28 7:49 ` Julia Lawall
2017-11-28 8:49 ` SF Markus Elfring
2017-11-28 8:49 ` SF Markus Elfring
2017-11-28 9:26 ` Julia Lawall
2017-11-28 9:26 ` Julia Lawall
2017-11-28 9:26 ` Julia Lawall
2017-11-28 9:56 ` SF Markus Elfring [this message]
2017-11-28 9:56 ` SF Markus Elfring
2017-11-28 9:56 ` SF Markus Elfring
2017-11-28 8:04 ` Joe Perches
2017-11-28 8:04 ` Joe Perches
2017-11-28 8:49 ` Ladislav Michl
2017-11-28 8:49 ` Ladislav Michl
2017-11-28 9:11 ` SF Markus Elfring
2017-11-28 9:11 ` SF Markus Elfring
2017-11-28 9:11 ` SF Markus Elfring
2017-11-28 9:28 ` Julia Lawall
2017-11-28 9:28 ` Julia Lawall
2017-11-28 9:28 ` Julia Lawall
2017-11-28 10:15 ` SF Markus Elfring
2017-11-28 10:15 ` SF Markus Elfring
2017-11-28 10:23 ` Ladislav Michl
2017-11-28 10:23 ` Ladislav Michl
2017-11-28 10:50 ` SF Markus Elfring
2017-11-28 10:50 ` SF Markus Elfring
2017-11-28 10:50 ` SF Markus Elfring
2017-11-28 11:41 ` Ladislav Michl
2017-11-28 11:41 ` Ladislav Michl
2017-11-28 12:13 ` SF Markus Elfring
2017-11-28 12:13 ` SF Markus Elfring
2017-11-28 12:13 ` SF Markus Elfring
2017-11-28 17:50 ` Ladislav Michl
2017-11-28 17:50 ` Ladislav Michl
2017-11-28 18:09 ` SF Markus Elfring
2017-11-28 18:09 ` SF Markus Elfring
2017-11-28 18:09 ` SF Markus Elfring
2017-11-28 14:36 ` Joe Perches
2017-11-28 14:36 ` Joe Perches
2017-12-03 18:20 ` SF Markus Elfring
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=62306606-9e30-d33d-d059-07fdcdbaae92@users.sourceforge.net \
--to=elfring@users.sourceforge.net \
--cc=afd@ti.com \
--cc=arvind.yadav.cs@gmail.com \
--cc=b.zolnierkie@samsung.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=joe@perches.com \
--cc=julia.lawall@lip6.fr \
--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 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.