From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Marc Kleine-Budde <mkl@pengutronix.de>,
Alexander Shiyan <shc_work@mail.ru>
Cc: linux-can@vger.kernel.org, Wolfgang Grandegger <wg@grandegger.com>
Subject: Re: [PATCH] can: mcp251x: Fix regulators operation without CONFIG_REGULATOR
Date: Mon, 17 Mar 2014 08:07:38 +0100 [thread overview]
Message-ID: <53269F3A.1040708@hartkopp.net> (raw)
In-Reply-To: <5322D6B2.90904@pengutronix.de>
On 14.03.2014 11:15, Marc Kleine-Budde wrote:
>
> Okay, applied to can-next, that goes via net-next into v3.15.
>
Hello Marc,
Linus just tagged 3.14-rc7 with a relaxed comment:
https://lkml.org/lkml/2014/3/16/166
So net-next might close this week.
Just FYI :-)
Regards,
Oliver
next prev parent reply other threads:[~2014-03-17 7:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-14 8:46 [PATCH] can: mcp251x: Fix regulators operation without CONFIG_REGULATOR Alexander Shiyan
2014-03-14 9:49 ` Marc Kleine-Budde
2014-03-14 9:55 ` Alexander Shiyan
2014-03-14 9:59 ` Marc Kleine-Budde
2014-03-14 10:11 ` Alexander Shiyan
2014-03-14 10:15 ` Marc Kleine-Budde
2014-03-17 7:07 ` Oliver Hartkopp [this message]
2014-03-17 9:37 ` 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=53269F3A.1040708@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=shc_work@mail.ru \
--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 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).