linux-kernel - Re: [GIT PULL] staging/fieldbus-dev for 5.2

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: <CAGngYiVznEOQk-Tbyh6km+=+70gJebBEATxN5A8OE6iEzrHXqA@mail.gmail.com>
Date:   Wed, 1 May 2019 10:30:06 -0400
From:   Sven Van Asbroeck <thesven73@...il.com>
To:     Greg KH <gregkh@...uxfoundation.org>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] staging/fieldbus-dev for 5.2

On Wed, May 1, 2019 at 10:24 AM Greg KH <gregkh@...uxfoundation.org> wrote:
>
> And as this is just a single patch, handling them as patches is much
> easier anyway.  Only when you get into the 20+ at a time does pull
> requests help.
>

Patches are much easier for me too, but I assumed this had to be done via a
pull request.

How do you distinguish between a patch that's still spinning on the
mailing list,
and one coming from my next tree? The Reviewed-by or Acked-by tag?

Patch coming up, thanks :)