Linux backports project
 help / color / mirror / Atom feed
From: Arend van Spriel <arend@broadcom.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "backports@vger.kernel.org" <backports@vger.kernel.org>
Subject: Re: backport devcoredump
Date: Wed, 9 Sep 2015 15:37:22 +0200	[thread overview]
Message-ID: <55F03612.6040809@broadcom.com> (raw)
In-Reply-To: <55F02882.5080207@broadcom.com>

On 09/09/2015 02:39 PM, Arend van Spriel wrote:
> On 09/09/2015 02:30 PM, Johannes Berg wrote:
>> On Wed, 2015-09-09 at 14:03 +0200, Arend van Spriel wrote:
>>>
>>>> I guess I'll need to run that - are you using a special copy-list?
>>>
>>> I do and maybe that is causing it. I attached it.
>>>
>>
>> Unlikely. However, I can't reproduce your issue - if I just add "select
>> WANT_DEV_COREDUMP" to your driver (brcmsmac) in my tree and compile
>> with that I do get it enabled.

I guess the WANT_DEV_COREDUMP must be in the source tree to generate 
drivers-base-devcoredump.c etc. I used backports generated tree using my 
copy-list so not driver selects WANT_DEV_COREDUMP, because I applied the 
brcmfmac devcoredump patch on the backports generated tree.

Gr. AvS

> Thanks for checking.
>
>> Can you share your driver changes for it?
>
> I will dig a bit deeper here. It must be something trivial. If I run
> with backports/master I do get drivers-base-devcoredump.c in compat
> folder so it must be in my branch which includes the copy-list change.
>
> Gr. AvS
>
> --
> To unsubscribe from this list: send the line "unsubscribe backports" in

--
To unsubscribe from this list: send the line "unsubscribe backports" in

  reply	other threads:[~2015-09-09 13:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-09  8:33 backport devcoredump Arend van Spriel
2015-09-09  8:49 ` Johannes Berg
2015-09-09 12:03   ` Arend van Spriel
2015-09-09 12:30     ` Johannes Berg
2015-09-09 12:39       ` Arend van Spriel
2015-09-09 13:37         ` Arend van Spriel [this message]
2015-09-09 13:54           ` Johannes Berg

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=55F03612.6040809@broadcom.com \
    --to=arend@broadcom.com \
    --cc=backports@vger.kernel.org \
    --cc=johannes@sipsolutions.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