From: Stephen Boyd <sboyd@kernel.org>
To: Konrad Dybcio <konrad.dybcio@somainline.org>,
linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org
Subject: Re: Increasing the maximum message size
Date: Sat, 23 Jul 2022 23:43:09 -0700 [thread overview]
Message-ID: <20220724064311.D04BBC3411E@smtp.kernel.org> (raw)
In-Reply-To: <833fa178-22fc-c47c-a7b8-2444de3bf9cc@somainline.org>
Quoting Konrad Dybcio (2022-07-23 04:44:32)
> Hi,
>
> when sending new clock drivers for Qualcomm SoCs I've been repeatedly
> getting a bounce with a reason of "too long (>100000 characters)". The
> drivers are pretty big for one email, for example gcc-sc8280xp.c has
> 201071 chars, but it only makes sense to add them big-as-they-are,
> because there are simply so many clocks, each of which needs to be
> defined as a struct with its properties set correctly.
Maybe it's time to collapse the structs into macro definitions.
Probably a decade ago I expanded the macros that we had because we kept
modifying the struct members while settling on something that described
the clks. Now it doesn't seem very useful to do that because the structs
almost never change. Certainly the struct members aren't changing
rapidly. I'd start with a macro for branches, rcgs, and plls and see how
small it can become. Hopefully there aren't many parameters to the macro
so that it is still somewhat readable.
next prev parent reply other threads:[~2022-07-24 6:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-23 11:44 Increasing the maximum message size Konrad Dybcio
2022-07-24 6:43 ` Stephen Boyd [this message]
2022-07-25 8:07 ` Abel Vesa
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=20220724064311.D04BBC3411E@smtp.kernel.org \
--to=sboyd@kernel.org \
--cc=konrad.dybcio@somainline.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).