public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Laszlo Ersek" <lersek@redhat.com>
To: devel@edk2.groups.io, yuinyee.chew@starfivetech.com,
	Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
Cc: Sunil V L <sunilvl@ventanamicro.com>, Li Yong <yong.li@intel.com>,
	Leif Lindholm <quic_llindhol@quicinc.com>,
	Ard Biesheuvel <ardb+tianocore@kernel.org>,
	Abner Chang <abner.chang@amd.com>,
	Daniel Schaefer <git@danielschaefer.me>,
	"ardb@kernel.org" <ardb@kernel.org>
Subject: Re: [edk2-devel] [PATCH v1] EmbeddedPkg/NorFlashInfoLib: Update norflash device list
Date: Fri, 20 Oct 2023 14:32:12 +0200	[thread overview]
Message-ID: <6e18393e-c82c-53c3-3f37-ccc90a7c4140@redhat.com> (raw)
In-Reply-To: <864cd8f6-2a52-2a42-4dc5-e36a23bc3d2f@redhat.com>

On 10/20/23 14:25, Laszlo Ersek wrote:
> On 10/20/23 13:30, John Chew wrote:
>> Hi Heinrich, Laszlo,
>>
>> Thank you very much for your support! Really appreciate it =D
>>
>> My account just approved few days ago, so original patch (submit few weeks back) is not in the mailing list.
> 
> Let me rectify that in a minute.

huh, I thought I'd find the patch email as "pending moderation" in the
moderators' queue, but it's not there.

(I can see you having been added as a member; your new messages seem to
be reflected, so that should be fine.)

I assume either one of the mods mis-clicked on your initial submission
(from 29 September, I think?), rejecting or deleting it instead or
approving it, or else nobody had taken notice and your patch email
"timed out". (I don't know if that's possible with groups.io; just
guessing.)

Either way I think I should have it from Heinrich now...

Laszlo



-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#109849): https://edk2.groups.io/g/devel/message/109849
Mute This Topic: https://groups.io/mt/101660590/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/leave/12367111/7686176/1913456212/xyzzy [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-



  reply	other threads:[~2023-10-20 12:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230929020222.2010-1-yuinyee.chew@starfivetech.com>
2023-09-29  8:54 ` [edk2-devel] [PATCH v1] EmbeddedPkg/NorFlashInfoLib: Update norflash device list Heinrich Schuchardt
     [not found]   ` <7844b7331b5f42019dfdf3fc706671c0@EXMBX073.cuchost.com>
2023-09-29 14:10     ` Heinrich Schuchardt
2023-10-18  8:49     ` John Chew
2023-10-18  8:57       ` Ard Biesheuvel
2023-10-20  8:51         ` John Chew
2023-10-20  9:49         ` Laszlo Ersek
2023-10-20 10:43           ` Heinrich Schuchardt
2023-10-20 11:30             ` John Chew
2023-10-20 12:25               ` Laszlo Ersek
2023-10-20 12:32                 ` Laszlo Ersek [this message]
2023-10-20 12:25           ` Ard Biesheuvel
2023-10-20 13:40             ` Laszlo Ersek
2023-10-23  1:20               ` John Chew

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-list 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=6e18393e-c82c-53c3-3f37-ccc90a7c4140@redhat.com \
    --to=devel@edk2.groups.io \
    /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