From: Greg KH <gregkh@linuxfoundation.org>
To: Sven Van Asbroeck <thesven73@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] staging/fieldbus-dev for 5.2
Date: Wed, 1 May 2019 16:41:47 +0200 [thread overview]
Message-ID: <20190501144147.GA31461@kroah.com> (raw)
In-Reply-To: <CAGngYiVznEOQk-Tbyh6km+=+70gJebBEATxN5A8OE6iEzrHXqA@mail.gmail.com>
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@linuxfoundation.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
next prev parent reply other threads:[~2019-05-01 14:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-01 14:06 Sven Van Asbroeck
2019-05-01 14:23 ` Greg KH
2019-05-01 14:24 ` Greg KH
2019-05-01 14:30 ` Sven Van Asbroeck
2019-05-01 14:41 ` Greg KH [this message]
2019-05-01 14:33 ` Sven Van Asbroeck
2019-05-01 14:43 ` Greg KH
2019-05-01 14:46 ` Sven Van Asbroeck
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=20190501144147.GA31461@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=thesven73@gmail.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
all inboxes | Powered by JetHome®