public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Paweł Dembicki" <paweldembicki@gmail.com>
Cc: stable@vger.kernel.org, Evgeniy Polyakov <zbr@ioremap.net>,
	"Andrew F. Davis" <afd@ti.com>,
	Sebastian Reichel <sre@kernel.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] w1: gpio: fix problem with platfom data in w1-gpio
Date: Thu, 29 Mar 2018 12:01:46 +0200	[thread overview]
Message-ID: <20180329100146.GA23906@kroah.com> (raw)
In-Reply-To: <CAJN1KkyrJLBVtzjnE69v-NNed3rjrXt+o46ALnN+wurHzecPTw@mail.gmail.com>

On Thu, Mar 29, 2018 at 11:47:25AM +0200, Paweł Dembicki wrote:
> 2018-03-17 12:55 GMT+01:00 Greg Kroah-Hartman <gregkh@linuxfoundation.org>:
> 
> > Where is this patch supposed to go?  Is this a stable backport patch, or
> > something to go into Linus's tree?
> 
> I tested it in 4.9 and 4.14 kernels in OpenERT. So it is a stable
> backport patch.

What commit is being backported.

> In current release this bug is fixed because w1-gpio use gpiod.

Then why can we not just use the actual patch that fixes this?

> Sorry. This was my first patch.

Please read:
    https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
for how to submit a patch for the stable tree.

thanks,

greg k-h

  reply	other threads:[~2018-03-29 10:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20180218170629.6045-1-paweldembicki@gmail.com>
2018-02-18 17:19 ` [PATCH] w1: gpio: fix problem with platfom data in w1-gpio Pawel Dembicki
2018-02-19 13:29   ` Andrew F. Davis
2018-03-14 13:59   ` Greg Kroah-Hartman
2018-03-17 10:39     ` Paweł Dembicki
2018-03-17 11:55       ` Greg Kroah-Hartman
2018-03-29  9:47         ` Paweł Dembicki
2018-03-29 10:01           ` Greg Kroah-Hartman [this message]
2018-04-04 16:44             ` Paweł Dembicki

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=20180329100146.GA23906@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=afd@ti.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paweldembicki@gmail.com \
    --cc=sre@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=zbr@ioremap.net \
    /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