From: patchwork-bot+netdevbpf@kernel.org
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
linux-can@vger.kernel.org, kernel@pengutronix.de
Subject: Re: pull-request: can-next 2020-12-14
Date: Tue, 15 Dec 2020 03:20:10 +0000 [thread overview]
Message-ID: <160800241091.26355.5049066543526105105.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20201214133145.442472-1-mkl@pengutronix.de>
Hello:
This pull request was applied to netdev/net-next.git (refs/heads/master):
On Mon, 14 Dec 2020 14:31:38 +0100 you wrote:
> Hello Jakub, hello David,
>
> this is a series of 7 patches for net-next/master.
>
> All 7 patches are by me and target the m_can driver. First there are 4 cleanup
> patches (fix link to doc, fix coding style, uniform variable name usage, mark
> function as static). Then the driver is converted to
> pm_runtime_resume_and_get(). The next patch lets the m_can class driver
> allocate the driver's private data, to get rid of one level of indirection. And
> the last patch consistently uses struct m_can_classdev as drvdata over all
> binding drivers.
>
> [...]
Here is the summary with links:
- pull-request: can-next 2020-12-14
https://git.kernel.org/netdev/net-next/c/b02487560740
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2020-12-15 3:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-14 13:31 pull-request: can-next 2020-12-14 Marc Kleine-Budde
2020-12-14 13:31 ` [net-next 1/7] can: m_can: update link to M_CAN user manual Marc Kleine-Budde
2020-12-14 13:31 ` [net-next 2/7] can: m_can: convert indention to kernel coding style Marc Kleine-Budde
2020-12-14 13:31 ` [net-next 3/7] can: m_can: use cdev as name for struct m_can_classdev uniformly Marc Kleine-Budde
2020-12-14 13:31 ` [net-next 4/7] can: m_can: m_can_config_endisable(): mark as static Marc Kleine-Budde
2020-12-14 13:31 ` [net-next 5/7] can: m_can: m_can_clk_start(): make use of pm_runtime_resume_and_get() Marc Kleine-Budde
2020-12-14 13:31 ` [net-next 6/7] can: m_can: let m_can_class_allocate_dev() allocate driver specific private data Marc Kleine-Budde
2020-12-14 13:31 ` [net-next 7/7] can: m_can: use struct m_can_classdev as drvdata Marc Kleine-Budde
2020-12-15 3:20 ` patchwork-bot+netdevbpf [this message]
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=160800241091.26355.5049066543526105105.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=kernel@pengutronix.de \
--cc=kuba@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
/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).