From: David Miller <davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
To: saeedm-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org
Cc: dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org
Subject: Re: [pull request][for-next] Mellanox mlx5 Reorganize core driver directory layout
Date: Fri, 13 Jan 2017 12:14:07 -0500 (EST) [thread overview]
Message-ID: <20170113.121407.448230751444957957.davem@davemloft.net> (raw)
In-Reply-To: <1484241755-17603-1-git-send-email-saeedm-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
From: Saeed Mahameed <saeedm-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
Date: Thu, 12 Jan 2017 19:22:34 +0200
> This pull request includes one patch from Leon, this patch as described
> below will change the driver directory structure and layout for better,
> logical and modular driver files separation.
>
> This change is important to both rdma and net maintainers in order to
> have smoother management of driver patches for different mlx5 sub modules
> and smoother rdma-next vs. net-next features submissions.
>
> Please find more info below -in the tag commit message-,
> review and let us know if there's any problem.
>
> This change doesn't introduce any conflicts with the current mlx5
> fixes and cleanups posted on 2017-01-10 to net branch, and merge tests
> worked flawlessly with no issues.
>
> This is the last pull request meant for both rdma-next and net-next.
> Once pulled, this will be the base shared code for both trees.
This is pretty crazy, it will make all bug fix backporting to -stable
a complete nightmare for myself, Doug, various distribution maintainers
and many other people who quietly have to maintain their own trees and
do backporting.
I really don't think you can justify this rearrangement based upon the
consequences and how much activity happens in this driver.
You should have thought long and hard about the layout a long time ago
rather than after the driver has been in the tree for many years.
Sorry.
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-01-13 17:14 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 ` David Miller [this message]
2017-01-13 20:29 ` [pull request][for-next] Mellanox mlx5 Reorganize core driver directory layout 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
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=20170113.121407.448230751444957957.davem@davemloft.net \
--to=davem-ft/pcqaiutieiz0/mpfg9q@public.gmane.org \
--cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=saeedm-VPRAkNaXOzVWk0Htik3J/w@public.gmane.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;
as well as URLs for NNTP newsgroup(s).