From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: John Garry <john.g.garry@oracle.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
Peter Zijlstra <peterz@infradead.org>,
Bart Van Assche <bvanassche@acm.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Nam Cao <namcao@linutronix.de>
Subject: Re: linux-next: manual merge of the scsi-mkp tree with the tip tree
Date: Wed, 26 Feb 2025 08:54:35 +1100 [thread overview]
Message-ID: <20250226085435.50a140ab@canb.auug.org.au> (raw)
In-Reply-To: <87h64hg6r7.ffs@tglx>
[-- Attachment #1: Type: text/plain, Size: 887 bytes --]
Hi all,
On Tue, 25 Feb 2025 20:32:28 +0100 Thomas Gleixner <tglx@linutronix.de> wrote:
>
> On Tue, Feb 25 2025 at 09:38, John Garry wrote:
> >
> > static int sdebug_init_cmd_priv(struct Scsi_Host *shost, struct
> > scsi_cmnd *cmd)
> > {
> > struct sdebug_scsi_cmd *sdsc = scsi_cmd_priv(cmd);
> > struct sdebug_defer *sd_dp = &sdsc->sd_dp;
> >
> > spin_lock_init(&sdsc->lock);
> > hrtimer_setup(&sd_dp->hrt, sdebug_q_cmd_hrt_complete, CLOCK_MONOTONIC,
> > HRTIMER_MODE_REL_PINNED);
> > sd_dp->hrt.function = sdebug_q_cmd_hrt_complete; ***
> > INIT_WORK(&sd_dp->ew.work, sdebug_q_cmd_wq_complete);
> >
> >
> > I guess that setting sd_dp->hrt.function explicitly, at *** above, is
> > not needed (as hrtimer_setup()) does this.
>
> Correct. hrtimer_setup is enough.
Thanks, I have updated my merge resolution.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-02-25 21:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-25 4:32 linux-next: manual merge of the scsi-mkp tree with the tip tree Stephen Rothwell
2025-02-25 9:38 ` John Garry
2025-02-25 19:32 ` Thomas Gleixner
2025-02-25 21:54 ` Stephen Rothwell [this message]
2025-03-04 7:11 ` Stephen Rothwell
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=20250226085435.50a140ab@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=bvanassche@acm.org \
--cc=hpa@zytor.com \
--cc=john.g.garry@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=mingo@redhat.com \
--cc=namcao@linutronix.de \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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