From: Mark Brown <broonie@kernel•org>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Liam Girdwood <lgirdwood@gmail•com>,
Linux Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Bard Liao <yung-chuan.liao@linux•intel.com>,
Pierre-Louis Bossart <pierre-louis.bossart@linux•intel.com>,
Daniel Baluta <daniel.baluta@nxp•com>
Subject: Re: linux-next: Fixes tags needs some work in the sound-asoc tree
Date: Thu, 16 Apr 2020 14:09:25 +0100 [thread overview]
Message-ID: <20200416130925.GJ5354@sirena.org.uk> (raw)
In-Reply-To: <20200416094111.3f37623f@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 875 bytes --]
On Thu, Apr 16, 2020 at 09:41:11AM +1000, Stephen Rothwell wrote:
> has these problem(s):
> - Subject has leading but no trailing parentheses
> - Subject has leading but no trailing quotes
> Please do not split Fixes tags over more than one line.
> Mark, since you don't seem to rebase your branches, please start pushing
> back on these before they are committed to your tree (especially the
> non existent SHA1s).
Is there some scripting that does these checks (ideally someone would be
running a bot for this)?
TBH aside from the missing SHA1s (which are a definite issue, mainly
coming from Intel unfortunately) I'm struggling to see most of the
things you're reporting as substantial issues - I'm not sure that
tooling should be caring about much beyond the SHA1 in the tag, and if
it is then supporting wrapping like RFC822 headers doesn't seem
unreasonable.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-04-16 13:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-15 23:41 linux-next: Fixes tags needs some work in the sound-asoc tree Stephen Rothwell
2020-04-16 12:55 ` Pierre-Louis Bossart
2020-04-16 13:09 ` Mark Brown [this message]
2020-04-22 7:27 ` Daniel Baluta
2020-04-22 7:48 ` Mark Brown
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=20200416130925.GJ5354@sirena.org.uk \
--to=broonie@kernel$(echo .)org \
--cc=daniel.baluta@nxp$(echo .)com \
--cc=lgirdwood@gmail$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=pierre-louis.bossart@linux$(echo .)intel.com \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=yung-chuan.liao@linux$(echo .)intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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