From: Andreas Herrmann <aherrmann@suse.de>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: liming.wu@jaguarmicro.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] genirq/debugfs: Fix a typo of irq debugfs
Date: Thu, 28 Sep 2023 11:48:31 +0200 [thread overview]
Message-ID: <20230928094831.GD7895@alberich> (raw)
In-Reply-To: <875y3ufxa2.ffs@tglx>
On Thu, Sep 28, 2023 at 11:43:33AM +0200, Thomas Gleixner wrote:
> On Wed, Sep 27 2023 at 10:29, liming wu wrote:
> > From: Liming Wu <liming.wu@jaguarmicro.com>
> >
> > Correct the spelling of effective.
>
> That spelling is on purpose to have tabular output, which you break with
> that change.
Hi Thomas,
I've received this email twice.
There seem to be many duplicate emails today (LKML, maybe other vger
lists as well).
Not sure what is causing this.
Do others observe this as well?
--
Regards,
Andreas
SUSE Software Solutions Germany GmbH
Frankenstrasse 146, 90461 Nürnberg, Germany
GF: Ivo Totev, Andrew McDonald, Werner Knoblich
(HRB 36809, AG Nürnberg)
next prev parent reply other threads:[~2023-09-28 9:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-27 2:29 [PATCH] genirq/debugfs: Fix a typo of irq debugfs liming.wu
2023-09-28 9:43 ` Thomas Gleixner
2023-09-28 9:48 ` Andreas Herrmann [this message]
2023-09-28 10:13 ` Andreas Herrmann
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=20230928094831.GD7895@alberich \
--to=aherrmann@suse.de \
--cc=liming.wu@jaguarmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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