From: Mike Frysinger <vapier.adi@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: zbr@ioremap.net, linux-kernel@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: [PATCH 1/3] connector: make callback argument type explicit
Date: Fri, 17 Jul 2009 23:45:35 -0400 [thread overview]
Message-ID: <8bd0f97a0907172045j2cff6987xb7ea0aab438bef9d@mail.gmail.com> (raw)
In-Reply-To: <20090717.101550.223298982.davem@davemloft.net>
On Fri, Jul 17, 2009 at 13:15, David Miller wrote:
> From: Evgeniy Polyakov <zbr@ioremap.net>
>>
>> Your patches look good, thanks a lot.
>> David, please apply to the appropriate tree.
>
> Applied to net-next-2.6, but I am being very generous.
>
> In the future please make sure netdev@vger.kernel.org receives all
> networking patch postings so that they properly get tracked at:
>
> http://patchwork.ozlabs.org/project/netdev/list/
>
> Otherwise they risk getting lost.
the fact that the connector code is maintained in the net tree is not
mentioned anywhere that i can see. it isnt in net/, it isnt in
drivers/net/, and it isnt in MAINTAINERS. that means anyone who
wishes to submit patches has to basically guess where to send them.
going by the default rules, that means the author (Evgeniy) and LKML.
expecting people to magically divine net ownership with this driver is
ridiculous.
-mike
next prev parent reply other threads:[~2009-07-18 3:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-15 22:14 Mike Frysinger
2009-07-15 22:14 ` [PATCH 2/3] connector: clean up grammar/style in documentation Mike Frysinger
2009-07-16 9:15 ` Will Newton
2009-07-16 17:58 ` [PATCH 2/3 v2] " Mike Frysinger
2009-07-15 22:14 ` [PATCH 3/3] connector: get test code working by default Mike Frysinger
2009-07-16 10:19 ` [PATCH 1/3] connector: make callback argument type explicit Evgeniy Polyakov
2009-07-17 17:15 ` David Miller
2009-07-18 3:45 ` Mike Frysinger [this message]
2009-07-18 5:33 ` Andrew Morton
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=8bd0f97a0907172045j2cff6987xb7ea0aab438bef9d@mail.gmail.com \
--to=vapier.adi@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=zbr@ioremap.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®