From: Stefan Agner <stefan@agner.ch>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: wg@grandegger.com, chripell@fsfe.org, linux-can@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] can: mcp251x: fix resume when device is down
Date: Wed, 15 Jul 2015 15:17:47 +0200 [thread overview]
Message-ID: <5f785ad6dbb16e7abe084a1d82e29efb@agner.ch> (raw)
In-Reply-To: <55A65CD5.20300@pengutronix.de>
On 2015-07-15 15:15, Marc Kleine-Budde wrote:
> On 07/15/2015 03:05 PM, Stefan Agner wrote:
>> Hi Marc, hi Wolfgang,
>>
>> Any comment on this two patches? I don't think these have made it in any
>> tree...
>
> Sorry - Should I add stable in Cc for 1/2 or even both?
2/2 does not fix an actual issue, it only prevents dummy regulators
being created. It even has a slight potential of a regression, in case
the absence of a dummy regulator could not be handled properly...
But 1/2 is definitely stable material.
--
Stefan
next prev parent reply other threads:[~2015-07-15 13:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-18 16:33 [PATCH 1/2] can: mcp251x: fix resume when device is down Stefan Agner
2015-05-18 16:33 ` [PATCH 2/2] can: mcp251x: get regulators optionally Stefan Agner
2015-07-15 13:05 ` [PATCH 1/2] can: mcp251x: fix resume when device is down Stefan Agner
2015-07-15 13:15 ` Marc Kleine-Budde
2015-07-15 13:17 ` Stefan Agner [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-07-16 8:33 pull-request: can 2015-07-16 Marc Kleine-Budde
2015-07-16 8:33 ` [PATCH 1/2] can: mcp251x: fix resume when device is down Marc Kleine-Budde
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=5f785ad6dbb16e7abe084a1d82e29efb@agner.ch \
--to=stefan@agner.ch \
--cc=chripell@fsfe.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=wg@grandegger.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.