public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jérôme Pouiller" <jerome.pouiller@silabs.com>
To: linux-wireless@vger.kernel.org,
	Johannes Berg <johannes@sipsolutions.net>
Cc: linux-kernel@vger.kernel.org, Kalle Valo <kvalo@kernel.org>,
	linux-devel@silabs.com
Subject: Re: [PATCH v2 0/5] wfx: add support for WoWLAN on Silabs WF200
Date: Wed, 05 Mar 2025 16:18:32 +0100	[thread overview]
Message-ID: <23857370.6Emhk5qWAg@nb0018864> (raw)
In-Reply-To: <98e39be3351190ec71ffb067c062c82883ebef24.camel@sipsolutions.net>

On Wednesday 5 March 2025 08:40:51 CET Johannes Berg wrote:
> On Tue, 2025-03-04 at 16:22 +0100, Jérôme Pouiller wrote:
> >
> > Patchwork also reports two warnings that I am going to ignore:
> >
> >   - "Target tree name not specified in the subject", I assume it
> >     is "wireless-next", but in the doubt I prefer to refrain.
> 
> It should be wireless-next for anything that isn't fixes for the current
> cycle, and please do add it - without it the checker won't always be
> able to pick up the patches to test them:
> 
> https://urldefense.com/v3/__https://lore.kernel.org/linux-wireless/ec3a3d891acfe5ed8763271a1df4151d75daf25f.camel@sipsolutions.net/__;!!N30Cs7Jr!X-PjgfbhIZWbgAa9xgbQsoUtAFxrhIPOL3GoEq_3Nan4ktwxzvTu7V17Q3HSxfYgjtdupGn3xRoIJwxLu9f0CcZx3Ys$
> 
> >   - Lines are larger then 80 columns. Checkpatch.pl now accepts up
> >     to 100 columns. I am not aware any local exception in net/, right?
> 
> It looks like that's not documented
> (https://urldefense.com/v3/__https://docs.kernel.org/process/maintainer-netdev.html__;!!N30Cs7Jr!X-PjgfbhIZWbgAa9xgbQsoUtAFxrhIPOL3GoEq_3Nan4ktwxzvTu7V17Q3HSxfYgjtdupGn3xRoIJwxLu9f0sNiJZZA$ ), but I had a
> conversation with Jakub about this in the past and he prefers to have
> the checks still at 80 because people were, in his telling, abusing it
> in a way and making really long lines for no good reason.
> 
> I'm not going to be super strict about it, but I'd encourage everyone
> who sees that warning to see if they can do better.
> 
> In this particular case, it's just a comment, so could trivially be
> wrapped, but I'm not going to complain about 85 columns. If someone's
> going to 100 columns with (text) comments though then I think that'd
> raise some eyebrows. Narrower text is easier to read anyway.

Thank you for the detailed answer.

I will send a new version in a couple of days. Thus the various robots
have time to test it.

-- 
Jérôme Pouiller



  reply	other threads:[~2025-03-05 15:18 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-02 14:47 [PATCH v2 0/5] wfx: add support for WoWLAN on Silabs WF200 Jérôme Pouiller
2025-03-02 14:47 ` [PATCH v2 1/5] wifi: wfx: align declarations between bus_spi.c and bus_sdio.c Jérôme Pouiller
2025-03-02 14:47 ` [PATCH v2 2/5] wifi: wfx: declare support for WoWLAN Jérôme Pouiller
2025-03-03 15:05   ` kernel test robot
2025-03-03 16:28   ` kernel test robot
2025-03-02 14:47 ` [PATCH v2 3/5] wifi: wfx: allow SPI device to wake up the host Jérôme Pouiller
2025-03-02 14:47 ` [PATCH v2 4/5] wifi: wfx: allow SDIO " Jérôme Pouiller
2025-03-02 14:47 ` [PATCH v2 5/5] wifi: wfx: allow to enable WoWLAN using NL80211 Jérôme Pouiller
2025-03-03  8:20 ` [PATCH v2 0/5] wfx: add support for WoWLAN on Silabs WF200 Johannes Berg
2025-03-04 15:22   ` Jérôme Pouiller
2025-03-05  7:40     ` Johannes Berg
2025-03-05 15:18       ` Jérôme Pouiller [this message]
2025-03-06  8:10         ` Johannes Berg
2025-03-06  8:35           ` Jérôme Pouiller
2025-03-06  8:37             ` Johannes Berg

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=23857370.6Emhk5qWAg@nb0018864 \
    --to=jerome.pouiller@silabs.com \
    --cc=johannes@sipsolutions.net \
    --cc=kvalo@kernel.org \
    --cc=linux-devel@silabs.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@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