From: Dave Kleikamp <dave.kleikamp@oracle.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
JFS Discussion <jfs-discussion@lists.sourceforge.net>
Subject: [GIT PULL] jfs patches for v4.19
Date: Wed, 15 Aug 2018 10:58:46 -0500 [thread overview]
Message-ID: <0937cae2-6fc5-49cb-1989-9472515fdeb4@oracle.com> (raw)
The following changes since commit ba4dbdedd3edc2798659bcd8b1a184ea8bdd04dc:
Merge tag 'jfs-4.18' of git://github.com/kleikamp/linux-shaggy
(2018-06-19 07:47:32 +0900)
are available in the Git repository at:
git://github.com/kleikamp/linux-shaggy.git tags/jfs-4.19
for you to fetch changes up to bd646104ac5a6bf8bdddaeaf4e441f5d439ded96:
jfs: use time64_t for otime (2018-06-19 14:09:30 -0500)
----------------------------------------------------------------
Just one jfs patch for 4.19
----------------------------------------------------------------
Arnd Bergmann (1):
jfs: use time64_t for otime
fs/jfs/jfs_incore.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
reply other threads:[~2018-08-15 15:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=0937cae2-6fc5-49cb-1989-9472515fdeb4@oracle.com \
--to=dave.kleikamp@oracle.com \
--cc=jfs-discussion@lists.sourceforge.net \
--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 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).