All of lore.kernel.org
 help / color / mirror / Atom feed
From: Madhumthia Prabakaran <madhumithabiw@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>, outreachy-kernel@googlegroups.com
Subject: Re: [PATCH] Staging: media: davinci_vpfe: Remove unused macros
Date: Wed, 27 Mar 2019 15:35:27 -0500	[thread overview]
Message-ID: <20190327203526.GA2510@madhuleo> (raw)
In-Reply-To: <20190327183606.GA9920@kroah.com>

On Thu, Mar 28, 2019 at 03:36:06AM +0900, Greg KH wrote:
> On Wed, Mar 27, 2019 at 12:21:50PM -0500, Madhumitha Prabakaran wrote:
> > Remove unused macros from kernel tree.
> 
> That says shat you did, but why?  What if someone wants to know this
> information in the future?  Deleting unused hardware description macros
> isn't always a good thing to do, as sometimes that is the only way
> people can find documentation on the chips involved.

I will drop this one

Thanks

> 
> thanks,
> 
> greg k-h


      reply	other threads:[~2019-03-27 20:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-27 17:21 [PATCH] Staging: media: davinci_vpfe: Remove unused macros Madhumitha Prabakaran
2019-03-27 18:36 ` Greg KH
2019-03-27 20:35   ` Madhumthia Prabakaran [this message]

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=20190327203526.GA2510@madhuleo \
    --to=madhumithabiw@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=outreachy-kernel@googlegroups.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 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.