Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] configs/raspberrypi3: sync kernel version with rpi/rpi2
Date: Wed, 27 Apr 2016 23:37:08 +0200	[thread overview]
Message-ID: <87oa8uzqbf.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <57212C26.5090308@beneth.fr> ("Benoît Mauduit"'s message of "Wed, 27 Apr 2016 23:16:22 +0200")

>>>>> "Beno?t" == Beno?t Mauduit <bmauduit@beneth.fr> writes:

 > On 04/27/2016 10:40 PM, Peter Korsgaard wrote:
 >> 
 >> Ehh, but we are already using rpi-4.4.y? (3de2328 from April 21st) -
 >> With that said, we can certainly move to e63db5. Care to send a patch to
 >> update raspberry{,2,3}_defconfig?
 >> 

 > Ouuups, I was already on this 4.4 branch after trying to work on Kodi,
 > before April 21st, I missed the buildroot change...

 > Patchs are ready for raspberry{,2,3}_defconfig, I am just waiting a
 > build to confirm that it is working.

Thanks. What about rpi1?

 > I took the last commit on rpi-4.4.y branch, which is now :
 > 26f3b72a9c049be10e6af196252283e1f6ab9d1f. (Kernel 4.4.8).

Ok.

 > Just a question, seeing how buildroot manage defconfig : Is it really
 > useful to add comments (And re-order Kconfig option) in defconfig ? Some
 > people read defconfigs ?

We don't really have any strong policy about it. I do find the commits
are nice for documentation, but it is true that they break 'make
savedefconfig'.

Anybody else having an opinion about this?

-- 
Venlig hilsen,
Peter Korsgaard 

  reply	other threads:[~2016-04-27 21:37 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-26 14:27 [Buildroot] [git commit] configs/raspberrypi3: sync kernel version with rpi/rpi2 Oscar Gomez Fuente
2016-04-26 14:38 ` Peter Korsgaard
2016-04-26 15:09   ` Oscar Gomez Fuente
2016-04-26 15:30     ` Peter Korsgaard
2016-04-26 17:51       ` Peter Korsgaard
2016-04-26 19:39         ` Peter Seiderer
2016-04-26 20:58           ` Benoît Mauduit
2016-04-27 20:40             ` Peter Korsgaard
2016-04-27 21:16               ` Benoît Mauduit
2016-04-27 21:37                 ` Peter Korsgaard [this message]
2016-04-27  6:50           ` Peter Korsgaard
2016-04-27  8:24             ` Peter Seiderer
2016-04-27 11:47               ` Oscar Gomez Fuente
2016-04-28  6:53               ` Peter Korsgaard
2016-04-27  6:58           ` Oscar Gomez Fuente
2016-04-27  7:28             ` Oscar Gomez Fuente
2016-04-27  8:19               ` Peter Seiderer
2016-04-27  8:14             ` Peter Seiderer
  -- strict thread matches above, loose matches on Subject: below --
2016-04-25 12:07 Peter Korsgaard

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=87oa8uzqbf.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.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