qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: Jared Rossi <jrossi@linux.ibm.com>,
	qemu-s390x@nongnu.org, qemu-devel@nongnu.org
Cc: frankja@linux.ibm.com, jjherne@linux.ibm.com
Subject: Re: [PATCH 0/1] pc-bios: Support List-Directed IPL from ECKD DASD
Date: Mon, 20 Feb 2023 17:33:06 +0100	[thread overview]
Message-ID: <25258b60-f752-99e1-8916-516399e02fac@redhat.com> (raw)
In-Reply-To: <eba35cef-32d1-69cd-2fc5-638880e2ee63@linux.ibm.com>

On 20/02/2023 17.21, Jared Rossi wrote:
> On 2/20/23 10:45 AM, Thomas Huth wrote:
>> On 20/02/2023 16.13, Jared Rossi wrote:
>>> Hi,
>>>
>>> Pinging this patch since v2.26.0 of s390-tools adds ECKD DASD 
>>> list-directed IPL.
>>> This patch set allows QEMU to utilize that new boot pointer format.
>>> Any feedback about what needs to be changed for acceptance is much 
>>> appreciated.
>>
>> Where did you send your patches to? I can't find it in neither my 
>> qemu-s390x nor my qemu-devel mailing list folders.
>>
>>  Thomas
> 
> Hi Thomas,
> 
> I tried to send them toqemu-s390x@nongnu.org  andqemu-devel@nongnu.org  lists with some additional people (including you)
> in CC.  The initial mail was on January 30th.  I can resend them if there was a problem with the delivery.

I also don't see your mail in the usual archives, e.g. not in:

  https://lore.kernel.org/qemu-devel/?q=Support+List-Directed+IPL+from+ECKD+DASD

and also not in:

  https://lists.gnu.org/archive/html/qemu-devel/2023-01/threads.html

It seems like your patches never left your mail server. Thus please resend!

  Thanks,
   Thomas



      reply	other threads:[~2023-02-20 16:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230130212411.1167822-1-jrossi@linux.ibm.com>
2023-02-20 15:13 ` [PATCH 0/1] pc-bios: Support List-Directed IPL from ECKD DASD Jared Rossi
2023-02-20 15:45   ` Thomas Huth
2023-02-20 16:21     ` Jared Rossi
2023-02-20 16:33       ` Thomas Huth [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=25258b60-f752-99e1-8916-516399e02fac@redhat.com \
    --to=thuth@redhat.com \
    --cc=frankja@linux.ibm.com \
    --cc=jjherne@linux.ibm.com \
    --cc=jrossi@linux.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-s390x@nongnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).