netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Horman <horms@kernel.org>
To: Suraj Patil <surajpatil522@gmail.com>
Cc: isdn@linux-pingi.de, kuba@kernel.org, quic_jjohnson@quicinc.com,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] isdn: mISDN: Fix typo 'intervall' to 'interval' in hfcsusb.c
Date: Mon, 17 Mar 2025 17:56:32 +0000	[thread overview]
Message-ID: <20250317175632.GJ688833@kernel.org> (raw)
In-Reply-To: <20250311160637.467759-1-surajpatil522@gmail.com>

On Tue, Mar 11, 2025 at 04:06:37PM +0000, Suraj Patil wrote:
> Signed-off-by: Suraj Patil <surajpatil522@gmail.com>
> ---
>  drivers/isdn/hardware/mISDN/hfcsusb.c | 16 ++++++++--------
>  1 file changed, 8 insertions(+), 8 deletions(-)
> 
> diff --git a/drivers/isdn/hardware/mISDN/hfcsusb.c b/drivers/isdn/hardware/mISDN/hfcsusb.c
> index e54419a4e731..ebe57c190476 100644
> --- a/drivers/isdn/hardware/mISDN/hfcsusb.c
> +++ b/drivers/isdn/hardware/mISDN/hfcsusb.c
> @@ -1063,7 +1063,7 @@ rx_iso_complete(struct urb *urb)
>  
>  		fill_isoc_urb(urb, fifo->hw->dev, fifo->pipe,
>  			      context_iso_urb->buffer, num_isoc_packets,
> -			      fifo->usb_packet_maxlen, fifo->intervall,
> +			      fifo->usb_packet_maxlen, fifo->interval,

Perhaps it is addressed in patch 1/2 (which i am unable to locate), in
which case the relevant change should be folded into this patch to avoid
breaking bisection. But as this stands, with this patch (only) applied
builds fail because there is no member called interval in struct usb_fifo.

-- 
pw-bot: not-applicable

      reply	other threads:[~2025-03-17 17:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-11 16:06 [PATCH 2/2] isdn: mISDN: Fix typo 'intervall' to 'interval' in hfcsusb.c Suraj Patil
2025-03-17 17:56 ` 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=20250317175632.GJ688833@kernel.org \
    --to=horms@kernel.org \
    --cc=isdn@linux-pingi.de \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=quic_jjohnson@quicinc.com \
    --cc=surajpatil522@gmail.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).