From: vitor <vitor.soares@synopsys.com>
To: Boris Brezillon <bbrezillon@kernel.org>,
linux-i3c <linux-i3c@lists.infradead.org>
Subject: I3C Tree - Development flow
Date: Mon, 28 Jan 2019 11:35:36 +0000 [thread overview]
Message-ID: <12d083d6-3973-0d07-ccc9-c28c2ae1aa81@synopsys.com> (raw)
Hi Boris,
I'm not understanding the development flow.
I see the fixes going to fixes and master branches but not to next.
I was expecting that next has the most recent fixes/new features
which it isn't the case. Any advice?
Thanks and best regards,
Vitor Soares
_______________________________________________
linux-i3c mailing list
linux-i3c@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-i3c
next reply other threads:[~2019-01-28 11:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-28 11:35 vitor [this message]
2019-01-28 11:52 ` I3C Tree - Development flow Boris Brezillon
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=12d083d6-3973-0d07-ccc9-c28c2ae1aa81@synopsys.com \
--to=vitor.soares@synopsys.com \
--cc=bbrezillon@kernel.org \
--cc=linux-i3c@lists.infradead.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).