From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux1394-devel@lists.sourceforge.net
Subject: [git pull] FireWire (IEEE 1394) update post v5.4
Date: Sun, 1 Dec 2019 19:53:08 +0100 [thread overview]
Message-ID: <20191201195308.363d0b83@kant> (raw)
Linus,
please pull from the tag "firewire-update" at
git://git.kernel.org/pub/scm/linux/kernel/git/ieee1394/linux1394.git firewire-update
to receive the following FireWire (IEEE 1394) subsystem updates:
- another y2038 fix
- janitorial: code movement
Arnd Bergmann (1):
firewire: ohci: stop using get_seconds() for BUS_TIME
Stefan Richter (1):
firewire: core: code cleanup after vm_map_pages_zero introduction
drivers/firewire/core-cdev.c | 3 ++-
drivers/firewire/core-iso.c | 7 -------
drivers/firewire/core.h | 2 --
drivers/firewire/ohci.c | 2 +-
4 files changed, 3 insertions(+), 11 deletions(-)
Tanks,
--
Stefan Richter
-======---== ==-- ----=
http://arcgraph.de/sr/
next reply other threads:[~2019-12-01 18:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-01 18:53 Stefan Richter [this message]
2019-12-02 22:20 ` [git pull] FireWire (IEEE 1394) update post v5.4 pr-tracker-bot
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=20191201195308.363d0b83@kant \
--to=stefanr@s5r6.in-berlin.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--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