mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: tanzheng <tanzheng@kylinos.cn>
Cc: arend.vanspriel@broadcom.com, linux-kernel@vger.kernel.org,
	 linux-wireless@vger.kernel.org
Subject: Re: [PATCH v3] wifi: cfg80211: Remove the redundant wiphy_dev
Date: Tue, 09 Sep 2025 14:06:55 +0200	[thread overview]
Message-ID: <2363d0a432d280cc2e374cce6603300868780592.camel@sipsolutions.net> (raw)
In-Reply-To: <20250909011444.86314-1-tanzheng@kylinos.cn>

On Tue, 2025-09-09 at 09:14 +0800, tanzheng wrote:
> > > > > There is no need to call wiphy_dev again.Simplifying the
> > > > > code makes it more readable.
> > > > > 
> > > > > Signed-off-by: Zheng tan <tanzheng@kylinos.cn>
> > > > > 
> > > > 
> > > > The bot complains this doesn't match your From: line, is that
> > > intentional?
> > > 
> > > Yes, I set it up this way on purpose. Sorry, I don't know 
> > > this rule. I'll modify Signed-off-by. Thank you for your comment.
> > 
> > Oh. I wasn't really thinking you _need_ to change it - actually I was
> > wondering if you _want_ to change it since I thought maybe "Zheng tan"
> > was your preferred spelling, and your email client just used the
> > localpart (before the @) instead of your name spelled out by accident.
> > 
> > So either way I'm fine. Let me know what you prefer.
> 
> In that case, perhaps I prefer "Zheng tan".

Ideally you could resend with your From: line adjusted, or even an extra
From: line thrown into the body of the mail, but I suppose I can try to
adjust the From: line as well on the other mail you sent, assuming I
remember :)

johannes

  reply	other threads:[~2025-09-09 12:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-05  6:39 tanzheng
2025-09-05  7:16 ` Johannes Berg
2025-09-08  1:45   ` tanzheng
2025-09-08  6:29     ` Johannes Berg
2025-09-09  1:14       ` tanzheng
2025-09-09 12:06         ` Johannes Berg [this message]
2025-09-10  1:49           ` Zheng tan

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=2363d0a432d280cc2e374cce6603300868780592.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=arend.vanspriel@broadcom.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=tanzheng@kylinos.cn \
    /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

all inboxes | Powered by JetHome®