ChanServ changed the topic of #armlinux to: ARM kernel talk [Upstream kernel, find your vendor forums for questions about their kernels] | https://libera.irclog.whitequark.org/armlinux
heat has quit [Ping timeout: 258 seconds]
prabhakarlad has quit [Quit: Client closed]
jclsn has quit [Ping timeout: 260 seconds]
jclsn has joined #armlinux
amitk has joined #armlinux
sally has joined #armlinux
sally has quit [Read error: Connection reset by peer]
sally has joined #armlinux
sally has quit [Client Quit]
sally has joined #armlinux
Furry has joined #armlinux
mvaittin has joined #armlinux
sally has quit [Remote host closed the connection]
Furry has quit [Quit: Leaving]
gclement has joined #armlinux
monstr has joined #armlinux
monstr has quit [Remote host closed the connection]
monstr has joined #armlinux
monstr has quit [Ping timeout: 272 seconds]
elastic_dog has quit [Ping timeout: 272 seconds]
elastic_dog has joined #armlinux
<krzk>
ukleinek: what do you mean you can find it? base would still be unknown. base works for commits in your tree.
<ukleinek>
krzk: --base does more than you seem to know
<krzk>
Yeah, maybe I misunderstood your point. I thought that it replaces dependencies, but it is another way to say it. You still need to find the prerequisities.
<ukleinek>
krzk: yeah, for human consumption it's not very comfortable, but the build bots are said to evaluate it.
<krzk>
one just must remember that base must be alrady in linux-next (Git doc's already explain it: It consists of the base commit, which is a well-known commit that is part of the stable part of the project history everybody else works off of)
<ukleinek>
my suggestion for [florian] was to do: git format-patch @~.. --base @~2 for the patch in question as the dependency wasn't in next at that point.
<ukleinek>
krzk: can you forward 2. to the iio maintainer? :-)
<ukleinek>
4. reminds me about lei not working as expected and that he should debug that
matthias_bgg has joined #armlinux
<geertu>
krzk: "Get yourself in linux-next" ;-)
rvalue has quit [Read error: Connection reset by peer]
rvalue has joined #armlinux
<geertu>
ukleinek: As git send-email uses the local SHA1 as the prefix for the Message-Id, the bots should be able to figure out dependencies on non-applied patches, too
ezulian has joined #armlinux
<ukleinek>
geertu: it doesn't for me?!
<geertu>
ukleinek: I forgot to add "in theory" ;-)
<ukleinek>
on that linked message the msgid is: 20230728065739.580281-1-u.kleine-koenig@pengutronix.de
<ukleinek>
I'd guess that's a timestamp, a pid, a counter and my email address
<geertu>
ukleinek: When feeding truncated Message-Ids to lore, it usually cannot find the email. But yesterday it did work in one particular case, where lore said "I don't have this, but perhaps you meant ...?"
<geertu>
ukleinek: Does your local MTA replace Message-Id when sending out patches? How does Message-Id (in the patch) look like after running git format-patch?
<ukleinek>
geertu: 663b14d07d6d716ddc34482834d6b65a2f714cfb is the commit id, not a patch id?
<geertu>
ukleinek: Yes, I mean the commit ID
<geertu>
Isn't the commit ID a better prerequisite?
iivanov has joined #armlinux
<ukleinek>
geertu: the commit id isn't reproducible, so no
<ukleinek>
If I apply the patch you generated from 663b14d07d6d716ddc34482834d6b65a2f714cfb it will have a different commit id for me.
<geertu>
ukleinek: If the commit is upsream, it is stable
<ukleinek>
geertu: but then you probably won't git-send-email it out?!
<ukleinek>
so the only chance you have as a submitter is to reference the patch-id which is (very) stable and predictable.
<geertu>
ukleinek: Sure. But you could still find the dependency in lore (if lore supported search on that)
<geertu>
ukleinek: You misunderstood. The patch you email out would refer to the commit ID of an earlier patch.
<ukleinek>
with patch-id it's easier. --base already supports it, so I don't understand the discussion
<ukleinek>
also patch-id is cryptographically safe, while I could simply send a mail with msgid 663b14d07d6d716ddc34482834d6b65a2f714cfb-just-to-disturb to sabotage your workflow
deathcamel57_ has quit [Read error: Connection reset by peer]
deathcamel57 has joined #armlinux
<geertu>
Right. TBH, initially I thought the discussion was about commit IDs.
monstr has joined #armlinux
headless has joined #armlinux
rgallaispou has quit [Read error: Connection reset by peer]
rgallaispou has joined #armlinux
sszy has joined #armlinux
monstr has quit [Ping timeout: 255 seconds]
gclement has quit [Remote host closed the connection]
headless has quit [Quit: Konversation terminated!]
monstr has joined #armlinux
rgallaispou has quit [Read error: Connection reset by peer]
rgallaispou has joined #armlinux
prabhakarlad has joined #armlinux
gclement has joined #armlinux
luispm has joined #armlinux
* gclement
arnd
<gclement>
sorry wrong command :)
* ukleinek
doesn't know the "arnd" command, but it sounds useful :-)
<milkylainen>
Is that like a chatgpt, but for embedded? :)
<gclement>
yes but with better result !
<gclement>
the only issue is that it doesn't scale
<ukleinek>
I guess you need an API key though
<milkylainen>
Hmm. I see. I guess cloning neural nets like that can be diffcult. Don't wan't the clones going haywire. :)
<milkylainen>
want even
mvaittin has quit [Ping timeout: 258 seconds]
ezulian has quit [Quit: ezulian]
ezulian has joined #armlinux
heat has joined #armlinux
heat has quit [Remote host closed the connection]
heat has joined #armlinux
iivanov has quit [Ping timeout: 255 seconds]
monstr has quit [Remote host closed the connection]
deathcamel57 has quit [Ping timeout: 255 seconds]
headless has joined #armlinux
matthias_bgg has quit [Ping timeout: 258 seconds]
iivanov has joined #armlinux
matthias_bgg has joined #armlinux
matthias_bgg has quit [Remote host closed the connection]
dliviu has quit [Quit: Going away]
dliviu has joined #armlinux
nsaenz has quit [Remote host closed the connection]
nsaenz has joined #armlinux
headless has quit [Quit: Konversation terminated!]