From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: linux-can@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
Wolfgang Grandegger <wg@grandegger.com>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>
Subject: Re: [PATCH v1 1/1] can: mcp251x: Get rid of duplicate of_node assignment
Date: Wed, 5 Jan 2022 16:47:25 +0200 [thread overview]
Message-ID: <YdWvfdRTpPZ0YcSD@smile.fi.intel.com> (raw)
In-Reply-To: <20220105143448.pnckx2wgal2y3rll@pengutronix.de>
On Wed, Jan 05, 2022 at 03:34:48PM +0100, Marc Kleine-Budde wrote:
> On 05.01.2022 16:21:13, Andy Shevchenko wrote:
> > On Fri, Dec 10, 2021 at 03:19:31PM +0200, Andy Shevchenko wrote:
> > > On Fri, Dec 10, 2021 at 02:06:07PM +0100, Marc Kleine-Budde wrote:
> > > > On 09.12.2021 13:58:40, Andy Shevchenko wrote:
> > > > > On Thu, Dec 02, 2021 at 10:58:55PM +0200, Andy Shevchenko wrote:
> > >
> > > ...
> > >
> > > > > Marc, what do you think about this change?
> > > >
> > > > LGTM, added to linux-can-next/testing.
> > >
> > > Thanks for applying this and hi311x patches!
> >
> > Can we have a chance to see it in the v5.17-rc1?
>
> Yes:
> https://git.kernel.org/pub/scm/linux/kernel/git/mkl/linux-can-next.git/log/?h=linux-can-next-for-5.17-20220105
>
> 'about to send that PR.
Cool, thanks! Happy new year!
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2022-01-05 14:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-02 20:58 [PATCH v1 1/1] can: mcp251x: Get rid of duplicate of_node assignment Andy Shevchenko
2021-12-09 11:58 ` Andy Shevchenko
2021-12-10 13:06 ` Marc Kleine-Budde
2021-12-10 13:19 ` Andy Shevchenko
2022-01-05 14:21 ` Andy Shevchenko
2022-01-05 14:34 ` Marc Kleine-Budde
2022-01-05 14:47 ` Andy Shevchenko [this message]
2022-01-05 14:54 ` 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=YdWvfdRTpPZ0YcSD@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.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 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).