linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: davidb@quicinc.com (David Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: apparently, numerous unused header files under arch/arm
Date: Wed, 30 Sep 2009 07:46:03 -0700	[thread overview]
Message-ID: <20090930144603.GC25416@huya.quicinc.com> (raw)
In-Reply-To: <alpine.LFD.2.00.0909300405080.14643@localhost>

On Wed, Sep 30, 2009 at 01:12:22AM -0700, Robert P. J. Day wrote:

> is there any interest in my posting that arm-specific list somewhere
> and people can peruse it and decide what, if anything, they want to do
> with it?

Any chance the script itself could be made available?  I would
find this useful as I'm working through large amounts of code to
get it to a state where it can be sent out as patches.

David

  reply	other threads:[~2009-09-30 14:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-30  8:12 apparently, numerous unused header files under arch/arm Robert P. J. Day
2009-09-30 14:46 ` David Brown [this message]
2009-09-30 18:21   ` Robert P. J. Day
2009-09-30 14:47 ` Bill Gatliff
2009-09-30 15:15   ` Robert P. J. Day

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=20090930144603.GC25416@huya.quicinc.com \
    --to=davidb@quicinc.com \
    --cc=linux-arm-kernel@lists.infradead.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).