mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Jan Kara <jack@suse.cz>, Arnd Bergmann <arnd@kernel.org>,
	Alexander Viro <viro@zeniv.linux.org.uk>,
	linux-fsdevel@vger.kernel.org, Thomas Schmitt <scdbackup@gmx.net>,
	stable@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
	Jeff Layton <jlayton@kernel.org>,
	Deepa Dinamani <deepa.kernel@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] isofs: prevent file time rollover after year 2038
Date: Tue, 25 Oct 2022 11:26:58 +0200	[thread overview]
Message-ID: <20221025092658.qshqotkncsbp5nr5@quack3> (raw)
In-Reply-To: <20221024135517.7d40b96a206020eca03e3802@linux-foundation.org>

On Mon 24-10-22 13:55:17, Andrew Morton wrote:
> On Mon, 24 Oct 2022 16:51:21 +0200 Jan Kara <jack@suse.cz> wrote:
> 
> > > Thanks! I've added the patch to my tree and will push it to Linus.
> > 
> > Oh, I have noticed Andrew has merged the patch already into his tree. So
> > dropped from mine.
> 
> You could have just added it and I'd drop my copy when Stephen tells
> us of the duplicate.  But whatever.

Yeah, I know. But since I've just pulled the patch in I figured it's less
work if I just take it out as well ;)

> Maybe you owe us an ISOFS MAINTAINERS entry ;)

Yeah, I can see isofs currently has no entry in MAINTAINERS. OK, I'll add
some ;)

								Honza

-- 
Jan Kara <jack@suse.com>
SUSE Labs, CR

      reply	other threads:[~2022-10-25  9:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-20 16:00 Arnd Bergmann
2022-10-21  9:19 ` Christian Brauner
2022-10-21 12:41 ` Jeff Layton
2022-10-24 12:26 ` Jan Kara
2022-10-24 14:51   ` Jan Kara
2022-10-24 20:55     ` Andrew Morton
2022-10-25  9:26       ` Jan Kara [this message]

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=20221025092658.qshqotkncsbp5nr5@quack3 \
    --to=jack@suse.cz \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=arnd@kernel.org \
    --cc=deepa.kernel@gmail.com \
    --cc=jlayton@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=scdbackup@gmx.net \
    --cc=stable@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    /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

all inboxes | Powered by JetHome®