From: Wolfram Sang <wsa@kernel.org>
To: Mikko Perttunen <cyndis@kapsi.fi>
Cc: Mikko Perttunen <mperttunen@nvidia.com>,
thierry.reding@gmail.com, jonathanh@nvidia.com, talho@nvidia.com,
linux-i2c@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v3] i2c: bpmp-tegra: Ignore unknown I2C_M flags
Date: Mon, 18 Jan 2021 12:34:59 +0100 [thread overview]
Message-ID: <20210118113459.GF1018@ninjato> (raw)
In-Reply-To: <99326ffc-7590-84ce-dfa7-7c09bc17ca31@kapsi.fi>
[-- Attachment #1: Type: text/plain, Size: 817 bytes --]
> > Also, this driver has no dedicated maintainer. Is there someone up for
> > this task? There is probably little to do and it will speed up patch
> > acceptance because I pick patches once the driver maintainer is happy.
> >
>
> I think it falls under the 'TEGRA ARCHITECTURE SUPPORT' wildcard (Thierry
> and Jon). Do we need a more specific maintainer entry?
>
> If it's helpful to Thierry and Jon, I guess I could pick it up.
I am fine with both. I'd just like a line
"F: drivers/i2c/busses/i2c-tegra-bpmp.c"
somewhere in MAINTAINERS. If that's in Tegra architecture, also good.
However, i2c-tegra.c already has a dedicated entry and spreading the
work avoids bottlenecks, so I think it might be the better option. But
I'll leave it to you guys. In any case, thanks for volunteering!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2021-01-18 11:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-12 10:22 [PATCH v3] i2c: bpmp-tegra: Ignore unknown I2C_M flags Mikko Perttunen
2021-01-17 11:20 ` Wolfram Sang
2021-01-18 11:22 ` Mikko Perttunen
2021-01-18 11:34 ` Wolfram Sang [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=20210118113459.GF1018@ninjato \
--to=wsa@kernel.org \
--cc=cyndis@kapsi.fi \
--cc=jonathanh@nvidia.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mperttunen@nvidia.com \
--cc=stable@vger.kernel.org \
--cc=talho@nvidia.com \
--cc=thierry.reding@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.