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: <CAP5jrPH5kQzqzeQwmynOYLisbzL1TUf=AwA=cRbCtxU4Y6dp9Q@mail.gmail.com>
Date:   Thu, 27 Apr 2023 22:57:27 -0600
From:   Max Georgiev <glipus@...il.com>
To:     Köry Maincent <kory.maincent@...tlin.com>
Cc:     kuba@...nel.org, netdev@...r.kernel.org,
        maxime.chevallier@...tlin.com, vladimir.oltean@....com,
        vadim.fedorenko@...ux.dev, richardcochran@...il.com,
        gerhard@...leder-embedded.com, thomas.petazzoni@...tlin.com
Subject: Re: [RFC PATCH v4 0/5] New NDO methods ndo_hwtstamp_get/set

Sorry, I'm still learning the kernel patch communication rules.
Thank you for guiding me here.

On Thu, Apr 27, 2023 at 2:43 AM Köry Maincent <kory.maincent@...tlin.com> wrote:
>
> On Wed, 26 Apr 2023 22:00:43 -0600
> Max Georgiev <glipus@...il.com> wrote:
>
> >
> > Thank you for giving it a try!
> > I'll drop the RFC tag starting from the next iteration.
>
> Sorry I didn't know the net-next submission rules. In fact keep the RFC tag
> until net-next open again.
> http://vger.kernel.org/~davem/net-next.html
>
> Your patch series don't appear in the cover letter thread:
> https://lore.kernel.org/all/20230423032437.285014-1-glipus@gmail.com/
> I don't know if it comes from your e-mail or just some issue from lore but could
> you check it?

Could you please elaborate what's missing in the cover letter?
Should the cover letter contain the latest version of the patch
stack (v4, then v5, etc.) and some description of the differences
between the patch versions?
Let me look up some written guidance on this.

>
> Please add "net:" prefix to your patches commit title when changing the net
> core, "macvlan:" prefix for macvlan driver change, etc ...

Will certainly add tem.

>
> Also I see you forgot "net-next" to the subject prefix in this iteration please
> don't in next one.

My bad, will add it back.

>
> Thanks for your work!

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