Kernel Newbies Archive on lore.kernel.org
 help / color / Atom feed
* patchset grooming question.
@ 2021-03-25 19:03 jim.cromie
  0 siblings, 0 replies; only message in thread
From: jim.cromie @ 2021-03-25 19:03 UTC (permalink / raw)
  To: kernelnewbies

[-- Attachment #1.1: Type: text/plain, Size: 370 bytes --]

I have a patchset which touches  vmlinux.lds.h 2x

1st inserts a few lines,
2nd moves them and related to a separate macro.

this is sub-optimal, if new macro is warranted,
it should just do that in 1st change.

or maybe 3rd option.
  move existing to macro- no functional change
  then do 2 changes, separately.

Whats best approach, considering history and blamelog ?

[-- Attachment #1.2: Type: text/html, Size: 576 bytes --]

[-- Attachment #2: Type: text/plain, Size: 170 bytes --]

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, back to index

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-03-25 19:03 patchset grooming question jim.cromie

Kernel Newbies Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/kernelnewbies/0 kernelnewbies/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 kernelnewbies kernelnewbies/ https://lore.kernel.org/kernelnewbies \
		kernelnewbies@kernelnewbies.org
	public-inbox-index kernelnewbies

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernelnewbies.kernelnewbies


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git