From: Krzysztof Kozlowski <krzk@kernel.org>
To: Andi Shyti <andi.shyti@kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Wolfram Sang <wsa@kernel.org>, linux-next <linux-next@vger.kernel.org>
Subject: Re: Request for i2c inclusion in linux-next
Date: Mon, 31 Jul 2023 12:29:51 +0200 [thread overview]
Message-ID: <3a347eac-383b-f43b-afdc-039436427a66@kernel.org> (raw)
In-Reply-To: <20230730222921.637gy5xbtfekmite@intel.intel>
On 31/07/2023 00:29, Andi Shyti wrote:
> Hi Stephen,
>
> could you please include in the linux-next i2c related branches
> from my repository:
>
> https://kernel.googlesource.com/pub/scm/linux/kernel/git/andi.shyti/linux.git
>
> the following branches:
>
> for next: i2c/andi-for-next
> fixes: i2c/andi-for-current
Andi, why you do not use kernel.org repo? I think it is preferred.
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-07-31 10:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-30 22:29 Request for i2c inclusion in linux-next Andi Shyti
2023-07-31 4:54 ` Stephen Rothwell
2023-07-31 10:29 ` Krzysztof Kozlowski [this message]
2023-07-31 11:04 ` Andi Shyti
2023-07-31 22:05 ` Stephen Rothwell
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=3a347eac-383b-f43b-afdc-039436427a66@kernel.org \
--to=krzk@kernel.org \
--cc=andi.shyti@kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--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 NNTP newsgroup(s).