All of lore.kernel.org
 help / color / mirror / Atom feed
From: Trond Myklebust <trondmy@primarydata.com>
To: "torvalds@linux-foundation.org" <torvalds@linux-foundation.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: [GIT PULL] Please pull NFS client bugfixes
Date: Sun, 25 Feb 2018 17:02:40 +0000	[thread overview]
Message-ID: <1519578159.3131.1.camel@primarydata.com> (raw)

Hi Linus,

The following changes since commit af3e79d29555b97dd096e2f8e36a0f50213808a8:

  Merge tag 'leds_for-4.16-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/j.anaszewski/linux-leds (2018-02-20 10:05:02 -0800)

are available in the Git repository at:

  git://git.linux-nfs.org/projects/trondmy/linux-nfs.git tags/nfs-for-4.16-3

for you to fetch changes up to 1b7204064582792b77c6be796e78bd821c9f71b1:

  NFS: make struct nlmclnt_fl_close_lock_ops static (2018-02-22 12:23:01 -0500)

----------------------------------------------------------------
NFS client bugfixes for Linux 4.16

Hightlights include:
- Fix a broken cast in nfs4_callback_recallany()
- Fix an Oops during NFSv4 migration events
- make struct nlmclnt_fl_close_lock_ops static

----------------------------------------------------------------
Bill.Baker@oracle.com (1):
      nfs: system crashes after NFS4ERR_MOVED recovery

Colin Ian King (1):
      NFS: make struct nlmclnt_fl_close_lock_ops static

Trond Myklebust (1):
      NFSv4: Fix broken cast in nfs4_callback_recallany()

 fs/nfs/callback_proc.c | 14 ++++++--------
 fs/nfs/nfs3proc.c      |  2 +-
 fs/nfs/nfs4client.c    |  6 ++++--
 3 files changed, 11 insertions(+), 11 deletions(-)
-- 
Trond Myklebust
Linux NFS client maintainer, PrimaryData
trond.myklebust@primarydata.com

WARNING: multiple messages have this Message-ID (diff)
From: Trond Myklebust <trondmy@primarydata.com>
To: "torvalds@linux-foundation.org" <torvalds@linux-foundation.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: [GIT PULL] Please pull NFS client bugfixes
Date: Sun, 25 Feb 2018 17:02:40 +0000	[thread overview]
Message-ID: <1519578159.3131.1.camel@primarydata.com> (raw)

