netdev - Re: [for-next V2 00/17][PULL request] Mellanox mlx5 core driver updates 2016-08-20

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CALzJLG-eucDbJc=eo4HPvqnw-nvoXXAR1vsGPts8WFP3NR5T+Q@mail.gmail.com>
Date:   Mon, 22 Aug 2016 20:56:43 +0300
From:   Saeed Mahameed <saeedm@....mellanox.co.il>
To:     David Miller <davem@...emloft.net>
Cc:     Saeed Mahameed <saeedm@...lanox.com>,
        Doug Ledford <dledford@...hat.com>,
        Linux Netdev List <netdev@...r.kernel.org>,
        linux-rdma@...r.kernel.org, Leon Romanovsky <leonro@...lanox.com>,
        Tal Alon <talal@...lanox.com>,
        Matan Barak <matanb@...lanox.com>
Subject: Re: [for-next V2 00/17][PULL request] Mellanox mlx5 core driver
 updates 2016-08-20

On Mon, Aug 22, 2016 at 8:11 PM, David Miller <davem@...emloft.net> wrote:
>
> Sorry, too many patches.
>
> Please keep your series to 10 to 15 patches maximum.
>
> Please do not push back on this, I made several other submitters do
> the same exact thing over the past few days.

Sure. Rules are rules. I will be more strict in the future.

Technical question though. Do i need to create a new tag for the new
pull request? I mean, should the tag always point to the "up to" patch
in the pull request? or can I just use the same tag for the new pull
request with different "up to" commit ?

Thanks,
Saeed.