From: Larry Finger <Larry.Finger@lwfinger.net>
To: Phillip Potter <phil@philpotter.co.uk>
Cc: gregkh@linuxfoundation.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org,
Dan Carpenter <dan.carpenter@oracle.com>
Subject: Re: [PATCH v3 0/2] Fix some compile warnings in v5.18+
Date: Tue, 31 May 2022 12:16:58 -0500 [thread overview]
Message-ID: <bf78b567-5c69-c968-3dc4-6c94eeb8d77a@lwfinger.net> (raw)
In-Reply-To: <YpW4WKxKIIgY0l7m@equinox>
On 5/31/22 01:40, Phillip Potter wrote:
>
> Hi Larry,
>
> Both patches look good to me, however I've already submitted a patch 10
> days ago that does exactly what your rtw_xmit.c patch does, in
> addition to fixing the changed error handling semantics for the relevant
> function (in f94b47c6bde6) which broke the driver.
Phil,
Sorry I missed your patch. I have been really busy the past month on another
problem, and I was not paying much attention to r8188eu.
When I built a mainline kernel in the middle of the merge from 5.18 to 5.19,
those two warnings stood out.
Your patch should be ahead of mine in Greg's queue, thus mine should fail, and I
will get the "does not apply" message. At that time, I will send the other
patch. As both of us missed the 5.19 merge, the build warnings will persist
until 5.20, but no harm.
Larry
next prev parent reply other threads:[~2022-05-31 17:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-31 1:31 [PATCH v3 0/2] Fix some compile warnings in v5.18+ Larry Finger
2022-05-31 1:31 ` [PATCH v3 1/2] staging: r8188eu: Fix undersized array in rtw_xmit.c Larry Finger
2022-05-31 7:25 ` Dan Carpenter
2022-05-31 1:31 ` [PATCH v3 2/2] staging: r8188eu: Fix warning of array overflow in ioctl_linux.c Larry Finger
2022-05-31 6:40 ` [PATCH v3 0/2] Fix some compile warnings in v5.18+ Phillip Potter
2022-05-31 17:16 ` Larry Finger [this message]
2022-05-31 18:44 ` Phillip Potter
2022-06-06 6:10 ` Greg KH
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=bf78b567-5c69-c968-3dc4-6c94eeb8d77a@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=dan.carpenter@oracle.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=phil@philpotter.co.uk \
/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.