All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Stefan Agner <stefan@agner.ch>, wg@grandegger.com
Cc: 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:15:01 +0200	[thread overview]
Message-ID: <55A65CD5.20300@pengutronix.de> (raw)
In-Reply-To: <a52e25bc10d3d669b41f19faedf82d57@agner.ch>

[-- Attachment #1: Type: text/plain, Size: 505 bytes --]

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?

Marc

-- 
Pengutronix e.K.                  | Marc Kleine-Budde           |
Industrial Linux Solutions        | Phone: +49-231-2826-924     |
Vertretung West/Dortmund          | Fax:   +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686  | http://www.pengutronix.de   |


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 455 bytes --]

  reply	other threads:[~2015-07-15 13:15 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 [this message]
2015-07-15 13:17     ` Stefan Agner
  -- 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=55A65CD5.20300@pengutronix.de \
    --to=mkl@pengutronix.de \
    --cc=chripell@fsfe.org \
    --cc=linux-can@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=stefan@agner.ch \
    --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.