openbmc.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Zev Weiss <zev@bewilderbeest.net>
To: Guenter Roeck <linux@roeck-us.net>,
	Jean Delvare <jdelvare@suse.com>,
	linux-hwmon@vger.kernel.org
Cc: devicetree@vger.kernel.org, webmaster@kernel.org,
	openbmc@lists.ozlabs.org, linux-kernel@vger.kernel.org,
	Krzysztof Kozlowski <krzk@kernel.org>,
	Oleksandr Natalenko <oleksandr@natalenko.name>,
	Rob Herring <robh+dt@kernel.org>, Renze Nicolai <renze@rnplus.nl>
Subject: Re: [PATCH v3 0/6] hwmon: (nct6775) Convert to regmap, add i2c support
Date: Tue, 26 Apr 2022 01:29:22 -0700	[thread overview]
Message-ID: <YmetYjSKFs+WWwYz@hatter.bewilderbeest.net> (raw)
In-Reply-To: <20220426071848.11619-1-zev@bewilderbeest.net>

[Adding korg webmaster re: list infrastructure]

On Tue, Apr 26, 2022 at 12:18:42AM PDT, Zev Weiss wrote:
>Hello,
>
>This is v3 of my effort to add i2c support to the nct6775 hwmon
>driver.
>
>Changes since v2 [0]:
> ...
> - Renamed drivers and Kconfig symbols to keep existing platform
>   driver as "nct6775" (SENSORS_NCT6775) and the core module as
>   "nct6775-core" (SENSORS_NCT6775_CORE) [Guenter]

Unfortunately while this was a simple enough change to make (a few 'git 
mv' commands and a handful of actual text changes), it ballooned the 
size of the diff for patch 5 to the point that vger bounced it for 
exceeding the 100K message-size limit.  As far as I can tell it looks 
like it went through elsewhere, but does leave a bit of a gap in the 
public list archives -- please let me know if there's anything I should 
try in terms of re-sending it.  (The only combination of 'git 
format-patch' flags I've been able to find that gets it back down to 
approximately its previous size is '-B -D', which isn't so useful for 
actually applying.)

I'm not sure how critical a limit that 100K is, or if it's something we 
might consider raising a bit?


Thanks,
Zev


  parent reply	other threads:[~2022-04-26  8:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-26  7:18 [PATCH v3 0/6] hwmon: (nct6775) Convert to regmap, add i2c support Zev Weiss
2022-04-26  7:18 ` [PATCH v3 1/6] dt-bindings: trivial-devices: Add Nuvoton Super I/O chips Zev Weiss
2022-04-26  7:18 ` [PATCH v3 2/6] hwmon: (nct6775) Convert register access to regmap API Zev Weiss
2022-04-26  7:18 ` [PATCH v3 3/6] hwmon: (nct6775) Rearrange attr-group initialization Zev Weiss
2022-04-26  7:18 ` [PATCH v3 4/6] hwmon: (nct6775) Add read-only mode Zev Weiss
2022-04-26  7:18 ` [PATCH v3 5/6] hwmon: (nct6775) Split core and platform driver Zev Weiss
2022-04-26  7:18 ` [PATCH v3 6/6] hwmon: (nct6775) Add i2c driver Zev Weiss
2022-04-26  8:29 ` Zev Weiss [this message]
2022-04-26  8:45   ` [PATCH v3 0/6] hwmon: (nct6775) Convert to regmap, add i2c support Joel Stanley
2022-04-26  8:57   ` Guenter Roeck
2022-04-26 19:38     ` Zev Weiss

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=YmetYjSKFs+WWwYz@hatter.bewilderbeest.net \
    --to=zev@bewilderbeest.net \
    --cc=devicetree@vger.kernel.org \
    --cc=jdelvare@suse.com \
    --cc=krzk@kernel.org \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=oleksandr@natalenko.name \
    --cc=openbmc@lists.ozlabs.org \
    --cc=renze@rnplus.nl \
    --cc=robh+dt@kernel.org \
    --cc=webmaster@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).