public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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 12:13:54 +0200	[thread overview]
Message-ID: <20230928101354.GA10436@alberich> (raw)
In-Reply-To: <20230928094831.GD7895@alberich>

On Thu, Sep 28, 2023 at 11:48:32AM +0200, Andreas Herrmann wrote:
> 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?

Never mind. It seems to be on my end -- somehow.
Don't care at the moment.

Examples:

fetchmail:
2023-09-28T12:02:34: reading message aherrmann@mutt@imap.suse.de:1 of 2 (15900 header octets) (2222 body octets) flushed
2023-09-28T12:02:34: reading message aherrmann@mutt@imap.suse.de:1 of 2 (15900 header octets) (2222 body octets) flushed
mutt:
23339     Sep 28 Miguel Luis     (2.1K) │   └─>
23340     Sep 28 Miguel Luis     (2.1K) │     └=>

fetchmail:
2023-09-28T12:02:35: reading message aherrmann@mutt@imap.suse.de:2 of 2 (6029 header octets) (9197 body octets) flushed
2023-09-28T12:02:35: reading message aherrmann@mutt@imap.suse.de:2 of 2 (6029 header octets) (0 body octets) flushed
mutt:
25751 N ! Sep 28 AngeloGioacchin (8.7K) └─>Re: [PATCH v10 5/9] drm/mediatek: Add connector dynamic selection capability
25752 N ! Sep 28 AngeloGioacchin (  0K)   └=>
{the 2nd mail has empty body}

The first duplicate email from LKML seems to be
Sep 11 Casey Schaufler (8.4K) &─&=>Re: [PATCH v14 04/11] LSM: syscalls for current process attributes
Date: Mon, 11 Sep 2023 15:08:48 -0700

Odd.

-- 
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)

      reply	other threads:[~2023-09-28 10:12 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
2023-09-28 10:13     ` Andreas Herrmann [this message]

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=20230928101354.GA10436@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