From: Borislav Petkov <bp@alien8.de>
To: Saurabh Singh Sengar <ssengar@microsoft.com>
Cc: Saurabh Sengar <ssengar@linux.microsoft.com>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"mingo@redhat.com" <mingo@redhat.com>,
"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
"x86@kernel.org" <x86@kernel.org>,
"hpa@zytor.com" <hpa@zytor.com>,
"johan+linaro@kernel.org" <johan+linaro@kernel.org>,
"isaku.yamahata@intel.com" <isaku.yamahata@intel.com>,
"Michael Kelley (LINUX)" <mikelley@microsoft.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"andriy.shevchenko@intel.com" <andriy.shevchenko@intel.com>
Subject: Re: [PATCH] x86/ioapic: Don't return 0 as valid virq
Date: Mon, 13 Mar 2023 12:07:23 +0100 [thread overview]
Message-ID: <20230313110723.GCZA8D6zsM7ZuXIBD+@fat_crate.local> (raw)
In-Reply-To: <PUZP153MB0749DD5C9CE7B60DDC75ADACBEB99@PUZP153MB0749.APCP153.PROD.OUTLOOK.COM>
On Mon, Mar 13, 2023 at 03:37:44AM +0000, Saurabh Singh Sengar wrote:
> I just see mail to rahul.tanwar@linux.intel.com is undelivered, shall I still add it in "Cc:" ?
> Please let me know what we usually do in such cases.
You were posting just fine inline, why do you have to top-post now?
If it is undelivered, then the address is probably invalid now so drop
it.
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2023-03-13 11:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-02 19:34 [PATCH] x86/ioapic: Don't return 0 as valid virq Saurabh Sengar
2023-03-09 17:14 ` Saurabh Singh Sengar
2023-03-12 20:40 ` Borislav Petkov
2023-03-13 3:29 ` [EXTERNAL] " Saurabh Singh Sengar
2023-03-13 3:37 ` Saurabh Singh Sengar
2023-03-13 11:07 ` Borislav Petkov [this message]
2023-03-13 11:14 ` [EXTERNAL] " Borislav Petkov
2023-03-14 10:23 ` Saurabh Singh Sengar
2023-03-24 7:09 ` Saurabh Singh Sengar
2023-03-24 15:39 ` [EXTERNAL] " Thomas Gleixner
2023-03-24 16:24 ` Saurabh Singh Sengar
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=20230313110723.GCZA8D6zsM7ZuXIBD+@fat_crate.local \
--to=bp@alien8.de \
--cc=andriy.shevchenko@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=isaku.yamahata@intel.com \
--cc=johan+linaro@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikelley@microsoft.com \
--cc=mingo@redhat.com \
--cc=ssengar@linux.microsoft.com \
--cc=ssengar@microsoft.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.