linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tinghan Shen <tinghan.shen@mediatek.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	Mark Brown <broonie@kernel.org>,
	Liam Girdwood <lgirdwood@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"Linux Next Mailing List" <linux-next@vger.kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the sound-asoc tree
Date: Thu, 28 Apr 2022 11:04:04 +0800	[thread overview]
Message-ID: <8e3aa7fce171bfcc5eeb7202906df89895330fd8.camel@mediatek.com> (raw)
In-Reply-To: <20220428105708.57aeda36@canb.auug.org.au>

Hi Stephen,

On Thu, 2022-04-28 at 10:57 +1000, Stephen Rothwell wrote:
> Hi all,
> 
> In commit
> 
>   9ce170dc9c08 ("ASoC: SOF: mediatek: Fix allyesconfig build error")
> 
> Fixes tag
> 
>   Fixes: 570c14dc92d5 ("ASoC: SOF: mediatek: Add mt8186 sof fw loader and
> 
> 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.  Also, please keep
> all the commit message tags together at the end of the commit message.
> 
> This whole commit message was badly word wrapped :-(

It's because I want to keep the original build message and 
wrap at the 75 columns at the same time. After look back of
your ealier email, I should refrain from doing so and leave the 
build message unwrapped, as you did.

I apologize for the fault, I'll keep this in my mind.


Thanks,
TingHan





  reply	other threads:[~2022-04-28  3:04 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-28  0:57 linux-next: Fixes tag needs some work in the sound-asoc tree Stephen Rothwell
2022-04-28  3:04 ` Tinghan Shen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-11-13 20:58 Stephen Rothwell
2023-09-28 21:41 Stephen Rothwell
2022-07-19 22:22 Stephen Rothwell
2022-05-17 22:01 Stephen Rothwell
2022-03-08 21:32 Stephen Rothwell
2022-03-02 21:01 Stephen Rothwell
2021-12-01 21:25 Stephen Rothwell
2021-12-02  9:29 ` Charles Keepax
2021-06-14 22:11 Stephen Rothwell
2021-05-12 22:40 Stephen Rothwell
2021-04-14 22:01 Stephen Rothwell
2020-07-29 22:04 Stephen Rothwell
2020-04-06 21:49 Stephen Rothwell
2020-03-29  0:09 Stephen Rothwell
2020-03-14 10:50 Stephen Rothwell
2020-03-16  8:21 ` Kai Vehmanen
2020-03-01  5:45 Stephen Rothwell
2020-02-24 22:30 Stephen Rothwell
2019-10-15 11:30 Stephen Rothwell
2019-10-15 11:35 ` Peter Ujfalusi
2019-08-20 22:25 Stephen Rothwell
2019-08-20 21:04 Stephen Rothwell
2019-08-20 22:27 ` Stephen Rothwell
2019-08-15 21:59 Stephen Rothwell
2019-08-15 21:34 Stephen Rothwell
2019-07-25 21:27 Stephen Rothwell
2019-07-26  6:04 ` Peter Ujfalusi
2019-07-26 12:11   ` Mark Brown
2019-07-29  5:57     ` Peter Ujfalusi
2019-07-10 16:13 Stephen Rothwell
2019-07-11  0:40 ` Tzung-Bi Shih
2019-06-30 21:49 Stephen Rothwell
2019-06-26 13:42 Stephen Rothwell
2019-05-30 22:02 Stephen Rothwell
2019-05-21 21:31 Stephen Rothwell
2019-05-17 11:12 Stephen Rothwell
2019-05-17  2:41 S.j. Wang
2019-05-16 22:34 Stephen Rothwell
2019-03-18 11:18 Stephen Rothwell
2019-03-17  1:34 Stephen Rothwell
     [not found] <CGME20190317012907epcas3p129240b3dcef7d974c2fea23c26a76f2a@epcas3p1.samsung.com>
2019-03-17  1:28 ` Stephen Rothwell
2019-03-18 10:08   ` Sylwester Nawrocki
2019-01-28 20:27 Stephen Rothwell

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=8e3aa7fce171bfcc5eeb7202906df89895330fd8.camel@mediatek.com \
    --to=tinghan.shen@mediatek.com \
    --cc=broonie@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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).