From: Nick Desaulniers <ndesaulniers@google.com>
To: Greg KH <greg@kroah.com>
Cc: "# 3.4.x" <stable@vger.kernel.org>,
Pi-Hsun Shih <pihsun@chromium.org>,
Johannes Berg <johannes.berg@intel.com>
Subject: Re: [PATCH 4.19] wireless: Use offsetof instead of custom macro.
Date: Mon, 3 Aug 2020 10:16:56 -0700 [thread overview]
Message-ID: <CAKwvOdmzGh9QyS81Xxz5vSPniYBrzEnTxBdG9B48+z27DEMn2A@mail.gmail.com> (raw)
In-Reply-To: <20200801120213.GA382353@kroah.com>
On Sat, Aug 1, 2020 at 5:02 AM Greg KH <greg@kroah.com> wrote:
>
> On Fri, Jul 31, 2020 at 02:02:55PM -0700, Nick Desaulniers wrote:
> > Fix landed in v5.7-rc1. Thanks to James Hsu of MediaTek for the report.
>
> What about 5.4.y? Why ignore that tree? You can not have people moving
> from an older stable to a newer stable tree and have regressions :(
>
> I'll queue it up there, but be more careful next time please.
Yes, sorry, my mistake. I don't know what happened; perhaps I forgot
how to count.
--
Thanks,
~Nick Desaulniers
prev parent reply other threads:[~2020-08-03 17:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-31 21:02 [PATCH 4.19] wireless: Use offsetof instead of custom macro Nick Desaulniers
2020-08-01 12:02 ` Greg KH
2020-08-03 17:16 ` Nick Desaulniers [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=CAKwvOdmzGh9QyS81Xxz5vSPniYBrzEnTxBdG9B48+z27DEMn2A@mail.gmail.com \
--to=ndesaulniers@google.com \
--cc=greg@kroah.com \
--cc=johannes.berg@intel.com \
--cc=pihsun@chromium.org \
--cc=stable@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 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).