[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH v2 5/5] bcm2835_dma: add emulation of Raspberry
Re: [Qemu-devel] [PATCH v2 5/5] bcm2835_dma: add emulation of Raspberry Pi DMA controller
Tue, 8 Mar 2016 12:48:00 +0700
On 8 March 2016 at 12:23, Andrew Baumann <address@hidden> wrote:
>> From: Peter Maydell [mailto:address@hidden
>> Sent: Monday, 7 March 2016 8:37 PM
>> On 4 March 2016 at 01:24, Andrew Baumann
>> <address@hidden> wrote:
>> > At present, all DMA transfers complete inline (so a looping descriptor
>> > queue will lock up the device). We also do not model pause/abort,
>> > arbitrarion/priority, or debug features.
>> > Signed-off-by: Andrew Baumann <address@hidden>
>> > ---
>> Reviewed-by: Peter Maydell <address@hidden>
>> Can you add Gregory's Signed-off-by (and authorship from?) to whichever
>> patches are appropriate when you resend (as per discussion on the
>> earlier version of this patch)?
> Yes, happily. But what's the best way to capture this when the code we're
> committing is a mixture of code from Gregory and Stefan (via a manual patch
> into Stefan's ar7 repo, so much of that history is lost to me) that I've
> then extended and refactored? I know what I added (e.g. aux), but for the
> files with joint authorship (fb, dma) should we just put Gregory as the
> author on those patches with a signed-off-by from me? Can I also add a
> signed-off-by on behalf of Gregory, or does he need to do it?
Gregory said an s-o-by from him was OK in the mail thread, so that's
sufficient for you to be able to add it.
The usual approach for multiple authors is that you have the author
be the original or major author, and then the signed-off-by section
Signed-off-by: Original Author <address@hidden>
[XYZ: changed foo, bar, baz]
Signed-off-by: XY Zed <address@hidden>
which preserves credit for the original author's work and also a
record of what changes have been made by the next person in the
If you search in 'git log' for "[PMM" you'll find a bunch of examples
of when I've done it in the past, eg commit f0c02d15b57da6.
(Overall there are two aspects to the signoff lines:
a: the legal aspect, where you're agreeing to the stuff in the
Developer's Certificate of Origin; one of the options in there
is "this code is under an acceptable license that allows me to
contribute it", so taking some out-of-tree open source code from
somebody else, fixing it up and sending it in with just your
signoff is perfectly fine from the strict legal/traceability
point of view.
b: credit for work done. This is a social/interpersonal question,
so there aren't any hard and fast rules, but generally I find the
best approach is to ask the original authors for their preferences[*],
let them know in advance about what you're planning and err on
the side of giving them authorship and other credit rather than
yourself, while also being clear about what you've done that they
should not be blamed for.
[*] Occasionally somebody actually prefers not to be credited
via signoff because they feel they're now a long way removed from
what it was.
- [Qemu-devel] [PATCH v2 1/5] bcm2835_peripherals: enable sdhci pending-insert quirk for raspberry pi, (continued)
- [Qemu-devel] [PATCH v2 1/5] bcm2835_peripherals: enable sdhci pending-insert quirk for raspberry pi, Andrew Baumann, 2016/03/03
- [Qemu-devel] [PATCH v2 3/5] bcm2835_fb: add framebuffer device for Raspberry Pi, Andrew Baumann, 2016/03/03
- [Qemu-devel] [PATCH v2 4/5] bcm2835_property: implement framebuffer control/configuration properties, Andrew Baumann, 2016/03/03
- [Qemu-devel] [PATCH v2 2/5] bcm2835_aux: add emulation of BCM2835 AUX (aka UART1) block, Andrew Baumann, 2016/03/03
- [Qemu-devel] [PATCH v2 5/5] bcm2835_dma: add emulation of Raspberry Pi DMA controller, Andrew Baumann, 2016/03/03