From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4 0/6] Board: Add Engicam i.MX6 SOMs
Date: Mon, 19 Jun 2017 14:18:34 +0200 [thread overview]
Message-ID: <20170619141834.56aedeb1@windsurf.lan> (raw)
In-Reply-To: <CAMty3ZBj53AcYx9dz-YjnjcW5S-O8fELPSvbmHz3fCmDSa3anQ@mail.gmail.com>
Hello,
On Mon, 19 Jun 2017 13:38:35 +0530, Jagan Teki wrote:
> > Thanks for this new iteration and those contributions. Since you're
> > regularly posting new iterations of this patch series, it would be nice
> > if you could create an account on patchwork, and mark yourself the
> > previous iterations of your patch series as "Superseded". This way, it
> > is easier for the maintainers to keep track of what is the latest
> > version of your patch series that should be considered for
> > review/merging.
> >
> > See https://patchwork.ozlabs.org/project/buildroot/list/. You just need
> > to create an account with the same e-mail address as the one used to
> > send the patches.
>
> I've a patchwork.ozlabs account with different mail id, I guess it is
> ok to reuse the same. What do you think?
It won't work: patchwork will only allow you to modify the patches for
which you are the author, by matching the email of the patchwork
account with the email of the patch author.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-06-19 12:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-19 7:27 [Buildroot] [PATCH v4 0/6] Board: Add Engicam i.MX6 SOMs Jagan Teki
2017-06-19 7:27 ` [Buildroot] [PATCH v4 1/6] board: Add support for Engicam i.CoreM6 DualLite/Solo boards Jagan Teki
2017-06-19 20:17 ` Thomas Petazzoni
2017-06-20 2:25 ` Jagan Teki
2017-06-20 5:46 ` Thomas Petazzoni
2017-06-20 8:56 ` Jagan Teki
2017-06-19 7:27 ` [Buildroot] [PATCH v4 2/6] board: engicam: Rename defconfig engicam_imx6qdl_icore_mmc_defconfig Jagan Teki
2017-06-19 20:19 ` Thomas Petazzoni
2017-06-20 2:30 ` Jagan Teki
2017-06-20 5:47 ` Thomas Petazzoni
2017-06-19 7:27 ` [Buildroot] [PATCH v4 3/6] board: Add support for Engicam i.CoreM6 RQS SOM Jagan Teki
2017-06-19 7:27 ` [Buildroot] [PATCH v4 4/6] board: engicam: Add icorem6 for i.CoreM6 support Jagan Teki
2017-06-19 7:27 ` [Buildroot] [PATCH v4 5/6] board: Add support for Engicam GEAM6UL SOM Jagan Teki
2017-06-19 7:27 ` [Buildroot] [PATCH v4 6/6] board: Add support for Engicam Is.IoT MX6UL SOM Jagan Teki
2017-06-19 7:41 ` [Buildroot] [PATCH v4 0/6] Board: Add Engicam i.MX6 SOMs Thomas Petazzoni
2017-06-19 8:08 ` Jagan Teki
2017-06-19 12:18 ` Thomas Petazzoni [this message]
2017-06-19 13:00 ` Jagan Teki
2017-06-19 13:24 ` Thomas Petazzoni
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=20170619141834.56aedeb1@windsurf.lan \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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