All of lore.kernel.org
 help / color / mirror / Atom feed
From: Al Viro <viro@zeniv.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [git pull] vfs.git misc bits
Date: Sat, 25 Feb 2023 03:45:05 +0000	[thread overview]
Message-ID: <Y/mEQUfLqf8m2s/G@ZenIV> (raw)
In-Reply-To: <CAHk-=wiPHkYmiFY_O=7MK-vbWtLEiRP90ufugj1H1QFeiLPoVw@mail.gmail.com>

On Fri, Feb 24, 2023 at 07:33:12PM -0800, Linus Torvalds wrote:
> On Thu, Feb 23, 2023 at 7:41 PM Al Viro <viro@zeniv.linux.org.uk> wrote:
> >
> > That should cover the rest of what I had in -next; I'd been sick for
> > several weeks, so a lot of pending stuff I hoped to put into -next
> > is going to miss this window ;-/
> 
> Does that include the uaccess fixes for weird architectures?
> 
> I was hoping that was coming...

Missed -next; I'll look for tested-by/reviewed-by/etc. and put the same
patches into #fixes; we have a week until the end of merge window, and
those are fixes, after all...

  reply	other threads:[~2023-02-25  3:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-24  3:40 [git pull] vfs.git misc bits Al Viro
2023-02-25  3:33 ` Linus Torvalds
2023-02-25  3:45   ` Al Viro [this message]
2023-02-25  4:57     ` Al Viro
2023-02-25 17:04       ` Linus Torvalds
2023-02-25 18:11         ` Al Viro
     [not found]           ` <3805D9F9-FB5D-4A8A-BE4B-845DDC508441@gmail.com>
2023-02-25 22:02             ` Al Viro
2023-02-25  3:40 ` pr-tracker-bot
2023-02-25  3:40 ` Linus Torvalds
  -- strict thread matches above, loose matches on Subject: below --
2017-09-14 23:03 Al Viro

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=Y/mEQUfLqf8m2s/G@ZenIV \
    --to=viro@zeniv.linux.org.uk \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.