On Fri, Nov 10, 2017 at 10:08:19PM +0100, Pali Rohár wrote:
> On Friday 10 November 2017 21:26:01 Luis R. Rodriguez wrote:
> > On Fri, Nov 10, 2017 at 12:38:27AM +0100, Pali Rohár wrote:
> > > This function works pretty much like request_firmware(), but it prefer
> > > usermode helper. If usermode
On Fri, Oct 20, 2017 at 09:33:31PM +0200, Christophe JAILLET wrote:
> If 'write' is 0, we can avoid a call to spin_lock/spin_unlock.
>
> Signed-off-by: Christophe JAILLET
Thanks for the patch!
Acked-by: Luis R. Rodriguez
I'll bounce a copy to
On Sat, 4 Nov 2017 21:20:04 +0100
Wolfram Sang wrote:
> Those two functions are very similar, the only differences are that one
> needs the I2C_M_RD flag for its message while the other one needs the
> buffer casted to drop the const. Introduce a generic helper
This is a fix on top of the KAISER [v3] patches I posted earlier.
It is a fix for:
[PATCH 05/30] x86, kaiser: prepare assembly for entry/exit CR3 switching
I made a mistake and stopped running the 32-bit selftests at
some point. My changes from one of Borislav's review comments
ended
From: Dave Airlie
This adds the infrastructure needed to quirk displays
using edid and to mark them a non-desktop.
A non-desktop display is one which shouldn't normally be included
as a part of a desktop environment.
This is meant to cover head mounted devices like HTC
From: Dave Airlie
We don't want fbcon to get used on non-desktop dislays,
don't pass them as enabled connectors to the fb helper setup.
This prevents my HMD from getting disorted fbcon, and from
affecting other displays console.
v2: Change description from non-standard to
This is the same as the series for non-standard displays but uses the
phrase 'non-desktop' instead. No functional changes.
From: Dave Airlie
This uses the EDID info from my HTC Vive to mark it as
non-desktop.
v2: Change description from non-standard to non-desktop
Signed-off-by: Dave Airlie
---
drivers/gpu/drm/drm_edid.c | 3 +++
1 file changed, 3 insertions(+)
diff --git
> On Nov 10, 2017, at 8:02 AM, Hector Martin 'marcan' wrote:
>
>> On 2017-11-10 23:57, Andy Lutomirski wrote:
>> This code is so wrong I don't even no where to start. Seriously, sub,
>> orq, add? How about just orq with an offset? How about a *load*
>> instead of a store?
>
>
> On Nov 10, 2017, at 8:36 AM, Hector Martin 'marcan' wrote:
>
>> On 2017-11-11 01:02, Hector Martin 'marcan' wrote:
>> Not entirely sure what's going on here.
>
> Actually, if you think about it, it doesn't matter that it skips the
> first page, since it's probing one page
Make use of the swap macro instead of _manually_ swapping values
and remove unnecessary variable tmp.
This makes the code easier to read and maintain.
This code was detected with the help of Coccinelle.
Signed-off-by: Gustavo A. R. Silva
---
drivers/tty/vt/selection.c
On Fri, Nov 10, 2017 at 1:57 PM, Mathieu Desnoyers
wrote:
>
> That core serializing instruction is not that much about I$ vs D$
> consistency, but rather about the processor speculatively executing code
> ahead of its retirement point. Ref. Intel Architecture
Make use of the swap macro instead of _manually_ swapping values
and remove unnecessary variable tmp.
This makes the code easier to read and maintain.
This code was detected with the help of Coccinelle.
Signed-off-by: Gustavo A. R. Silva
---
Hi Michael, Tobin,
On 11/08/17 04:10, Michael Ellerman wrote:
> "Tobin C. Harding" writes:
>> Currently we are leaking addresses from the kernel to user space. This
>> script is an attempt to find some of those leakages. Script parses
>> `dmesg` output and /proc and /sys files for
- On Nov 10, 2017, at 5:02 PM, Andy Lutomirski l...@kernel.org wrote:
> On Fri, Nov 10, 2017 at 1:37 PM, Mathieu Desnoyers
> wrote:
>> Introduce an architecture function that ensures the current CPU
>> issues a core serializing instruction before returning to
> On Nov 10, 2017, at 2:20 PM, Mathieu Desnoyers
> wrote:
>
> - On Nov 10, 2017, at 5:02 PM, Andy Lutomirski l...@kernel.org wrote:
>
>> On Fri, Nov 10, 2017 at 1:37 PM, Mathieu Desnoyers
>> wrote:
>>> Introduce an
On Fri, Nov 10, 2017 at 04:32:45PM -0500, Jason Baron wrote:
>
> On 11/09/2017 03:56 PM, Paul E. McKenney wrote:
> > On Thu, Nov 09, 2017 at 03:13:24PM -0500, Jason Baron wrote:
> >> On 11/08/2017 02:01 AM, Fengguang Wu wrote:
> >>> On Tue, Nov 07, 2017 at 05:17:38PM -0500, Jason Baron wrote:
>
On Sat, 4 Nov 2017 21:20:05 +0100
Wolfram Sang wrote:
> Use the new helper to create variants of i2c_master_{send|recv} which
> mark their buffers as DMA safe.
>
> Signed-off-by: Wolfram Sang
Can't really argue with such a
On Mon, 6 Nov 2017 08:19:58 +0100
Martin Kepplinger wrote:
> This adds the power_mode sysfs interface to the device as documented in
> sysfs-bus-iio.
>
> ---
>
> Note that I explicitely don't sign off on this.
>
> This is a starting point for anybody who can test it and
On Tue, 7 Nov 2017 22:36:00 +0100
Martin Blumenstingl wrote:
> Hi Yixun,
>
> On Tue, Nov 7, 2017 at 3:09 PM, Yixun Lan wrote:
> > patch [1/4]:
> > Fix wrong SARADC/SANA clock gate bit in Meson-GXBB/GXL,
> > the published
On Sat, Nov 11, 2017 at 12:45 AM, Rafael J. Wysocki wrote:
> On Fri, Nov 10, 2017 at 10:09 AM, Ulf Hansson wrote:
>> On 8 November 2017 at 14:25, Rafael J. Wysocki wrote:
>>> From: Rafael J. Wysocki
>>>
>-Original Message-
>From: Jiri Olsa [mailto:jo...@redhat.com]
>Sent: Saturday, November 4, 2017 6:26 AM
>To: Megha Dey
>Cc: x...@kernel.org; linux-kernel@vger.kernel.org; linux-
>d...@vger.kernel.org; t...@linutronix.de; mi...@redhat.com;
>h...@zytor.com;
Currently only get_user_pages_fast() can safely handle the writable gup
case due to its use of pud_access_permitted() to check whether the pud
entry is writable. In the gup slow path pud_write() is used instead of
pud_access_permitted() and to date it has been unimplemented, just calls
BUG_ON().
On Fri, Nov 10, 2017 at 03:26:27PM -0800, Patrick McLean wrote:
>
>
> On 2017-11-10 10:42 AM, Linus Torvalds wrote:
> > On Thu, Nov 9, 2017 at 5:58 PM, Patrick McLean wrote:
> >>
> >> Something must have changed since 4.13.8 to trigger this though.
> >
> > Arnd pointed to
On Mon, Sep 18, 2017 at 05:15:01PM +0200, Greg KH wrote:
> On Thu, Sep 14, 2017 at 03:54:22PM -0700, Luis R. Rodriguez wrote:
> > +enum fw_priv_reqs {
> > + FW_PRIV_REQ_FALLBACK= 1 << 0,
> > + FW_PRIV_REQ_FALLBACK_UEVENT = 1 << 1,
> > + FW_PRIV_REQ_NO_CACHE
On Sat, Nov 11, 2017 at 12:45 AM, Rafael J. Wysocki wrote:
> On Fri, Nov 10, 2017 at 10:09 AM, Ulf Hansson wrote:
>> On 8 November 2017 at 14:25, Rafael J. Wysocki wrote:
[cut]
>> Moreover, you should check the return value from
It isn't clear if this function of_node_put()s the 'from'
argument, or the node it finds in the search. Clearly indicate
which variable is touched.
Signed-off-by: Stephen Boyd
---
drivers/of/base.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
> -Original Message-
> From: intel-gvt-dev [mailto:intel-gvt-dev-boun...@lists.freedesktop.org] On
> Behalf Of Gerd Hoffmann
> Sent: Friday, November 10, 2017 3:03 PM
> To: Alex Williamson
> Cc: Tian, Kevin ; Yuan, Hang
--
Good day!
What is the best way to reach you for business? I am writing you because I have
an opportunity to present to you. I have a business that I would like to
discuss with you.
Waiting to read from you soon.
Thank you
On 08/07, Guodong Xu wrote:
> From: Zhong Kaihua
>
> UART3 clock rate is doubled in previous commit.
>
> This error is not detected until recently a mezzanine board which makes
> real use of uart3 port (through LS connector of 96boards) was setup
> and tested on
On 09/26, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Tue, 26 Sep 2017 22:00:05 +0200
>
> Omit an extra message for a memory allocation failure in this function.
>
> This issue was detected by using the Coccinelle software.
>
> Signed-off-by: Markus
On Thu, Nov 9, 2017 at 10:33 AM, Greg Kroah-Hartman
wrote:
> On Thu, Nov 09, 2017 at 09:16:52AM +0100, Takashi Iwai wrote:
>> On Thu, 09 Nov 2017 09:04:58 +0100,
>> Greg Kroah-Hartman wrote:
>> >
>> > On Wed, Nov 08, 2017 at 03:38:35PM +0100, Takashi Iwai wrote:
>> > >
On Sat, 11 Nov 2017 02:06:00 +
Yafang Shao wrote:
> 2017-11-10 15:07 GMT+00:00 Steven Rostedt :
> > On Fri, 10 Nov 2017 12:56:06 +0800
> > Yafang Shao wrote:
> >
> >> Could the macro tcp_state_name() be renamed ?
> >> If is
On 2017/11/9 13:51, Hyunchul Lee wrote:
> From: Hyunchul Lee
>
> Select the type of the segment using write hints, when blocks are
> allocated for direct write.
>
> There are unhandled corner cases. Hints are not applied in
> in-place update. And if the blocks of a file is
>-Original Message-
>From: Jiri Olsa [mailto:jo...@redhat.com]
>Sent: Saturday, November 4, 2017 6:25 AM
>To: Megha Dey
>Cc: x...@kernel.org; linux-kernel@vger.kernel.org; linux-
>d...@vger.kernel.org; t...@linutronix.de; mi...@redhat.com;
>h...@zytor.com;
>-Original Message-
>From: Jiri Olsa [mailto:jo...@redhat.com]
>Sent: Saturday, November 4, 2017 6:25 AM
>To: Megha Dey
>Cc: x...@kernel.org; linux-kernel@vger.kernel.org; linux-
>d...@vger.kernel.org; t...@linutronix.de; mi...@redhat.com;
>h...@zytor.com;
>-Original Message-
>From: Jiri Olsa [mailto:jo...@redhat.com]
>Sent: Saturday, November 4, 2017 6:26 AM
>To: Megha Dey
>Cc: x...@kernel.org; linux-kernel@vger.kernel.org; linux-
>d...@vger.kernel.org; t...@linutronix.de; mi...@redhat.com;
>h...@zytor.com;
Forgot to Cc: linux-kernel.
On Fri, Nov 10, 2017 at 01:30:39PM -0800, Jörn Engel wrote:
> Regrand is a replacement for drivers/char/random.c. It is supposed to
> achieve the following design goals:
>
> 1. /dev/random shall never block.
> 2. /dev/urandom shall never return bad randomness.
> 3.
On Fri, Sep 15, 2017 at 10:30:46AM +0200, Martin Fuzzey wrote:
> On 15/09/17 00:54, Luis R. Rodriguez wrote:
> > The above benefits makes the code much easier to understand and maintain.
>
> Yes I agree it is much cleaner that way.
>
> A couple of nitpicks below.
>
> > +/**
> > + * enum
From: Miles Chen
When slub_debug=O is set. It is possible to clear debug flags
for an "unmergeable" slab cache in kmem_cache_open().
It makes the "unmergeable" cache became "mergeable" in sysfs_slab_add().
These caches will generate their "unique IDs" by
On 11/10/2017 03:56 PM, a...@linux-foundation.org wrote:
> The mm-of-the-moment snapshot 2017-11-10-15-56 has been uploaded to
>
>http://www.ozlabs.org/~akpm/mmotm/
>
> mmotm-readme.txt says
>
> README for mm-of-the-moment:
>
> http://www.ozlabs.org/~akpm/mmotm/
>
> This is a snapshot of
Gustavo A. R. Silva, on ven. 10 nov. 2017 16:13:03 -0600, wrote:
> Make use of the swap macro instead of _manually_ swapping values
> and remove unnecessary variable tmp.
>
> This makes the code easier to read and maintain.
>
> This code was detected with the help of Coccinelle.
>
>
On 11/10/2017 05:45 PM, Stephen Boyd wrote:
> It isn't clear if this function of_node_put()s the 'from'
> argument, or the node it finds in the search. Clearly indicate
> which variable is touched.
>
> Signed-off-by: Stephen Boyd
> ---
> drivers/of/base.c | 2 +-
> 1 file
IIRC, 4.14 comes tomorrow-ish? If possible, it would be nice to get
this in 4.14 before then, so it doesn't have to take time to trickle
down through stable.
Jason
On Thu, Nov 9, 2017 at 1:04 PM, Jason A. Donenfeld wrote:
> The way people generally use netlink_dump is that they
On Fri, Nov 10, 2017 at 08:13:06PM -0500, J. Bruce Fields wrote:
> On Fri, Nov 10, 2017 at 03:26:27PM -0800, Patrick McLean wrote:
> >
> >
> > On 2017-11-10 10:42 AM, Linus Torvalds wrote:
> > > On Thu, Nov 9, 2017 at 5:58 PM, Patrick McLean
> > > wrote:
> > >>
> > >>
> My assumption here is:
> 1) there are some less important and so security-insensitive firmwares,
>by which I mean that such firmwares won't be expected to be signed in
>terms of vulnerability or integrity.
>(I can't give you examples though.)
> 2) firmware's signature will be
From: "Jason A. Donenfeld"
Date: Sat, 11 Nov 2017 11:26:12 +0900
> IIRC, 4.14 comes tomorrow-ish? If possible, it would be nice to get
> this in 4.14 before then, so it doesn't have to take time to trickle
> down through stable.
Jason I'm already pushing my luck as-is with the
On Fri, 10 Nov 2017 14:42:51 -0800
Deepa Dinamani wrote:
> diff --git a/arch/x86/include/asm/ftrace.h b/arch/x86/include/asm/ftrace.h
> index 09ad88572746..db25aa15b705 100644
> --- a/arch/x86/include/asm/ftrace.h
> +++ b/arch/x86/include/asm/ftrace.h
> @@ -49,7 +49,7 @@
On Wed, 8 Nov 2017 16:43:17 -0800
Patrick McLean wrote:
> As of 4.13.11 (and also with 4.14-rc) we have an issue where when
> serving nfs4 sometimes we get the following BUG. When this bug happens,
> it usually also causes the motherboard to no longer POST until we
>
On Sat, Nov 11, 2017 at 11:37 AM, David Miller wrote:
> Jason I'm already pushing my luck as-is with the pull request I made
> yesterday.
>
> I've seen your original requst to get this in, you don't have to say
> it multiple times.
>
> We can get this into the merge window
On Wed, Nov 8, 2017 at 9:38 PM, Pierre-Louis Bossart
wrote:
> Nice work, thanks! I double-checked all the descriptors and values and
> didn't find anything problematic, the main comment I have is that the clock
> source/selection could probably be refactored
Lieber Benutzer
Ihre E-Mail-Adresse hat 15 GB überschritten, die vom Webmaster erstellt wurden.
Wir haben derzeit 15,3 GB und können in den nächsten 24 Stunden keine neuen
Nachrichten senden oder empfangen. Geben Sie Ihre Daten unten ein, um Ihr Konto
zu bestätigen und zu aktualisieren:
I'm going to move SYSENTER_stack to the beginning of cpu_tss to help
detect overflow. Before this can happen, I need to fix several code
paths that hardcode assumptions about the old layout.
Signed-off-by: Andy Lutomirski
---
arch/x86/include/asm/desc.h | 2 +-
This isn't quite done (the TSS remap patch is busted on 32-bit, but
that's a straightforward fix), but it should be ready for at least a
conceptual review.
The idea here is to prepare us to have all kernel data needed for
user mode execution and early entry located in the fixmap. To do
this, I
Currently, the GDT is an ad-hoc array of pages, one per CPU, in the
fixmap. Generalize it to be an array of a new struct cpu_entry_area
so that we can cleanly add new things to it.
Signed-off-by: Andy Lutomirski
---
arch/x86/include/asm/desc.h | 9 +
The Intel SDM says (Volume 3, 7.2.1):
Avoid placing a page boundary in the part of the TSS that the
processor reads during a task switch (the first 104 bytes). The
processor may not correctly perform address translations if a
boundary occurs in this area. During a task switch, the
This has a secondary purpose: it puts the entry stack into a region
with a well-controlled layout. A subsequent patch will take
advantage of this to streamline the SYSCALL entry code to be able to
find it more easily.
XXX: This either needs to not happen on 32-bit or we need to fix the 32-bit
Signed-off-by: Andy Lutomirski
---
arch/x86/include/asm/stacktrace.h | 1 +
arch/x86/kernel/dumpstack_32.c| 3 +++
arch/x86/kernel/dumpstack_64.c| 23 +++
3 files changed, 27 insertions(+)
diff --git a/arch/x86/include/asm/stacktrace.h
We currently have CPU 0's GDT at the top of the GDT range and
higher-numbered CPUs at lower addreses. This happens because the
fixmap is upside down (index 0 is the top of the fixmap).
Flip it so that GDTs are in ascending order by virtual address.
This will simplify a future patch that will
This will simplify some future code changes that will want some
temporary stack space in more places. It also lets us get rid of a
SWAPGS_UNSAFE_STACK user.
This does not depend on CONFIG_IA32_EMULATION because we'll want the
stack space even without IA32 emulation.
Signed-off-by: Andy
On Fri, Nov 10, 2017 at 8:05 PM, Andy Lutomirski wrote:
> The Intel SDM says (Volume 3, 7.2.1):
>
>Avoid placing a page boundary in the part of the TSS that the
>processor reads during a task switch (the first 104 bytes). The
>processor may not correctly perform
On 2017/11/10 15:41, LiFan wrote:
> In flush_nat_entries, all dirty nats will be flushed and if
> their new address isn't NULL_ADDR, their bitmaps will be updated,
> the free_nid_count of the bitmaps will be increaced regardless
> of whether the nats have already been occupied before.
> This could
The 'access_permitted' helper is used in the gup-fast path and goes
beyond the simple _PAGE_RW check to also:
* validate that the mapping is writable from a protection keys
standpoint
* validate that the pte has _PAGE_USER set since all fault paths where
pmd_write is must be referencing
The 'access_permitted' helper is used in the gup-fast path and goes
beyond the simple _PAGE_RW check to also:
* validate that the mapping is writable from a protection keys
standpoint
* validate that the pte has _PAGE_USER set since all fault paths where
pte_write is must be referencing
The 'access_permitted' helper is used in the gup-fast path and goes
beyond the simple _PAGE_RW check to also:
* validate that the mapping is writable from a protection keys
standpoint
* validate that the pte has _PAGE_USER set since all fault paths where
pud_write is must be referencing
Andrew,
Here is a new version to the pud_write() fix [1], and some follow-on
patches to use the '_access_permitted' helpers in fault and
get_user_pages() paths where we are checking if the thread has access to
write. I explicitly omit conversions for places where the kernel is
checking the
In ulpi_of_register() we call of_find_node_by_name() which
unconditionally calls of_node_put() on the 'from' argument. We
haven't called of_node_get() though, so we've put the node once
without getting it first. Add the of_node_get() call so that
things are properly balanced.
Fixes: ef6a7bcfb01c
2017-11-10 15:07 GMT+00:00 Steven Rostedt :
> On Fri, 10 Nov 2017 12:56:06 +0800
> Yafang Shao wrote:
>
>> Could the macro tcp_state_name() be renamed ?
>> If is included in include/net/tcp.h, it will
>
> Ideally, you don't want to include
[ Bringing in the gcc plugin people and the kernel hardening list,
since it now is no longer even remotely looking like a nfsd, vfs or
filesystem issue any more ]
Kees, Emese,
the whole thread is on lkml, but there's clearly something horribly
wrong with RANDSTRUCT, and it's not new even though
From: Josef Bacik
Date: Tue, 7 Nov 2017 15:28:41 -0500
> I'm sending this through Dave since it'll conflict with other BPF changes in
> his
> tree, but since it touches tracing as well Dave would like a review from
> somebody on the tracing side.
...
> A lot of our error
On Fri, 10 Nov 2017 16:28:41 +0900
Namhyung Kim wrote:
> > + hist_data->attrs->var_defs.expr[n_vars++] = s;
> > +
> > + hist_data->attrs->var_defs.n_vars = n_vars;
> > +
> > + if (n_vars == TRACING_MAP_VARS_MAX)
> > +
On 10/11/2017 at 09:59, Alexandre Belloni wrote:
> Calculating yday in the read_alarm callback is useless as this value is
> never used later. Also, it was buggy anyway because at the time this is
> done, tm_year is always 0 as the alarm register doesn't hold the year.
>
> Signed-off-by:
On Fri, 2017-11-10 at 14:42 +0800, Leo Yan wrote:
> If one patch has Kconfig section, the check script variable '$is_start'
> will be set by first 'config' line and the variable '$is_end' is to be
> set by the second 'config' line. But patches often only has one
> 'config' line so we have no
On 11/10/2017 05:33 AM, Hans de Goede wrote:
Hi,
On 09-11-17 22:07, Jeremy Cline wrote:
Replace the sst_acpi_check_hid helper function added in
commit 915ae2b9f0fe ("ASoC: Intel: Create a helper to search for
matching machine") with the generic acpi_dev_present helper function
and remove the
Hi! Yesterday I updated https://elinux.org/N900 page based on data which
I found in linux git repository. So driver status should be up-to-date.
I would like to ask, what is current status of the bluetooth driver? It
is working on N900, or it has a problems?
Also are the any plans for bringing
On Fri, Nov 10, 2017 at 10:09:46AM -0500, Anna Schumaker wrote:
>
>
> On 11/09/2017 09:21 PM, J. Bruce Fields wrote:
> > On Tue, Oct 17, 2017 at 12:40:27PM -0400, Jeff Layton wrote:
> >> On Tue, 2017-10-17 at 18:14 +0200, Bhumika Goyal wrote:
> >>> Make the function argument as const. After
Hi Dan,
I checked it on my local SVN. You are right. I submitted the code with '&'.
Accodring to a check-in message on my SVN, there was a bugreport end of
July and most probably a patch - either from me, you, Joseph Wright,
Colin King or Julia Lawall, changing '&' to '|'. I guess the patch for
On Thu 09 Nov 09:14 PST 2017, Damien Riegel wrote:
> Hi Bjorn,
>
>
> On Thu, Nov 09, 2017 at 09:00:16AM -0800, Bjorn Andersson wrote:
> > On Wed 01 Nov 10:53 PDT 2017, Damien Riegel wrote:
> >
> > I think it's better to use the word "nodes" (add nodes...)
>
> Will reword that.
>
> >
> > >
On (11/10/17 10:11), Luck, Tony wrote:
> On Fri, Nov 10, 2017 at 08:48:24AM +0900, Sergey Senozhatsky wrote:
> > All Ack-s/Tested-by-s were dropped, since the patch set has been
> > reworked. I'm kindly asking arch-s maintainers and developers to test it
> > once again. Sorry for any
Hi folks,
This relates to WireGuard [0].
Following a very nice conference with the Linux kernel networking subsystem
community [1,2], I thought it might be a good idea to spell out the roadmap
for the coming months and the trajectory into upstream, based on my
discussions with several developers
On (11/10/17 10:09), Luck, Tony wrote:
> On Fri, Nov 10, 2017 at 08:48:29AM +0900, Sergey Senozhatsky wrote:
> > -Examples::
> > -
> > - printk("Going to call: %pF\n", gettimeofday);
> > - printk("Going to call: %pF\n", p->func);
> > - printk("%s: called from %pS\n", __func__, (void
Hi Dmitry,
this is another patch of my series for switching the
touchscreen drivers to to the managed resource allocators.
The second patch is very trivial and perhaps bothering only me,
feel free to ignore.
Thanks,
Andi
Andi Shyti (2):
Input: ili210x - use managed allocated resources
Split the error between devm_kzalloc and
devm_input_allocate_device, there is no need to call the second
allocator if the first has failed. Besides this doesn't provide
practical advantages.
Signed-off-by: Andi Shyti
---
drivers/input/touchscreen/ili210x.c | 5 -
1 file
Use managed allocated resources to simplify error handling during
probing.
Adjust goto labels and remove function accordingly.
Signed-off-by: Andi Shyti
---
drivers/input/touchscreen/ili210x.c | 36 +++-
1 file changed, 11 insertions(+), 25
Add an expansion slot attribute to allow drivers to properly handle
cards like Comm Slot cards and PDS cards without declaration ROMs.
Tested-by: Stan Johnson
Signed-off-by: Finn Thain
---
arch/m68k/include/asm/macintosh.h | 9 ++-
It is misleading to use "dev" to mean a functional resource. And
in adopting the Linux Driver Model, struct nubus_board will embed a
struct device. Drivers will then bind with boards, not with functional
resources.
Rename struct nubus_dev as struct nubus_functional_resource. This is
the vendor's
Due to the '#ifdef __KERNEL__' being located in the wrong place, some
definitions from the kernel API were placed in the UAPI header during
the scripted header split. Fix this. Also, remove the duplicate comment
which is only relevant to the UAPI header.
Fixes: 607ca46e97a1 ("UAPI: (Scripted)
Check array indices. Avoid sprintf. Use buffers of sufficient size.
Use appropriate types for the parameters to nubus_get_rsrc_{mem,str}()
functions.
Tested-by: Stan Johnson
Signed-off-by: Finn Thain
---
drivers/nubus/nubus.c | 29
Testing shows that a single Radius PrecisionColor 24X display board,
which has 95 functional resources, produces over a thousand lines of
log messages. Suppress these messages with pr_debug().
Remove some redundant messages relating to nubus_get_subdir() calls.
Fix the format block debug messages
This fixes a couple of warnings from 'make W=1':
drivers/nubus/nubus.c:790: warning: no previous prototype for 'nubus_probe_slot'
drivers/nubus/nubus.c:824: warning: no previous prototype for 'nubus_scan_bus'
Tested-by: Stan Johnson
Signed-off-by: Finn Thain
From: Samuel Mendoza-Jonas
Date: Wed, 8 Nov 2017 16:30:44 +1100
> The NCSI driver is mostly silent which becomes a headache when trying to
> determine what has occurred on the NCSI connection. This adds additional
> logging in a few key areas such as state transitions and
From: Samuel Mendoza-Jonas
Date: Wed, 8 Nov 2017 16:30:45 +1100
> Several response handlers return EBUSY if the data corresponding to the
> command/response pair is already set. There is no reason to return an
> error here; the channel is advertising something as enabled
Tested-by: Stan Johnson
Signed-off-by: Finn Thain
---
drivers/net/ethernet/natsemi/macsonic.c | 170 ++--
1 file changed, 118 insertions(+), 52 deletions(-)
diff --git a/drivers/net/ethernet/natsemi/macsonic.c
This patch series adds support for the Linux Driver Model for Mac NIC
drivers, fixes some logging bugs, removes dead code, and adopts netif_*
calls to reduce code duplication.
All up, about 100 lines of code are eliminated.
This patch series has been tested on a variety of Macs, with coverage
Don't log unexpanded "eth%d".
Log the chip revision in the probe message (consistent with mace.c).
Drop redundant debug messages for FIFO events recorded in the
interface statistics (also consistent with mace.c).
Tested-by: Stan Johnson
Signed-off-by: Finn Thain
Fix log message fragments which no longer produce the desired output
(since the behaviour of printk() was changed).
Add missing printk severity levels.
Drop deprecated "out of memory" message as per checkpatch advice.
Signed-off-by: Finn Thain
---
AFAIK the only version of smc9194.c with Mac support is the one in the
linux-mac68k CVS repo, which never made it to the mainline.
Despite that, as of v2.3.45, arch/m68k/config.in listed CONFIG_SMC9194
under CONFIG_MAC. This mistake got carried over into Kconfig in v2.5.55.
(See pre-git era
Use dev_foo() and log the slot number instead of the unexpanded "eth%d".
Disambiguate the two identical "Card type %s is unsupported" messages.
Tested-by: Stan Johnson
Signed-off-by: Finn Thain
---
drivers/net/ethernet/8390/mac8390.c | 36
The patch which introduced the 8390 core module parameter 'msg_enable'
failed to do anything useful with it: it merely causes an ancient
version string to be logged.
Remove the other code that logs the same string. Use the msg_enable
module parameter as the default value for ei_local->msg_enable.
From: Lipeng
Date: Wed, 8 Nov 2017 15:52:21 +0800
> This patch-set introduces some bug fixes and code improvements.
> As [patch 1/2] depends on the patch {5392902 net: hns3: Consistently using
> GENMASK in hns3 driver}, which exists in net-next, not exists in net, so
> push
501 - 600 of 1268 matches
Mail list logo