qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: Mohamed ElSayed <m.elsayed4420@gmail.com>
Cc: qemu-arm@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [PULL SUBSYSTEM arm 0/8] TivaC Implementation
Date: Tue, 16 May 2023 10:00:09 +0100	[thread overview]
Message-ID: <87bkikprs7.fsf@linaro.org> (raw)
In-Reply-To: <20230516072959.49994-1-m.elsayed4420@gmail.com>


Mohamed ElSayed <m.elsayed4420@gmail.com> writes:

> ***
> This is an implementation for the TivaC board.
> For now it models the system control block, the general purpose I/O, the general purpose timers, the watchdog timers and the usart module.
>
> The code is available at https://github.com/moesay/qemu_TivaC.git
> ***

Hi Mohamed,

I'm afraid this pull request won't get processed. Pull requests are sent
by maintainers who are listed in the MAINTAINERS file with signed PRs.
If you want to get support for the TivacC board up-streamed you should
post a series of patches and participate in code review. We have some
general guidance for the process here:

  https://qemu.readthedocs.io/en/latest/devel/submitting-a-patch.html

A couple of general points to get you started:

 - patch 7

   This is obviously wrong as it updates the project README with your
   personal fork information.

 - patch 8

   code format fixes to your own code should be folded into the relevant commit

 - use of qemu_log

   direct use of qemu_log is discouraged. Generally for devices you
   would be using qemu_log_mask with LOG_UNIMP or LOG_GUEST_ERROR as
   appropriate. Think about if the log point would be better handled at
   a tracepoint (or removed completely if it was a debugging aid during
   development).

-- 
Alex Bennée
Virtualisation Tech Lead @ Linaro


      parent reply	other threads:[~2023-05-16  9:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-16  7:29 [PULL SUBSYSTEM arm 0/8] TivaC Implementation Mohamed ElSayed
2023-05-16  7:29 ` [PULL 1/8] the tivac machine def init commit Mohamed ElSayed
2023-05-16  7:29 ` [PULL 2/8] tivac usart module implementation Mohamed ElSayed
2023-05-16  7:29 ` [PULL 3/8] tivac gpio " Mohamed ElSayed
2023-05-16  7:29 ` [PULL 4/8] tivac system control implementation Mohamed ElSayed
2023-05-16  7:29 ` [PULL 5/8] tivac general purpose timers implementation Mohamed ElSayed
2023-05-16  7:29 ` [PULL 6/8] tivac watchdog " Mohamed ElSayed
2023-05-16  7:29 ` [PULL 7/8] editing the meson and KConfig files to add tivac to qemu build system Mohamed ElSayed
2023-05-16  7:29 ` [PULL 8/8] code style fixes Mohamed ElSayed
2023-05-16  9:00 ` Alex Bennée [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=87bkikprs7.fsf@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=m.elsayed4420@gmail.com \
    --cc=qemu-arm@nongnu.org \
    --cc=qemu-devel@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).