From: Brian Norris <briannorris@chromium.org>
To: Lee Jones <lee.jones@linaro.org>
Cc: Olof Johansson <olof@lixom.net>,
Benson Leung <bleung@chromium.org>,
linux-kernel@vger.kernel.org,
Doug Anderson <dianders@chromium.org>,
Brian Norris <computersforpeace@gmail.com>,
Javier Martinez Canillas <javier@osg.samsung.com>,
Shawn Nematbakhsh <shawnn@chromium.org>,
Gwendal Grignou <gwendal@chromium.org>,
Enric Balletbo <enric.balletbo@collabora.co.uk>,
Tomeu Vizoso <tomeu.vizoso@collabora.com>
Subject: Re: [PATCH] mfd: cros_ec: Use proper protocol transfer function
Date: Mon, 28 Nov 2016 14:13:21 -0800 [thread overview]
Message-ID: <20161128221320.GA55972@google.com> (raw)
In-Reply-To: <20161123083749.GN10134@dell.home>
Hi Lee,
On Wed, Nov 23, 2016 at 08:37:49AM +0000, Lee Jones wrote:
> On Tue, 22 Nov 2016, Brian Norris wrote:
> > On Wed, Aug 10, 2016 at 01:45:12PM -0700, Brian Norris wrote:
> > > From: Shawn Nematbakhsh <shawnn@chromium.org>
> > >
> > > pkt_xfer should be used for protocol v3, and cmd_xfer otherwise. We had
> > > one instance of these functions correct, but not the second, fall-back
> > > case. We use the fall-back only when the first command returns an
> > > IN_PROGRESS status, which is only used on some EC firmwares where we
> > > don't want to constantly poll the bus, but instead back off and
> > > sleep/retry for a little while.
> > >
> > > Fixes: 2c7589af3c4d ("mfd: cros_ec: add proto v3 skeleton")
>
> You need to Cc stable with a note saying which kernel version it
> fixes. Grep the `git log`s for stable.*#.
I understand how the stable process works. This was intentional. Fixes
!= stable. It's easy to tag what commit it's supposed to fix. It's less
easy to backport and verify that it's a useful for all affected kernels.
(If somebody else determines it should be backported -- e.g., Benson or
Olof -- then I won't stop them, of course.)
Side note: isn't 'Fixes' a more accurate way of describing which version
it applies to than just putting the kernel version with a '#' comment?
That helps anyone who might have backported the buggy commit -- e.g., as
part of the stable process.
> > > Signed-off-by: Shawn Nematbakhsh <shawnn@chromium.org>
> > > Signed-off-by: Brian Norris <briannorris@chromium.org>
> > > ---
> > > MAINTAINERS tells me this goes through Olof, but many things have gone through
> > > Lee.
> >
> > I believe this was supposed to go through Olof. Olof, are you out there?
>
> Yes, I concur.
>
> There maybe some confusion since the $SUBJECT line is
> misleading/incorrect.
Thanks. I'll resend with a 'platform/chrome:' prefix, and make sure it
shows up in Benson's inbox too. I think I didn't look deeply enough into
history -- the last few commits touching drivers/platform/chrome/ had an
'mfd' tag, but they also happened to touch mfd-prefixed files too.
Brian
> > Or Benson? I see this:
> >
> > http://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1273587.html
> > [PATCH] platform/chrome : Add myself as Maintainer
> >
> > but it's not merged anywhere AFAICT.
> >
> > I can resend if that helps.
> >
> > Brian
[...]
prev parent reply other threads:[~2016-11-28 22:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-10 20:45 [PATCH] mfd: cros_ec: Use proper protocol transfer function Brian Norris
2016-08-30 14:38 ` Lee Jones
2016-11-22 22:19 ` Brian Norris
2016-11-22 23:01 ` Benson Leung
2016-11-23 8:37 ` Lee Jones
2016-11-28 22:13 ` Brian Norris [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=20161128221320.GA55972@google.com \
--to=briannorris@chromium.org \
--cc=bleung@chromium.org \
--cc=computersforpeace@gmail.com \
--cc=dianders@chromium.org \
--cc=enric.balletbo@collabora.co.uk \
--cc=gwendal@chromium.org \
--cc=javier@osg.samsung.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
--cc=shawnn@chromium.org \
--cc=tomeu.vizoso@collabora.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.