From: Joe Perches <joe@perches.com>
To: Greg KH <gregkh@linuxfoundation.org>,
Andrew Morton <akpm@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: RFC -next: Converting dev_<level> function to return void
Date: Tue, 28 Oct 2014 13:33:13 -0700 [thread overview]
Message-ID: <1414528393.10912.6.camel@perches.com> (raw)
I believe -next currently has no more uses of the dev_<level>
return value, so it's possible to make these return void.
There are dependencies on changes in drivers/net/wireless/ath
that have just been pulled into next-20141028 but not earlier.
Given the dependencies, when would be a good time to submit
changes to these dev_<level> declarations and uses?
It's not urgent, it could wait until 3.19, but maybe sooner
is better.
reply other threads:[~2014-10-28 20:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1414528393.10912.6.camel@perches.com \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®