From: Al Viro <viro@zeniv.linux.org.uk>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Hans de Goede <hdegoede@redhat.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] vboxsf fixes for 5.14-1
Date: Tue, 13 Jul 2021 20:32:57 +0000 [thread overview]
Message-ID: <YO34eTRpEQKuCzpW@zeniv-ca.linux.org.uk> (raw)
In-Reply-To: <fac8ca82-8e9e-cbcf-2e68-b2b281ab0127@infradead.org>
On Tue, Jul 13, 2021 at 01:24:06PM -0700, Randy Dunlap wrote:
> Hi Al,
>
> Where would you prefer for kernel-doc changes in fs/*.[ch] be merged?
>
> E.g., from June 27:
>
> https://lore.kernel.org/linux-fsdevel/20210628014613.11296-1-rdunlap@infradead.org/
Umm... I'd been under impression that kernel-doc stuff in general goes
through akpm, TBH. I don't remember ever having a problem with your
patches of that sort; I can grab that kind of stuff, but if there's
an existing pipeline for that I'd just as well leave it there...
next prev parent reply other threads:[~2021-07-13 20:35 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-13 10:45 Hans de Goede
2021-07-13 19:15 ` Linus Torvalds
2021-07-13 20:14 ` Al Viro
2021-07-13 20:18 ` Al Viro
2021-07-13 20:24 ` Randy Dunlap
2021-07-13 20:32 ` Al Viro [this message]
2021-07-13 21:43 ` Randy Dunlap
2021-07-14 10:50 ` Rafał Miłecki
2021-07-14 14:13 ` Christoph Hellwig
2021-07-14 14:51 ` Greg KH
2021-07-14 15:59 ` Rafał Miłecki
2021-07-14 16:05 ` Matthew Wilcox
2021-07-14 16:18 ` Rafał Miłecki
2021-07-15 21:50 ` Neal Gompa
2021-07-16 11:46 ` Leonidas P. Papadakos
2021-07-16 18:07 ` Linus Torvalds
2021-07-30 15:55 ` Konstantin Komarov
2021-07-30 17:23 ` Paragon NTFSv3 (was Re: [GIT PULL] vboxsf fixes for 5.14-1) Linus Torvalds
2021-08-13 16:11 ` Konstantin Komarov
2021-08-15 20:32 ` Stephen Rothwell
2021-08-16 3:00 ` Kari Argillander
2021-09-02 21:55 ` Linus Torvalds
2021-08-03 22:48 ` [GIT PULL] vboxsf fixes for 5.14-1 Theodore Ts'o
2021-08-03 23:44 ` Matthew Wilcox
2021-08-04 0:04 ` Theodore Ts'o
2021-08-04 0:10 ` Linus Torvalds
2021-08-04 0:49 ` Theodore Ts'o
2021-08-04 1:03 ` Darrick J. Wong
2021-08-04 6:38 ` Kari Argillander
2021-08-04 16:30 ` Theodore Ts'o
2021-08-05 15:48 ` Konstantin Komarov
2021-08-10 7:02 ` Darrick J. Wong
2021-09-02 22:09 ` NTFS testing (was: " Szabolcs Szakacsits
2021-09-03 17:48 ` Eric Biggers
2021-09-03 21:17 ` Szabolcs Szakacsits
2021-07-17 16:47 ` Pali Rohár
2021-07-14 16:13 ` Darrick J. Wong
2021-07-14 16:18 ` Christoph Hellwig
2021-07-14 16:38 ` Gao Xiang
2021-07-14 20:03 ` Eric W. Biederman
2021-07-15 22:14 ` Darrick J. Wong
2021-07-13 19:17 ` 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=YO34eTRpEQKuCzpW@zeniv-ca.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=hdegoede@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=torvalds@linux-foundation.org \
--subject='Re: [GIT PULL] vboxsf fixes for 5.14-1' \
/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
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).