SGkgTGludXMsDQoNClRoZSBmb2xsb3dpbmcgY2hhbmdlcyBzaW5jZSBjb21taXQgYWYzZTc5ZDI5
NTU1Yjk3ZGQwOTZlMmY4ZTM2YTBmNTAyMTM4MDhhODoNCg0KICBNZXJnZSB0YWcgJ2xlZHNfZm9y
LTQuMTYtcmMzJyBvZiBnaXQ6Ly9naXQua2VybmVsLm9yZy9wdWIvc2NtL2xpbnV4L2tlcm5lbC9n
aXQvai5hbmFzemV3c2tpL2xpbnV4LWxlZHMgKDIwMTgtMDItMjAgMTA6MDU6MDIgLTA4MDApDQoN
CmFyZSBhdmFpbGFibGUgaW4gdGhlIEdpdCByZXBvc2l0b3J5IGF0Og0KDQogIGdpdDovL2dpdC5s
aW51eC1uZnMub3JnL3Byb2plY3RzL3Ryb25kbXkvbGludXgtbmZzLmdpdCB0YWdzL25mcy1mb3It
NC4xNi0zDQoNCmZvciB5b3UgdG8gZmV0Y2ggY2hhbmdlcyB1cCB0byAxYjcyMDQwNjQ1ODI3OTJi
NzdjNmJlNzk2ZTc4YmQ4MjFjOWY3MWIxOg0KDQogIE5GUzogbWFrZSBzdHJ1Y3QgbmxtY2xudF9m
bF9jbG9zZV9sb2NrX29wcyBzdGF0aWMgKDIwMTgtMDItMjIgMTI6MjM6MDEgLTA1MDApDQoNCi0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0NCk5GUyBjbGllbnQgYnVnZml4ZXMgZm9yIExpbnV4IDQuMTYNCg0KSGlnaHRsaWdodHMg
aW5jbHVkZToNCi0gRml4IGEgYnJva2VuIGNhc3QgaW4gbmZzNF9jYWxsYmFja19yZWNhbGxhbnko
KQ0KLSBGaXggYW4gT29wcyBkdXJpbmcgTkZTdjQgbWlncmF0aW9uIGV2ZW50cw0KLSBtYWtlIHN0
cnVjdCBubG1jbG50X2ZsX2Nsb3NlX2xvY2tfb3BzIHN0YXRpYw0KDQotLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQpCaWxsLkJh
a2VyQG9yYWNsZS5jb20gKDEpOg0KICAgICAgbmZzOiBzeXN0ZW0gY3Jhc2hlcyBhZnRlciBORlM0
RVJSX01PVkVEIHJlY292ZXJ5DQoNCkNvbGluIElhbiBLaW5nICgxKToNCiAgICAgIE5GUzogbWFr
ZSBzdHJ1Y3QgbmxtY2xudF9mbF9jbG9zZV9sb2NrX29wcyBzdGF0aWMNCg0KVHJvbmQgTXlrbGVi
dXN0ICgxKToNCiAgICAgIE5GU3Y0OiBGaXggYnJva2VuIGNhc3QgaW4gbmZzNF9jYWxsYmFja19y
ZWNhbGxhbnkoKQ0KDQogZnMvbmZzL2NhbGxiYWNrX3Byb2MuYyB8IDE0ICsrKysrKy0tLS0tLS0t
DQogZnMvbmZzL25mczNwcm9jLmMgICAgICB8ICAyICstDQogZnMvbmZzL25mczRjbGllbnQuYyAg
ICB8ICA2ICsrKystLQ0KIDMgZmlsZXMgY2hhbmdlZCwgMTEgaW5zZXJ0aW9ucygrKSwgMTEgZGVs
ZXRpb25zKC0pDQotLSANClRyb25kIE15a2xlYnVzdA0KTGludXggTkZTIGNsaWVudCBtYWludGFp
bmVyLCBQcmltYXJ5RGF0YQ0KdHJvbmQubXlrbGVidXN0QHByaW1hcnlkYXRhLmNvbQ0K


             reply	other threads:[~2018-02-25 17:02 UTC|newest]

