qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Gavin Shan <gwshan@linux.vnet.ibm.com>
Cc: Alexey Kardashevskiy <aik@ozlabs.ru>,
	Peter Maydell <peter.maydell@linaro.org>,
	"qemu-ppc@nongnu.org" <qemu-ppc@nongnu.org>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v4 1/3] linux-headers: Add eeh.h
Date: Thu, 13 Aug 2015 11:42:59 +1000	[thread overview]
Message-ID: <20150813014259.GB7910@voom.redhat.com> (raw)
In-Reply-To: <20150813013037.GA9791@gwshan>

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

On Thu, Aug 13, 2015 at 11:30:37AM +1000, Gavin Shan wrote:
> On Wed, Aug 12, 2015 at 12:00:35PM +1000, Alexey Kardashevskiy wrote:
> >On 08/11/2015 07:11 PM, Peter Maydell wrote:
> >>On 10 August 2015 at 08:13, Gavin Shan <gwshan@linux.vnet.ibm.com> wrote:
> >>>The header file was introduced by following Linux upstream commits:
> >>>
> >>>     commit ed3e81f ("powerpc/eeh: Move PE state constants around")
> >>>     commit ec33d36 ("powerpc/eeh: Introduce eeh_pe_inject_err()")
> >>>
> >>>Signed-off-by: Gavin Shan <gwshan@linux.vnet.ibm.com>
> >>>---
> >>>  linux-headers/asm-powerpc/eeh.h | 56 +++++++++++++++++++++++++++++++++++++++++
> >>>  1 file changed, 56 insertions(+)
> >>>  create mode 100644 linux-headers/asm-powerpc/eeh.h
> >>
> >>Shouldn't this be added by updating scripts/update-linux-headers.sh
> >>and then doing a plain "synchronize headers against kernel version $X" ?
> >
> >
> >I also thought this is the protocol but then I looked into the git history
> >and discovered this is not always the case :)
> >
> >
> 
> So should I use scripts/update-linux-headers.sh or what I had is
> fine?

Please use update-linux-headers.sh - and make sure you also update the
script itself (if necessary) so it will pull in future updates to
eeh.h

-- 
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: Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2015-08-13  1:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-10  7:13 [Qemu-devel] [PATCH v4 0/3] sPAPR: Support EEH Error Injection Gavin Shan
2015-08-10  7:13 ` [Qemu-devel] [PATCH v4 1/3] linux-headers: Add eeh.h Gavin Shan
2015-08-11  9:11   ` Peter Maydell
2015-08-12  1:55     ` David Gibson
2015-08-12  2:00     ` Alexey Kardashevskiy
2015-08-13  1:30       ` Gavin Shan
2015-08-13  1:42         ` David Gibson [this message]
2015-08-14  1:10           ` Gavin Shan
2015-08-24  7:23     ` Gavin Shan
2015-08-24 12:00       ` Gavin Shan
2015-08-10  7:13 ` [Qemu-devel] [PATCH v4 2/3] sPAPR: Support RTAS call ibm, {open, close}-errinjct Gavin Shan
2015-08-10  7:13 ` [Qemu-devel] [PATCH v4 3/3] sPAPR: Support RTAS call ibm,errinjct Gavin Shan

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=20150813014259.GB7910@voom.redhat.com \
    --to=david@gibson.dropbear.id.au \
    --cc=aik@ozlabs.ru \
    --cc=gwshan@linux.vnet.ibm.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    /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).