mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: florian@mickler.org
To: "John W. Linville" <linville@tuxdriver.com>
Cc: "Marcel Holtmann" <marcel@holtmann.org>,
	"Henrique de Moraes Holschuh" <hmh@hmh.eng.br>,
	"Johannes Berg" <johannes@sipsolutions.net>,
	linux-wireless@vger.kernel.org,
	"Randy Dunlap" <rdunlap@xenotime.net>,
	"Alan Jenkins" <alan-jenkins@tuffmail.co.uk>,
	linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
	Florian Mickler <florian@mickler.org>
Subject: [PATCH 0/2]  rfkill sysfs ABI
Date: Fri, 12 Mar 2010 19:03:06 +0100	[thread overview]
Message-ID: <1268416988-24862-1-git-send-email-florian@mickler.org> (raw)

Hi all!

The first patch moves the rfkill sysfs ABI Documentation to Documentation/ABI
and deprecates the state and claim file. 

The second patch creates a replacement for the state file. Instead of exporting
some made-up state we just export the state of the 2 kill lines. 

The first patch should probably go into 2.6.34, as to warn users 
(if there are any) early about this removal. 
If there is no intent to remove the broken files, the feature-removal-schedule hunk 
should probably be skipped. 

Cheers,
Flo

p.s.: first discussion of this: http://lkml.org/lkml/2010/2/22/127

Florian Mickler (2):
  Document the rfkill sysfs ABI
  enhance sysfs rfkill interface

 Documentation/ABI/obsolete/sysfs-class-rfkill |   29 +++++++++++
 Documentation/ABI/stable/sysfs-class-rfkill   |   67 +++++++++++++++++++++++++
 Documentation/feature-removal-schedule.txt    |   18 +++++++
 Documentation/rfkill.txt                      |   44 +++++-----------
 net/rfkill/core.c                             |   57 +++++++++++++++++++++
 5 files changed, 184 insertions(+), 31 deletions(-)
 create mode 100644 Documentation/ABI/obsolete/sysfs-class-rfkill
 create mode 100644 Documentation/ABI/stable/sysfs-class-rfkill


             reply	other threads:[~2010-03-12 18:03 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-12 18:03 florian [this message]
2010-03-12 18:03 ` [PATCH 1/2] Document the " florian
2010-03-12 18:03   ` [PATCH 2/2] enhance sysfs rfkill interface florian
2010-03-12 18:22     ` Dmitry Torokhov
2010-03-12 20:57       ` Florian Mickler
2010-03-12 21:20         ` Dmitry Torokhov
2010-03-12 22:39           ` Florian Mickler
2010-03-12 22:48             ` Dmitry Torokhov
2010-03-13  9:41               ` Florian Mickler
2010-03-13  9:44                 ` [PATCH] rename new rfkill sysfs knobs florian
2010-03-13  9:56                   ` Dmitry Torokhov
2010-03-13 12:31                     ` [PATCH v2] " florian
2010-03-18 10:59                       ` Florian Mickler
2010-03-18 13:42                         ` John W. Linville
2010-03-13  9:55                 ` [PATCH 2/2] enhance sysfs rfkill interface Dmitry Torokhov
2010-03-13 12:33                   ` Florian Mickler
2010-03-12 23:48             ` Valdis.Kletnieks
2010-03-12 18:18 ` [PATCH 0/2] rfkill sysfs ABI Florian Mickler
2010-03-12 19:52   ` John W. Linville

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=1268416988-24862-1-git-send-email-florian@mickler.org \
    --to=florian@mickler.org \
    --cc=alan-jenkins@tuffmail.co.uk \
    --cc=hmh@hmh.eng.br \
    --cc=johannes@sipsolutions.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=marcel@holtmann.org \
    --cc=rdunlap@xenotime.net \
    /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®