Linux wireless drivers development
 help / color / mirror / Atom feed
From: Ping-Ke Shih <pkshih@realtek.com>
To: Johannes Berg <johannes@sipsolutions.net>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: RE: please use tree tags in patches
Date: Mon, 24 Feb 2025 01:18:19 +0000	[thread overview]
Message-ID: <a5451ef8e9534ed4b2223f50c3ddda14@realtek.com> (raw)
In-Reply-To: <ec3a3d891acfe5ed8763271a1df4151d75daf25f.camel@sipsolutions.net>

Johannes Berg <johannes@sipsolutions.net> wrote:
> Hi,
> 
> I couldn't (yet?) figure out how to make the nipa bot stuff run
> properly, so please start using
> 
>   [PATCH wireless] wifi: xyz
> 
> or
> 
>   [PATCH wireless-next] wifi: xyz
> 
> for the subject line. This way the automation can pick it up, see e.g.
> 
> https://patchwork.kernel.org/project/linux-wireless/list/?series=936374
> 
> I'll need to fix some username stuff etc.
> 
> I likely also need to add more trees to it - please reply with your
> subject tags, trees and branches to use, e.g.
> 
> wireless: main
> https://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless.git/
> 
> wireless-next: main
> https://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless-next.git/
> 
> but perhaps we want to have
> 
> rtw-next: rtw-next
> https://github.com/pkshih/rtw
> 
> or so? Not sure if you maintain a fixes branch there too?
> 
> 
> Anyway, good luck to me, and please don't try to attack it ;-) I spent
> all day setting it up, and haven't pulled out everything yet.
> 

Thanks for the automation. I think it will be very useful for me to detect
patch errors earlier, so submitters can fix problems earlier before I'm
trying to merge. 

I have created rtw branch as the fixes branch, so

[PATCH rtw-next]
https://github.com/pkshih/rtw rtw-next
(clone from wirless-next/main; this is for regular development)

[PATCH rtw]
https://github.com/pkshih/rtw rtw
(clone from wireless/main; this is for urgent fixes)

Ping-Ke


  parent reply	other threads:[~2025-02-24  1:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-21 12:17 please use tree tags in patches Johannes Berg
2025-02-21 18:27 ` Jeff Johnson
2025-02-24  9:35   ` Johannes Berg
2025-02-24  1:18 ` Ping-Ke Shih [this message]
2025-02-24  9:33   ` Johannes Berg
2025-02-24 11:15     ` Johannes Berg
2025-02-27 18:23       ` Jeff Johnson

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=a5451ef8e9534ed4b2223f50c3ddda14@realtek.com \
    --to=pkshih@realtek.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@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