linux-kernel - Re: [PATCH] Linux 6.1.9

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 for Android: free password hash cracker in your pocket

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

Date:   Fri, 3 Feb 2023 17:12:42 +0700
From:   Bagas Sanjaya <bagasdotme@...il.com>
To:     Vinayak Hegde <vinayakph123@...il.com>
Cc:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Florian Fainelli <f.fainelli@...il.com>,
        Shuah Khan <skhan@...uxfoundation.org>,
        Conor Dooley <conor.dooley@...rochip.com>,
        "Justin M . Forbes" <jforbes@...oraproject.org>,
        Takeshi Ogasawara <takeshi.ogasawara@...uring-girl.com>,
        Ronald Warsow <rwarsow@....de>,
        Guenter Roeck <linux@...ck-us.net>,
        Sudip Mukherjee <sudip.mukherjee@...ethink.co.uk>,
        Salvatore Bonaccorso <carnil@...ian.org>,
        Jon Hunter <jonathanh@...dia.com>,
        Linux Kernel Functional Testing <lkft@...aro.org>,
        Allen Pais <apais@...ux.microsoft.com>,
        Fenil Jain <fkjainco@...il.com>, Ron Economos <re@...z.net>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Stable <stable@...r.kernel.org>
Subject: Re: [PATCH] Linux 6.1.9

On 2/3/23 16:42, Vinayak Hegde wrote:
> Hi Everyone,
> I was going through A Beginner's Guide to Linux Kernel Development (LFD103) course and was trying out a few things
> mistakenly sending this mail.
> 

Hi and welcome to LKML!

Some netiquette tips:

* Don't top-post when replying; reply inline with appropriate context
  instead. Some people (like me) tends to cut quoted reply below
  if you top-post.
* Don't send HTML emails - many kernel development lists (including
  LKML) don't like them for being common spam method.
* Wait for at least a day before replying - people may respond to
  your message at different pace.
* Use git-send-email(1) to submit patches (see
  Documentation/process/submitting-patches.rst for how to do that).

Regarding your patch, I think Greg has already bumped SUBLEVEL
whenever new stable release is made, so no need to send separate
patch just for that.

Thanks.

-- 
An old man doll... just what I always wanted! - Clara