linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-i3c@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] I3C changes for 6.6
Date: Thu, 7 Sep 2023 16:03:53 +0200	[thread overview]
Message-ID: <202309071403530b8897e7@mail.local> (raw)
In-Reply-To: <20230906220710e64b2b71@mail.local>

Hello,

On 07/09/2023 00:07:11+0200, Alexandre Belloni wrote:
> Hello Linus,
> 
> Here is the i3c subsytem pull request for 6.6. There are mostly small
> fixes as people ar finally starting to have access to actual hardware.
> 

I forgot to add that I extended my signing key expiration date so you
should updated my keyto be able to verify the tag signature.

> The following changes since commit 06c2afb862f9da8dc5efa4b6076a0e48c3fbaaa5:
> 
>   Linux 6.5-rc1 (2023-07-09 13:53:13 -0700)
> 
> are available in the Git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/i3c/linux.git tags/i3c/for-6.6
> 
> for you to fetch changes up to 6e13d6528be2f7e801af63c8153b87293f25d736:
> 
>   i3c: master: svc: fix probe failure when no i3c device exist (2023-09-06 01:21:47 +0200)
> 
> ----------------------------------------------------------------
> I3C for 6.6
> 
> Core:
>  - Fix SETDASA when static and dynamic adress are equal
>  - Fix cmd_v1 DAA exit criteria
> 
> Drivers:
>  - svc: allow probing without any device
> 
> ----------------------------------------------------------------
> Aniket (2):
>       dt-bindings: i3c: Fix description for assigned-address
>       i3c: master: Fix SETDASA process
> 
> Billy Tsai (1):
>       i3c/master: cmd_v1: Fix the exit criteria for the daa procedure
> 
> Frank Li (1):
>       i3c: master: svc: fix probe failure when no i3c device exist
> 
> Miquel Raynal (1):
>       i3c: master: svc: Describe member 'saved_regs'
> 
> Rob Herring (1):
>       i3c: Explicitly include correct DT includes
> 
> Ruan Jinjie (1):
>       i3c: master: svc: Do not check for 0 return after calling platform_get_irq()
> 
>  Documentation/devicetree/bindings/i3c/i3c.yaml | 15 +++++++++++----
>  drivers/i3c/master.c                           |  6 +++++-
>  drivers/i3c/master/ast2600-i3c-master.c        |  1 -
>  drivers/i3c/master/i3c-master-cdns.c           |  1 -
>  drivers/i3c/master/mipi-i3c-hci/cmd_v1.c       |  2 +-
>  drivers/i3c/master/svc-i3c-master.c            | 19 +++++++++++++++----
>  6 files changed, 32 insertions(+), 12 deletions(-)
> 
> -- 
> Alexandre Belloni, co-owner and COO, Bootlin
> Embedded Linux and Kernel engineering
> https://bootlin.com

-- 
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2023-09-07 15:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-06 22:07 [GIT PULL] I3C changes for 6.6 Alexandre Belloni
2023-09-07 14:03 ` Alexandre Belloni [this message]
2023-09-07 23:10 ` pr-tracker-bot

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=202309071403530b8897e7@mail.local \
    --to=alexandre.belloni@bootlin.com \
    --cc=linux-i3c@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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 NNTP newsgroup(s).