All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yoshinori Sato <ysato@users.sourceforge.jp>
To: Richard Henderson <richard.henderson@linaro.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] How to add a new target architecture
Date: Mon, 07 Jan 2019 22:00:06 +0900	[thread overview]
Message-ID: <874laklj1l.wl-ysato@users.sourceforge.jp> (raw)
In-Reply-To: <f94b78c0-888e-4c53-d314-9739c0b0cc3a@linaro.org>

On Mon, 07 Jan 2019 06:48:33 +0900,
Richard Henderson wrote:
> 
> On 1/6/19 11:11 PM, Yoshinori Sato wrote:
> > Hello.
> > I written Renesas RX port.
> > It is works to boot linux kernel of minimal configuration.
> > 
> > I'd like to merge this into the qmeu release and I need some
> > advice on how to proceed.
> > I tried reading wiki.qemu.org, but I could not find useful
> > information about adding subsystems.
> > 
> > git repository is bellow.
> > git://git.pf.osdn.net/gitroot/y/ys/ysato/qemu.git
> 
> You'll need to produce a patch set that applies to master.
> The easiest way is probably to merge master, diff, and then
> apply the diff to a new branch.  Try to split the diff into
> a few logical parts, e.g. target/rx/, hw/rx/, and last to
> enable the port in configure.
> 
> The patch set should follow the CODING_STYLE.  You can use
> ./scripts/check_patch.pl to help find coding style problems.
> 
> Your patch set should modify MAINTAINERS to group all of the
> rx related files, and list whoever is going to maintain the
> port going forward, e.g. yourself.
>

Thanks comment.
I understood the composition of the patch.
I will clean up and post.

> 
> r~
> 

-- 
Yosinori Sato

      reply	other threads:[~2019-01-07 13:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-06 13:11 [Qemu-devel] How to add a new target architecture Yoshinori Sato
2019-01-06 21:48 ` Richard Henderson
2019-01-07 13:00   ` Yoshinori Sato [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=874laklj1l.wl-ysato@users.sourceforge.jp \
    --to=ysato@users.sourceforge.jp \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.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.