From: Greg KH <gregkh@linuxfoundation.org>
To: Shresth Prasad <shresthprasad7@gmail.com>
Cc: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
davem@davemloft.net, jirislaby@kernel.org,
sparclinux@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-serial@vger.kernel.org, javier.carrasco.cruz@gmail.com,
skhan@linuxfoundation.org, "Julia Lawall" <julia.lawall@inria.fr>
Subject: Re: [PATCH v2][next] tty: sunsu: Simplify device_node cleanup by using __free
Date: Fri, 3 May 2024 07:34:25 +0200 [thread overview]
Message-ID: <2024050357-shading-fedora-2d4f@gregkh> (raw)
In-Reply-To: <CAE8VWiJy-2x6sKCAmN69Uq9Kf1cTRnaJezOoLDyZ0SbgPWuHAQ@mail.gmail.com>
On Thu, May 02, 2024 at 10:21:16PM +0530, Shresth Prasad wrote:
> On Thu, May 2, 2024 at 9:35 PM Ilpo Järvinen
> <ilpo.jarvinen@linux.intel.com> wrote:
> >
> > On Wed, 1 May 2024, Shresth Prasad wrote:
> >
> > > Add `__free` function attribute to `ap` and `match` pointer
> > > initialisations which ensure that the pointers are freed as soon as they
> > > go out of scope, thus removing the need to manually free them using
> > > `of_node_put`.
> > >
> > > This also removes the need for the `goto` statement and the `rc`
> > > variable.
> > >
> > > Tested using a qemu x86_64 virtual machine.
> >
> > Eh, how can you test this with an x86_64 VM ???
> >
> > config SERIAL_SUNSU
> > tristate "Sun SU serial support"
> > depends on SPARC && PCI
> >
>
> By that, I mean that I compiled the kernel and ran the produced bzImage
> on a x86_64 qemu machine.
But you didn't include the driver you were testing :(
> I unfortunately don't have the hardware to test it on, but I don't
> think the change is complex enough to require testing on real hardware
> (unless I'm assuming incorrectly).
That's why I asked if you had tested this or not...
next prev parent reply other threads:[~2024-05-03 5:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-01 8:41 [PATCH v2][next] tty: sunsu: Simplify device_node cleanup by using __free Shresth Prasad
2024-05-02 7:56 ` Jiri Slaby
2024-05-02 8:55 ` Shresth Prasad
2024-05-02 16:05 ` Ilpo Järvinen
2024-05-02 16:51 ` Shresth Prasad
2024-05-03 5:34 ` Greg KH [this message]
2024-05-03 9:01 ` Shresth Prasad
2024-05-04 16:02 ` Greg KH
2024-05-14 19:37 ` Shresth Prasad
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=2024050357-shading-fedora-2d4f@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=davem@davemloft.net \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=javier.carrasco.cruz@gmail.com \
--cc=jirislaby@kernel.org \
--cc=julia.lawall@inria.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=shresthprasad7@gmail.com \
--cc=skhan@linuxfoundation.org \
--cc=sparclinux@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.