From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH/next] gitlab-ci: regenerate after new defconfig addition
Date: Mon, 25 Nov 2019 20:46:36 +0100 [thread overview]
Message-ID: <20191125204636.67bc004f@windsurf> (raw)
In-Reply-To: <20191125204558.6a9f4e58@windsurf>
On Mon, 25 Nov 2019 20:45:58 +0100
Thomas Petazzoni <thomas.petazzoni@bootlin.com> wrote:
> On Mon, 25 Nov 2019 19:13:07 +0100
> Pierre-Jean Texier <pjtexier@koncepto.io> wrote:
>
> > Fixes b68022c7cb17d27acc14ff64434413e8c93d7a56 ("board: add Beelink GS1 support")
> >
> > Signed-off-by: Pierre-Jean Texier <pjtexier@koncepto.io>
> > ---
> > .gitlab-ci.yml | 1 +
> > 1 file changed, 1 insertion(+)
>
> Applied to master, thanks.
Sorry, I've applied to next, I used the wrong keyboard shortcut when
replying.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-11-25 19:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-25 18:13 [Buildroot] [PATCH/next] gitlab-ci: regenerate after new defconfig addition Pierre-Jean Texier
2019-11-25 19:45 ` Thomas Petazzoni
2019-11-25 19:46 ` Thomas Petazzoni [this message]
2019-11-25 19:48 ` Pierre-Jean Texier
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=20191125204636.67bc004f@windsurf \
--to=thomas.petazzoni@bootlin.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 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.