public inbox for linux-arch@vger.kernel.org
 help / color / mirror / Atom feed
From: Christian Borntraeger <borntraeger-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org>
To: Linus Torvalds
	<torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
Cc: akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org,
	avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org,
	dwmw2-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org,
	linux-arch-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	sam-uyr5N9Q2VtJg9hUCZPvPmw@public.gmane.org
Subject: Re: [patch 06/24] kvm: provide kvm.h for all architecture: fixes headers_install
Date: Fri, 28 Mar 2008 22:51:34 +0100	[thread overview]
Message-ID: <200803282251.34635.borntraeger@de.ibm.com> (raw)
In-Reply-To: <alpine.LFD.1.00.0803281435090.14670-5CScLwifNT1QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>

Am Freitag, 28. März 2008 schrieb Linus Torvalds:
> That makes no sense. Commit 040922c04cf2c8ac70be2e88a8a9614ecdb41d2e is 
> "include falloc.h in header-y", and seems to have nothing to do with 
> kvm.h.
[...]
> So please - add the one-liner to all SHA1 ones, so that non-git people see 
> what it is all about, and so that people who just read the commit log can 
> make sense of it. And in trying to make sense of it, it can become obvious 
> that it doesn't actually make any sense!

Sorry, you are right. The proper commit is 
fb56dbb31c4738a3918db81fd24da732ce3b4ae6 (KVM: Export include/linux/kvm.h 
only if $ARCH actually supports KVM) and I have clue at all, why I wrote 
the wrong SHA1 id. Sorry, I will double check the next time and also add 
the description.

Christian

WARNING: multiple messages have this Message-ID (diff)
From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: akpm@linux-foundation.org, avi@qumranet.com, dwmw2@infradead.org,
	linux-arch@vger.kernel.org, sam@ravnborg.org
Subject: Re: [patch 06/24] kvm: provide kvm.h for all architecture: fixes headers_install
Date: Fri, 28 Mar 2008 22:51:34 +0100	[thread overview]
Message-ID: <200803282251.34635.borntraeger@de.ibm.com> (raw)
Message-ID: <20080328215134._zE0HEmHqJqGkxwC8mcySZlGWcn4odRow9yPehPpN10@z> (raw)
In-Reply-To: <alpine.LFD.1.00.0803281435090.14670@woody.linux-foundation.org>

Am Freitag, 28. März 2008 schrieb Linus Torvalds:
> That makes no sense. Commit 040922c04cf2c8ac70be2e88a8a9614ecdb41d2e is 
> "include falloc.h in header-y", and seems to have nothing to do with 
> kvm.h.
[...]
> So please - add the one-liner to all SHA1 ones, so that non-git people see 
> what it is all about, and so that people who just read the commit log can 
> make sense of it. And in trying to make sense of it, it can become obvious 
> that it doesn't actually make any sense!

Sorry, you are right. The proper commit is 
fb56dbb31c4738a3918db81fd24da732ce3b4ae6 (KVM: Export include/linux/kvm.h 
only if $ARCH actually supports KVM) and I have clue at all, why I wrote 
the wrong SHA1 id. Sorry, I will double check the next time and also add 
the description.

Christian

  parent reply	other threads:[~2008-03-28 21:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-28 21:15 [patch 06/24] kvm: provide kvm.h for all architecture: fixes headers_install akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b
2008-03-28 21:15 ` akpm
     [not found] ` <200803282115.m2SLFscm010265-AB4EexQrvXRQetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>
2008-03-28 21:40   ` Linus Torvalds
2008-03-28 21:40     ` Linus Torvalds
     [not found]     ` <alpine.LFD.1.00.0803281435090.14670-5CScLwifNT1QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>
2008-03-28 21:51       ` Christian Borntraeger [this message]
2008-03-28 21:51         ` Christian Borntraeger

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=200803282251.34635.borntraeger@de.ibm.com \
    --to=borntraeger-ta70fqpds9bqt0dzr+alfa@public.gmane.org \
    --cc=akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org \
    --cc=avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org \
    --cc=dwmw2-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org \
    --cc=linux-arch-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=sam-uyr5N9Q2VtJg9hUCZPvPmw@public.gmane.org \
    --cc=torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.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