qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Ninad Palsule <ninad@linux.ibm.com>
To: "Cédric Le Goater" <clg@kaod.org>,
	qemu-devel@nongnu.org, peter.maydell@linaro.org,
	andrew@codeconstruct.com.au, joel@jms.id.au, pbonzini@redhat.com,
	marcandre.lureau@redhat.com, berrange@redhat.com,
	thuth@redhat.com, philmd@linaro.org, lvivier@redhat.com
Cc: qemu-arm@nongnu.org, Andrew Jeffery <andrew@aj.id.au>
Subject: Re: [PATCH v10 2/9] hw/fsi: Introduce IBM's FSI Bus and FSI slave
Date: Thu, 25 Jan 2024 17:59:45 -0600	[thread overview]
Message-ID: <efe97ee9-c773-4779-90e0-b7eef7a4e68c@linux.ibm.com> (raw)
In-Reply-To: <aded5ed9-bdf5-4ee0-a213-aba7c1dcd74c@kaod.org>

Hello Cedric,

>>
>> The FSI slave: The slave is the terminal point of the FSI bus for
>> FSI symbols addressed to it. Slaves can be cascaded off of one
>> another. The slave's configuration registers appear in address space
>> of the CFAM to which it is attached.
>
> Please add another patch.
Added new patch for FSI-slave.
>
>> [ clg: - removed include/hw/fsi/engine-scratchpad.h and
>>              hw/fsi/engine-scratchpad.c
>>         - dropped FSI_SCRATCHPAD
>>         - included FSIBus definition
>>         - dropped hw/fsi/trace-events changes ]
>
> Move the list down before my S-o-b.
Moved the list.

Thanks for the review.

Regards,

Ninad




  reply	other threads:[~2024-01-26  0:01 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-10 23:15 [PATCH v10 0/9] Introduce model for IBM's FSI Ninad Palsule
2024-01-10 23:15 ` [PATCH v10 1/9] hw/fsi: Introduce IBM's Local bus and scratchpad Ninad Palsule
2024-01-12 14:53   ` Cédric Le Goater
2024-01-25 23:29     ` Ninad Palsule
2024-01-10 23:15 ` [PATCH v10 2/9] hw/fsi: Introduce IBM's FSI Bus and FSI slave Ninad Palsule
2024-01-12 15:03   ` Cédric Le Goater
2024-01-25 23:59     ` Ninad Palsule [this message]
2024-01-10 23:15 ` [PATCH v10 3/9] hw/fsi: Introduce IBM's cfam Ninad Palsule
2024-01-12 15:02   ` Cédric Le Goater
2024-01-26  0:09     ` Ninad Palsule
2024-01-10 23:15 ` [PATCH v10 4/9] hw/fsi: Introduce IBM's FSI master Ninad Palsule
2024-01-12 15:05   ` Cédric Le Goater
2024-01-16 19:43     ` Ninad Palsule
2024-01-10 23:15 ` [PATCH v10 5/9] hw/fsi: Aspeed APB2OPB interface, Onchip perif bus Ninad Palsule
2024-01-12 16:00   ` Cédric Le Goater
2024-01-26  2:23     ` Ninad Palsule
2024-01-10 23:15 ` [PATCH v10 6/9] hw/arm: Hook up FSI module in AST2600 Ninad Palsule
2024-01-10 23:15 ` [PATCH v10 7/9] hw/fsi: Added qtest Ninad Palsule
2024-01-12 16:02   ` Cédric Le Goater
2024-01-16 19:37     ` Ninad Palsule
2024-01-10 23:15 ` [PATCH v10 8/9] hw/fsi: Added FSI documentation Ninad Palsule
2024-01-12 16:02   ` Cédric Le Goater
2024-01-16 19:33     ` Ninad Palsule
2024-01-10 23:15 ` [PATCH v10 9/9] hw/fsi: Update MAINTAINER list Ninad Palsule
2024-01-12 16:03   ` Cédric Le Goater
2024-01-16 19:30     ` Ninad Palsule
2024-01-12 14:42 ` [PATCH v10 0/9] Introduce model for IBM's FSI Cédric Le Goater

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=efe97ee9-c773-4779-90e0-b7eef7a4e68c@linux.ibm.com \
    --to=ninad@linux.ibm.com \
    --cc=andrew@aj.id.au \
    --cc=andrew@codeconstruct.com.au \
    --cc=berrange@redhat.com \
    --cc=clg@kaod.org \
    --cc=joel@jms.id.au \
    --cc=lvivier@redhat.com \
    --cc=marcandre.lureau@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=philmd@linaro.org \
    --cc=qemu-arm@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@redhat.com \
    /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).