All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: "Zavras, Alexios" <alexios.zavras@intel.com>
Cc: "linux-spdx@vger.kernel.org" <linux-spdx@vger.kernel.org>
Subject: Re: are more reviewers required?
Date: Mon, 27 May 2019 12:11:53 +0200	[thread overview]
Message-ID: <20190527101153.GA1060@kroah.com> (raw)
In-Reply-To: <20190527092957.GA27222@kroah.com>

On Mon, May 27, 2019 at 11:29:57AM +0200, Greg KH wrote:
> On Mon, May 27, 2019 at 08:48:39AM +0000, Zavras, Alexios wrote:
> > Hi all,
> > 
> > I just got back from a week off and found my mailbox full patches and reviews 😉.
> > A quick look shows that almost everything has already been ACK'ed by Allison, Richard and Kate.
> > Is there need/use for me to provide another "Reviewed-by"
> > today/tomorrow? I don't mind going through the list, but if the task
> > is already done, it will be useless...
> 
> Patches from batches 1-5 that had no objections are all now merged
> upstream and are in the 5.2-rcw kernel release, so there's nothing we
> can do about reviewing them now, unless you have objections to some
> specific things that we need to revisit.
> 
> Batch 6 you can still review, as I have not queued them up.  Note that
> I, and Thomas, are traveling this week to a conference, so either that
> means we will react to these slower, or faster, than normal, depending
> on how interesting the talks are :)

And now there are 50 more patches for you to review :)

thanks,

greg k-h

      reply	other threads:[~2019-05-27 10:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-27  8:48 are more reviewers required? Zavras, Alexios
2019-05-27  9:29 ` Greg KH
2019-05-27 10:11   ` Greg KH [this message]

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=20190527101153.GA1060@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=alexios.zavras@intel.com \
    --cc=linux-spdx@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.