From: "Jarkko Sakkinen" <jarkko@kernel.org>
To: "Linus Torvalds" <torvalds@linux-foundation.org>
Cc: "Peter Huewe" <peterhuewe@gmx.de>,
"Jason Gunthorpe" <jgg@ziepe.ca>,
"Lino Sanfilippo" <l.sanfilippo@kunbus.com>,
<linux-integrity@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] tpmdd changes for v6.5-rc2
Date: Mon, 17 Jul 2023 14:32:43 +0000 [thread overview]
Message-ID: <CU4IRD6Z82AN.1NSKWR27ODX5I@seitikki> (raw)
In-Reply-To: <CAHk-=wg6Gv+zbBt7RLN43KD0BaegS=SYkwaHjd_YM5BDsvS08w@mail.gmail.com>
On Sun Jul 16, 2023 at 7:11 PM UTC, Linus Torvalds wrote:
> On Fri, 14 Jul 2023 at 11:14, Jarkko Sakkinen <jarkko@kernel.org> wrote:
> >
> > are available in the Git repository at:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/jarkko/linux-tpmdd.git/ tpmdd-v6.5-rc2-fixed
>
> No, that still isn't a valid git repo path.
>
> This all also looks like it should have come in during the merge
> window, so I'm just going to ignore it.
>
> Feel free to send in actual fixes - not this massive update - once you
> have fixed your workflow.
>
> But don't even bother emailing me until you have actually *verified*
> what the heck you are sending me.
>
> No more broken script garbage. No more untested git pull requests that
> don't actually work.
>
> Linus
NP, I'll cut down the pr, and fix the issues.
BR, Jarkko
next prev parent reply other threads:[~2023-07-17 14:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-14 18:13 [GIT PULL] tpmdd changes for v6.5-rc2 Jarkko Sakkinen
2023-07-16 19:11 ` Linus Torvalds
2023-07-17 14:32 ` Jarkko Sakkinen [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-07-14 11:58 Jarkko Sakkinen
2023-07-14 16:21 ` Linus Torvalds
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=CU4IRD6Z82AN.1NSKWR27ODX5I@seitikki \
--to=jarkko@kernel.org \
--cc=jgg@ziepe.ca \
--cc=l.sanfilippo@kunbus.com \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterhuewe@gmx.de \
--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