From: Linus Torvalds <torvalds@linux-foundation.org>
To: David Howells <dhowells@redhat.com>
Cc: "Gustavo A. R. Silva" <gustavo@embeddedor.com>,
Marc Dionne <marc.dionne@auristor.com>,
linux-afs@lists.infradead.org,
Linux List Kernel Mailing <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/6] AFS fixes
Date: Fri, 18 Jan 2019 06:31:31 +1200 [thread overview]
Message-ID: <CAHk-=whSXM3YgJfRwuWtP0BS9jiUvdYM-xmCUw1PjMO=DtKm0g@mail.gmail.com> (raw)
In-Reply-To: <CAHk-=wgM+h9K-MdyOAjonMchJViy-7stCKHqn0vMgitKDmpVbQ@mail.gmail.com>
On Fri, Jan 18, 2019 at 6:29 AM Linus Torvalds
<torvalds@linux-foundation.org> wrote:
>
> > http://git.kernel.org/cgit/linux/kernel/git/dhowells/linux-fs.git
> > tag afs-fixes-20190117
>
> is not valid pull address.. Yes, I can fix up the thing (and have
> done so), but a normal git pull-request wouldn't have had that issue.
Side note: I suspect that also means that this won't get an automated
pr-tracker reply now that I've pulled it. But maybe pr-tracker ends up
being very permissive.. We'll see.
Linus
next prev parent reply other threads:[~2019-01-17 18:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-17 15:27 [PATCH 0/6] AFS fixes David Howells
2019-01-17 15:27 ` [PATCH 1/6] afs: Use struct_size() in kzalloc() David Howells
2019-01-17 15:27 ` [PATCH 2/6] afs: Set correct lock type for the yfs CreateFile David Howells
2019-01-17 15:27 ` [PATCH 3/6] afs: Don't set vnode->cb_s_break in afs_validate() David Howells
2019-01-17 15:27 ` [PATCH 4/6] afs: Fix key refcounting in file locking code David Howells
2019-01-17 15:28 ` [PATCH 5/6] afs: Provide a function to get a ref on a call David Howells
2019-01-17 15:28 ` [PATCH 6/6] afs: Fix race in async call refcounting David Howells
2019-01-17 18:29 ` [PATCH 0/6] AFS fixes Linus Torvalds
2019-01-17 18:31 ` Linus Torvalds [this message]
2020-06-09 16:13 [PATCH 0/6] afs: Fixes David Howells
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-=whSXM3YgJfRwuWtP0BS9jiUvdYM-xmCUw1PjMO=DtKm0g@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=gustavo@embeddedor.com \
--cc=linux-afs@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.dionne@auristor.com \
/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;
as well as URLs for NNTP newsgroup(s).