From: Lee Jones <lee.jones@linaro.org>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: "Linus Walleij" <linus.walleij@linaro.org>,
"Ville Syrjälä" <ville.syrjala@linux.intel.com>,
"Alexandre Courbot" <gnurou@gmail.com>,
"Samuel Ortiz" <sameo@linux.intel.com>,
"Shobhit Kumar" <shobhit.kumar@intel.com>,
intel-gfx <intel-gfx@lists.freedesktop.org>,
stable <stable@vger.kernel.org>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"Thierry Reding" <thierry.reding@gmail.com>
Subject: Re: [Intel-gfx] [PATCH] mfd: intel_soc_pmic_core: Terminate panel control GPIO lookup table correctly
Date: Mon, 9 May 2016 08:17:29 +0100 [thread overview]
Message-ID: <20160509071729.GA1444@dell> (raw)
In-Reply-To: <20160509065703.GL27098@phenom.ffwll.local>
On Mon, 09 May 2016, Daniel Vetter wrote:
> On Wed, May 04, 2016 at 08:32:17AM +0100, Lee Jones wrote:
> > On Mon, 02 May 2016, Daniel Vetter wrote:
> >
> > > On Fri, Apr 29, 2016 at 11:31:44AM +0200, Linus Walleij wrote:
> > > > On Fri, Apr 22, 2016 at 9:38 PM, <ville.syrjala@linux.intel.com> wrote:
> > > >
> > > > > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > > > >
> > > > > GPIO lookup tables are supposed to be zero terminated. Let's do that
> > > > > and avoid accidentally walking off the end.
> > > > >
> > > > > Cc: Shobhit Kumar <shobhit.kumar@intel.com>
> > > > > Cc: Samuel Ortiz <sameo@linux.intel.com>
> > > > > Cc: Linus Walleij <linus.walleij@linaro.org>
> > > > > Cc: Alexandre Courbot <gnurou@gmail.com>
> > > > > Cc: Thierry Reding <thierry.reding@gmail.com>
> > > > > Cc: Lee Jones <lee.jones@linaro.org>
> > > > > Cc: stable@vger.kernel.org
> > > > > Fixes: 61dd2ca2d44e ("mfd: intel_soc_pmic_core: Add lookup table for Panel Control as GPIO signal")
> > > > > Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > > >
> > > > Acked-by: Linus Walleij <linus.walleij@linaro.org>
> > >
> > > Applied to drm-intel trees, thanks for patch, reviews&acks.
> >
> > Do what now? How can you apply a patch for a subsystem you don't have
> > responsibility for? This is bound to cause merge conflicts.
>
> Oh crap, I thought Linus' ack was for the mfd stuff and didn't bother
> double-checking with MAINTAINTERS. Should I throw it out again and you'll
> pick it up, or ok as such?
Yes please.
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
--
To unsubscribe from this list: send the line "unsubscribe linux-gpio" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-05-09 7:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-22 19:38 [PATCH] mfd: intel_soc_pmic_core: Terminate panel control GPIO lookup table correctly ville.syrjala
2016-04-25 7:40 ` Jani Nikula
2016-04-25 10:06 ` Thierry Reding
2016-04-29 9:31 ` Linus Walleij
2016-05-02 8:19 ` Daniel Vetter
2016-05-04 7:32 ` Lee Jones
2016-05-09 6:57 ` Daniel Vetter
2016-05-09 7:17 ` Lee Jones [this message]
2016-05-09 7:18 ` Lee Jones
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=20160509071729.GA1444@dell \
--to=lee.jones@linaro.org \
--cc=daniel@ffwll.ch \
--cc=gnurou@gmail.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=sameo@linux.intel.com \
--cc=shobhit.kumar@intel.com \
--cc=stable@vger.kernel.org \
--cc=thierry.reding@gmail.com \
--cc=ville.syrjala@linux.intel.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 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).