mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: dbaryshkov@gmail.com
Cc: johannes@sipsolutions.net, linux-kernel@vger.kernel.org,
	netdev@vger.kernel.org, linux-wireless@vger.kernel.org,
	slapin@ossfans.org, sfr@canb.auug.org.au
Subject: Re: [PATCH 3/5] net: add NL802154 interface for configuration of 802.15.4 devices
Date: Fri, 05 Jun 2009 00:54:18 -0700 (PDT)	[thread overview]
Message-ID: <20090605.005418.07362083.davem@davemloft.net> (raw)
In-Reply-To: <20090605071529.GA7064@doriath.ww600.siemens.net>

From: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
Date: Fri, 5 Jun 2009 11:15:29 +0400

> On Fri, Jun 05, 2009 at 08:52:17AM +0200, Johannes Berg wrote:
>> On Fri, 2009-06-05 at 06:29 +0400, Dmitry Eremin-Solenikov wrote:
>> 
>> > +/* This source file is shared between kernel and userspace sources, thus
>> > + * a bit of __KERNEL__ checks
>> > + */
>> > +#ifdef __KERNEL__
>> 
>> It's a C file. It can't be shared expect by copying, hence IMO these
>> things are pointless.
> 
> It is shared by copying. And I'd strongly prefer to have it shared
> directly by 'cp', not by 'cp' and 'patch'. E.g. currently I can ensure
> that policy definitions and commands are current just by comparing
> files. I'd like to still have that ability. Thus, I'd ask to permit this
> stuff in.

You can maintain your own code in your own directories in your
own source tree however you like.

But if you want you code in the upstream kernel, you have to clean it
of things like this.

I agree with Johannes, you have to get rid of this.

  reply	other threads:[~2009-06-05  7:54 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-05  2:29 [PULL REQUEST] IEEE 802.15.4 stack: generic parts v2 Dmitry Eremin-Solenikov
2009-06-05  2:29 ` [PATCH 1/5] Add constants for the ieee 802.15.4 stack Dmitry Eremin-Solenikov
2009-06-05  2:29   ` [PATCH 2/5] net: add IEEE 802.15.4 socket family implementation Dmitry Eremin-Solenikov
2009-06-05  2:29     ` [PATCH 3/5] net: add NL802154 interface for configuration of 802.15.4 devices Dmitry Eremin-Solenikov
2009-06-05  2:29       ` [PATCH 4/5] ieee802154: add documentation about our stack Dmitry Eremin-Solenikov
2009-06-05  2:29         ` [PATCH 5/5] ieee802154: add simple HardMAC driver sample Dmitry Eremin-Solenikov
2009-06-05 13:18         ` [PATCH 4/5] ieee802154: add documentation about our stack Marcel Holtmann
2009-06-05 13:40           ` Dmitry Eremin-Solenikov
2009-06-05 14:25             ` Marcel Holtmann
2009-06-05 16:00               ` Dmitry Eremin-Solenikov
2009-06-06  7:12               ` Maxim Osipov
2009-06-05  6:52       ` [PATCH 3/5] net: add NL802154 interface for configuration of 802.15.4 devices Johannes Berg
2009-06-05  7:15         ` Dmitry Eremin-Solenikov
2009-06-05  7:54           ` David Miller [this message]
2009-06-05  9:12             ` Dmitry Eremin-Solenikov
2009-06-05  9:46               ` Sergey Lapin
2009-06-05 10:45                 ` Dmitry Eremin-Solenikov
2009-06-05 11:51                   ` Jesper Dangaard Brouer
2009-06-05 13:23                   ` Marcel Holtmann
2009-06-05 13:27                     ` Dmitry Eremin-Solenikov
2009-06-06  0:58                   ` David Miller
2009-06-06  7:06                     ` Dmitry Eremin-Solenikov
2009-06-07  1:18 [PATCH 0/5] IEEE 802.15.4 stack: generic parts v3 Sergey Lapin
2009-06-07  1:18 ` [PATCH 1/5] Add constants for the ieee 802.15.4 stack Sergey Lapin
2009-06-07  1:18   ` [PATCH 2/5] net: add IEEE 802.15.4 socket family implementation Sergey Lapin
2009-06-07  1:18     ` [PATCH 3/5] net: add NL802154 interface for configuration of 802.15.4 devices Sergey Lapin
2009-06-08 22:18 [PULL REQUEST] IEEE 802.15.4 stack: generic parts v4 Sergey Lapin
2009-06-08 22:18 ` [PATCH 1/5] Add constants for the ieee 802.15.4 stack Sergey Lapin
2009-06-08 22:18   ` [PATCH 2/5] net: add IEEE 802.15.4 socket family implementation Sergey Lapin
2009-06-08 22:18     ` [PATCH 3/5] net: add NL802154 interface for configuration of 802.15.4 devices Sergey Lapin

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=20090605.005418.07362083.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=dbaryshkov@gmail.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=slapin@ossfans.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®