From: Jakub Kicinski <kuba@kernel.org>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: David Miller <davem@davemloft.net>,
"linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>,
"open list:NETWORKING [GENERAL]" <netdev@vger.kernel.org>
Subject: Re: pull request: bluetooth 2022-08-05
Date: Mon, 8 Aug 2022 14:50:34 -0700 [thread overview]
Message-ID: <20220808145034.63fc918e@kernel.org> (raw)
In-Reply-To: <CABBYNZKmuUpmUChz+tixFCOE_pUeaJq0Sbqkvjy54zd9H=GB4A@mail.gmail.com>
On Mon, 8 Aug 2022 14:36:16 -0700 Luiz Augusto von Dentz wrote:
> > > Still rebasing, I thought that didn't make any difference as long as
> > > the patches apply.
> >
> > Long term the non-rebasing model is probably better since it'd be great
> > for the bluetooth tree to be included in linux-next.
>
> You mean that bluetooth-next would be pulled directly into linux-next
> rather than net-next?
No, no. linux-next is just an integration tree, it doesn't take PRs.
Some more info:
https://www.kernel.org/doc/html/latest/process/howto.html#linux-next-integration-testing-tree
It's mostly for checking for conflicts and automated testing.
All the compilation bots run on it.
> > Since you haven't started using that model, tho, would you mind
> > repairing the Fixes tags in this PR? :)
>
> Let me fix them.
Thanks!
next prev parent reply other threads:[~2022-08-08 21:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-05 23:28 pull request: bluetooth 2022-08-05 Luiz Augusto von Dentz
2022-08-06 0:47 ` Jakub Kicinski
2022-08-08 19:38 ` Luiz Augusto von Dentz
2022-08-08 21:30 ` Jakub Kicinski
2022-08-08 21:36 ` Luiz Augusto von Dentz
2022-08-08 21:50 ` Jakub Kicinski [this message]
2022-08-08 21:51 ` Luiz Augusto von Dentz
2022-08-08 23:46 ` Jakub Kicinski
2022-08-09 0:08 ` Luiz Augusto von Dentz
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=20220808145034.63fc918e@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=netdev@vger.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).