From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Jakub Kicinski <jakub.kicinski@netronome.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net,
kernel@pengutronix.de, linux-can@vger.kernel.org,
Oliver Hartkopp <socketcan@hartkopp.net>,
Bastian Stender <bst@pengutronix.de>,
Elenita Hinds <ecathinds@gmail.com>,
Kurt Van Dijck <dev.kurt@vandijck-laurijssen.be>,
Maxime Jayat <maxime.jayat@mobile-devices.fr>,
Robin van der Gracht <robin@protonic.nl>,
Oleksij Rempel <ore@pengutronix.de>,
David Jander <david@protonic.nl>
Subject: Re: pull-request: can-next 2019-10-07
Date: Wed, 9 Oct 2019 09:40:38 +0200 [thread overview]
Message-ID: <1196c661-5145-4931-031b-13b16249d632@pengutronix.de> (raw)
In-Reply-To: <20191008120953.515a3dbd@cakuba.netronome.com>
[-- Attachment #1.1: Type: text/plain, Size: 1939 bytes --]
On 10/8/19 9:09 PM, Jakub Kicinski wrote:
> On Mon, 7 Oct 2019 16:38:14 +0200, Marc Kleine-Budde wrote:
>> Hello David,
>>
>> this is a pull request for net-next/master consisting of 12 patches.
>>
>> The first patch is by Andy Shevchenko for the mcp251x driver and removes
>> the legacy platform data from all in-tree users and the driver.
>>
>> The next two patches target the peak_canfd driver, the first one is by
>> me and fixes several checkpatch warnings, the second one is by Stephane
>> Grosjean and adds hardware timestamps to the rx skbs.
>>
>> Followed by two patches for the xilinx_can driver. Again the first is by
>> me and fixes checkpatch warnings, the second one is by Anssi Hannula and
>> avoids non-requested bus error frames, which improves performance.
>>
>> Pankaj Sharma's patch for the m_can driver adds support for the one shot
>> mode.
>>
>> YueHaibing provides a patch for the grcan driver to use
>> devm_platform_ioremap_resource() to simplify code.
>>
>> Joakim Zhang provides a similar patch for the flexcan driver.
>>
>> The last 4 patches are by me and target the rx-offload infrastructure.
>> The first 3 fix checkpatch warnings, the last one removes a no-op
>> function.
>
> Hi Marc,
>
> I think the correction should have been s/Substract/Subtract/,
> sorry for the nit pick.
Thanks for noticing that. checkpatch wasn't complaining about my new
typo though :)
> Would you be able to fix that up or do you prefer to do a follow up?
As another patch from the pull request is broken, I've asked David to
not merge it. I've squashed your fix into the original patch.
Thanks,
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: 488 bytes --]
next prev parent reply other threads:[~2019-10-09 7:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-07 14:38 pull-request: can-next 2019-10-07 Marc Kleine-Budde
2019-10-08 19:09 ` Jakub Kicinski
2019-10-09 7:40 ` Marc Kleine-Budde [this message]
2019-10-09 7:33 ` Marc Kleine-Budde
2019-11-12 15:57 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=1196c661-5145-4931-031b-13b16249d632@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=bst@pengutronix.de \
--cc=davem@davemloft.net \
--cc=david@protonic.nl \
--cc=dev.kurt@vandijck-laurijssen.be \
--cc=ecathinds@gmail.com \
--cc=jakub.kicinski@netronome.com \
--cc=kernel@pengutronix.de \
--cc=linux-can@vger.kernel.org \
--cc=maxime.jayat@mobile-devices.fr \
--cc=netdev@vger.kernel.org \
--cc=ore@pengutronix.de \
--cc=robin@protonic.nl \
--cc=socketcan@hartkopp.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;
as well as URLs for NNTP newsgroup(s).