Thread overview: 98+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-25 17:02 Trond Myklebust [this message]
2018-02-25 17:02 ` [GIT PULL] Please pull NFS client bugfixes Trond Myklebust
  -- strict thread matches above, loose matches on Subject: below --
2023-01-07 18:09 Trond Myklebust
2023-01-07 18:43 ` pr-tracker-bot
2022-09-12 21:34 Trond Myklebust
2022-09-12 21:57 ` pr-tracker-bot
2021-01-12 14:31 Trond Myklebust
2021-01-12 18:00 ` pr-tracker-bot
2020-09-28 17:27 Trond Myklebust
2020-09-28 18:16 ` pr-tracker-bot
2020-05-15 21:00 Trond Myklebust
2020-05-15 21:10 ` pr-tracker-bot
2020-05-02 13:35 Trond Myklebust
2020-05-02 18:45 ` pr-tracker-bot
2019-08-27 19:26 Trond Myklebust
2019-08-27 20:55 ` pr-tracker-bot
2019-08-08 21:26 Trond Myklebust
2019-08-09  1:30 ` pr-tracker-bot
2019-06-05 21:02 Schumaker, Anna
2019-04-13 14:56 Trond Myklebust
2019-04-13 22:00 ` pr-tracker-bot
2018-12-19 16:49 Trond Myklebust
2018-12-20  2:50 ` pr-tracker-bot
2018-12-20 15:23 ` Geert Uytterhoeven
2018-03-12 17:29 Trond Myklebust
2018-03-12 17:29 ` Trond Myklebust
2017-01-28 17:04 Trond Myklebust
2017-01-28 17:04 ` Trond Myklebust
2017-01-16 20:14 Trond Myklebust
2017-01-16 20:14 ` Trond Myklebust
2016-10-21 20:30 Anna Schumaker
2015-10-07  2:52 Trond Myklebust
2015-09-25 15:14 Trond Myklebust
2015-07-28 16:03 Trond Myklebust
2015-03-06  3:46 Trond Myklebust
2015-01-29 21:37 Trond Myklebust
2015-01-16 14:35 Trond Myklebust
2014-11-14 23:04 Trond Myklebust
2014-09-19 19:32 Trond Myklebust
2014-01-31 21:41 Trond Myklebust
2013-12-05 17:20 Trond Myklebust
2013-11-16 21:09 Myklebust, Trond
2013-09-30 22:02 Myklebust, Trond
2013-09-30 22:02 ` Myklebust, Trond
2013-05-26 19:29 Myklebust, Trond
2013-03-26 18:26 Myklebust, Trond
2013-03-03  0:08 Myklebust, Trond
2013-02-21  3:38 Myklebust, Trond
2013-01-07 15:45 Myklebust, Trond
2012-11-03 19:48 Myklebust, Trond
2012-11-03 19:48 ` Myklebust, Trond
2012-10-22 17:42 Myklebust, Trond
2012-10-22 17:42 ` Myklebust, Trond
2012-09-12 19:19 Myklebust, Trond
2012-09-12 19:19 ` Myklebust, Trond
2012-07-13 15:14 Myklebust, Trond
2012-07-13 15:14 ` Myklebust, Trond
2012-05-02  3:57 Myklebust, Trond
2012-05-02  3:57 ` Myklebust, Trond
2012-04-24 20:18 [GIT PULL] please " Myklebust, Trond
2012-04-24 20:18 ` Myklebust, Trond
2011-12-20  6:15 [GIT PULL] Please " Trond Myklebust
2011-11-22 11:50 Trond Myklebust
2011-08-19  1:05 Trond Myklebust
2011-07-12 23:30 Trond Myklebust
2011-05-13 20:23 Trond Myklebust
2011-04-08 18:40 [GIT PULL] please " Trond Myklebust
2011-03-14 18:09 [GIT PULL] Please " Trond Myklebust
2010-11-26 18:56 Trond Myklebust
2010-05-26 19:42 Trond Myklebust
2010-05-07  2:22 Trond Myklebust
2010-04-29 16:48 Trond Myklebust
2010-03-23 17:00 Trond Myklebust
2010-03-17 21:55 Trond Myklebust
2010-02-04 19:10 Trond Myklebust
2010-01-07 20:29 Trond Myklebust
2010-01-07 21:00 ` Andi Kleen
2010-01-07 21:23   ` Peter Staubach
2010-01-07 21:35     ` Andi Kleen
2010-01-07 21:53   ` Trond Myklebust
2010-01-07 23:51     ` Andi Kleen
2010-01-08  0:14       ` Trond Myklebust
2010-01-08  0:34         ` Linus Torvalds
2010-01-08  0:45           ` Andi Kleen
2010-01-08  1:03             ` Trond Myklebust
2010-01-08  1:03           ` Trond Myklebust
2010-01-08  1:12             ` Linus Torvalds
2010-01-08  1:22               ` Trond Myklebust
2010-01-08  1:26                 ` Trond Myklebust
2010-01-08  1:30                 ` Linus Torvalds
2010-01-08  1:35                   ` Linus Torvalds
2010-01-08  2:00                     ` Linus Torvalds
2010-01-14 13:18                       ` Peter Zijlstra
2010-01-08  5:19                   ` Andi Kleen
2010-01-08  1:22               ` Linus Torvalds
2010-01-08  0:43         ` Andi Kleen
2009-05-26 19:06 Trond Myklebust
2009-05-26 19:06 ` Trond Myklebust

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=1519578159.3131.1.camel@primarydata.com \
    --to=trondmy@primarydata.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@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.