From: Brian Norris <briannorris@chromium.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: jonathanh@nvidia.com, bleung@chromium.org, dianders@chromium.org,
lee.jones@linaro.org, stable@vger.kernel.org,
stable-commits@vger.kernel.org
Subject: Re: Patch "mfd: cros ec: spi: Don't send first message too soon" has been added to the 3.18-stable tree
Date: Wed, 3 Jan 2018 12:35:45 -0800 [thread overview]
Message-ID: <20180103203543.GA232288@google.com> (raw)
In-Reply-To: <20180103194425.GC25621@kroah.com>
On Wed, Jan 03, 2018 at 08:44:25PM +0100, Greg Kroah-Hartman wrote:
> On Wed, Jan 03, 2018 at 10:49:21AM -0800, Brian Norris wrote:
> > Umm, that's not even close to correct? You've stuck this line just below
> > the headers... You may still need to adjust for some context changes in
> > 3.18 vs. Linus' latest, but this should at least be in
> > cros_ec_spi_probe().
> >
> > (The kbuild bots are complaining about your RC branch.)
>
> This was long fixed, did your email just sync?
No. I see no update in my mail (neither in reply to this thread nor to
the kbuild email I saw). However, I also don't see this patch in your
stable-rc repo now, so maybe you just backed the change out? Perhaps
there's some thread(s) where I'm CC'd and some where I'm not?
Anyway, if you aren't applying the previously-quoted patch, then we're
OK for now :) It might be good to see a corrected version of this show
up in 3.18 -stable still.
Brian
next prev parent reply other threads:[~2018-01-03 20:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-27 15:24 Patch "mfd: cros ec: spi: Don't send first message too soon" has been added to the 3.18-stable tree gregkh
2018-01-03 18:49 ` Brian Norris
2018-01-03 19:44 ` Greg KH
2018-01-03 20:35 ` Brian Norris [this message]
2018-01-03 20:52 ` 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=20180103203543.GA232288@google.com \
--to=briannorris@chromium.org \
--cc=bleung@chromium.org \
--cc=dianders@chromium.org \
--cc=gregkh@linuxfoundation.org \
--cc=jonathanh@nvidia.com \
--cc=lee.jones@linaro.org \
--cc=stable-commits@vger.kernel.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 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.