From: Linus Torvalds <torvalds@linux-foundation.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: SoC Team <soc@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [GIT PULL 4/4] ARM: devicetree updates
Date: Fri, 3 Apr 2020 15:27:52 -0700 [thread overview]
Message-ID: <CAHk-=wiZHmvCmXmGNQmmwDOYXLqpg3X=-LLRZ=Yq9p6V3pSEig@mail.gmail.com> (raw)
In-Reply-To: <CAK8P3a3iGtudeWTwufBYYM29jL5b_FRkqzU2QZiQRu0B2NhyZg@mail.gmail.com>
On Fri, Apr 3, 2020 at 2:46 PM Arnd Bergmann <arnd@arndb.de> wrote:
>
> To spare you the 80kb of git-request-pull output, here is a very
> abbreviated version
So you didn't do a test-merge and generate the diffstat from that?
That's just 567 lines and about 35kB, and I get
488 files changed, 18917 insertions(+), 4522 deletions(-)
Anyway, it didn't cause any conflicts, and looks as expected for a DT
update, but I generally like to have the ability to compare to what
the sender thinks I should get..
Linus
WARNING: multiple messages have this Message-ID (diff)
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: SoC Team <soc@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [GIT PULL 4/4] ARM: devicetree updates
Date: Fri, 3 Apr 2020 15:27:52 -0700 [thread overview]
Message-ID: <CAHk-=wiZHmvCmXmGNQmmwDOYXLqpg3X=-LLRZ=Yq9p6V3pSEig@mail.gmail.com> (raw)
In-Reply-To: <CAK8P3a3iGtudeWTwufBYYM29jL5b_FRkqzU2QZiQRu0B2NhyZg@mail.gmail.com>
On Fri, Apr 3, 2020 at 2:46 PM Arnd Bergmann <arnd@arndb.de> wrote:
>
> To spare you the 80kb of git-request-pull output, here is a very
> abbreviated version
So you didn't do a test-merge and generate the diffstat from that?
That's just 567 lines and about 35kB, and I get
488 files changed, 18917 insertions(+), 4522 deletions(-)
Anyway, it didn't cause any conflicts, and looks as expected for a DT
update, but I generally like to have the ability to compare to what
the sender thinks I should get..
Linus
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-04-03 22:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-03 21:29 [GIT PULL 0/4] ARM: SoC changes for v5.7 Arnd Bergmann
2020-04-03 21:29 ` Arnd Bergmann
2020-04-03 21:32 ` [GIT PULL 1/4] ARM: SoC updates Arnd Bergmann
2020-04-03 21:32 ` Arnd Bergmann
2020-04-03 22:30 ` pr-tracker-bot
2020-04-03 21:35 ` [GIT PULL 2/4] ARM: driver updates Arnd Bergmann
2020-04-03 21:35 ` Arnd Bergmann
2020-04-03 22:30 ` pr-tracker-bot
2020-04-03 21:36 ` [GIT PULL 3/4] ARM: defconfig updates Arnd Bergmann
2020-04-03 21:36 ` Arnd Bergmann
2020-04-03 22:17 ` Linus Torvalds
2020-04-03 22:17 ` Linus Torvalds
2020-04-03 22:30 ` pr-tracker-bot
2020-04-03 21:45 ` [GIT PULL 4/4] ARM: devicetree updates Arnd Bergmann
2020-04-03 21:45 ` Arnd Bergmann
2020-04-03 22:27 ` Linus Torvalds [this message]
2020-04-03 22:27 ` Linus Torvalds
2020-04-04 10:03 ` Arnd Bergmann
2020-04-04 10:03 ` Arnd Bergmann
2020-04-03 22:30 ` pr-tracker-bot
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='CAHk-=wiZHmvCmXmGNQmmwDOYXLqpg3X=-LLRZ=Yq9p6V3pSEig@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=soc@kernel.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.