linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Jan Kara <jack@suse.cz>
Cc: y2038 Mailman List <y2038@lists.linaro.org>,
	Al Viro <viro@zeniv.linux.org.uk>,
	Deepa Dinamani <deepa.kernel@gmail.com>,
	Linux FS-devel Mailing List <linux-fsdevel@vger.kernel.org>,
	Anders Larsen <al@alarsen.net>,
	"# 3.4.x" <stable@vger.kernel.org>,
	David Howells <dhowells@redhat.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 1/2] isofs: fix timestamps beyond 2027
Date: Tue, 31 Oct 2017 22:36:31 +0100	[thread overview]
Message-ID: <CAK8P3a2zGYvq31LXceZH7Lz+V1i0wdsAE+PpW=BO_JGtaMpSzQ@mail.gmail.com> (raw)
In-Reply-To: <20171031165913.GH26128@quack2.suse.cz>

On Tue, Oct 31, 2017 at 5:59 PM, Jan Kara <jack@suse.cz> wrote:
> On Thu 19-10-17 17:29:12, Arnd Bergmann wrote:
>> On Thu, Oct 19, 2017 at 5:17 PM, Jan Kara <jack@suse.cz> wrote:

>> >>
>> >> -     year = p[0];
>> >> +     year = (int)(u8)p[0];
>> >
>> > The cast seems unnecessary now?
>> >
>>
>> Sorry, I must have rebased the patch incorrectly, this was intended to
>> be removed
>> of course.
>
> OK, I've picked up this patch to my tree with this correction.

Thanks! I was planning to send the fixed version but didn't get
around to it before ELC, and by now I had forgotten about it.

       Arnd

      reply	other threads:[~2017-10-31 21:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-19 14:47 [PATCH v2 1/2] isofs: fix timestamps beyond 2027 Arnd Bergmann
2017-10-19 14:47 ` [PATCH v2 2/2] isofs: use unsigned char types consistently Arnd Bergmann
2017-10-31 17:11   ` Jan Kara
2017-10-19 15:17 ` [PATCH v2 1/2] isofs: fix timestamps beyond 2027 Jan Kara
2017-10-19 15:29   ` Arnd Bergmann
2017-10-31 16:59     ` Jan Kara
2017-10-31 21:36       ` Arnd Bergmann [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='CAK8P3a2zGYvq31LXceZH7Lz+V1i0wdsAE+PpW=BO_JGtaMpSzQ@mail.gmail.com' \
    --to=arnd@arndb.de \
    --cc=al@alarsen.net \
    --cc=deepa.kernel@gmail.com \
    --cc=dhowells@redhat.com \
    --cc=jack@suse.cz \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    --cc=y2038@lists.linaro.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 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).