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: <20190501144147.GA31461@kroah.com>
Date:   Wed, 1 May 2019 16:41:47 +0200
From:   Greg KH <gregkh@...uxfoundation.org>
To:     Sven Van Asbroeck <thesven73@...il.com>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] staging/fieldbus-dev for 5.2

On Wed, May 01, 2019 at 10:30:06AM -0400, Sven Van Asbroeck wrote:
> 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?

If you forward it on, I trust that one :)

But for cleanup stuff, I'll take them from anyone usually, that's what
staging is there for.  I can wait until I see a reviewed or acked tag
from you before queueing it up, if you want me to.  I do that for some
portions of staging today as the maintainers of those areas want a
chance to test/review it.

thanks,

greg k-h