From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Mark Brown <broonie@kernel.org>,
linux-spi@vger.kernel.org,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 1/3] parport: Introduce module_parport_driver() helper macro
Date: Tue, 2 Mar 2021 17:06:27 +0200 [thread overview]
Message-ID: <YD5Uc7j2MAFbFWZ3@smile.fi.intel.com> (raw)
In-Reply-To: <CADVatmP7V+pbpUC4xV+BmNzbfudPE5S0tT-6CgUKbQrC-FMrBA@mail.gmail.com>
On Tue, Mar 02, 2021 at 02:51:45PM +0000, Sudip Mukherjee wrote:
> On Mon, Mar 1, 2021 at 12:12 PM Andy Shevchenko
> <andriy.shevchenko@linux.intel.com> wrote:
> >
> > On Sun, Feb 28, 2021 at 11:27:10PM +0000, Sudip Mukherjee wrote:
> > > On Fri, Feb 26, 2021 at 07:03:09PM +0200, Andy Shevchenko wrote:
> > > > On Tue, Feb 16, 2021 at 01:07:39PM +0200, Andy Shevchenko wrote:
> > > > > Introduce module_parport_driver() helper macro to reduce boilerplate
> > > > > in the existing and new code.
> > > >
> > > > Sudip, any comments on this?
> > >
> > > Sorry for the delay in reply.
> > > lgtm. I think there are few more drivers which can also use this new helper.
> > > Will you like to do them also?
> >
> > Yes, that's the (slow going) plan.
> >
> > > Acked-by: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
> >
> > Thanks! I considered that you take it thru parport tree. Do you have something
> > else in mind?
>
> I dont have a separate parport tree (parport is not under active
> development to have a separate tree). I send everything parport
> related to Greg and then he adds it to his tree.
MAINTAINERS doesn't show this. But good to know.
> I guess in this case if Greg agrees it can go via Mark's tree as the
> series will also have SPI related patches.
Okay, if Greg wants to handle this himself, I think I have to resend (he wasn't
in the Cc list). Otherwise Mark can also apply this if Greg is okay (but sounds
like I have to resend anyway to let him understand what's going on here).
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2021-03-02 17:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-16 11:07 [PATCH v2 1/3] parport: Introduce module_parport_driver() helper macro Andy Shevchenko
2021-02-16 11:07 ` [PATCH v2 2/3] spi: butterfly: Switch to use module_parport_driver() Andy Shevchenko
2021-02-16 11:07 ` [PATCH v2 3/3] spi: lm70llp: " Andy Shevchenko
2021-02-26 17:03 ` [PATCH v2 1/3] parport: Introduce module_parport_driver() helper macro Andy Shevchenko
2021-02-28 23:27 ` Sudip Mukherjee
2021-03-01 12:11 ` Andy Shevchenko
2021-03-02 14:51 ` Sudip Mukherjee
2021-03-02 15:06 ` Andy Shevchenko [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=YD5Uc7j2MAFbFWZ3@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.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.