linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Horman <simon.horman@corigine.com>
To: Kalle Valo <kvalo@kernel.org>
Cc: Bo Liu <liubo03@inspur.com>,
	johannes@sipsolutions.net, davem@davemloft.net,
	edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
	linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rfkill: Use sysfs_emit() to instead of sprintf()
Date: Tue, 7 Feb 2023 17:07:28 +0100	[thread overview]
Message-ID: <Y+J3QBuOYSj4ONrh@corigine.com> (raw)
In-Reply-To: <87pmal7bsh.fsf@kernel.org>

On Tue, Feb 07, 2023 at 05:09:02PM +0200, Kalle Valo wrote:
> Simon Horman <simon.horman@corigine.com> writes:
> 
> > Hi Bo Liu,
> >
> > On Wed, Feb 01, 2023 at 03:17:18AM -0500, Bo Liu wrote:
> >> Follow the advice of the Documentation/filesystems/sysfs.rst and show()
> >> should only use sysfs_emit() or sysfs_emit_at() when formatting the
> >> value to be returned to user space.
> >
> > Thanks for your patch. As it is not a bug fix it should be targeted at
> > 'net-next' (as opposed to 'net'). This should be specified in the patch
> > subject something like this:
> >
> > [PATCH net-next v2] rfkill: Use sysfs_emit() to instead of sprintf()
> 
> rfkill patches should go to wireless-next, right?

Yes, my bad.

      reply	other threads:[~2023-02-07 16:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-01  8:17 [PATCH] rfkill: Use sysfs_emit() to instead of sprintf() Bo Liu
2023-02-03 19:07 ` Simon Horman
2023-02-07 15:09   ` Kalle Valo
2023-02-07 16:07     ` Simon Horman [this message]

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=Y+J3QBuOYSj4ONrh@corigine.com \
    --to=simon.horman@corigine.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=johannes@sipsolutions.net \
    --cc=kuba@kernel.org \
    --cc=kvalo@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=liubo03@inspur.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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;
as well as URLs for NNTP newsgroup(s).