From: Dan Carpenter <dan.carpenter@linaro.org>
To: Vasanthakumar Thiagarajan <vasanthakumar.thiagarajan@oss.qualcomm.com>
Cc: Harsh Kumar Bijlani <quic_hbijlani@quicinc.com>,
Jeff Johnson <jjohnson@kernel.org>,
Ripan Deuri <quic_rdeuri@quicinc.com>,
Baochen Qiang <baochen.qiang@oss.qualcomm.com>,
linux-wireless@vger.kernel.org, ath12k@lists.infradead.org,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH next] wifi: ath12k: clean up on error in ath12k_dp_setup()
Date: Fri, 19 Dec 2025 11:03:24 +0300 [thread overview]
Message-ID: <aUUGzCA-M-D3VFj9@stanley.mountain> (raw)
In-Reply-To: <aUT8KrV36wF8ITIK@stanley.mountain>
On Fri, Dec 19, 2025 at 10:18:02AM +0300, Dan Carpenter wrote:
> On Fri, Dec 19, 2025 at 10:54:03AM +0530, Vasanthakumar Thiagarajan wrote:
> >
> >
> > On 12/18/2025 1:14 PM, Dan Carpenter wrote:
> > > Destroy the rhash_tbl before returning the error code.
> > >
> > > Fixes: a88cf5f71adf ("wifi: ath12k: Add hash table for ath12k_dp_link_peer")
> > > Signed-off-by: Dan Carpenter <dan.carpenter@linaro.org>
> >
> > nit: The next branch in ath is actually ath-next.
>
> I'm working with over 400 different branches, right? I can't keep track
> of them all so I just put "next" if it's in linux-next and leave it
> blanke if it's in Linus's tree. It's automated.
For automated QC, it's really easy to automate on the recieving side.
In some ways, since there is only one place which recieves code and
does QC and a hundred different people sending patches, then it makes
more sense to do it on the recieving side.
This rule started with Dave Miller. He was handling a hundred patches
a day. Everything in networking except for wireless. Also Sparc and
ata. This was before I invented the Fixes tag, so that wasn't an
option. Greg and Andrew still handle that level of traffic but they
just use Fixes tags to automate their process.
regards,
dan carpenter
next prev parent reply other threads:[~2025-12-19 8:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-18 7:44 [PATCH next] wifi: ath12k: clean up on error in ath12k_dp_setup() Dan Carpenter
2025-12-19 5:24 ` Vasanthakumar Thiagarajan
2025-12-19 7:18 ` Dan Carpenter
2025-12-19 8:03 ` Dan Carpenter [this message]
2025-12-19 5:42 ` Baochen Qiang
2025-12-22 10:25 ` kernel test robot
2026-01-16 1:26 ` 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=aUUGzCA-M-D3VFj9@stanley.mountain \
--to=dan.carpenter@linaro.org \
--cc=ath12k@lists.infradead.org \
--cc=baochen.qiang@oss.qualcomm.com \
--cc=jjohnson@kernel.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_hbijlani@quicinc.com \
--cc=quic_rdeuri@quicinc.com \
--cc=vasanthakumar.thiagarajan@oss.qualcomm.com \
/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