From: Luis Chamberlain <mcgrof@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: sfr@canb.auug.org.au, linux-next@vger.kernel.org,
jeyu@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Next/Trees: update the modules tree
Date: Fri, 10 Dec 2021 13:56:45 -0800 [thread overview]
Message-ID: <YbPNHcF9UrvrR5jb@bombadil.infradead.org> (raw)
In-Reply-To: <YbPI6Novz3ikiKEI@sirena.org.uk>
On Fri, Dec 10, 2021 at 09:38:48PM +0000, Mark Brown wrote:
> On Wed, Dec 08, 2021 at 11:59:31AM -0800, Luis Chamberlain wrote:
>
> > pull request which was merged for v5.16-rc1. I'll queue up fixes
> > on the modules_linus branch.
>
> > those in the modules_next branch to match parity with the same style
>
> Actually, note that your e-mail says the branches are modules_X while
> the diff says modules-X which looks like it's the correct thing:
modules-linus and modules-next are the correct ones indeed.
Sorry about the confusion.
Luis
>
> > -modules-fixes git git://git.kernel.org/pub/scm/linux/kernel/git/jeyu/linux.git#modules-linus
> > +modules-fixes git git://git.kernel.org/pub/scm/linux/kernel/git/mcgrof/linux.git#modules-linus
>
> > -modules git git://git.kernel.org/pub/scm/linux/kernel/git/jeyu/linux.git#modules-next
> > +modules git git://git.kernel.org/pub/scm/linux/kernel/git/mcgrof/linux.git#modules-next
next prev parent reply other threads:[~2021-12-10 21:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-08 19:59 [PATCH] Next/Trees: update the modules tree Luis Chamberlain
2021-12-10 21:30 ` Mark Brown
2021-12-10 21:38 ` Mark Brown
2021-12-10 21:56 ` Luis Chamberlain [this message]
2021-12-16 12:16 ` 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=YbPNHcF9UrvrR5jb@bombadil.infradead.org \
--to=mcgrof@kernel.org \
--cc=broonie@kernel.org \
--cc=jeyu@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--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