From: Johannes Berg <johannes@sipsolutions.net>
To: Paulo Miguel Almeida <paulo.miguel.almeida.rodenas@gmail.com>,
richard@nod.at, anton.ivanov@cambridgegreys.com,
kees@kernel.org, tiwei.btw@antgroup.com,
linux-um@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][next] um: Malloc just enough space for fitting pid file
Date: Sat, 26 Oct 2024 09:44:53 +0200 [thread overview]
Message-ID: <cd892fb5436f1de0fa2ffc9c9ec229873227210f.camel@sipsolutions.net> (raw)
In-Reply-To: <ZxxmLngMg3iNjOfK@mail.google.com>
On Sat, 2024-10-26 at 16:46 +1300, Paulo Miguel Almeida wrote:
> umid is already generated during make_umid_init __initcall so there is
> no need to allocate UMID_LEN bytes to accommodate the max possible name
> for the umid segment of the filepath
>
> This patch replaces UMID_LEN occurences in which it's redundant
OK, I guess that's maybe all true, but can you say _why_ in the commit
log?
johannes
next prev parent reply other threads:[~2024-10-26 7:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-26 3:46 [PATCH][next] um: Malloc just enough space for fitting pid file Paulo Miguel Almeida
2024-10-26 7:44 ` Johannes Berg [this message]
2024-10-26 7:59 ` Paulo Miguel Almeida
2024-10-26 8:03 ` Johannes Berg
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=cd892fb5436f1de0fa2ffc9c9ec229873227210f.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=anton.ivanov@cambridgegreys.com \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-um@lists.infradead.org \
--cc=paulo.miguel.almeida.rodenas@gmail.com \
--cc=richard@nod.at \
--cc=tiwei.btw@antgroup.com \
/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