From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Li, Philip" <philip.li@intel.com>
Cc: "sfr@canb.auug.org.au" <sfr@canb.auug.org.au>,
lkp <lkp@intel.com>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>
Subject: Re: The driver-core.git tree has moved.
Date: Wed, 16 Apr 2025 08:10:03 +0200 [thread overview]
Message-ID: <2025041657-arguable-reflector-5ab3@gregkh> (raw)
In-Reply-To: <SJ0PR11MB568008B6732C110FF372E645E0B22@SJ0PR11MB5680.namprd11.prod.outlook.com>
On Tue, Apr 15, 2025 at 01:15:41PM +0000, Li, Philip wrote:
> > Subject: The driver-core.git tree has moved.
> >
> > The driver-core.git tree has moved from:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git
> > to
> > git://git.kernel.org/pub/scm/linux/kernel/git/driver-core/driver-core.git
> >
> > So can you adjust this in the linux-next and 0-day bot scripts so that
> > you can pull in the updated stuff?
>
> This is done for the 0-day side, thanks
thank you!
prev parent reply other threads:[~2025-04-16 6:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-15 12:00 The driver-core.git tree has moved Greg Kroah-Hartman
2025-04-15 12:29 ` Stephen Rothwell
2025-04-16 6:10 ` Greg Kroah-Hartman
2025-04-15 13:15 ` Li, Philip
2025-04-16 6:10 ` Greg Kroah-Hartman [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=2025041657-arguable-reflector-5ab3@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=linux-next@vger.kernel.org \
--cc=lkp@intel.com \
--cc=philip.li@intel.com \
--cc=sfr@canb.auug.org.au \
/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