From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: Mark Brown <broonie@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Zhu Yingjiang <yingjiang.zhu@linux.intel.com>,
Guennadi Liakhovetski <guennadi.liakhovetski@linux.intel.com>,
Keyon Jie <yang.jie@linux.intel.com>,
Libin Yang <libin.yang@intel.com>,
Ranjani Sridharan <ranjani.sridharan@linux.intel.com>
Subject: Re: linux-next: Fixes tags need some work in the sound-asoc tree
Date: Wed, 29 May 2019 10:00:23 +1000 [thread overview]
Message-ID: <20190529100023.4a7cfacc@canb.auug.org.au> (raw)
In-Reply-To: <44bbb3f1-5674-6431-5818-d8b5cca708dd@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 760 bytes --]
Hi Pierre-Louis,
On Tue, 28 May 2019 17:22:40 -0500 Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com> wrote:
>
> On 5/28/19 4:56 PM, Stephen Rothwell wrote:
> > Hi all,
> >
> > In commit
> >
> > be1b577d0178 ("ASoC: SOF: Intel: hda: fix the hda init chip")
> >
> > Fixes tag
> >
> > Fixes: 8a300c8fb17 ("ASoC: SOF: Intel: Add HDA controller for Intel DSP")
>
> Sorry about that, not sure how I managed to add an off-by-one in all
> these tags. Checkpatch.pl --strict did not report any issues, something
> must be broken either in my setup or the script.
> Not sure how I can fix this now?
Its not worth the rebase necessary to fix them. Just use it as a
learning experience.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-05-29 0:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-28 21:56 linux-next: Fixes tags need some work in the sound-asoc tree Stephen Rothwell
2019-05-28 21:57 ` Stephen Rothwell
2019-05-28 22:22 ` Pierre-Louis Bossart
2019-05-29 0:00 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-04-08 21: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=20190529100023.4a7cfacc@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=broonie@kernel.org \
--cc=guennadi.liakhovetski@linux.intel.com \
--cc=lgirdwood@gmail.com \
--cc=libin.yang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=ranjani.sridharan@linux.intel.com \
--cc=yang.jie@linux.intel.com \
--cc=yingjiang.zhu@linux.intel.com \
/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