All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Perez-Gonzalez, Inaky" <inaky.perez-gonzalez@intel.com>
To: Randy Dunlap <rdunlap@xenotime.net>, lkml <linux-kernel@vger.kernel.org>
Cc: linux-wimax <linux-wimax@intel.com>,
	"wimax@linuxwimax.org" <wimax@linuxwimax.org>
Subject: RE: [PATCH 1/1] wimax: delete struct wimax_dev field rfkill_input
Date: Mon, 11 Jul 2011 09:33:58 -0700	[thread overview]
Message-ID: <8F0C2E89B9AA20448D482EB589641EB3010264C7E2@orsmsx507.amr.corp.intel.com> (raw)
In-Reply-To: <1310350888180@xenotime.net>


Hi Randy

>From: Randy Dunlap <rdunlap@xenotime.net>
>
> "make htmldocs" warns that struct member "rfkill_input" does not have
> a description.  After searching all kernel .[hc] files, this field
> is not used, so remove it.

Vitaly sent a patch a couple weeks ago to do this same cleanup.

Thank you anyway!

  reply	other threads:[~2011-07-11 16:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-11  2:21 [PATCH 1/1] wimax: delete struct wimax_dev field rfkill_input Randy Dunlap
2011-07-11 16:33 ` Perez-Gonzalez, Inaky [this message]
2011-07-13 14:05   ` Vitaliy Ivanov

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=8F0C2E89B9AA20448D482EB589641EB3010264C7E2@orsmsx507.amr.corp.intel.com \
    --to=inaky.perez-gonzalez@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wimax@intel.com \
    --cc=rdunlap@xenotime.net \
    --cc=wimax@linuxwimax.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 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.