From: Christoph Hellwig <hch@infradead.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Joel Becker <jlbec@evilplan.org>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] configfs updates for 5.10
Date: Thu, 15 Oct 2020 19:54:01 +0200 [thread overview]
Message-ID: <20201015175312.GA2648919@infradead.org> (raw)
[resent with the mailing lists in Cc]
The following changes since commit ba4f184e126b751d1bffad5897f263108befc780:
Linux 5.9-rc6 (2020-09-20 16:33:55 -0700)
are available in the Git repository at:
git://git.infradead.org/users/hch/configfs.git tags/configfs-5.10
for you to fetch changes up to 76ecfcb0852eb0390881a695a2f349b804d80147:
samples: configfs: prefer pr_err() over bare printk(KERN_ERR (2020-10-07 15:46:22 +0200)
----------------------------------------------------------------
configfs updates for 5.10
- various cleanups for the configfs samples (Bartosz Golaszewski)
----------------------------------------------------------------
Bartosz Golaszewski (9):
MAINTAINERS: add the sample directory to the configfs entry
samples: configfs: remove redundant newlines
samples: configfs: drop unnecessary ternary operators
samples: configfs: fix alignment in item struct
samples: configfs: replace simple_strtoul() with kstrtoint()
samples: configfs: don't reinitialize variables which are already zeroed
samples: configfs: consolidate local variables of the same type
samples: configfs: don't use spaces before tabs
samples: configfs: prefer pr_err() over bare printk(KERN_ERR
MAINTAINERS | 1 +
samples/configfs/configfs_sample.c | 59 ++++++++++++--------------------------
2 files changed, 20 insertions(+), 40 deletions(-)
next reply other threads:[~2020-10-15 17:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-15 17:54 Christoph Hellwig [this message]
2020-10-15 22:19 ` [GIT PULL] configfs updates for 5.10 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=20201015175312.GA2648919@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).