All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johan Hovold <johan@kernel.org>
To: Alex Henrie <alexhenrie24@gmail.com>
Cc: linux-parport@lists.infradead.org, linux-usb@vger.kernel.org,
	sudipm.mukherjee@gmail.com,
	daniel@gimpelevich.san-francisco.ca.us, hkzlabnet@gmail.com,
	reboots@g-cipher.net, mike@trausch.us
Subject: Re: [PATCH 4/7] usb: misc: uss720: point pp->dev to usbdev->dev
Date: Wed, 13 Mar 2024 09:24:34 +0100	[thread overview]
Message-ID: <ZfFiwlWTbF5_zoUA@hovoldconsulting.com> (raw)
In-Reply-To: <CAMMLpeRpMwL3+c-uBrASuDOT4=YmxGRn5q1g8xKw2BAfdpujNQ@mail.gmail.com>

On Tue, Mar 12, 2024 at 07:30:21PM -0600, Alex Henrie wrote:
> On Tue, Mar 12, 2024 at 1:39 AM Johan Hovold <johan@kernel.org> wrote:
> >
> > On Mon, Mar 11, 2024 at 11:50:29PM -0600, Alex Henrie wrote:
> > > This avoids a "fix this legacy no-device port driver" warning.
> >
> > Please be more specific.
> 
> Hello Johan, thanks for taking a look at these patches.
> 
> The warning comes from parport_announce_port in
> drivers/parport/share.c. include/linux/parport.h says that dev is the
> "Physical device associated with IO/DMA." Commit 4edb38695d9a
> ("parisc: parport0: fix this legacy no-device port driver!",
> 2013-05-30) fixed a similar issue and says only "Fix the above kernel
> error from parport_announce_port() on 32bit GSC machines (e.g. B160L).
> The parport driver requires now a pointer to the device struct."
> 
> Do I just need to include "The parport driver now requires a pointer
> to the device struct" in the commit message? If not, where can I learn
> more about what the dev field is for, to be able to write a better
> description of why it's necessary to fill it in?

Your commit messages need to be self-contained and explain *why* you
think your proposed change is needed, and in enough detail that a
reviewer can make a judgement as to whether the patch is correct or not.

Basically all my comments were just pointing this out.

Johan

  reply	other threads:[~2024-03-13  8:24 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-12  5:50 [PATCH 1/7] docs: driver-api: parport-lowlevel: clarify purpose of PARPORT_MODE_PCSPP Alex Henrie
2024-03-12  5:50 ` [PATCH 2/7] usb: serial: mos7720: don't advertise PARPORT_MODE_PCSPP Alex Henrie
2024-03-12  7:39   ` Johan Hovold
2024-03-12  9:53     ` Sudip Mukherjee
2024-03-12 15:27       ` Daniel Gimpelevich
2024-03-13  1:30     ` Alex Henrie
2024-03-26  9:10   ` Greg KH
2024-03-12  5:50 ` [PATCH 3/7] usb: misc: uss720: " Alex Henrie
2024-03-12  5:50 ` [PATCH 4/7] usb: misc: uss720: point pp->dev to usbdev->dev Alex Henrie
2024-03-12  7:40   ` Johan Hovold
2024-03-13  1:30     ` Alex Henrie
2024-03-13  8:24       ` Johan Hovold [this message]
2024-03-26 15:07   ` [PATCH v2 0/4] usb: misc: uss720: improve support for Belkin F5U002 devices Alex Henrie
2024-03-26 15:07     ` [PATCH v2 1/4] usb: misc: uss720: point pp->dev to usbdev->dev Alex Henrie
2024-03-26 20:14       ` Sudip Mukherjee
2024-03-26 15:07     ` [PATCH v2 2/4] usb: misc: uss720: document the names of the compatible devices Alex Henrie
2024-03-26 15:07     ` [PATCH v2 3/4] usb: misc: uss720: add support for another variant of the Belkin F5U002 Alex Henrie
2024-03-26 15:07     ` [PATCH v2 4/4] usb: misc: uss720: check for incompatible versions " Alex Henrie
2024-03-12  5:50 ` [PATCH 5/7] usb: misc: uss720: document the names of the compatible devices Alex Henrie
2024-03-12 16:00   ` Daniel Gimpelevich
2024-03-12  5:50 ` [PATCH 6/7] usb: misc: uss720: add support for another variant of the Belkin F5U002 Alex Henrie
2024-03-12 15:31   ` Daniel Gimpelevich
2024-03-13  1:22     ` Alex Henrie
2024-03-12  5:50 ` [PATCH 7/7] usb: misc: uss720: check for incompatible versions " Alex Henrie
2024-03-12  7:38 ` [PATCH 1/7] docs: driver-api: parport-lowlevel: clarify purpose of PARPORT_MODE_PCSPP Johan Hovold
2024-03-12 15:24   ` Daniel Gimpelevich
2024-03-13  1:18     ` Alex Henrie

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=ZfFiwlWTbF5_zoUA@hovoldconsulting.com \
    --to=johan@kernel.org \
    --cc=alexhenrie24@gmail.com \
    --cc=daniel@gimpelevich.san-francisco.ca.us \
    --cc=hkzlabnet@gmail.com \
    --cc=linux-parport@lists.infradead.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mike@trausch.us \
    --cc=reboots@g-cipher.net \
    --cc=sudipm.mukherjee@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.