From: Randy Dunlap <rdunlap@infradead.org>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
helpdesk@kernel.org
Subject: Re: Linux 4.14-rc2 (bad patch file on kernel.org)
Date: Sun, 24 Sep 2017 19:57:25 -0700 [thread overview]
Message-ID: <b2cda80f-fea1-aad0-24eb-ae925e517d70@infradead.org> (raw)
In-Reply-To: <CA+55aFxk1SGj+s+P==3aydk56kejXUiB-O+orp=EbTByTyFL0A@mail.gmail.com>
On 09/24/17 17:03, Linus Torvalds wrote:
> I'm back to my usual Sunday release schedule, and rc2 is out there in
> all the normal places.
Downloading & applying 4.14-rc2 [patch] <https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/rawdiff/?id=v4.14-rc2&id2=v4.13>
from kernel.org (home page) gives me a file that does not apply cleanly to v4.13:
--------------------------
|diff --git a/virt/kvm/kvm_main.c b/virt/kvm/kvm_main.c
|index 4d81f6d..9deb5a2 100644
|--- a/virt/kvm/kvm_main.c
|+++ b/virt/kvm/kvm_main.c
--------------------------
checking file virt/kvm/kvm_main.c
Using Plan A...
patch unexpectedly ends in middle of line
patch: **** unexpected end of file in patch
I also notice that the [pgp] signing is not there. Is that normal?
thanks,
--
~Randy
next prev parent reply other threads:[~2017-09-25 2:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <RT-Ticket-46182@linuxfoundation>
2017-09-25 0:03 ` Linux 4.14-rc2 Linus Torvalds
2017-09-25 2:57 ` Randy Dunlap [this message]
2017-09-25 3:41 ` Linux 4.14-rc2 (bad patch file on kernel.org) Linus Torvalds
2017-09-25 3:41 ` [Kernel.org Helpdesk #46182] [linuxfoundation.org #46182] " Linus Torvalds via RT
2017-09-25 3:43 ` Linus Torvalds
2017-09-25 3:43 ` [Kernel.org Helpdesk #46182] [linuxfoundation.org #46182] " Linus Torvalds via RT
2017-10-15 6:58 ` Pavel Machek
2017-10-15 21:59 ` [Kernel.org Helpdesk #46182] [linuxfoundation.org #46182] " Pavel Machek via RT
2017-09-25 13:16 ` [Kernel.org Helpdesk " Konstantin Ryabitsev via RT
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=b2cda80f-fea1-aad0-24eb-ae925e517d70@infradead.org \
--to=rdunlap@infradead.org \
--cc=helpdesk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®