From: Michel Machado <michel@digirati.com.br>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Daniel Borkmann <daniel@iogearbox.net>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Linux XIA - merge proposal
Date: Wed, 04 Mar 2015 08:01:04 -0500 [thread overview]
Message-ID: <54F70210.5070900@digirati.com.br> (raw)
In-Reply-To: <20150304054924.GA27610@kroah.com>
On 03/04/2015 12:49 AM, Greg KH wrote:
> On Tue, Mar 03, 2015 at 07:31:58PM -0500, Michel Machado wrote:
>> Hi Daniel,
>>
>>>> We're fine with clearly marking Linux XIA as being under staging
>>>> as well as helping to define this review process for network stacks.
>>>
>>> With regard to staging, the code there is usually horrible and I'm
>>> not sure anyone really looks there, that would mitigate the review
>>> problem to the time when you try to get it out from there, so I'm
>>> not sure it brings anything. ;)
>>
>> I suggested staging as a way to incrementally review the code.
>
> Yet you failed to at least ask the maintainer of the staging portion of
> the kernel, if this is a valid use of staging, and his resources...
>
> Not nice :(
>
> greg k-h
Hi Greg,
I am sorry for having not asked you. Given that the staging process
doesn't include network stacks, I'd thought that the correct way to go
would be to bring the discussion to netdev first. Please understand that
I'm not gaming, I'm just following my best understanding of the
documentation of how to submit code. I'm really in uncharted waters here
since all my accepted patches are tiny.
In addition, I intend to work on the feedback I get. I'm not
planning to have the code upstream and run away.
[ ]'s
Michel Machado
next prev parent reply other threads:[~2015-03-04 13:01 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-03 17:29 Linux XIA - merge proposal Michel Machado
2015-03-03 23:33 ` Eric W. Biederman
2015-03-04 0:14 ` Michel Machado
2015-03-04 0:01 ` Daniel Borkmann
2015-03-04 0:31 ` Michel Machado
2015-03-04 5:49 ` Greg KH
2015-03-04 13:01 ` Michel Machado [this message]
2015-03-05 16:31 ` Alex Elsayed
2015-03-05 18:34 ` Michel Machado
2015-03-10 17:01 ` Bjorn Helgaas
2015-03-10 17:19 ` Eric Dumazet
2015-03-10 22:01 ` Bjorn Helgaas
2015-03-13 15:26 ` Michel Machado
2015-03-15 9:37 ` Greg KH
2015-03-15 10:03 ` Oded Gabbay
2015-03-17 12:37 ` Michel Machado
2015-03-17 12:25 ` Michel Machado
2015-03-18 10:27 ` Oded Gabbay
2015-03-20 18:46 ` Michel Machado
2015-03-20 19:41 ` Bjorn Helgaas
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=54F70210.5070900@digirati.com.br \
--to=michel@digirati.com.br \
--cc=daniel@iogearbox.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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