From: Greg KH <gregkh@linuxfoundation.org>
To: Roman Storozhenko <romeusmeister@gmail.com>
Cc: jirislaby@kernel.org, Julia.Lawall@inria.fr,
skhan@linuxfoundation.org, javier.carrasco.cruz@gmail.com,
linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org
Subject: Re: [PATCH] sysrq: Auto release device node using __free attribute
Date: Fri, 12 Apr 2024 07:20:54 +0200 [thread overview]
Message-ID: <2024041245-surfboard-expenses-ba74@gregkh> (raw)
In-Reply-To: <CALsPMBOx2LeNSL+i+7K3UZ2mvpDDRz0UVoAEuB0ouiEjk73pqw@mail.gmail.com>
A: http://en.wikipedia.org/wiki/Top_post
Q: Were do I find info about this thing called top-posting?
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
A: No.
Q: Should I include quotations after my reply?
http://daringfireball.net/2007/07/on_top
On Thu, Apr 11, 2024 at 08:28:17PM +0200, Roman Storozhenko wrote:
> This change allows us to put this pointer under automatic scope
> management and get rid of node_put. Besides, if a new code path is
> introduced we won't need to add a new of_node_put.
We worry about future stuff then, in the future. So no need for
changing code today for things that are not present at all, otherwise
you would never be finished with anything, right?
Don't make things more complex when it is not needed. Only add
complexity when it is needed.
thanks,
greg k-h
prev parent reply other threads:[~2024-04-12 5:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-11 18:02 [PATCH] sysrq: Auto release device node using __free attribute Roman Storozhenko
2024-04-11 18:10 ` Greg KH
2024-04-11 18:25 ` Roman Storozhenko
2024-04-12 5:22 ` Greg KH
2024-04-11 18:11 ` Greg KH
2024-04-11 18:17 ` Julia Lawall
2024-04-12 5:22 ` Greg KH
2024-04-12 6:21 ` Julia Lawall
2024-04-13 19:15 ` Julia Lawall
2024-04-11 18:28 ` Roman Storozhenko
2024-04-12 5:20 ` Greg KH [this message]
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=2024041245-surfboard-expenses-ba74@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=Julia.Lawall@inria.fr \
--cc=javier.carrasco.cruz@gmail.com \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=romeusmeister@gmail.com \
--cc=skhan@linuxfoundation.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