ATH10K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Bart.Jooris@intec.ugent.be
Cc: ath10k@lists.infradead.org
Subject: Re: Compiling custom ath10k: step 5 minor issue
Date: Wed, 26 Feb 2014 19:35:38 +0200	[thread overview]
Message-ID: <87wqghkc9h.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <530BB3E2.8000705@intec.ugent.be> (Bart Jooris's message of "Mon,  24 Feb 2014 22:04:34 +0100")

Bart Jooris <Bart.Jooris@intec.ugent.be> writes:

> ../ath/net/core/flow_dissector.c seems to be changed?
>
> ./gentree.py --verbose --clean --git-revision master --copy-list
> copy-list.ath ../ath ../backports-output
> Get original source files from git ...
> Apply patches ...
> Not applying backport-adjustments/dma-buf.patch, not needed
> Applying patch backport-adjustments/flow_dissector.patch
>> patching file compat/net-core-flow_dissector.c
>> Hunk #1 FAILED at 177.
>> 1 out of 1 hunk FAILED -- saving rejects to file 
> compat/net-core-flow_dissector.c.rej

backports is always a moving target and you might get errors like these
when you create it on your own. There really isn't a reliable to avoid
it, you just have to fix the errors as you see them. 

Another option is that you use official backports releases, but then
ath10k will be few weeks old.

-- 
Kalle Valo

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

  reply	other threads:[~2014-02-26 17:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-24 21:04 Compiling custom ath10k: step 5 minor issue Bart Jooris
2014-02-26 17:35 ` Kalle Valo [this message]
2014-03-30 20:43   ` Bart Jooris
2014-03-30 21:26     ` Dave Taht

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=87wqghkc9h.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@qca.qualcomm.com \
    --cc=Bart.Jooris@intec.ugent.be \
    --cc=ath10k@lists.infradead.org \
    /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