All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Murphy <dmurphy@ti.com>
To: Wolfgang Grandegger <wg@grandegger.com>,
	mkl@pengutronix.de, davem@davemloft.net
Cc: linux-can@vger.kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v11 1/5] can: m_can: Create a m_can platform framework
Date: Wed, 1 May 2019 09:10:27 -0500	[thread overview]
Message-ID: <a8b9fcca-dc35-3ca4-e3eb-109bc534e804@ti.com> (raw)
In-Reply-To: <2d594ba8-e4e4-14f9-1eb0-8f753c79eb54@ti.com>

Hello

On 4/18/19 9:36 AM, Dan Murphy wrote:
> Marc
> 
> On 4/2/19 7:17 AM, Wolfgang Grandegger wrote:
>> Hello Dan,
>>
>> Am 02.04.19 um 14:03 schrieb Dan Murphy:
>>> Wolfgang
>>>
>>> On 3/19/19 12:26 PM, Dan Murphy wrote:
>>>> Create a m_can platform framework that peripheral
>>>> devices can register to and use common code and register sets.
>>>> The peripheral devices may provide read/write and configuration
>>>> support of the IP.
>>>>
>>>> Acked-by: Wolfgang Grandegger <wg@grandegger.com>
>>>> Signed-off-by: Dan Murphy <dmurphy@ti.com>
>>>> ---
>>>>
>>>
>>> Wondering if this will be going into 5.1 PR?
>>
>> it's Marc who is doing the upstreaming ... and maybe a final review as well.
>>
> 
> Can you tell me if this will be taken?

This patchset has gone unresponded to from the maintainers for quite some time.

I have numerous customers using this patchset from my public repo and they want the
driver in the mainline kernel.

Is there any help or anything needed to get this merged for 5.2?

Dan

> 
> Dan
> 
>> Wolfgang.
>>

WARNING: multiple messages have this Message-ID (diff)
From: Dan Murphy <dmurphy@ti.com>
To: Wolfgang Grandegger <wg@grandegger.com>, <mkl@pengutronix.de>,
	<davem@davemloft.net>
Cc: <linux-can@vger.kernel.org>, <netdev@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v11 1/5] can: m_can: Create a m_can platform framework
Date: Wed, 1 May 2019 09:10:27 -0500	[thread overview]
Message-ID: <a8b9fcca-dc35-3ca4-e3eb-109bc534e804@ti.com> (raw)
In-Reply-To: <2d594ba8-e4e4-14f9-1eb0-8f753c79eb54@ti.com>

Hello

On 4/18/19 9:36 AM, Dan Murphy wrote:
> Marc
> 
> On 4/2/19 7:17 AM, Wolfgang Grandegger wrote:
>> Hello Dan,
>>
>> Am 02.04.19 um 14:03 schrieb Dan Murphy:
>>> Wolfgang
>>>
>>> On 3/19/19 12:26 PM, Dan Murphy wrote:
>>>> Create a m_can platform framework that peripheral
>>>> devices can register to and use common code and register sets.
>>>> The peripheral devices may provide read/write and configuration
>>>> support of the IP.
>>>>
>>>> Acked-by: Wolfgang Grandegger <wg@grandegger.com>
>>>> Signed-off-by: Dan Murphy <dmurphy@ti.com>
>>>> ---
>>>>
>>>
>>> Wondering if this will be going into 5.1 PR?
>>
>> it's Marc who is doing the upstreaming ... and maybe a final review as well.
>>
> 
> Can you tell me if this will be taken?

This patchset has gone unresponded to from the maintainers for quite some time.

I have numerous customers using this patchset from my public repo and they want the
driver in the mainline kernel.

Is there any help or anything needed to get this merged for 5.2?

Dan

> 
> Dan
> 
>> Wolfgang.
>>

  reply	other threads:[~2019-05-01 14:10 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-19 17:26 [PATCH v11 1/5] can: m_can: Create a m_can platform framework Dan Murphy
2019-03-19 17:26 ` Dan Murphy
2019-03-19 17:26 ` [PATCH v11 2/5] can: m_can: Rename m_can_priv to m_can_classdev Dan Murphy
2019-03-19 17:26   ` Dan Murphy
2019-03-19 17:26 ` [PATCH v11 3/5] dt-bindings: can: tcan4x5x: Add DT bindings for TCAN4x5X driver Dan Murphy
2019-03-19 17:26   ` Dan Murphy
2019-03-19 17:26 ` [PATCH v11 4/5] can: tcan4x5x: Add tcan4x5x driver to the kernel Dan Murphy
2019-03-19 17:26   ` Dan Murphy
2019-03-19 17:26 ` [PATCH v11 5/5] can: m_can: Fix checkpatch issues on existing code Dan Murphy
2019-03-19 17:26   ` Dan Murphy
2019-04-02 12:03 ` [PATCH v11 1/5] can: m_can: Create a m_can platform framework Dan Murphy
2019-04-02 12:03   ` Dan Murphy
2019-04-02 12:17   ` Wolfgang Grandegger
2019-04-10 13:24     ` Dan Murphy
2019-04-10 13:24       ` Dan Murphy
2019-04-18 14:36     ` Dan Murphy
2019-04-18 14:36       ` Dan Murphy
2019-05-01 14:10       ` Dan Murphy [this message]
2019-05-01 14:10         ` Dan Murphy
2019-05-08 14:35 ` Marc Kleine-Budde
2019-05-08 19:54   ` Dan Murphy
2019-05-08 19:54     ` Dan Murphy
2019-05-09  6:38     ` 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=a8b9fcca-dc35-3ca4-e3eb-109bc534e804@ti.com \
    --to=dmurphy@ti.com \
    --cc=davem@davemloft.net \
    --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 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.