From: Greg KH <gregkh@linuxfoundation.org>
To: Juerg Haefliger <juergh@gmail.com>
Cc: aford173@gmail.com, tony@atomide.com, stable@vger.kernel.org,
stable-commits@vger.kernel.org
Subject: Re: Patch "ARM: dts: LogicPD Torpedo: Fix I2C1 pinmux" has been added to the 4.4-stable tree
Date: Tue, 17 Apr 2018 12:24:17 +0200 [thread overview]
Message-ID: <20180417102417.GB7813@kroah.com> (raw)
In-Reply-To: <CADLDEKuXR9MPitLF8=3bYFq6HPxkF+MwcF2aszjMKp8+_tFoew@mail.gmail.com>
On Tue, Apr 17, 2018 at 10:52:34AM +0200, Juerg Haefliger wrote:
> On Mon, Mar 19, 2018 at 4:27 PM, <gregkh@linuxfoundation.org> wrote:
> >
> > This is a note to let you know that I've just added the patch titled
> >
> > ARM: dts: LogicPD Torpedo: Fix I2C1 pinmux
> >
> > to the 4.4-stable tree which can be found at:
> > http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
> >
> > The filename of the patch is:
> > arm-dts-logicpd-torpedo-fix-i2c1-pinmux.patch
> > and it can be found in the queue-4.4 subdirectory.
> >
> > If you, or anyone else, feels it should not be added to the stable tree,
> > please let <stable@vger.kernel.org> know about it.
>
>
> This commit was reverted in 4.4.122:
> 8d02a5519885 Revert "ARM: dts: LogicPD Torpedo: Fix I2C1 pinmux"
>
> Is this a mistake that it came back again?
It showed up in 4.16-rc4. Should it be reverted again in Linus's tree?
If so, please do so and I'll take the revert.
thanks,
greg k-h
next prev parent reply other threads:[~2018-04-17 10:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-19 15:27 Patch "ARM: dts: LogicPD Torpedo: Fix I2C1 pinmux" has been added to the 4.4-stable tree gregkh
2018-04-17 8:52 ` Juerg Haefliger
2018-04-17 10:24 ` Greg KH [this message]
[not found] ` <CAHCN7xLbRnqfhNKYonj=VZZuNmKdYi8geLJk0Z6=sfNfacAdxQ@mail.gmail.com>
2018-04-17 11:27 ` Adam Ford
2018-04-17 11:51 ` Juerg Haefliger
-- strict thread matches above, loose matches on Subject: below --
2018-03-07 17:36 gregkh
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=20180417102417.GB7813@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=aford173@gmail.com \
--cc=juergh@gmail.com \
--cc=stable-commits@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=tony@atomide.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.