From: Greg KH <gregkh@linuxfoundation.org>
To: Jim Cromie <jim.cromie@gmail.com>
Cc: jbaron@akamai.com, linux-kernel@vger.kernel.org
Subject: Re: [driver-core-next] vmlinux.lds.h fix (corrected)
Date: Thu, 17 Nov 2022 19:38:59 +0100 [thread overview]
Message-ID: <Y3Z/w29imUu6MpN+@kroah.com> (raw)
In-Reply-To: <20221117171633.923628-1-jim.cromie@gmail.com>
On Thu, Nov 17, 2022 at 10:16:31AM -0700, Jim Cromie wrote:
> hi Greg,
>
> Im not quite sure what went wrong with last rev.
> Im intrinsically noisy. Its hard to fix permamently.
>
> 1st patch restores basic BOUNDED_SECTION wo header reservation.
>
> 2nd redoes the HEADERED_SECTION idea with separate macros, so it cant
> affect the basic case. I havent actually used this yet.
>
> I should have stared at this patchset longer before sending.
> sorry about that.
Worked better, thanks, now applied.
greg k-h
next prev parent reply other threads:[~2022-11-17 18:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-22 22:56 [PATCH 0/2] RESEND vmlinux.lds.h tweaks Jim Cromie
2022-10-22 22:56 ` [PATCH 1/2] vmlinux.lds.h: add BOUNDED_SECTION* macros Jim Cromie
2022-10-22 22:56 ` [PATCH 2/2] vmlinux.lds.h: place optional header space in BOUNDED_SECTION Jim Cromie
2022-11-10 18:09 ` [PATCH 0/2] RESEND vmlinux.lds.h tweaks Greg KH
2022-11-11 22:36 ` jim.cromie
2022-11-17 0:20 ` [driver-core-next] vmlinux.lds.h fix Jim Cromie
2022-11-17 0:20 ` [PATCH 1/2] vmlinux.lds.h: fix BOUNDED_SECTION_(PRE|POST)_LABEL macros Jim Cromie
2022-11-17 6:29 ` Greg KH
2022-11-17 16:43 ` jim.cromie
2022-11-17 17:16 ` [driver-core-next] vmlinux.lds.h fix (corrected) Jim Cromie
2022-11-17 17:16 ` [PATCH 1/2] vmlinux.lds.h: fix BOUNDED_SECTION_(PRE|POST)_LABEL macros Jim Cromie
2022-11-17 17:16 ` [PATCH 2/2] vmlinux.lds.h: add HEADERED_SECTION_* macros Jim Cromie
2022-11-17 18:38 ` Greg KH [this message]
2022-11-17 0:20 ` Jim Cromie
2022-12-16 16:25 ` Alexander Lobakin
2022-12-16 18:11 ` Alexander Lobakin
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=Y3Z/w29imUu6MpN+@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=jbaron@akamai.com \
--cc=jim.cromie@gmail.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox