From: "Dutt, Sudeep" <sudeep.dutt@intel.com>
To: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
Cc: "corbet@lwn.net" <corbet@lwn.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"sherry.sun@nxp.com" <sherry.sun@nxp.com>,
"dmaengine@vger.kernel.org" <dmaengine@vger.kernel.org>,
"Dutt, Sudeep" <sudeep.dutt@intel.com>,
"Rao, Nikhil" <nikhil.rao@intel.com>,
"Dixit, Ashutosh" <ashutosh.dixit@intel.com>,
"vkoul@kernel.org" <vkoul@kernel.org>,
"arnd@arndb.de" <arnd@arndb.de>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>
Subject: Re: [PATCH char-misc-next 1/1] misc: mic: remove the MIC drivers
Date: Wed, 28 Oct 2020 17:22:01 +0000 [thread overview]
Message-ID: <f64a1f67781441c8ed48b991afbf8dd2f9030289.camel@intel.com> (raw)
In-Reply-To: <20201028055429.GA244117@kroah.com>
On Wed, 2020-10-28 at 06:54 +0100, Greg Kroah-Hartman wrote:
> On Tue, Oct 27, 2020 at 08:14:15PM -0700, Sudeep Dutt wrote:
> > This patch removes the MIC drivers from the kernel tree
> > since the corresponding devices have been discontinued.
>
> Does "discontinued" mean "never shipped a device so no one has access
> to
> this hardware anymore", or does it mean "we stopped shipping devices
> and
> there are customers with this?"
Hi Greg,
We are not aware of any customers of the upstreamed MIC drivers. The
drivers were upstreamed primarily to lay a foundation for enabling the
next generation MIC devices which did not ship.
> > Removing the dma and char-misc changes in one patch and
> > merging via the char-misc tree is best to avoid any
> > potential build breakage.
> >
> > Cc: Nikhil Rao <nikhil.rao@intel.com>
> > Reviewed-by: Ashutosh Dixit <ashutosh.dixit@intel.com>
> > Signed-off-by: Sudeep Dutt <sudeep.dutt@intel.com>
>
> I like deleting code, can this go into 5.10-final?
Yes, we would prefer this goes into v5.10. I am hoping you can carry
the Ack from Vinod and the Reviewed-by from Sherry but I can resend the
patch with those updates in the commit message if required. I did
verify that this patch passes allmodconfig and allyesconfig builds with
your latest char-misc-next tree.
Many thanks for your help with this subsystem Greg.
Best Regards,
Sudeep Dutt
next prev parent reply other threads:[~2020-10-28 22:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8c1443136563de34699d2c084df478181c205db4.1603854416.git.sudeep.dutt@intel.com>
2020-10-28 5:54 ` [PATCH char-misc-next 1/1] misc: mic: remove the MIC drivers Greg Kroah-Hartman
2020-10-28 6:04 ` Vinod Koul
2020-10-28 17:22 ` Dutt, Sudeep [this message]
2020-10-28 18:09 ` gregkh
2020-10-28 7:15 ` Sherry Sun
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=f64a1f67781441c8ed48b991afbf8dd2f9030289.camel@intel.com \
--to=sudeep.dutt@intel.com \
--cc=arnd@arndb.de \
--cc=ashutosh.dixit@intel.com \
--cc=corbet@lwn.net \
--cc=dmaengine@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nikhil.rao@intel.com \
--cc=sherry.sun@nxp.com \
--cc=vkoul@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 NNTP newsgroup(s).