From: Borislav Petkov <bp@alien8.de>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>,
Tony Luck <tony.luck@intel.com>,
Sergey Shtylyov <s.shtylyov@omp.ru>,
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 edac tree
Date: Sun, 30 Jan 2022 01:08:11 +0100 [thread overview]
Message-ID: <YfXW6+1hTVVTodeI@zn.tnic> (raw)
In-Reply-To: <20220130103712.391407a7@canb.auug.org.au>
On Sun, Jan 30, 2022 at 10:37:12AM +1100, Stephen Rothwell wrote:
> Fixes tag
>
> Fixes: 0d4429301c4 ("EDAC: Add APM X-Gene SoC EDAC driver")
Fixes: 0d4429301c4a ("EDAC: Add APM X-Gene SoC EDAC driver")
Somebody ate the trailing 'a'. Fixed.
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2022-01-30 0:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-29 23:37 linux-next: Fixes tag needs some work in the edac tree Stephen Rothwell
2022-01-30 0:08 ` Borislav Petkov [this message]
2022-01-30 9:30 ` Sergey Shtylyov
2022-01-30 10:31 ` Borislav Petkov
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=YfXW6+1hTVVTodeI@zn.tnic \
--to=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mchehab+samsung@kernel.org \
--cc=s.shtylyov@omp.ru \
--cc=sfr@canb.auug.org.au \
--cc=tony.luck@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