mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: Thomas Fourier <fourier.thomas@gmail.com>,
	Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Cc: linux1394-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] firewire: nosy: Fix dma_free_coherent() size
Date: Fri, 26 Dec 2025 22:12:45 +0900	[thread overview]
Message-ID: <20251226131245.GA92232@workstation.local> (raw)
In-Reply-To: <7ffdcfff-0f2f-4563-9051-d398f3c5c6a7@wanadoo.fr>

Hi,

On Tue, Dec 16, 2025 at 06:47:30PM +0100, Christophe JAILLET wrote:
> Le 16/12/2025 à 17:54, Thomas Fourier a écrit :
> > It looks like the buffer allocated and mapped in add_card() is done
> > with size RCV_BUFFER_SIZE which is 16 KB and 4KB.
> > 
> > Fixes: 286468210d83 ("firewire: new driver: nosy - IEEE 1394 traffic sniffer")
> > Signed-off-by: Thomas Fourier <fourier.thomas@gmail.com>
> 
> Reviewed-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
> 
> And for the records, see [1].
> 
> CJ
> 
> [1]: https://lore.kernel.org/lkml/20200625191554.941614-1-christophe.jaillet@wanadoo.fr/
> 
> > ---
> >   drivers/firewire/nosy.c | 10 +++++-----
> >   1 file changed, 5 insertions(+), 5 deletions(-)

Applied to for-linus branch[1], with my handy modification for the place
of the macro, using 'Co-developed-by' tags with all of you. I'll send it
to mainline in this weekend so that it will be included in v6.19-rc3.


[1] https://git.kernel.org/pub/scm/linux/kernel/git/ieee1394/linux1394.git/log/?h=for-linus

Thanks

Takashi Sakamoto

      parent reply	other threads:[~2025-12-26 13:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-16 16:54 Thomas Fourier
2025-12-16 17:47 ` Christophe JAILLET
2025-12-19 14:16   ` Takashi Sakamoto
2025-12-26 13:12   ` Takashi Sakamoto [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=20251226131245.GA92232@workstation.local \
    --to=o-takashi@sakamocchi.jp \
    --cc=christophe.jaillet@wanadoo.fr \
    --cc=fourier.thomas@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux1394-devel@lists.sourceforge.net \
    /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®