linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joerg Roedel <joro@8bytes.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Hans de Goede <hdegoede@redhat.com>
Subject: Re: linux-next: Fixes tag needs some work in the iommu tree
Date: Fri, 13 Mar 2020 14:26:01 +0100	[thread overview]
Message-ID: <20200313132601.GM3794@8bytes.org> (raw)
In-Reply-To: <20200311093638.3b442a3d@canb.auug.org.au>

On Wed, Mar 11, 2020 at 09:36:38AM +1100, Stephen Rothwell wrote:
> Hi all,
> 
> In commit
> 
>   57744190bf30 ("iommu/vt-d: dmar: replace WARN_TAINT with pr_warn + add_taint")
> 
> Fixes tag
> 
>   Fixes: fd0c8894893c ("intel-iommu: Set a more specific taint flag for invalid BI
> 
> has these problem(s):
> 
>   - Subject has leading but no trailing parentheses
>   - Subject has leading but no trailing quotes
> 
> Please do not truncate Fixes tag lines.

Fixed now, thanks.



  reply	other threads:[~2020-03-13 13:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-10 22:36 linux-next: Fixes tag needs some work in the iommu tree Stephen Rothwell
2020-03-13 13:26 ` Joerg Roedel [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-02-11 21:12 Stephen Rothwell
2025-02-14  8:13 ` Joerg Roedel
2022-04-29 13:01 Stephen Rothwell
2022-05-04  8:33 ` Joerg Roedel
2021-04-15 21:51 Stephen Rothwell
2021-04-16  7:57 ` Dafna Hirschfeld
2020-06-30 21:01 Stephen Rothwell
2020-05-19 18:36 Stephen Rothwell
2020-05-25 11:55 ` Joerg Roedel
2019-09-01 21:36 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=20200313132601.GM3794@8bytes.org \
    --to=joro@8bytes.org \
    --cc=hdegoede@redhat.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).