All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Cc: Paul Cercueil <paul@crapouillou.net>,
	Harvey Hunt <harveyhuntnexus@gmail.com>,
	linux-mips@vger.kernel.org
Subject: Re: [PATCH] MIPS: ingenic: remove unused platform_data header file
Date: Tue, 27 Oct 2020 17:30:29 +0100	[thread overview]
Message-ID: <20201027163029.GA442200@ravnborg.org> (raw)
In-Reply-To: <20201027121043.GB13777@alpha.franken.de>

Hi Thomas,

On Tue, Oct 27, 2020 at 01:10:43PM +0100, Thomas Bogendoerfer wrote:
> On Mon, Oct 26, 2020 at 08:20:40PM +0100, Sam Ravnborg wrote:
> > There are no users of this headers file in the kernel.
> > All users are likely migrated to device tree which is a good thing.
> > 
> > Signed-off-by: Sam Ravnborg <sam@ravnborg.org>
> > Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
> > Cc: Paul Cercueil <paul@crapouillou.net>
> > Cc: Harvey Hunt <harveyhuntnexus@gmail.com>
> > Cc: linux-mips@vger.kernel.org
> > ---
> > 
> > I noticed this while surfing around in platform_data for no apperant
> > reason. So no fancy tooling or some such involved.
> > 
> > 	Sam
> > 
> >  .../linux/platform_data/jz4740/jz4740_nand.h  | 25 -------------------
> >  1 file changed, 25 deletions(-)
> >  delete mode 100644 include/linux/platform_data/jz4740/jz4740_nand.h
> 
> applied to mips-next.

Thanks for the quick response. Hopefully I can contribute something a little
more useful next time :-)

But then cleaning out old cruft is never a waste of time.

	Sam

      reply	other threads:[~2020-10-27 16:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-26 19:20 [PATCH] MIPS: ingenic: remove unused platform_data header file Sam Ravnborg
2020-10-26 22:16 ` Paul Cercueil
2020-10-27 12:10 ` Thomas Bogendoerfer
2020-10-27 16:30   ` Sam Ravnborg [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=20201027163029.GA442200@ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=harveyhuntnexus@gmail.com \
    --cc=linux-mips@vger.kernel.org \
    --cc=paul@crapouillou.net \
    --cc=tsbogend@alpha.franken.de \
    /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.