[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190725062834.GC5647@kroah.com>
Date: Thu, 25 Jul 2019 08:28:34 +0200
From: Greg KH <gregkh@...uxfoundation.org>
To: Dan Murphy <dmurphy@...com>
Cc: wg@...ndegger.com, mkl@...gutronix.de, davem@...emloft.net,
linux-can@...r.kernel.org, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v12 1/5] can: m_can: Create a m_can platform framework
On Wed, Jul 24, 2019 at 10:36:02AM -0500, Dan Murphy wrote:
> Hello
>
> On 7/24/19 1:47 AM, Greg KH wrote:
> > On Tue, Jul 23, 2019 at 10:14:14AM -0500, Dan Murphy wrote:
> > > Hello
> > >
> > > On 7/10/19 7:08 AM, Dan Murphy wrote:
> > > > Hello
> > > >
> > > > On 6/17/19 10:09 AM, Dan Murphy wrote:
> > > > > Marc
> > > > >
> > > > > On 6/10/19 11:35 AM, Dan Murphy wrote:
> > > > > > Bump
> > > > > >
> > > > > > On 6/6/19 8:16 AM, Dan Murphy wrote:
> > > > > > > Marc
> > > > > > >
> > > > > > > Bump
> > > > > > >
> > > > > > > On 5/31/19 6:51 AM, Dan Murphy wrote:
> > > > > > > > Marc
> > > > > > > >
> > > > > > > > On 5/15/19 3:54 PM, Dan Murphy wrote:
> > > > > > > > > Marc
> > > > > > > > >
> > > > > > > > > On 5/9/19 11:11 AM, 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@...ndegger.com>
> > > > > > > > > > Signed-off-by: Dan Murphy <dmurphy@...com>
> > > > > > > > > > ---
> > > > > > > > > >
> > > > > > > > > > v12 - Update the m_can_read/write functions to
> > > > > > > > > > create a backtrace if the callback
> > > > > > > > > > pointer is NULL. - https://lore.kernel.org/patchwork/patch/1052302/
> > > > > > > > > >
> > > > > > > > > Is this able to be merged now?
> > > > > > > > ping
> > > > > Wondering if there is anything else we need to do?
> > > > >
> > > > > The part has officially shipped and we had hoped to have driver
> > > > > support in Linux as part of the announcement.
> > > > >
> > > > Is this being sent in a PR for 5.3?
> > > >
> > > > Dan
> > > >
> > > Adding Greg to this thread as I have no idea what is going on with this.
> > Why me? What am I supposed to do here? I see no patches at all to do
> > anything with :(
>
> I am not sure who to email. The maintainer seems to be on hiatus or super
> busy with other work.
Who is the maintainer?
> So I added you to see if you know how to handle this. Wolfgang Acked it but
> he said Marc needs to pull
Then work with them, again, what can I do if I can't even see the
patches here?
> it in. We have quite a few users of this patchset. I have been hosting the
> patchset in a different tree.
>
> These users keep pinging us for upstream status and all we can do is point
> them to the
>
> LKML to show we are continuing to pursue inclusion.
>
> https://lore.kernel.org/patchwork/project/lkml/list/?series=393454
Looks sane, work with the proper developers, good luck!
greg k-h
Powered by blists - more mailing lists