From: "Linus Torvalds via RT" <kernel-helpdesk@rt.linuxfoundation.org>
To: rdunlap@infradead.org
Cc: linux-kernel@vger.kernel.org
Subject: [Kernel.org Helpdesk #46182] [linuxfoundation.org #46182] Re: Linux 4.14-rc2 (bad patch file on kernel.org)
Date: Sun, 24 Sep 2017 23:41:33 -0400 [thread overview]
Message-ID: <rt-4.4.0-6213-1506310893-1455.46182-6-0@linuxfoundation> (raw)
In-Reply-To: <CA+55aFyushnyoKZi+E-BEZX94S_7HGmXiwrAmfCPUNyYZxfyzQ@mail.gmail.com>
On Sun, Sep 24, 2017 at 7:57 PM, Randy Dunlap <rdunlap@infradead.org> wrote:
>
> 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:
Hmm. The rc patches are automatically generated from the git tree
these days, so I don't have control over them.
It does sound like you might have caught it while it was being generated:
> patch unexpectedly ends in middle of line
> patch: **** unexpected end of file in patch
which would seem to indicate that maybe you just caught it while it
was still being generated.
But I just tried it myself, and get the same breakage. In fact, the
patch it downloads is exactly 50397184 bytes in size. That may not
sound like a round number, but it is: it is hex 0x3010000, so it's
evenly divisible by 65536.
Methinks there's some incorrect flushing of block IO going on. Konstantin?
> I also notice that the [pgp] signing is not there. Is that normal?
So I don't sign the rc patches any more because I don't generate them
(but the final release patches and tar-balls I *do* sign).
But maybe they could be signed by some kernel.org key.
Again, that would be an automation issue..
Linus
next prev parent reply other threads:[~2017-09-25 3:50 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 ` Linux 4.14-rc2 (bad patch file on kernel.org) Randy Dunlap
2017-09-25 3:41 ` Linus Torvalds
2017-09-25 3:41 ` Linus Torvalds via RT [this message]
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=rt-4.4.0-6213-1506310893-1455.46182-6-0@linuxfoundation \
--to=kernel-helpdesk@rt.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.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®