All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alan Stern <stern@rowland.harvard.edu>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: braewoods@braewoods.net, linux-usb@vger.kernel.org
Subject: Re: [PATCH] usb-storage: Add compatibility quirk flags for iODD 2531/2541
Date: Fri, 15 Oct 2021 09:38:57 -0400	[thread overview]
Message-ID: <20211015133857.GA968676@rowland.harvard.edu> (raw)
In-Reply-To: <YWkzxWyIhW08ZCcX@kroah.com>

On Fri, Oct 15, 2021 at 09:54:45AM +0200, Greg KH wrote:
> On Fri, Oct 15, 2021 at 01:29:20AM -0500, braewoods@braewoods.net wrote:
> > On 2021-10-13 21:20, Alan Stern wrote:
> > > In the future, you should always include a version number in the email
> > > Subject: line (for example, "[PATCH v2]") so that readers will know
> > > which patch is which.  And you should include, here just below the "---"
> > > line, a description of how this version differs from the previous
> > > version.  See the email archives for examples of multi-version patches.
> > > 
> > > Nevertheless, this looks okay.
> > > 
> > > Acked-by: Alan Stern <stern@rowland.harvard.edu>
> > 
> > Noted. I'll do that for future patches. On a side note, any idea how long it
> > normally takes to get a simple patch like this committed? I've had mixed
> > experiences with getting feedback on patches. Sometimes my patches just get
> > totally ignored.
> 
> Depends on the subsystem and the patch submitted.

Greg tends to be quite good at merging patches in a timely manner.  They 
generally are committed within a few weeks.

In this case, should the patch also be added to the -stable kernels?

Alan Stern

> Also always use scripts/get_maintainer.pl to properly copy the needed
> maintainers and mailing lists.  Sometimes patches get lost in the noise
> if the right people are not copied.
> 
> thanks,
> 
> greg k-h

  reply	other threads:[~2021-10-15 13:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-14  1:55 [PATCH] usb-storage: Add compatibility quirk flags for iODD 2531/2541 James Buren
2021-10-14  2:20 ` Alan Stern
2021-10-15  6:29   ` braewoods
2021-10-15  7:54     ` Greg KH
2021-10-15 13:38       ` Alan Stern [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-10-14  1:50 James Buren
2021-10-14  2:01 ` braewoods

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=20211015133857.GA968676@rowland.harvard.edu \
    --to=stern@rowland.harvard.edu \
    --cc=braewoods@braewoods.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-usb@vger.kernel.org \
    /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.