From: Greg KH <gregkh@linuxfoundation.org>
To: Michael Straube <straube.linux@gmail.com>
Cc: Phillip Potter <phil@philpotter.co.uk>,
Larry Finger <Larry.Finger@lwfinger.net>,
Martin Kaiser <martin@kaiser.cx>,
"Fabio M. De Francesco" <fmdefrancesco@gmail.com>,
linux-staging@lists.linux.dev,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] staging: r8188eu: use common ieee80211 constants
Date: Mon, 16 Aug 2021 09:12:33 +0200 [thread overview]
Message-ID: <YRoP4T4W9Iub1sLG@kroah.com> (raw)
In-Reply-To: <9f13258d-5fa1-aa28-e2e6-14f0721b8eb5@gmail.com>
On Sun, Aug 15, 2021 at 10:04:58AM +0200, Michael Straube wrote:
> On 8/14/21 7:36 PM, Phillip Potter wrote:
> >
> > Dear Michael,
> >
> > Constants seem to be correct values still, nice. That said, the other
> > patches that have come through from others before this prevent this
> > applying to my copy of staging-testing branch. Assuming Greg takes the
> > patches in order, this will therefore need reworking. That said, it
> > builds fine for me when applied directly to fresh staging-testing tip
> > without the patches that have come in since, so:
> >
> > Acked-by: Phillip Potter <phil@philpotter.co.uk>
> >
> > By all means apply that Acked-by to v2 if needed. Many thanks.
> >
> > Regards,
> > Phil
> >
>
> Thanks for the hint Phillip. Sure I can send v2 if needed.
>
> Greg, is this ok as is or should I send v2 rebased on staging-testing
> with other pending patches applied?
This applied just fine, no need for a v2 at all, thanks.
greg k-h
prev parent reply other threads:[~2021-08-16 7:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-14 16:55 [PATCH] staging: r8188eu: use common ieee80211 constants Michael Straube
2021-08-14 17:36 ` Phillip Potter
2021-08-15 8:04 ` Michael Straube
2021-08-16 7:12 ` 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=YRoP4T4W9Iub1sLG@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Larry.Finger@lwfinger.net \
--cc=fmdefrancesco@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=martin@kaiser.cx \
--cc=phil@philpotter.co.uk \
--cc=straube.linux@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 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.