[illumos-gate] 17335 remove duplicate bool definition from Intel NIC drivers -- Robert Mustacchi <rm⊙fo>

Some of the early stlouis commit messages by wesolows channel how I write some of them at work e.g. illumos/illumos-gate 35176f7

→ GitHub commit 35176f7: HPET sync (how the hell did I miss this file?) (committed)

They are fun to go over when bored (stuck sick at home atm)

wait did I grab the wrong one?

Interesting fenix could grab it as it's not part of vanilla gate

I think GitHub leaks commits from forks sometimes

Would a card like this work with Illumos? fujitsu.com/global/products/computi…rimergy/components/pmod-157814.html

It uses a LSI SAS3008 control chip. I plan to use it in IT mode.

if it is identifying itself as PCI 1000:0097 then apparently mpt_sas driver should work (mpt_sas "pciex1000,97" from /etc/driver_aliases)

Illumos hcl lists LSI SAS 3008 as supported device: 1000,97 and 1000,5f

gist.github.com/sjorge/ba979652938fc30b3b26630707dfdfba this one is built in on my mobo but it works well

and could be yeah, the oxide one is a fork from the vanilla one so it probably has some references in there from shared commits and somehow is able to link it up 🤔

git be weird sometimes

Hmm now i wonder if you can leak commits from a private repo that was forked from a public one

sjorge - I'm pretty sure you can't fork a public repo into a private one.

that matches my memory too

all repos on github are sort of shared and all references sort of land there

so you can request your object on someone elses repo, I seem to recall mjg59 playing games with this to try to convince github it was obviously bad

isn't that one of their 'tricks' is that it's I guess in effect 'dedup'ing all the various forks?

I suppose technically all commits on a fork somehow also end up on the tree... although it might be a dead end branch or a branch that got chopped off and is on the ground