All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 1207] New: linux26-menuconfig does not apply all kernel patches
Date: Mon,  1 Mar 2010 18:57:43 +0000 (UTC)	[thread overview]
Message-ID: <bug-1207-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=1207

           Summary: linux26-menuconfig does not apply all kernel patches
           Product: buildroot
           Version: unspecified
          Platform: PC
        OS/Version: Windows
            Status: NEW
          Severity: minor
          Priority: P5
         Component: Other
        AssignedTo: unassigned at buildroot.uclibc.org
        ReportedBy: will_wagner at carallon.com
                CC: buildroot at uclibc.org
   Estimated Hours: 0.0


Created an attachment (id=1171)
 --> (https://bugs.busybox.net/attachment.cgi?id=1171)
fix for linux26-menuconfig

If your target has board specific kernel patches and you do the following:

make linux26clean
make linux26-menuconfig

Then it will not apply your board patches before opening menuconfig. The
attached patch fixes the issue.


-- 
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

             reply	other threads:[~2010-03-01 18:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-01 18:57 bugzilla at busybox.net [this message]
2010-04-09 14:54 ` [Buildroot] [Bug 1207] linux26-menuconfig does not apply all kernel patches bugzilla at busybox.net
2010-06-24 10:26 ` bugzilla at busybox.net

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=bug-1207-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --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.