From: Greg KH <gregkh@suse.de>
To: Vipin Mehta <Vipin.Mehta@Atheros.com>
Cc: Andy Shevchenko <andy.shevchenko@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>
Subject: Re: [PATCH 2/2] staging: ath6kl: use native methods from kernel library
Date: Tue, 7 Sep 2010 17:03:31 -0700 [thread overview]
Message-ID: <20100908000331.GA15785@suse.de> (raw)
In-Reply-To: <35B17FE5076C7040809188FBE7913F983F23479F74@SC1EXMB-MBCL.global.atheros.com>
On Tue, Sep 07, 2010 at 02:18:02PM -0700, Vipin Mehta wrote:
> Andy,
> Thanks for the patch. Although the driver supports Linux but it has
> been architected to support other OSes if desired. The code is,
> therefore, organized into generic and OS specific components with the
> latter part of the code captured into the os/linux directory. As such,
> the patch will be more useful if we can move out the inclusion of
> linux specific header files <linux/kernel.h> and <linux/ctype.h> into
> a header file in os/linux/include directory.
Ick, no.
The driver is now in the main kernel tree, the "compatiblity" wrappers
are to now be removed as the kernel code does not need to run on any
other operating systems.
That whole subdir needs to be deleted entirely.
> You can refer to
> os/linux/include/osapi_linux.h for example. A macro could be defined
> which would use linux specific APIs for Linux and keep the original
> definitions for any other OS.
Again, no, this is not ok at all. If you are going to insist on trying
to do this for the driver, I will just delete it from the tree right now
as that is now how kernel development happens, sorry.
thanks,
greg k-h
next prev parent reply other threads:[~2010-09-08 0:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-07 15:20 [PATCH 1/2] staging: rtl8712: throw away custom hex_to_bin() Andy Shevchenko
2010-09-07 15:20 ` [PATCH 2/2] staging: ath6kl: use native methods from kernel library Andy Shevchenko
2010-09-07 21:18 ` Vipin Mehta
2010-09-07 22:26 ` Andy Shevchenko
2010-09-08 0:03 ` Greg KH [this message]
2010-09-08 2:29 ` Vipin Mehta
2010-09-08 7:08 ` Greg KH
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=20100908000331.GA15785@suse.de \
--to=gregkh@suse.de \
--cc=Vipin.Mehta@Atheros.com \
--cc=andy.shevchenko@gmail.com \
--cc=devel@driverdev.osuosl.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