From: Andi Shyti <andi.shyti@kernel.org>
To: Heiner Kallweit <hkallweit1@gmail.com>
Cc: Wolfram Sang <wsa@kernel.org>, Jean Delvare <jdelvare@suse.com>,
linux-i2c@vger.kernel.org
Subject: Re: [PATCH] i2c: i801: Call i2c_register_spd for muxed child segments
Date: Thu, 4 Apr 2024 01:24:55 +0200 [thread overview]
Message-ID: <ucg3nwboyzm5hwml3ce6kpsvhfrmzt7g7h5m4r477bnmt4blzv@rww45hznmwlu> (raw)
In-Reply-To: <4cb242be-2dbf-4b6d-a962-42e31df165d0@gmail.com>
Hi Heiner,
On Wed, Apr 03, 2024 at 09:18:04PM +0200, Heiner Kallweit wrote:
> On 31.03.2024 01:27, Andi Shyti wrote:
> > Hi
> >
> > On Tue, 26 Mar 2024 21:42:44 +0100, Heiner Kallweit wrote:
> >> Once the gpio mux driver binds to the "i2c-mux-gpio" platform device,
> >> this creates the i2c adapters for the muxed child segments.
> >> We can use the bus notifier mechanism to check for creation of the
> >> child i2d adapters, and call i2c_register_spd() for them. This allows
> >> to detect all DIMM's on systems with more than 8 memory slots.
> >>
> >>
> >> [...]
> >
> > Applied to i2c/i2c-host on
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/andi.shyti/linux.git
> >
> I don't see the patch in this repo. Technical problem or any other
> reason I may be missing?
It's there, so that either I forgot to push it or you checked
something else. In any case, thanks for checking and please,
don't hesitate to ping when you see something unusual.
Andi
PS I'm setting up some new scripts for handling the whole thing,
so that it's likely that sometimes might I miss the order of
things :-)
> > Thank you,
> > Andi
> >
> Heiner
>
> > Patches applied
> > ===============
> > [1/1] i2c: i801: Call i2c_register_spd for muxed child segments
> > commit: d33bd3b707f476efcb907a7fd3ba3352f49775ed
> >
>
prev parent reply other threads:[~2024-04-03 23:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-26 20:42 [PATCH] i2c: i801: Call i2c_register_spd for muxed child segments Heiner Kallweit
2024-03-31 0:27 ` Andi Shyti
2024-04-03 19:18 ` Heiner Kallweit
2024-04-03 23:24 ` Andi Shyti [this message]
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=ucg3nwboyzm5hwml3ce6kpsvhfrmzt7g7h5m4r477bnmt4blzv@rww45hznmwlu \
--to=andi.shyti@kernel.org \
--cc=hkallweit1@gmail.com \
--cc=jdelvare@suse.com \
--cc=linux-i2c@vger.kernel.org \
--cc=wsa@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).