From: John Crispin <email@example.com> To: Christoph Hellwig <firstname.lastname@example.org> Cc: Bjorn Helgaas <email@example.com>, firstname.lastname@example.org, email@example.com, Gabor Juhos <firstname.lastname@example.org> Subject: Re: [PATCH] pci: add kernel config option for disabling common PCI quirks Date: Thu, 22 Dec 2016 06:54:51 +0100 [thread overview] Message-ID: <email@example.com> (raw) In-Reply-To: <20161221142607.GA8594@infradead.org> On 21/12/2016 15:26, Christoph Hellwig wrote: > On Wed, Dec 21, 2016 at 02:11:25PM +0100, John Crispin wrote: >> I can turn it into an enable patch that is selected by default. >> >> The current patch disables all those quirks that are used for x86/PC >> style machines and hence are not required in the embedded world. > > Maybe we'll just need to reorganize the quirks so that most of them > arch in arch code or the affected drivers? > Hi Christoph to be honest i have no opinion on this. I am currently trying to reduce the amount of patches that we have inside the LEDE tree. the patches were written by other people and then dumped on us. obviously i am interested to get this upstream with the least amount of effort. I am quite aware though that some patches will need an overhaul to be applicable for upstream. its not really my call if it is enough to make this an enable patch and review the quirks enabled by it or if the code needs to be moved. John
next prev parent reply other threads:[~2016-12-22 5:55 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-12-21 7:53 John Crispin 2016-12-21 10:19 ` Lukas Wunner 2016-12-21 12:22 ` Christoph Hellwig 2016-12-21 13:11 ` John Crispin 2016-12-21 14:26 ` Christoph Hellwig 2016-12-22 5:54 ` John Crispin [this message] 2016-12-22 18:45 ` Bjorn Helgaas
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 \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [PATCH] pci: add kernel config option for disabling common PCI quirks' \ /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
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).