From: Greg KH <gregkh@linuxfoundation.org>
To: "Gupta, Nipun" <nipun.gupta@amd.com>
Cc: "Dr. David Alan Gilbert" <linux@treblig.org>,
nikhil.agarwal@amd.com, abhijit.gangurde@amd.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cdx: remove unused struct 'cdx_mcdi_copy_buffer'
Date: Mon, 22 Jul 2024 06:46:39 +0200 [thread overview]
Message-ID: <2024072226-strength-subtext-cde4@gregkh> (raw)
In-Reply-To: <7141e8f9-db0f-43e0-98ed-c3e2c44720d7@amd.com>
On Mon, Jul 22, 2024 at 09:59:27AM +0530, Gupta, Nipun wrote:
> On 7/22/2024 4:17 AM, Dr. David Alan Gilbert wrote:
> > * Gupta, Nipun (nipun.gupta@amd.com) wrote:
> > >
> > >
> > > On 5/31/2024 5:04 AM, linux@treblig.org wrote:
> > > > From: "Dr. David Alan Gilbert" <linux@treblig.org>
> > > >
> > > > 'cdx_mcdi_copy_buffer' has been unused since the original
> > > > commit eb96b740192b ("cdx: add MCDI protocol interface for firmware
> > > > interaction").
> > > >
> > > > Looking at lkml, it was used in the V1 posting but was removed
> > > > somewhere before V6.
> > > >
> > > > Remove it.
> > > >
> > > > Signed-off-by: Dr. David Alan Gilbert <linux@treblig.org>
> > > Acked-by: Nipun Gupta <nipun.gupta@amd.com>
> >
> > Hi Nipun,
> > Do you know who would pick this one up? I don't think it's made it's
> > way into -next yet.
>
> Added Greg k-h for this.
For what? Sorry, I have no context here...
next prev parent reply other threads:[~2024-07-22 4:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-30 23:34 [PATCH] cdx: remove unused struct 'cdx_mcdi_copy_buffer' linux
2024-06-21 0:02 ` Dr. David Alan Gilbert
2024-06-21 5:17 ` Gupta, Nipun
2024-07-21 22:47 ` Dr. David Alan Gilbert
2024-07-22 4:29 ` Gupta, Nipun
2024-07-22 4:46 ` Greg KH [this message]
2024-07-22 5:27 ` Gupta, Nipun
2024-07-22 5:35 ` Greg KH
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=2024072226-strength-subtext-cde4@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=abhijit.gangurde@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@treblig.org \
--cc=nikhil.agarwal@amd.com \
--cc=nipun.gupta@amd.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