Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] configs/arcturus_ucls1012a: new defconfig
Date: Thu, 1 Mar 2018 22:43:21 +0100	[thread overview]
Message-ID: <20180301224321.1b3ee3ef@windsurf.lan> (raw)
In-Reply-To: <3349d749-230a-60ef-c341-9a7e438bf921@arcturusnetworks.com>

Hello Oleksandr,

On Thu, 1 Mar 2018 14:19:18 -0500, Oleksandr G Zhadan wrote:

> I am addressing these questions to you, because we where working 
> together to commit previous Arcturus BSP package to the buildroot.
> Your help was very useful and it was done in relatively short period of 
> time.
> 
> The questions:
> I sent our new BSP support patches (see bellow)? month ago and no one 
> applied them or replied with any comments.
> Is anything changed in patches submitting procedure ?
> What is the usual and the longest wait time for patches to be committed ?

There is nothing wrong in how you submitted your patch. It's just that
we have a 250+ patches backlog. Yours is by far not the oldest: you can
check the list at http://patchwork.ozlabs.org/project/buildroot/list/.
I know it is not great to have so many patches waiting for so long, but
we are doing our best to review all those contributions.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
http://bootlin.com

  reply	other threads:[~2018-03-01 21:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-29 23:08 [Buildroot] [PATCH] configs/arcturus_ucls1012a: new defconfig Oleksandr Zhadan
2018-03-01 19:19 ` Oleksandr G Zhadan
2018-03-01 21:43   ` Thomas Petazzoni [this message]
2018-03-02 14:33     ` Oleksandr G Zhadan

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=20180301224321.1b3ee3ef@windsurf.lan \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox