Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] Bug report or teaching moment -- downloading kernel patches
Date: Sat, 30 Dec 2017 19:01:27 +0100	[thread overview]
Message-ID: <20171230180127.GI2921@scaer> (raw)
In-Reply-To: <CAF_dkJD0Qp_U5Efes44iiZegnG4+4++1DSQA7CvG9M_ekK84xA@mail.gmail.com>

Patrick, All,

On 2017-12-30 12:55 -0500, Patrick Doyle spake thusly:
> On Sat, Dec 30, 2017 at 12:10 PM, Yann E. MORIN <yann.morin.1998@free.fr> wrote:
> > On 2017-12-30 11:32 -0500, Patrick Doyle spake thusly:
> >> I can't figure this out...am I doing something wrong or have I uncovered a bug?
> >
> > Bug.
> Is there a workaround?  Or should I just wget the patch set into my dl
> directory (and put a big README reminding me & others to do the same)
> and hope that nobody forgets.

If the kernel is also available as a tarball, then use that instead of a
git clone.

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

      reply	other threads:[~2017-12-30 18:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-30 16:32 [Buildroot] Bug report or teaching moment -- downloading kernel patches Patrick Doyle
2017-12-30 17:10 ` Yann E. MORIN
2017-12-30 17:55   ` Patrick Doyle
2017-12-30 18:01     ` Yann E. MORIN [this message]

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=20171230180127.GI2921@scaer \
    --to=yann.morin.1998@free.fr \
    --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