linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Andi Shyti <andi.shyti@kernel.org>
Cc: Krzysztof Kozlowski <krzk@kernel.org>,
	Wolfram Sang <wsa@kernel.org>,
	linux-next <linux-next@vger.kernel.org>
Subject: Re: Request for i2c inclusion in linux-next
Date: Tue, 1 Aug 2023 08:05:41 +1000	[thread overview]
Message-ID: <20230801080541.6f351e4c@canb.auug.org.au> (raw)
In-Reply-To: <20230731110403.pxo34g6kodur4ble@intel.intel>

[-- Attachment #1: Type: text/plain, Size: 906 bytes --]

Hi Andi,

On Mon, 31 Jul 2023 13:04:03 +0200 Andi Shyti <andi.shyti@kernel.org> wrote:
>
> On Mon, Jul 31, 2023 at 12:29:51PM +0200, Krzysztof Kozlowski wrote:
> > 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.  
> 
> uuhh... yes... I did a blind copy/paste of the link and did not
> realise that this was from googlesource... Stephen, can you
> please take it from:
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/andi.shyti/linux.git

Done.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

      reply	other threads:[~2023-07-31 22:06 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
2023-07-31 11:04   ` Andi Shyti
2023-07-31 22:05     ` Stephen Rothwell [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=20230801080541.6f351e4c@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=andi.shyti@kernel.org \
    --cc=krzk@kernel.org \
    --cc=linux-next@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 NNTP newsgroup(s).