All of lore.kernel.org
 help / color / mirror / Atom feed
From: Boris Brezillon <boris.brezillon@bootlin.com>
To: Marek Vasut <marek.vasut@gmail.com>
Cc: Joakim Tjernlund <Joakim.Tjernlund@infinera.com>,
	"mika.westerberg@linux.intel.com"
	<mika.westerberg@linux.intel.com>,
	"computersforpeace@gmail.com" <computersforpeace@gmail.com>,
	"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
	"richard@nod.at" <richard@nod.at>,
	"dwmw2@infradead.org" <dwmw2@infradead.org>
Subject: Re: [PATCH] spi-nor: intel-spi: Add support for Intel Ice Lake SPI serial flash
Date: Wed, 29 Aug 2018 13:46:58 +0200	[thread overview]
Message-ID: <20180829134658.1fa24b40@bbrezillon> (raw)
In-Reply-To: <cf194aa6-a694-f309-46e2-68c44452afaf@gmail.com>

On Wed, 29 Aug 2018 12:54:22 +0200
Marek Vasut <marek.vasut@gmail.com> wrote:

> On 08/29/2018 12:44 PM, Joakim Tjernlund wrote:
> > On Wed, 2018-08-29 at 12:33 +0200, Boris Brezillon wrote:  
> >> CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
> >>
> >>
> >> On Wed, 29 Aug 2018 10:28:05 +0000
> >> Joakim Tjernlund <Joakim.Tjernlund@infinera.com> wrote:
> >>  
> >>> On Wed, 2018-08-29 at 11:17 +0200, Boris Brezillon wrote:  
> >>>> CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
> >>>>
> >>>>
> >>>> Hi Marek,
> >>>>
> >>>> On Tue, 28 Aug 2018 18:56:38 +0200
> >>>> Marek Vasut <marek.vasut@gmail.com> wrote:
> >>>>  
> >>>>> On 08/28/2018 06:50 PM, Mika Westerberg wrote:  
> >>>>>> Intel Ice Lake exposes the SPI serial flash controller as a PCI device
> >>>>>> in the same way than Intel Denverton. Add Ice Lake SPI serial flash PCI
> >>>>>> ID to the driver list of supported devices.
> >>>>>>
> >>>>>> Signed-off-by: Mika Westerberg <mika.westerberg@linux.intel.com>  
> >>>>>
> >>>>> This should probably go through trivial patches ML, no ?  
> >>>>
> >>>> Nope, it should go through the spi-nor tree. Actually, even for trivial
> >>>> fixes like typos, I prefer to take them directly to avoid possible
> >>>> future conflicts in case something changes near the typo.
> >>>>  
> >>>>> Also, CC Stable.  
> >>>>
> >>>> Why? It's adding a new entry in pci_ids[] table, it looks like
> >>>> supporting new HW to me, not fixing a bug.  
> >>>
> >>> So you can boot/use new HW with stable kernels. Stable kernels would become
> >>> useless fairly quickly otherwise.
> >>> HW enablement patches are OK when they don't affect existing HW by much.  
> >>
> >> Where did you get that from? I've always been told that Cc-ing stable
> >> was reserved for bug fixes.  
> > 
> > From following linux dev lists. I don't have a reference, sorry.
> > 
> > If you look at the commit log for stable kernels you will see that a lot more
> > than pure bug fixes. Sometimes backport of new infra structure to
> > allow for easy backporting of fixes too.  
> 
> Documentation/process/stable-kernel-rules.rst
>  24  - New device IDs and quirks are also accepted.
> 
> 

Okay. I didn't know that.

Thanks,

Boris

  reply	other threads:[~2018-08-29 11:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-28 16:50 [PATCH] spi-nor: intel-spi: Add support for Intel Ice Lake SPI serial flash Mika Westerberg
2018-08-28 16:56 ` Marek Vasut
2018-08-28 16:59   ` Mika Westerberg
2018-08-28 19:20     ` Marek Vasut
2018-08-29  9:09       ` Mika Westerberg
2018-08-29  9:17   ` Boris Brezillon
2018-08-29 10:28     ` Joakim Tjernlund
2018-08-29 10:33       ` Boris Brezillon
2018-08-29 10:37         ` Marek Vasut
2018-08-29 10:44         ` Joakim Tjernlund
2018-08-29 10:54           ` Marek Vasut
2018-08-29 11:46             ` Boris Brezillon [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-06-27 12:11 Mika Westerberg

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=20180829134658.1fa24b40@bbrezillon \
    --to=boris.brezillon@bootlin.com \
    --cc=Joakim.Tjernlund@infinera.com \
    --cc=computersforpeace@gmail.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=marek.vasut@gmail.com \
    --cc=mika.westerberg@linux.intel.com \
    --cc=richard@nod.at \
    /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.