* Re: Intel-gfx Digest, Vol 86, Issue 409
[not found] <mailman.6618.1427399059.3171.intel-gfx@lists.freedesktop.org>
@ 2015-04-18 5:01 ` Ben Widawsky
2015-04-20 16:16 ` Daniel Vetter
0 siblings, 1 reply; 3+ messages in thread
From: Ben Widawsky @ 2015-04-18 5:01 UTC (permalink / raw)
To: yu.dai, intel-gfx; +Cc: vinit.azad
On Thu, Mar 26, 2015 at 12:44:19PM -0700, intel-gfx-request@lists.freedesktop.org wrote:
> Send Intel-gfx mailing list submissions to
> intel-gfx@lists.freedesktop.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
> or, via email, send a message with subject or body 'help' to
> intel-gfx-request@lists.freedesktop.org
>
> You can reach the person managing the list at
> intel-gfx-owner@lists.freedesktop.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Intel-gfx digest..."
>
>
> Today's Topics:
>
> 1. [PATCH 04/18] drm/i915: GuC firmware loader (yu.dai@intel.com)
> 2. [PATCH 05/18] drm/i915: Add firmware version check
> (yu.dai@intel.com)
> 3. [PATCH 06/18] drm/i915: Defer default hardware context
> initialisation until first open (yu.dai@intel.com)
There is a lot of work here from both Vinit and myself in these patches, and
removing my authorship and the notes I made about Vinit's important
contributions are not appropriate in all the cases. Our SOBs should be retained
on several of the GuC patches, and authorship should be retained where
appropriate.
If you've written a majority of the patch, or vastly changed how the code works,
then you should change authorship.
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Intel-gfx Digest, Vol 86, Issue 409
2015-04-18 5:01 ` Intel-gfx Digest, Vol 86, Issue 409 Ben Widawsky
@ 2015-04-20 16:16 ` Daniel Vetter
2015-04-20 16:29 ` Yu Dai
0 siblings, 1 reply; 3+ messages in thread
From: Daniel Vetter @ 2015-04-20 16:16 UTC (permalink / raw)
To: Ben Widawsky; +Cc: vinit.azad, intel-gfx
On Fri, Apr 17, 2015 at 10:01:11PM -0700, Ben Widawsky wrote:
> On Thu, Mar 26, 2015 at 12:44:19PM -0700, intel-gfx-request@lists.freedesktop.org wrote:
> > Send Intel-gfx mailing list submissions to
> > intel-gfx@lists.freedesktop.org
> >
> > To subscribe or unsubscribe via the World Wide Web, visit
> > http://lists.freedesktop.org/mailman/listinfo/intel-gfx
> > or, via email, send a message with subject or body 'help' to
> > intel-gfx-request@lists.freedesktop.org
> >
> > You can reach the person managing the list at
> > intel-gfx-owner@lists.freedesktop.org
> >
> > When replying, please edit your Subject line so it is more specific
> > than "Re: Contents of Intel-gfx digest..."
> >
> >
> > Today's Topics:
> >
> > 1. [PATCH 04/18] drm/i915: GuC firmware loader (yu.dai@intel.com)
> > 2. [PATCH 05/18] drm/i915: Add firmware version check
> > (yu.dai@intel.com)
> > 3. [PATCH 06/18] drm/i915: Defer default hardware context
> > initialisation until first open (yu.dai@intel.com)
>
> There is a lot of work here from both Vinit and myself in these patches, and
> removing my authorship and the notes I made about Vinit's important
> contributions are not appropriate in all the cases. Our SOBs should be retained
> on several of the GuC patches, and authorship should be retained where
> appropriate.
>
> If you've written a majority of the patch, or vastly changed how the code works,
> then you should change authorship.
And even when the patches are completely rewritten please retain a note
along the lines of "based upon patches from $original_author". Yes I've
recently complained about retaining the original authorship when the patch
is completely rewritten, but removing all trails of the patch's history
isn't the right thing either. Acknowledging other people's contributions
is important.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Intel-gfx Digest, Vol 86, Issue 409
2015-04-20 16:16 ` Daniel Vetter
@ 2015-04-20 16:29 ` Yu Dai
0 siblings, 0 replies; 3+ messages in thread
From: Yu Dai @ 2015-04-20 16:29 UTC (permalink / raw)
To: Daniel Vetter, Ben Widawsky; +Cc: vinit.azad, intel-gfx
On 04/20/2015 09:16 AM, Daniel Vetter wrote:
> On Fri, Apr 17, 2015 at 10:01:11PM -0700, Ben Widawsky wrote:
> > On Thu, Mar 26, 2015 at 12:44:19PM -0700, intel-gfx-request@lists.freedesktop.org wrote:
> > > Send Intel-gfx mailing list submissions to
> > > intel-gfx@lists.freedesktop.org
> > >
> > > To subscribe or unsubscribe via the World Wide Web, visit
> > > http://lists.freedesktop.org/mailman/listinfo/intel-gfx
> > > or, via email, send a message with subject or body 'help' to
> > > intel-gfx-request@lists.freedesktop.org
> > >
> > > You can reach the person managing the list at
> > > intel-gfx-owner@lists.freedesktop.org
> > >
> > > When replying, please edit your Subject line so it is more specific
> > > than "Re: Contents of Intel-gfx digest..."
> > >
> > >
> > > Today's Topics:
> > >
> > > 1. [PATCH 04/18] drm/i915: GuC firmware loader (yu.dai@intel.com)
> > > 2. [PATCH 05/18] drm/i915: Add firmware version check
> > > (yu.dai@intel.com)
> > > 3. [PATCH 06/18] drm/i915: Defer default hardware context
> > > initialisation until first open (yu.dai@intel.com)
> >
> > There is a lot of work here from both Vinit and myself in these patches, and
> > removing my authorship and the notes I made about Vinit's important
> > contributions are not appropriate in all the cases. Our SOBs should be retained
> > on several of the GuC patches, and authorship should be retained where
> > appropriate.
> >
> > If you've written a majority of the patch, or vastly changed how the code works,
> > then you should change authorship.
>
> And even when the patches are completely rewritten please retain a note
> along the lines of "based upon patches from $original_author". Yes I've
> recently complained about retaining the original authorship when the patch
> is completely rewritten, but removing all trails of the patch's history
> isn't the right thing either. Acknowledging other people's contributions
> is important.
> -Daniel
Totally agree. Thanks Ben and Daniel. The authors information will be
shown either in file header or commit message in next submission.
Thanks,
Alex
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2015-04-20 16:30 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <mailman.6618.1427399059.3171.intel-gfx@lists.freedesktop.org>
2015-04-18 5:01 ` Intel-gfx Digest, Vol 86, Issue 409 Ben Widawsky
2015-04-20 16:16 ` Daniel Vetter
2015-04-20 16:29 ` Yu Dai
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox