From: Andy Gospodarek <andy@greyhouse.net>
To: Or Gerlitz <gerlitz.or@gmail.com>
Cc: Linux Netdev List <netdev@vger.kernel.org>,
mchan@broadcom.com, Tal Gilboa <talgi@mellanox.com>,
Or Gerlitz <ogerlitz@mellanox.com>,
Andy Gospodarek <gospo@broadcom.com>
Subject: Re: [net-next 00/10] net: create dynamic software irq moderation library
Date: Thu, 4 Jan 2018 17:46:44 -0500 [thread overview]
Message-ID: <20180104224644.GB64505@C02RW35GFVH8> (raw)
In-Reply-To: <CAJ3xEMhSGCbYVA2dwgbtFObHb--GQZcUJv6SOQkJ_GDOjw4VeA@mail.gmail.com>
On Thu, Jan 04, 2018 at 10:37:37PM +0200, Or Gerlitz wrote:
> > net/mlx5e: move interrupt moderation structs to new file
> > net/mlx5e: move interrupt moderation forward declarations
> > net/mlx5e: remove rq references in mlx5e_rx_am
> > net/mlx5e: move AM logic enums
> > net/mlx5e: move generic functions to new file
> > net/mlx5e: change Mellanox references in DIM code
>
> Hi, Andy && happy new 2018 -- this is indeed a nit, but I have
> provided it to you twice (...),
> please get the commit titles to align with what we do which is capital
> letter after the net/mlx5e: prefix
>
> from: net/mlx5e: move interrupt moderation structs to new file
> to: net/mlx5e: Move interrupt moderation structs to new file
>
> If you get other comments, just apply this for the next version, if everyone
> is happy, that would be a very small effort to just fix and get that in..
Or, you did mention this part and I'm _really_ sorry to forgot to add
the capitalization. I will do that if there is a v2 (which is looks
like there might be since I cannot spell 'Maintained' correctly.
next prev parent reply other threads:[~2018-01-04 22:46 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-04 20:21 [net-next 00/10] net: create dynamic software irq moderation library Andy Gospodarek
2018-01-04 20:21 ` [net-next 01/10] net/mlx5e: move interrupt moderation structs to new file Andy Gospodarek
2018-01-04 20:21 ` [net-next 02/10] net/mlx5e: move interrupt moderation forward declarations Andy Gospodarek
2018-01-04 20:21 ` [net-next 03/10] net/mlx5e: remove rq references in mlx5e_rx_am Andy Gospodarek
2018-01-04 20:21 ` [net-next 04/10] net/mlx5e: move AM logic enums Andy Gospodarek
2018-01-04 20:21 ` [net-next 05/10] net/mlx5e: move generic functions to new file Andy Gospodarek
2018-01-04 20:21 ` [net-next 06/10] net/mlx5e: change Mellanox references in DIM code Andy Gospodarek
2018-01-05 8:04 ` Tal Gilboa
2018-01-05 13:55 ` Andy Gospodarek
2018-01-05 20:57 ` Andy Gospodarek
2018-01-04 20:21 ` [net-next 07/10] net: move dynamic interrupt coalescing code to include/linux Andy Gospodarek
2018-01-04 20:21 ` [net-next 08/10] net/dim: use struct net_dim_sample as arg to net_dim Andy Gospodarek
2018-01-05 8:13 ` Tal Gilboa
2018-01-04 20:21 ` [net-next 09/10] bnxt_en: add support for software dynamic interrupt moderation Andy Gospodarek
2018-01-04 22:16 ` Michael Chan
2018-01-05 13:44 ` Andy Gospodarek
2018-01-04 20:21 ` [net-next 10/10] MAINTAINERS: add entry for Dynamic Interrupt Moderation Andy Gospodarek
2018-01-04 22:36 ` Stephen Hemminger
2018-01-04 22:45 ` Andy Gospodarek
2018-01-04 20:37 ` [net-next 00/10] net: create dynamic software irq moderation library Or Gerlitz
2018-01-04 22:46 ` Andy Gospodarek [this message]
2018-01-04 21:37 ` Saeed Mahameed
2018-01-05 8:14 ` Tal Gilboa
2018-01-05 13:48 ` Andy Gospodarek
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=20180104224644.GB64505@C02RW35GFVH8 \
--to=andy@greyhouse.net \
--cc=gerlitz.or@gmail.com \
--cc=gospo@broadcom.com \
--cc=mchan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=ogerlitz@mellanox.com \
--cc=talgi@mellanox.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