From: 'Greg KH' <gregkh@linuxfoundation.org>
To: John Aron <john@aronetics.com>
Cc: 'Mark Salter' <mark.salter@canonical.com>,
'Mark Lewis' <mark.lewis@canonical.com>,
regressions@lists.linux.dev, stable@vger.kernel.org,
kernelnewbies@kernelnewbies.org
Subject: Re: OBJTOOL Build error
Date: Thu, 1 Dec 2022 17:40:05 +0100 [thread overview]
Message-ID: <Y4jY5TTLkfoSb0CJ@kroah.com> (raw)
In-Reply-To: <002e01d9059c$eb052400$c10f6c00$@aronetics.com>
On Thu, Dec 01, 2022 at 10:52:16AM -0500, John Aron wrote:
> On Wed, Nov 30, 2022 at 06:36:19PM -0500, John Aron wrote:
> > One C file and a few header files.
>
> Can you provide a link to them so that we can see what might be the problem?
> Without that, it's impossible to help, sorry.
> --
> The repo is in a private repo online, the entry is:
> static int __init kernel_module_start(void)
<snip>
Without the full source, it's pretty impossible to help, sorry.
thanks,
greg k-h
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
WARNING: multiple messages have this Message-ID (diff)
From: 'Greg KH' <gregkh@linuxfoundation.org>
To: John Aron <john@aronetics.com>
Cc: 'Mark Salter' <mark.salter@canonical.com>,
'Mark Lewis' <mark.lewis@canonical.com>,
regressions@lists.linux.dev, stable@vger.kernel.org,
kernelnewbies@kernelnewbies.org
Subject: Re: OBJTOOL Build error
Date: Thu, 1 Dec 2022 17:40:05 +0100 [thread overview]
Message-ID: <Y4jY5TTLkfoSb0CJ@kroah.com> (raw)
In-Reply-To: <002e01d9059c$eb052400$c10f6c00$@aronetics.com>
On Thu, Dec 01, 2022 at 10:52:16AM -0500, John Aron wrote:
> On Wed, Nov 30, 2022 at 06:36:19PM -0500, John Aron wrote:
> > One C file and a few header files.
>
> Can you provide a link to them so that we can see what might be the problem?
> Without that, it's impossible to help, sorry.
> --
> The repo is in a private repo online, the entry is:
> static int __init kernel_module_start(void)
<snip>
Without the full source, it's pretty impossible to help, sorry.
thanks,
greg k-h
next prev parent reply other threads:[~2022-12-01 16:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-24 18:48 OBJTOOL Build error John Aron
2022-11-24 18:48 ` John Aron
2022-11-24 21:06 ` Greg KH
2022-11-24 21:06 ` Greg KH
2022-11-30 23:36 ` John Aron
2022-11-30 23:36 ` John Aron
2022-12-01 5:57 ` Greg KH
2022-12-01 5:57 ` Greg KH
2022-12-01 15:52 ` John Aron
2022-12-01 15:52 ` John Aron
2022-12-01 16:40 ` 'Greg KH' [this message]
2022-12-01 16:40 ` 'Greg KH'
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=Y4jY5TTLkfoSb0CJ@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=john@aronetics.com \
--cc=kernelnewbies@kernelnewbies.org \
--cc=mark.lewis@canonical.com \
--cc=mark.salter@canonical.com \
--cc=regressions@lists.linux.dev \
--cc=stable@vger.kernel.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 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.