qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Andrew Randrianasulu <randrianasulu@gmail.com>
Cc: BALATON Zoltan <balaton@eik.bme.hu>,
	"qemu-ppc@nongnu.org" <qemu-ppc@nongnu.org>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCH v2] Re-applying Freescale PPC E500 i2c/RTC patch
Date: Wed, 6 Mar 2019 11:53:01 +1100	[thread overview]
Message-ID: <20190306005301.GG19715@umbus.fritz.box> (raw)
In-Reply-To: <201903041326.28249.randrianasulu@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 4881 bytes --]

On Mon, Mar 04, 2019 at 01:26:27PM +0300, Andrew Randrianasulu wrote:
> В сообщении от Monday 04 March 2019 05:51:27 BALATON Zoltan написал(а):
> > On Mon, 4 Mar 2019, Andrew Randrianasulu wrote:
> > > From: Amit Singh Tomar <amit.tomar@freescale.com>
> > >
> > > Original commit message:
> > > This patch adds an emulation model for i2c controller found on most of the FSL SoCs.
> > > It also integrates the RTC (ds1338) that sits on the i2c Bus with e500 machine model.
> > >
> > > Patch was originally written by Amit Singh Tomar <amit.tomar@freescale.com>
> > > see http://patchwork.ozlabs.org/patch/431475/
> > > I only fixed it enough for application on top of current qemu master
> > > 20b084c4b1401b7f8fbc385649d48c67b6f43d44, and hopefully fixed checkpatch errors
> > >
> > > Tested by booting Linux kernel 4.20.12. Now e500 machine doesn't need
> > > network time protocol daemon because it will have working RTC
> > > (before all timestamps on files were from 2016)
> > >
> > > ---
> > >
> > > v1->v2: Expanded and fixed commit message
> > >
> > >
> > > Signed-off-by: Andrew Randrianasulu <randrianasulu@gmail.com>
> > > ---
> > 
> > Almost... Patch now applies but subject and commit message are not yet 
> > right. Look at existing commit messages for examples how it should look 
> > (e.g. git log hw/ppc/e500.c). The email subject will become commit title, 
> > this should start with something showing which part you change like e500:. 
> > Then one line summary of what the patch is doing. You can probably keep 
> > original title, no need to say re-applying or things like that there. You 
> > can explain this in patch body. The text up to the first --- will be the 
> > body of the commit message so you should describe in more detail what the 
> > patch does here. Also this should include all Signed-off-by and other 
> > tags at the end before the ---.
> > 
> > Everything after --- are additional comments that won't be included in the 
> > commit message so you can put version history or any other remarks there 
> > that should not be kept after applying the patch.
> > 
> > This patch is missing Signed-off-by of the original author and has yours 
> > below --- that's why checkpatch complains. You should keep the the 
> > original Signed-off-by even if you add From: of the original author. I 
> > think you may not include From: since you're not forwarding a patch 
> > unchanged but this is now your patch based on the original since you've 
> > changed it so it can have your From: address from email header and 
> > Signed-off-by of both original author and yours to show where it came from 
> > originally. You can also mention this in commit message to make it clear.
> > 
> > Or you can keep From of original author and explain in commit message what 
> > you've changed but it still needs both Signed-off-by lines even then.
> > 
> > Hopefully this makes sense. This should already be explained in the 
> > SubmitAPatch wiki page but that can be complicated at first.
> 
> Thanks for explaining all this.
> Right now top of my patch looks like this:
> 
> From ad2b4baf8b369c8ef354e56f75ae780413acd989 Mon Sep 17 00:00:00 2001
> From: Andrew Randrianasulu <randrianasulu@gmail.com>
> Date: Sun, 3 Mar 2019 00:05:04 +0300
> Subject: [PATCH v3] PPC: E500: Add FSL I2C controller and integrate RTC with it
> 
> Original commit message:
> This patch adds an emulation model for i2c controller found on most of the FSL SoCs.
> It also integrates the RTC (ds1338) that sits on the i2c Bus with e500 machine model.
> 
> Patch was originally written by Amit Singh Tomar <amit.tomar@freescale.com>
> see http://patchwork.ozlabs.org/patch/431475/
> I only fixed it enough for application on top of current qemu master
> 20b084c4b1401b7f8fbc385649d48c67b6f43d44, and hopefully fixed checkpatch errors
> 
> Tested by booting Linux kernel 4.20.12. Now e500 machine doesn't need.
> network time protocol daemon because it will have working RTC.
> (before all timestamps on files were from 2016)
> 
> 
> Signed-off-by: Amit Singh Tomar <amit.tomar@freescale.com>
> Signed-off-by: Andrew Randrianasulu <randrianasulu@gmail.com>
> ---
> 
> v1->v2: Expanded and fixed commit message
> 
> v2->v3: Changed Subject line back to original and From: field to.
> my email address, moved my SoB line above first '---' and
> added Tomar's Signed-off line back.
> 
> ---
> 
> is it OK ok to send? (assuming it applies, compiles and boots, I test this now
> with git am, make and launching qemu with -kernel option.)

That looks good, please go ahead and send.

-- 
David Gibson			| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you.  NOT _the_ _other_
				| _way_ _around_!
http://www.ozlabs.org/~dgibson

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2019-03-06  0:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-04  1:54 [Qemu-devel] [PATCH v2] Re-applying Freescale PPC E500 i2c/RTC patch Andrew Randrianasulu
2019-03-04  2:01 ` no-reply
2019-03-04  2:51 ` [Qemu-devel] [Qemu-ppc] " BALATON Zoltan
2019-03-04 10:26   ` Andrew Randrianasulu
2019-03-06  0:53     ` David Gibson [this message]

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=20190306005301.GG19715@umbus.fritz.box \
    --to=david@gibson.dropbear.id.au \
    --cc=balaton@eik.bme.hu \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    --cc=randrianasulu@gmail.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).