public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Sudeep Dutt <sudeep.dutt@intel.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
	linux-kernel@vger.kernel.org, dmaengine@vger.kernel.org,
	linux-doc@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
	Vinod Koul <vkoul@kernel.org>, Sherry Sun <sherry.sun@nxp.com>,
	Ashutosh Dixit <ashutosh.dixit@intel.com>,
	Nikhil Rao <nikhil.rao@intel.com>
Subject: Re: [PATCH char-misc-next 1/1] misc: mic: remove the MIC drivers
Date: Wed, 28 Oct 2020 06:54:29 +0100	[thread overview]
Message-ID: <20201028055429.GA244117@kroah.com> (raw)
In-Reply-To: <8c1443136563de34699d2c084df478181c205db4.1603854416.git.sudeep.dutt@intel.com>

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?"

> 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?

thanks,

greg k-h

       reply	other threads:[~2020-10-29  1:01 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 ` Greg Kroah-Hartman [this message]
2020-10-28  6:04   ` [PATCH char-misc-next 1/1] misc: mic: remove the MIC drivers Vinod Koul
2020-10-28 17:22   ` Dutt, Sudeep
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=20201028055429.GA244117@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=arnd@arndb.de \
    --cc=ashutosh.dixit@intel.com \
    --cc=corbet@lwn.net \
    --cc=dmaengine@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nikhil.rao@intel.com \
    --cc=sherry.sun@nxp.com \
    --cc=sudeep.dutt@intel.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