From: Randy Dunlap <rdunlap@xenotime.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
linux-kernel@vger.kernel.org, ian.campbell@citrix.com,
JBeulich@suse.com, annie.li@oracle.com, waldi@debian.org,
dgdegra@tycho.nsa.gov, david.vrabel@citrix.com, julia@diku.dk,
tony.luck@intel.com, maxim.uvarov@oracle.com, anil@recoil.org,
dkiper@net-space.pl, Jeremy Fitzhardinge <jeremy@goop.org>
Subject: Re: [GIT PULL] (xen) stable/for-linus-3.3 patches for 3.3-rc0
Date: Tue, 10 Jan 2012 11:11:20 -0800 [thread overview]
Message-ID: <4F0C8D58.6020003@xenotime.net> (raw)
In-Reply-To: <CA+55aFxbnPstMx9Bajcq8cen7vpY_yOoGE86GG_Fu_ZUpL2zXg@mail.gmail.com>
On 01/10/2012 10:08 AM, Linus Torvalds wrote:
> On Mon, Jan 9, 2012 at 9:25 AM, Konrad Rzeszutek Wilk
> <konrad.wilk@oracle.com> wrote:
>> 46 files changed, 2499 insertions(+), 1251 deletions(-)
>
> Please, you too also start using -M (and --summary) for the diffstat output.
This is even included in Documentation/SubmittingPatches (not that anyone reads
documentation ;).
> It should look like this:
>
> 44 files changed, 1513 insertions(+), 265 deletions(-)
> create mode 100644 Documentation/ABI/stable/sysfs-bus-xen-backend
> create mode 100644 Documentation/ABI/stable/sysfs-devices-system-xen_memory
> rename drivers/xen/{xenfs => }/privcmd.c (92%)
> create mode 100644 drivers/xen/privcmd.h
> create mode 100644 drivers/xen/xenbus/xenbus_dev_backend.c
> rename drivers/xen/{xenfs/xenbus.c => xenbus/xenbus_dev_frontend.c} (95%)
> create mode 100644 include/xen/xenbus_dev.h
>
> which is a lot more true about the *real* changes.
--
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
prev parent reply other threads:[~2012-01-10 18:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-09 17:25 [GIT PULL] (xen) stable/for-linus-3.3 patches for 3.3-rc0 Konrad Rzeszutek Wilk
2012-01-10 18:08 ` Linus Torvalds
2012-01-10 19:11 ` Randy Dunlap [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=4F0C8D58.6020003@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=JBeulich@suse.com \
--cc=anil@recoil.org \
--cc=annie.li@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=dgdegra@tycho.nsa.gov \
--cc=dkiper@net-space.pl \
--cc=ian.campbell@citrix.com \
--cc=jeremy@goop.org \
--cc=julia@diku.dk \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maxim.uvarov@oracle.com \
--cc=tony.luck@intel.com \
--cc=torvalds@linux-foundation.org \
--cc=waldi@debian.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.