linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Sven Van Asbroeck <thesven73@gmail.com>
Cc: devel@driverdev.osuosl.org, YueHaibing <yuehaibing@huawei.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 -next] staging: fieldbus: Fix build error without CONFIG_REGMAP_MMIO
Date: Mon, 10 Jun 2019 16:09:47 +0200	[thread overview]
Message-ID: <20190610140947.GB18627@kroah.com> (raw)
In-Reply-To: <CAGngYiV9XsPL8Mk9_K9=0a-k6P6JN_waJvk5bDH+mDwGMAYbmw@mail.gmail.com>

On Mon, Jun 10, 2019 at 08:51:10AM -0400, Sven Van Asbroeck wrote:
> Hello Greg, just a friendly ping regarding this patch. It got my Reviewed-by tag
> two weeks ago, no further feedback from anyone. Is there anything you would
> like us to do before queuing this?
> 
> Link to v2 that got the Reviewed-by:
> https://lkml.org/lkml/2019/5/28/609
> 
> On Tue, May 28, 2019 at 1:31 PM Sven Van Asbroeck <thesven73@gmail.com> wrote:
> > For the v2 patch:
> > Reviewed-by: Sven Van Asbroeck <TheSven73@gmail.com>

Odd, sorry, must have fell through the cracks, I'll pick it up now.

thanks,

greg k-h

  reply	other threads:[~2019-06-10 14:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-28 13:32 [PATCH -next] staging: fieldbus: Fix build error without CONFIG_REGMAP_MMIO YueHaibing
2019-05-28 13:41 ` Sven Van Asbroeck
2019-05-28 14:10   ` YueHaibing
2019-05-28 14:29   ` [PATCH v2 " YueHaibing
2019-05-28 14:35     ` Sven Van Asbroeck
2019-05-28 15:41       ` YueHaibing
2019-05-28 15:59         ` Greg KH
2019-05-28 17:31           ` Sven Van Asbroeck
2019-06-10 12:51             ` Sven Van Asbroeck
2019-06-10 14:09               ` Greg KH [this message]
2019-05-28 14:36     ` YueHaibing

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=20190610140947.GB18627@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=devel@driverdev.osuosl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thesven73@gmail.com \
    --cc=yuehaibing@huawei.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;
as well as URLs for NNTP newsgroup(s).