From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Wolfram Sang <wsa@kernel.org>,
Jarkko Nikula <jarkko.nikula@linux.intel.com>,
linux-i2c@vger.kernel.org,
Mika Westerberg <mika.westerberg@linux.intel.com>
Subject: Re: [PATCH 4/6] i2c: designware-pci: Group MODULE_*() macros
Date: Fri, 17 Dec 2021 13:30:00 +0200 [thread overview]
Message-ID: <Ybx0uPds3auwqO7a@smile.fi.intel.com> (raw)
In-Reply-To: <YbutJCYnoMwjV6Zn@kunai>
On Thu, Dec 16, 2021 at 10:18:28PM +0100, Wolfram Sang wrote:
> On Wed, Dec 15, 2021 at 05:12:03PM +0200, Jarkko Nikula wrote:
> > From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> >
> > For better maintenance group MODULE_*() macros together.
> Removed an empty line and applied to for-next, thanks!
Agree on the change and thanks!
> > +MODULE_ALIAS("i2c_designware-pci");
> > +
>
> This one.
>
> > MODULE_AUTHOR("Baruch Siach <baruch@tkos.co.il>");
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2021-12-17 11:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-15 15:12 [PATCH 1/6] i2c: designware: Do not complete i2c read without RX_FULL interrupt Jarkko Nikula
2021-12-15 15:12 ` [PATCH 2/6] i2c: designware-pci: Fix to change data types of hcnt and lcnt parameters Jarkko Nikula
2021-12-16 21:17 ` Wolfram Sang
2021-12-15 15:12 ` [PATCH 3/6] i2c: designware-pci: Add a note about struct dw_scl_sda_cfg usage Jarkko Nikula
2021-12-16 21:17 ` Wolfram Sang
2021-12-15 15:12 ` [PATCH 4/6] i2c: designware-pci: Group MODULE_*() macros Jarkko Nikula
2021-12-16 21:18 ` Wolfram Sang
2021-12-17 11:30 ` Andy Shevchenko [this message]
2021-12-15 15:12 ` [PATCH 5/6] i2c: designware-pci: use __maybe_unused for PM functions Jarkko Nikula
2021-12-16 21:18 ` Wolfram Sang
2021-12-15 15:12 ` [PATCH 6/6] i2c: designware-pci: Convert to use dev_err_probe() Jarkko Nikula
2021-12-16 21:18 ` Wolfram Sang
2021-12-16 21:17 ` [PATCH 1/6] i2c: designware: Do not complete i2c read without RX_FULL interrupt Wolfram Sang
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=Ybx0uPds3auwqO7a@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=jarkko.nikula@linux.intel.com \
--cc=linux-i2c@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=wsa@kernel.org \
/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.