public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* [git pull] work.fd fix
@ 2022-06-05 19:13 Al Viro
  2022-06-06  0:15 ` Linus Torvalds
  2022-06-06  0:23 ` pr-tracker-bot
  0 siblings, 2 replies; 3+ messages in thread
From: Al Viro @ 2022-06-05 19:13 UTC (permalink / raw)
  To: Linus Torvalds; +Cc: linux-fsdevel, linux-kernel

[BTW, what conventions are generally used for pull tag names?]

The following changes since commit 6319194ec57b0452dcda4589d24c4e7db299c5bf:

  Unify the primitives for file descriptor closing (2022-05-14 18:49:01 -0400)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git tags/pull-work.fd-fixes

for you to fetch changes up to 40a1926022d128057376d35167128a7c74e3dca4:

  fix the breakage in close_fd_get_file() calling conventions change (2022-06-05 15:03:03 -0400)

----------------------------------------------------------------
fix for breakage in #work.fd this window
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>

----------------------------------------------------------------
Al Viro (1):
      fix the breakage in close_fd_get_file() calling conventions change

 drivers/android/binder.c | 2 ++
 fs/file.c                | 3 +--
 fs/io_uring.c            | 5 +----
 3 files changed, 4 insertions(+), 6 deletions(-)

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [git pull] work.fd fix
  2022-06-05 19:13 [git pull] work.fd fix Al Viro
@ 2022-06-06  0:15 ` Linus Torvalds
  2022-06-06  0:23 ` pr-tracker-bot
  1 sibling, 0 replies; 3+ messages in thread
From: Linus Torvalds @ 2022-06-06  0:15 UTC (permalink / raw)
  To: Al Viro; +Cc: linux-fsdevel, Linux Kernel Mailing List

On Sun, Jun 5, 2022 at 12:13 PM Al Viro <viro@zeniv.linux.org.uk> wrote:
>
> [BTW, what conventions are generally used for pull tag names?]

I don't think we have conventions.

There's a few common patterns, where the tag-name might be the
subsystem name, followed by the version number, followed by a possible
sequential tag number. So "acpi-5.17-rc1-3" or "powerpc-5.16-1" or
"net-5.15-rc8" or "mtd/fixes-for-5.14-rc7".

But another common pattern is to just re-use the same tag-name over
and over again, just updating the tag: "arm64-fixes" or
"clk-fixes-for-linus" or whatever.

In fact, the most common tag-name is just some variation of
"for-linus" (variations: "fixes-for-linus", "for_linus",
"hwmon-for-linus" etc etc)

It really doesn't matter, and your "pull-work.fd-fixes" name is fine.

                  Linus

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [git pull] work.fd fix
  2022-06-05 19:13 [git pull] work.fd fix Al Viro
  2022-06-06  0:15 ` Linus Torvalds
@ 2022-06-06  0:23 ` pr-tracker-bot
  1 sibling, 0 replies; 3+ messages in thread
From: pr-tracker-bot @ 2022-06-06  0:23 UTC (permalink / raw)
  To: Al Viro; +Cc: Linus Torvalds, linux-fsdevel, linux-kernel

The pull request you sent on Sun, 5 Jun 2022 19:13:46 +0000:

> git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git tags/pull-work.fd-fixes

has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/6684cf42906ff5f44580e16a1f898e89c19aabd5

Thank you!

-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/prtracker.html

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2022-06-06  0:23 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2022-06-05 19:13 [git pull] work.fd fix Al Viro
2022-06-06  0:15 ` Linus Torvalds
2022-06-06  0:23 ` pr-tracker-bot

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox