From: "Enrico Weigelt, metux IT consult" <lkml@metux.net>
To: Justin He <Justin.He@arm.com>, Al Viro <viro@zeniv.linux.org.uk>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: Petr Mladek <pmladek@suse.com>,
Steven Rostedt <rostedt@goodmis.org>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Jonathan Corbet <corbet@lwn.net>,
Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
"Eric W . Biederman" <ebiederm@xmission.com>,
"Darrick J. Wong" <darrick.wong@oracle.com>,
"Peter Zijlstra (Intel)" <peterz@infradead.org>,
Ira Weiny <ira.weiny@intel.com>,
Eric Biggers <ebiggers@google.com>,
"Ahmed S. Darwish" <a.darwish@linutronix.de>,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-s390 <linux-s390@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>, nd <nd@arm.com>
Subject: Re: [PATCH 09/14] d_path: introduce struct prepend_buffer
Date: Mon, 28 Jun 2021 18:42:48 +0200 [thread overview]
Message-ID: <eedc09ed-f13a-8a08-4e3a-83b2382d43cc@metux.net> (raw)
In-Reply-To: <AM0PR08MB4370B5A85FFDD36D79DE73E2F7069@AM0PR08MB4370.eurprd08.prod.outlook.com>
>> this smells like a generic enough thing to go into lib, doesn't it ?
>>
> Maybe, but the struct prepend_buffer also needs to be moved into lib.
> Is it necessary? Is there any other user of struct prepend_buffer?
Don't have a specific use case right now, but it smells like a pretty
generic string function. Is already having more than one user a hard
requirement for putting something into lib ?
--mtx
--
---
Hinweis: unverschlüsselte E-Mails können leicht abgehört und manipuliert
werden ! Für eine vertrauliche Kommunikation senden Sie bitte ihren
GPG/PGP-Schlüssel zu.
---
Enrico Weigelt, metux IT consult
Free software and Linux embedded engineering
info@metux.net -- +49-151-27565287
next prev parent reply other threads:[~2021-06-28 16:44 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-08 12:25 [PATCH RFC 0/3] make '%pD' print full path for file Jia He
2021-05-08 12:25 ` [PATCH RFC 1/3] fs: introduce helper d_path_fast() Jia He
2021-05-08 15:30 ` Linus Torvalds
2021-05-08 19:13 ` Al Viro
2021-05-08 20:39 ` Linus Torvalds
2021-05-08 21:05 ` Al Viro
2021-05-08 22:17 ` Linus Torvalds
2021-05-08 22:46 ` Al Viro
2021-05-08 22:48 ` Linus Torvalds
2021-05-08 23:15 ` Al Viro
2021-05-08 23:18 ` Al Viro
2021-05-09 22:58 ` Eric W. Biederman
2021-05-10 12:51 ` Christian Brauner
2021-05-10 7:20 ` Christian Brauner
2021-05-08 22:42 ` Linus Torvalds
2021-05-08 22:47 ` Linus Torvalds
2021-05-09 2:28 ` Al Viro
2021-05-09 2:53 ` Linus Torvalds
2021-05-19 0:43 ` [PATCHSET] d_path cleanups Al Viro
2021-05-19 0:48 ` [PATCH 01/14] d_path: "\0" is {0,0}, not {0} Al Viro
2021-05-19 0:48 ` [PATCH 02/14] d_path: saner calling conventions for __dentry_path() Al Viro
2021-06-25 9:32 ` Justin He
2021-07-07 4:52 ` Justin He
2021-05-19 0:48 ` [PATCH 03/14] d_path: regularize handling of root dentry in __dentry_path() Al Viro
2021-07-07 4:50 ` Justin He
2021-05-19 0:48 ` [PATCH 04/14] d_path: get rid of path_with_deleted() Al Viro
2021-05-19 0:48 ` [PATCH 05/14] getcwd(2): saner logics around prepend_path() call Al Viro
2021-07-07 7:41 ` Justin He
2021-05-19 0:48 ` [PATCH 06/14] d_path: don't bother with return value of prepend() Al Viro
2021-06-24 6:13 ` Justin He
2021-05-19 0:48 ` [PATCH 07/14] d_path: lift -ENAMETOOLONG handling into callers of prepend_path() Al Viro
2021-06-25 9:18 ` Justin He
2021-06-28 5:20 ` Justin He
2021-05-19 0:48 ` [PATCH 08/14] d_path: make prepend_name() boolean Al Viro
2021-05-20 9:12 ` Justin He
2021-05-20 9:19 ` Andy Shevchenko
2021-05-20 14:53 ` Petr Mladek
2021-05-20 19:35 ` Al Viro
2021-07-07 7:43 ` Justin He
2021-05-19 0:48 ` [PATCH 09/14] d_path: introduce struct prepend_buffer Al Viro
2021-06-23 13:28 ` Justin He
2021-06-24 9:29 ` Enrico Weigelt, metux IT consult
2021-06-25 0:43 ` Justin He
2021-06-28 16:42 ` Enrico Weigelt, metux IT consult [this message]
2021-06-28 17:10 ` Andy Shevchenko
2021-05-19 0:48 ` [PATCH 10/14] d_path: prepend_path(): get rid of vfsmnt Al Viro
2021-05-19 0:48 ` [PATCH 11/14] d_path: prepend_path(): lift resetting b in case when we'd return 3 out of loop Al Viro
2021-05-19 0:48 ` [PATCH 12/14] d_path: prepend_path(): lift the inner loop into a new helper Al Viro
2021-05-19 8:07 ` Andy Shevchenko
2021-05-19 15:55 ` Al Viro
2021-07-07 7:52 ` Justin He
2021-05-19 0:49 ` [PATCH 13/14] d_path: prepend_path() is unlikely to return non-zero Al Viro
2021-06-25 8:00 ` Justin He
2021-06-25 17:58 ` Al Viro
2021-06-28 3:28 ` Justin He
2021-06-28 4:14 ` Al Viro
2021-06-28 4:36 ` Justin He
2021-06-28 4:37 ` Justin He
2021-05-19 0:49 ` [PATCH 14/14] getcwd(2): clean up error handling Al Viro
2021-07-07 8:03 ` Justin He
2021-06-24 6:05 ` [PATCH 01/14] d_path: "\0" is {0,0}, not {0} Justin He
2021-05-19 2:39 ` [PATCHSET] d_path cleanups Linus Torvalds
2021-06-22 14:00 ` Justin He
2021-05-09 2:20 ` [PATCH RFC 1/3] fs: introduce helper d_path_fast() Al Viro
2021-05-09 4:58 ` Al Viro
2021-05-10 16:16 ` Eric W. Biederman
2021-05-10 15:07 ` Justin He
2021-05-10 17:03 ` Linus Torvalds
2021-05-08 12:25 ` [PATCH RFC 2/3] lib/vsprintf.c: make %pD print full path for file Jia He
2021-05-10 3:46 ` Sergey Senozhatsky
2021-05-10 13:04 ` Petr Mladek
2021-05-10 14:25 ` Justin He
2021-05-27 7:20 ` Justin He
2021-05-27 9:14 ` Petr Mladek
2021-05-08 12:25 ` [PATCH RFC 3/3] s390/hmcdrv: remove the redundant directory path in debug message Jia He
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=eedc09ed-f13a-8a08-4e3a-83b2382d43cc@metux.net \
--to=lkml@metux.net \
--cc=Justin.He@arm.com \
--cc=a.darwish@linutronix.de \
--cc=andriy.shevchenko@linux.intel.com \
--cc=borntraeger@de.ibm.com \
--cc=corbet@lwn.net \
--cc=darrick.wong@oracle.com \
--cc=ebiederm@xmission.com \
--cc=ebiggers@google.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=ira.weiny@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=nd@arm.com \
--cc=peterz@infradead.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.org \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/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).