From: "Janne Grunau" <j@jannau.net>
To: "Arnd Bergmann" <arnd@arndb.de>,
"Arnd Bergmann" <arnd@kernel.org>,
"Alyssa Rosenzweig" <alyssa@rosenzweig.io>,
"Martin Povišer" <povik+lin@cutebit.org>
Cc: asahi@lists.linux.dev, "Hector Martin" <marcan@marcan.st>,
"Sven Peter" <sven@svenpeter.dev>,
"Asahi Lina" <lina@asahilina.net>,
dri-devel@lists.freedesktop.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] drm: apple: mark local functions static
Date: Tue, 23 Jan 2024 19:51:23 +0100 [thread overview]
Message-ID: <489e3e5d-25e7-4e84-9e62-b6e52bf7455c@app.fastmail.com> (raw)
In-Reply-To: <3da403ff-365d-4cea-86f0-4009d1da6baa@app.fastmail.com>
Hej Arnd,
On Tue, Jan 23, 2024, at 08:34, Arnd Bergmann wrote:
> On Mon, Jan 22, 2024, at 21:50, Janne Grunau wrote:
>> On Wed, Jan 17, 2024, at 11:44, Arnd Bergmann wrote:
>>>
>>> -int parse_sample_rate_bit(struct dcp_parse_ctx *handle, unsigned int
>>> *ratebit)
>>> +static int parse_sample_rate_bit(struct dcp_parse_ctx *handle,
>>> unsigned int *ratebit)
>>> {
>>> s64 rate;
>>> int ret = parse_int(handle, &rate);
>>> @@ -715,7 +715,7 @@ int parse_sample_rate_bit(struct dcp_parse_ctx
>>> *handle, unsigned int *ratebit)
>>> return 0;
>>> }
>>>
>>> -int parse_sample_fmtbit(struct dcp_parse_ctx *handle, u64 *fmtbit)
>>> +static int parse_sample_fmtbit(struct dcp_parse_ctx *handle, u64 *fmtbit)
>>> {
>>> s64 sample_size;
>>> int ret = parse_int(handle, &sample_size);
>>
>> thanks, patch included in my dev branch and will be in the next pull
>> request I'll send to Hector.
>>
>> I suppose the recipients are generated by an automated
>> get_maintainers.pl invocation. Is that desired for out of tree drivers?
>
> I was wondering about that as well, as I don't usually send
> patches for code that isn't at least in linux-next yet.
>
> I ended up using what is in the MAINTAINERS file for this driver
> in the branch as that is is all I have at this point:
>
> APPLE DRM DISPLAY DRIVER
> M: Alyssa Rosenzweig <alyssa@rosenzweig.io>
> L: dri-devel@lists.freedesktop.org
> S: Maintained
> T: git git://anongit.freedesktop.org/drm/drm-misc
> F: drivers/gpu/drm/apple/
>
> I left out the drivers/gpu/ maintainer addresses though.
oops, answered to the wrong patch. The strscpy one has the drivers/gpu/ maintainers and the question. I replied here first assuming it has the same recipient list. I'd consider the recipients for this mail reasonable.
Janne
prev parent reply other threads:[~2024-01-23 18:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-17 10:44 Arnd Bergmann
2024-01-22 20:50 ` Janne Grunau
2024-01-23 7:34 ` Arnd Bergmann
2024-01-23 18:51 ` Janne Grunau [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=489e3e5d-25e7-4e84-9e62-b6e52bf7455c@app.fastmail.com \
--to=j@jannau.net \
--cc=alyssa@rosenzweig.io \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=asahi@lists.linux.dev \
--cc=dri-devel@lists.freedesktop.org \
--cc=lina@asahilina.net \
--cc=linux-kernel@vger.kernel.org \
--cc=marcan@marcan.st \
--cc=povik+lin@cutebit.org \
--cc=sven@svenpeter.dev \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®