From: David Miller <davem@davemloft.net>
To: tom@herbertland.com
Cc: saeedm@dev.mellanox.co.il, saeedm@mellanox.com,
dledford@redhat.com, netdev@vger.kernel.org,
linux-rdma@vger.kernel.org, leon@kernel.org
Subject: Re: [pull request][for-next] Mellanox mlx5 Reorganize core driver directory layout
Date: Thu, 19 Jan 2017 00:38:32 -0500 (EST) [thread overview]
Message-ID: <20170119.003832.1262212358977773325.davem@davemloft.net> (raw)
In-Reply-To: <CALx6S36p2g8EP48R+nWQu9tHtS5h8eKo7bj7rskmSMxCU36KXA@mail.gmail.com>
From: Tom Herbert <tom@herbertland.com>
Date: Wed, 18 Jan 2017 21:22:53 -0800
> In principle I agree, but as I previously wrote backporting this
> driver is already a bear. We need to do something here as this is
> quickly approaching being infeasible to backport. Even if we don't
> restructure the directories I'd still like to see some effort towards
> feature modularization and isolation.
There simply is a lot changing all the time, no restructuring is going
to reduce that. The driver simply gets a lot of churn.
Backporting such things through a bunch of file and/or directory
renames is seriously nothing but asking for more punishment.
That's why I am against it.
next prev parent reply other threads:[~2017-01-19 5:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-12 17:22 [pull request][for-next] Mellanox mlx5 Reorganize core driver directory layout Saeed Mahameed
2017-01-12 17:22 ` [for-next] {net, IB}/mlx5: Reorganize driver file layout Saeed Mahameed
[not found] ` <1484241755-17603-1-git-send-email-saeedm-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2017-01-13 17:14 ` [pull request][for-next] Mellanox mlx5 Reorganize core driver directory layout David Miller
2017-01-13 20:29 ` Leon Romanovsky
2017-01-13 22:06 ` Tom Herbert
2017-01-13 22:45 ` Saeed Mahameed
[not found] ` <CALzJLG_RsvgszVxGZ7+VgYjET9w=XTjq36Z72diOQFNJWz9tQw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-01-13 22:56 ` Tom Herbert
[not found] ` <CALx6S35cSnMoBtxi+Eb_mH=LCLy9yY6U5sxofndce9r0eCs8+w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-01-13 22:59 ` Rick Jones
[not found] ` <10e998b7-0008-2f26-2874-57ec61c8cacb-ZPxbGqLxI0U@public.gmane.org>
2017-01-13 23:07 ` Tom Herbert
2017-01-16 20:15 ` Saeed Mahameed
2017-01-14 17:37 ` Tom Herbert
[not found] ` <CALx6S37FHv3d0_hsXd63m37CEgT4N8myjUey29iDo1DRR=T9tQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-01-15 7:20 ` Leon Romanovsky
2017-01-13 22:07 ` Saeed Mahameed
[not found] ` <CALzJLG_fjiGyuB_buZqOSMU7SaCnuqFiZ0UyW+hPDq+3yx7TWg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-01-16 20:30 ` Saeed Mahameed
2017-01-16 21:06 ` Tom Herbert
[not found] ` <CALx6S377hzH8_DbUSKafkbCzMEunr0H7vrfcb2WfEWFHFnfUpw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-01-16 23:36 ` Saeed Mahameed
[not found] ` <CALzJLG--ZRVk0Zy+6UaGCWbOhki+PZnkmrh9rjojU1ZDm_5Y6w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-01-18 17:32 ` David Miller
2017-01-19 5:22 ` Tom Herbert
2017-01-19 5:38 ` David Miller [this message]
2017-01-19 6:32 ` Doug Ledford
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=20170119.003832.1262212358977773325.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dledford@redhat.com \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=saeedm@dev.mellanox.co.il \
--cc=saeedm@mellanox.com \
--cc=tom@herbertland.com \
/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;
as well as URLs for NNTP newsgroup(s).