From: Shresth Prasad <shresthprasad7@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: davem@davemloft.net, jirislaby@kernel.org,
linux-serial@vger.kernel.org,
Javier Carrasco <javier.carrasco.cruz@gmail.com>,
Julia Lawall <julia.lawall@inria.fr>,
Shuah Khan <skhan@linuxfoundation.org>,
sparclinux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][next] tty: sunsu: Simplify device_node cleanup by using __free
Date: Wed, 1 May 2024 11:02:24 +0530 [thread overview]
Message-ID: <CAE8VWiKZSGM_JXnvsbp3jo+A80puYGA58FoLY3+ZQar5tFAyCg@mail.gmail.com> (raw)
In-Reply-To: <2024050149-blob-afoot-af04@gregkh>
> Yes, but you did not include it in your response at all, so how were we
> to see it?
Oh, really sorry about that.
I thought I was replying to the thread with the patch.
> Great, please say so in your changelog text.
Right, I'll do that. My bad.
I'll resubmit the patch.
Regards,
Shresth
On Wed, May 1, 2024 at 10:33 AM Greg KH <gregkh@linuxfoundation.org> wrote:
>
> On Wed, May 01, 2024 at 10:28:35AM +0530, Shresth Prasad wrote:
> > > I don't see anything here, sorry.
> > I'm sorry but is this patch not visible?
> > https://lore.kernel.org/all/20240425060303.8045-2-shresthprasad7@gmail.com/
>
> Yes, but you did not include it in your response at all, so how were we
> to see it?
>
> > > Also, how was this tested?
> > I tested it using a qemu x86_64 virtual machine
>
> Great, please say so in your changelog text.
>
> thanks,
>
> greg k-h
next prev parent reply other threads:[~2024-05-01 5:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-01 4:31 [PATCH][next] tty: sunsu: Simplify device_node cleanup by using __free Shresth Prasad
2024-05-01 4:51 ` Greg KH
2024-05-01 4:58 ` Shresth Prasad
2024-05-01 5:03 ` Greg KH
2024-05-01 5:32 ` Shresth Prasad [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-04-25 6:03 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=CAE8VWiKZSGM_JXnvsbp3jo+A80puYGA58FoLY3+ZQar5tFAyCg@mail.gmail.com \
--to=shresthprasad7@gmail.com \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--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=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 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 read-only IMAP folder(s) and NNTP newsgroup(s).