linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	Joel Becker <jlbec@evilplan.org>
Subject: [GIT PULL] configfs updates for Linux 5.13
Date: Fri, 2 Jul 2021 18:09:37 +0200	[thread overview]
Message-ID: <YN86Qdthbzfa5wfY@infradead.org> (raw)

The following changes since commit c4681547bcce777daf576925a966ffa824edd09d:

  Linux 5.13-rc3 (2021-05-23 11:42:48 -1000)

are available in the Git repository at:

  git://git.infradead.org/users/hch/configfs.git tags/configfs-5.13

for you to fetch changes up to c886fa3cf6ffbe13006053ceb27c93d41928de30:

  configfs: simplify configfs_release_bin_file (2021-06-22 09:46:28 +0200)

----------------------------------------------------------------
configfs updates for Linux 5.13

 - fix a memleak in configfs_release_bin_file (Chung-Chiang Cheng)
 - implement the .read_iter and .write_iter (Bart Van Assche)
 - minor cleanups (Bart Van Assche, me)

----------------------------------------------------------------
Bart Van Assche (2):
      configfs: fix the kerneldoc comment for configfs_create_bin_file
      configfs: implement the .read_iter and .write_iter methods

Christoph Hellwig (2):
      configfs: drop pointless kerneldoc comments
      configfs: simplify configfs_release_bin_file

Chung-Chiang Cheng (1):
      configfs: fix memleak in configfs_release_bin_file

 fs/configfs/file.c | 181 +++++++++++++++--------------------------------------
 1 file changed, 51 insertions(+), 130 deletions(-)

             reply	other threads:[~2021-07-02 16:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-02 16:09 Christoph Hellwig [this message]
2021-07-02 21:47 ` [GIT PULL] configfs updates for Linux 5.13 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=YN86Qdthbzfa5wfY@infradead.org \
    --to=hch@infradead.org \
    --cc=jlbec@evilplan.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --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).