From: Thierry Reding <treding@nvidia.com>
To: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>,
<swarren@nvidia.com>, <pdeschrijver@nvidia.com>
Cc: <linux-kernel@vger.kernel.org>, <akpm@linux-foundation.org>,
Greg KH <gregkh@linuxfoundation.org>
Subject: Re: [PATCH] misc: Remove unused fuse/Makefile
Date: Tue, 18 Nov 2014 22:43:31 +0100 [thread overview]
Message-ID: <149c4dc1108.2771.03bddb20d4030f1f862c9d4a07956621@nvidia.com> (raw)
In-Reply-To: <546B6D14.3090807@vanguardiasur.com.ar>
On November 18, 2014 5:02:14 PM Ezequiel Garcia
<ezequiel@vanguardiasur.com.ar> wrote:
> (increasing CC list)
>
> On 10/28/2014 02:12 PM, Ezequiel Garcia wrote:
> > This commit:
> >
> > commit 783c8f4c84451bc444e314a71b447239c6ef6fd9
> > Author: Peter De Schrijver <pdeschrijver@nvidia.com>
> > Date: Thu Jun 12 18:36:37 2014 +0300
> >
> > soc/tegra: Add efuse driver for Tegra
> >
> > introduced a fuse driver in drivers/soc. While at it, an unused file
> > drivers/misc/fuse/Makefile sneaked in, apparently as a left over from
> > a previous series. Remove it.
> >
> > Signed-off-by: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
> > ---
> > drivers/misc/fuse/Makefile | 1 -
> > 1 file changed, 1 deletion(-)
> > delete mode 100644 drivers/misc/fuse/Makefile
> >
> > diff --git a/drivers/misc/fuse/Makefile b/drivers/misc/fuse/Makefile
> > deleted file mode 100644
> > index 0679c4f..0000000
> > --- a/drivers/misc/fuse/Makefile
> > +++ /dev/null
> > @@ -1 +0,0 @@
> > -obj-$(CONFIG_ARCH_TEGRA) += tegra/
> >
I sent the same patch a couple of days ago, so:
Acked-by: Thierry Reding <treding@nvidia.com>
--
nvpublic
prev parent reply other threads:[~2014-11-18 21:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-28 17:12 Ezequiel Garcia
2014-11-18 16:00 ` Ezequiel Garcia
2014-11-18 21:43 ` Thierry Reding [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=149c4dc1108.2771.03bddb20d4030f1f862c9d4a07956621@nvidia.com \
--to=treding@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=ezequiel@vanguardiasur.com.ar \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pdeschrijver@nvidia.com \
--cc=swarren@nvidia.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
all inboxes | Powered by JetHome®