Re: [PATCH RFC 1/3] crypto: Prevent to register duplicate cra_driver_name

On Wed, Dec 20, 2017 at 08:09:25PM +, Corentin Labbe wrote: > Each crypto algorithm "cra_name" can have multiple implementation called > "cra_driver_name". > If two different implementation have the same cra_driver_name, nothing > can easily differentiate them. > Furthermore the mechanism for

Re: [PATCH RFC 1/3] crypto: Prevent to register duplicate cra_driver_name

On Wed, Dec 20, 2017 at 08:09:25PM +, Corentin Labbe wrote: > Each crypto algorithm "cra_name" can have multiple implementation called > "cra_driver_name". > If two different implementation have the same cra_driver_name, nothing > can easily differentiate them. > Furthermore the mechanism for

Re: [PATCH v4] checkpatch.pl: Add SPDX license tag check

On Wed, 2017-12-20 at 17:46 -0600, Rob Herring wrote: > Add SPDX license tag check based on the rules defined in > Documentation/process/license-rules.rst. To summarize, SPDX license tags > should be on the 1st line (or 2nd line in scripts) using the appropriate > comment style for the file type.

Re: [PATCH v4] checkpatch.pl: Add SPDX license tag check

On Wed, 2017-12-20 at 17:46 -0600, Rob Herring wrote: > Add SPDX license tag check based on the rules defined in > Documentation/process/license-rules.rst. To summarize, SPDX license tags > should be on the 1st line (or 2nd line in scripts) using the appropriate > comment style for the file type.

Re: [PATCH RFC 1/3] crypto: Prevent to register duplicate cra_driver_name

Am Mittwoch, 20. Dezember 2017, 21:09:25 CET schrieb Corentin Labbe: Hi Corentin, > Each crypto algorithm "cra_name" can have multiple implementation called > "cra_driver_name". > If two different implementation have the same cra_driver_name, nothing > can easily differentiate them. >

Re: [PATCH RFC 1/3] crypto: Prevent to register duplicate cra_driver_name

Am Mittwoch, 20. Dezember 2017, 21:09:25 CET schrieb Corentin Labbe: Hi Corentin, > Each crypto algorithm "cra_name" can have multiple implementation called > "cra_driver_name". > If two different implementation have the same cra_driver_name, nothing > can easily differentiate them. >

[PATCH 1/5] bindings: regulator: added support for suspend states

Documented a few new added properties which are used for supporting regulator suspend states. Signed-off-by: Chunyan Zhang --- Documentation/devicetree/bindings/regulator/regulator.txt | 11 +-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git

[PATCH 1/5] bindings: regulator: added support for suspend states

Documented a few new added properties which are used for supporting regulator suspend states. Signed-off-by: Chunyan Zhang --- Documentation/devicetree/bindings/regulator/regulator.txt | 11 +-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git

[PATCH 4/5] drivers: regulator: empty the old suspend functions

Regualtor suspend/resume functions should only be called by PM suspend core via registering dev_pm_ops, and regulator devices should implement the callback functions. Thus, any regulator consumer shouldn't call the regulator suspend/resume functions directly. In order to avoid compile errors,

[PATCH 4/5] drivers: regulator: empty the old suspend functions

Regualtor suspend/resume functions should only be called by PM suspend core via registering dev_pm_ops, and regulator devices should implement the callback functions. Thus, any regulator consumer shouldn't call the regulator suspend/resume functions directly. In order to avoid compile errors,

[PATCH 5/5] regulator: add PM suspend and resume hooks

In this patch, consumers are allowed to set suspend voltage, and this actually just set the "uV" in constraint::regulator_state, when the regulator_suspend_late() was called by PM core through callback when the system is entering into suspend, the regulator device would act suspend activity then.

Re: [PATCH] proc: rearrange struct proc_dir_entry

On Wed, Dec 20, 2017 at 03:10:48PM -0800, Randy Dunlap wrote: > On 12/20/2017 01:59 PM, Alexey Dobriyan wrote: > > struct proc_dir_entry became bit messy over years: > > > > * move 16-bit ->mode_t before namelen to get rid of padding > > * make ->in_use first field: it seems to be most used

[PATCH 5/5] regulator: add PM suspend and resume hooks

In this patch, consumers are allowed to set suspend voltage, and this actually just set the "uV" in constraint::regulator_state, when the regulator_suspend_late() was called by PM core through callback when the system is entering into suspend, the regulator device would act suspend activity then.

Re: [PATCH] proc: rearrange struct proc_dir_entry

On Wed, Dec 20, 2017 at 03:10:48PM -0800, Randy Dunlap wrote: > On 12/20/2017 01:59 PM, Alexey Dobriyan wrote: > > struct proc_dir_entry became bit messy over years: > > > > * move 16-bit ->mode_t before namelen to get rid of padding > > * make ->in_use first field: it seems to be most used

[PATCH 0/5] Add regulator suspend and resume support

Some systems need to set regulators to specific states when they enter low power modes, especially around CPUs. Currently the regulator driver, for suspend and resume features, provides two functions which are exported for being called directly by any modules or subsystems when they thought the

[PATCH 2/5] regulator: make regulator voltage be an array to support more states

Some regulator consumers would like to make the regulator device keeping a voltage range output when the system entering into suspend states. Making regulator voltage be an array can allow consumers to set voltage for normal state as well as for suspend states through the same code.

[PATCH 3/5] drivers: regulator: leave one item to record whether regulator is enabled

The items "disabled" and "enabled" are a little redundant, since only one of them would be set to record if the regulator device should keep on or be switched to off in suspend states. So in this patch, the "disabled" was removed, only leave the "enabled": - enabled == 1 for

[PATCH 0/5] Add regulator suspend and resume support

Some systems need to set regulators to specific states when they enter low power modes, especially around CPUs. Currently the regulator driver, for suspend and resume features, provides two functions which are exported for being called directly by any modules or subsystems when they thought the

[PATCH 2/5] regulator: make regulator voltage be an array to support more states

Some regulator consumers would like to make the regulator device keeping a voltage range output when the system entering into suspend states. Making regulator voltage be an array can allow consumers to set voltage for normal state as well as for suspend states through the same code.

[PATCH 3/5] drivers: regulator: leave one item to record whether regulator is enabled

The items "disabled" and "enabled" are a little redundant, since only one of them would be set to record if the regulator device should keep on or be switched to off in suspend states. So in this patch, the "disabled" was removed, only leave the "enabled": - enabled == 1 for

Re: [PATCH v3 01/21] docs: fpga: add a document for Intel FPGA driver overview

On Wed, Dec 20, 2017 at 04:31:15PM -0600, Alan Tull wrote: > On Mon, Nov 27, 2017 at 12:42 AM, Wu Hao wrote: > > + > > +PORT > > + > > +A port represents the interface between the static FPGA fabric (the "blue > > +bitstream") and a partially reconfigurable region containing

Re: [PATCH v3 01/21] docs: fpga: add a document for Intel FPGA driver overview

On Wed, Dec 20, 2017 at 04:31:15PM -0600, Alan Tull wrote: > On Mon, Nov 27, 2017 at 12:42 AM, Wu Hao wrote: > > + > > +PORT > > + > > +A port represents the interface between the static FPGA fabric (the "blue > > +bitstream") and a partially reconfigurable region containing an AFU (the > >

Re: [PATCH 00/13] replace print_symbol() with printk()-s

On (12/11/17 19:10), Joe Perches wrote: [..] > As far as I'm concerned, as soon as there is > no longer a single user in the kernel tree, > better to delete it instead. sounds good to me. can drop it, once the series upstreamed. 8< --- From: Sergey Senozhatsky

Re: [PATCH 00/13] replace print_symbol() with printk()-s

On (12/11/17 19:10), Joe Perches wrote: [..] > As far as I'm concerned, as soon as there is > no longer a single user in the kernel tree, > better to delete it instead. sounds good to me. can drop it, once the series upstreamed. 8< --- From: Sergey Senozhatsky Subject: [PATCH] kallsyms: remove

[PATCHv3] printk: add console_msg_format command line option

0day and kernelCI automatically parse kernel log - basically some sort of grepping using the pre-defined text patterns - in order to detect and report regressions/errors. There are several sources they get the kernel logs from: a) dmesg or /proc/ksmg This is the preferred way. Because `dmesg

[PATCHv3] printk: add console_msg_format command line option

0day and kernelCI automatically parse kernel log - basically some sort of grepping using the pre-defined text patterns - in order to detect and report regressions/errors. There are several sources they get the kernel logs from: a) dmesg or /proc/ksmg This is the preferred way. Because `dmesg

Re: [PATCH/RFC] VFS: don't keep disconnected dentries on d_anon

On Wed, Dec 20, 2017 at 04:57:28PM -0800, Linus Torvalds wrote: > On Wed, Dec 20, 2017 at 2:45 PM, NeilBrown wrote: > > > > We could just leave the code unchanged, but apart from that being > > potentially confusing, the (unfair) bit-spin-lock which protects > > s_anon can become

Re: [PATCH/RFC] VFS: don't keep disconnected dentries on d_anon

On Wed, Dec 20, 2017 at 04:57:28PM -0800, Linus Torvalds wrote: > On Wed, Dec 20, 2017 at 2:45 PM, NeilBrown wrote: > > > > We could just leave the code unchanged, but apart from that being > > potentially confusing, the (unfair) bit-spin-lock which protects > > s_anon can become a bottle neck

Re: [PATCH] kobject: fix suppressing modalias in uevents delivered over netlink

On Tue, Dec 19, 2017 at 3:20 PM, Casey Leedom wrote: > By the way, Komali went back and tried 4.14.7 and it does exhibit the > issue which she originally reported. As noted before, the origin of the new > behavior was tracked down to kernel.org:1455cf8 ... Also as noted,

Re: [PATCH] kobject: fix suppressing modalias in uevents delivered over netlink

On Tue, Dec 19, 2017 at 3:20 PM, Casey Leedom wrote: > By the way, Komali went back and tried 4.14.7 and it does exhibit the > issue which she originally reported. As noted before, the origin of the new > behavior was tracked down to kernel.org:1455cf8 ... Also as noted, Dmitry's > patch does

linux-next: Signed-off-by missing for commits in the drm tree

Hi all, Commits bb5cdf8d1c76 ("drm: omapdrm: Remove filename from header and fix copyright tag") d66c36a3ee79 ("drm: omapdrm: Simplify platform registration") are missing a Signed-off-by from their committer. -- Cheers, Stephen Rothwell

linux-next: Signed-off-by missing for commits in the drm tree

Hi all, Commits bb5cdf8d1c76 ("drm: omapdrm: Remove filename from header and fix copyright tag") d66c36a3ee79 ("drm: omapdrm: Simplify platform registration") are missing a Signed-off-by from their committer. -- Cheers, Stephen Rothwell

Re: [PATCH] hw: Fix permissions for OCRDMA_RESET_STATS

On Tue, Dec 19, 2017 at 11:14:03PM +0530, Selvin Xavier wrote: > On Tue, Dec 19, 2017 at 6:00 PM, Leon Romanovsky wrote: > >> status = ocrdma_nonemb_mbx_cmd(dev, mqe, dev->stats_mem.va); > > > > It still doesn't make a lot of sense to me: > > > > ocrdma_mbx_rdma_stats(): > > 1315

Re: [PATCH] hw: Fix permissions for OCRDMA_RESET_STATS

On Tue, Dec 19, 2017 at 11:14:03PM +0530, Selvin Xavier wrote: > On Tue, Dec 19, 2017 at 6:00 PM, Leon Romanovsky wrote: > >> status = ocrdma_nonemb_mbx_cmd(dev, mqe, dev->stats_mem.va); > > > > It still doesn't make a lot of sense to me: > > > > ocrdma_mbx_rdma_stats(): > > 1315if

Re: [PATCH] powerpc/powernv : Add support to enable sensor groups

Hi, On 12/04/2017 10:11 AM, Stewart Smith wrote: > Shilpasri G Bhat writes: >> On 11/28/2017 05:07 PM, Michael Ellerman wrote: >>> Shilpasri G Bhat writes: >>> Adds support to enable/disable a sensor group. This can be used to

Re: [PATCH] powerpc/powernv : Add support to enable sensor groups

Hi, On 12/04/2017 10:11 AM, Stewart Smith wrote: > Shilpasri G Bhat writes: >> On 11/28/2017 05:07 PM, Michael Ellerman wrote: >>> Shilpasri G Bhat writes: >>> Adds support to enable/disable a sensor group. This can be used to select the sensor groups that needs to be copied to main

[PATCH v1 1/1] ASoC: rsnd: ssi: Fix issue in dma data address assignment

From: Jiada Wang Same SSI device may be used in different dai links, by only having one dma struct in rsnd_ssi, after the first instance's dma config be initilized, the following instances can no longer configure dma, this causes issue, when their dma data address are

[PATCH v1 1/1] ASoC: rsnd: ssi: Fix issue in dma data address assignment

From: Jiada Wang Same SSI device may be used in different dai links, by only having one dma struct in rsnd_ssi, after the first instance's dma config be initilized, the following instances can no longer configure dma, this causes issue, when their dma data address are different from the first

linux-next: Tree for Dec 21

Hi all, News: tomorrow will be the last linux-next for 2017. The next release (after tomorrow) will be on January 2nd. Changes since 20171220: The net-next tree gained a conflict against the net tree. It also gained a build failure due to an interaction with the net tree for which I applied

linux-next: Tree for Dec 21

Hi all, News: tomorrow will be the last linux-next for 2017. The next release (after tomorrow) will be on January 2nd. Changes since 20171220: The net-next tree gained a conflict against the net tree. It also gained a build failure due to an interaction with the net tree for which I applied

Re: [PATCH net-next v4 0/6] net: tcp: sctp: dccp: Replace jprobe usage with trace events

From: Masami Hiramatsu Date: Thu, 21 Dec 2017 11:36:57 +0900 > Could you share your .config file? You never need to ask me this question. All of my test builds are with "allmodconfig".

Re: [PATCH net-next v4 0/6] net: tcp: sctp: dccp: Replace jprobe usage with trace events

From: Masami Hiramatsu Date: Thu, 21 Dec 2017 11:36:57 +0900 > Could you share your .config file? You never need to ask me this question. All of my test builds are with "allmodconfig".

Re: [PATCH V3 net-next 00/17] add some features and fix some bugs for HNS3 driver

From: "lipeng (Y)" Date: Thu, 21 Dec 2017 09:30:01 +0800 > > > On 2017/12/21 3:28, David Miller wrote: >> From: Lipeng >> Date: Wed, 20 Dec 2017 16:43:02 +0800 >> >>> This patchset adds some new feature support and fixes some bugs: >>> [Patch 1/17 -

Re: [PATCH V3 net-next 00/17] add some features and fix some bugs for HNS3 driver

From: "lipeng (Y)" Date: Thu, 21 Dec 2017 09:30:01 +0800 > > > On 2017/12/21 3:28, David Miller wrote: >> From: Lipeng >> Date: Wed, 20 Dec 2017 16:43:02 +0800 >> >>> This patchset adds some new feature support and fixes some bugs: >>> [Patch 1/17 - 5/17] add the support to modify/query the

Re: [BUG] Build error for 4.15-rc3 kernel caused by patch "kbuild: Add a cache for generated variables"

Hi Doug 2017-12-21 2:07 GMT+09:00 Doug Anderson : > Hi, > > On Tue, Dec 19, 2017 at 6:29 PM, Masahiro Yamada > wrote: >> 2017-12-19 2:17 GMT+09:00 Doug Anderson : >>> Hi, >>> >>> On Mon, Dec 18, 2017 at 7:50 AM,

Re: [BUG] Build error for 4.15-rc3 kernel caused by patch "kbuild: Add a cache for generated variables"

Hi Doug 2017-12-21 2:07 GMT+09:00 Doug Anderson : > Hi, > > On Tue, Dec 19, 2017 at 6:29 PM, Masahiro Yamada > wrote: >> 2017-12-19 2:17 GMT+09:00 Doug Anderson : >>> Hi, >>> >>> On Mon, Dec 18, 2017 at 7:50 AM, Masahiro Yamada >>> wrote: 2017-12-18 23:56 GMT+09:00 Masahiro Yamada : >

Re: [PATCH 5/7] blk-mq: remove REQ_ATOM_COMPLETE usages from blk-mq

Hi tejun On 12/16/2017 08:07 PM, Tejun Heo wrote: > After the recent updates to use generation number and state based > synchronization, blk-mq no longer depends on REQ_ATOM_COMPLETE except > to avoid firing the same timeout multiple times. > > Remove all REQ_ATOM_COMPLETE usages and use a new

Re: [PATCH 5/7] blk-mq: remove REQ_ATOM_COMPLETE usages from blk-mq

Hi tejun On 12/16/2017 08:07 PM, Tejun Heo wrote: > After the recent updates to use generation number and state based > synchronization, blk-mq no longer depends on REQ_ATOM_COMPLETE except > to avoid firing the same timeout multiple times. > > Remove all REQ_ATOM_COMPLETE usages and use a new

Re: [BUG] Build error for 4.15-rc3 kernel caused by patch "kbuild: Add a cache for generated variables"

2017-12-21 1:55 GMT+09:00 Doug Anderson : > Hi, > > On Mon, Dec 18, 2017 at 9:22 AM, Yang Shi wrote: >> >> >> On 12/18/17 9:17 AM, Doug Anderson wrote: >>> >>> Hi, >>> >>> On Mon, Dec 18, 2017 at 7:50 AM, Masahiro Yamada >>>

Re: [BUG] Build error for 4.15-rc3 kernel caused by patch "kbuild: Add a cache for generated variables"

2017-12-21 1:55 GMT+09:00 Doug Anderson : > Hi, > > On Mon, Dec 18, 2017 at 9:22 AM, Yang Shi wrote: >> >> >> On 12/18/17 9:17 AM, Doug Anderson wrote: >>> >>> Hi, >>> >>> On Mon, Dec 18, 2017 at 7:50 AM, Masahiro Yamada >>> wrote: 2017-12-18 23:56 GMT+09:00 Masahiro Yamada :

Re: Prototype patch for Linux-kernel memory model

Hi, On Wed, Dec 20, 2017 at 08:45:38AM -0800, Paul E. McKenney wrote: > On Wed, Dec 20, 2017 at 05:01:45PM +0530, afzal mohammed wrote: > > > +It is tempting to assume that CPU0()'s store to x is globally ordered > > > +before CPU1()'s store to z, but this is not the case: > > > + > > > + /* See

Re: Prototype patch for Linux-kernel memory model

Hi, On Wed, Dec 20, 2017 at 08:45:38AM -0800, Paul E. McKenney wrote: > On Wed, Dec 20, 2017 at 05:01:45PM +0530, afzal mohammed wrote: > > > +It is tempting to assume that CPU0()'s store to x is globally ordered > > > +before CPU1()'s store to z, but this is not the case: > > > + > > > + /* See

Re: proc_flush_task oops

On Wed, Dec 20, 2017 at 12:25:52PM -0600, Eric W. Biederman wrote: > > > > > > If the warning triggers it means the bug is in alloc_pid and somehow > > > something has gotten past the is_child_reaper check. > > > > You're onto something. > > > I am not seeing where things go wrong, but

Re: proc_flush_task oops

On Wed, Dec 20, 2017 at 12:25:52PM -0600, Eric W. Biederman wrote: > > > > > > If the warning triggers it means the bug is in alloc_pid and somehow > > > something has gotten past the is_child_reaper check. > > > > You're onto something. > > > I am not seeing where things go wrong, but

Re: [PATCH net-next v4 0/6] net: tcp: sctp: dccp: Replace jprobe usage with trace events

On Thu, 21 Dec 2017 11:36:57 +0900 Masami Hiramatsu wrote: > On Wed, 20 Dec 2017 14:24:24 -0500 (EST) > David Miller wrote: > > > From: David Miller > > Date: Wed, 20 Dec 2017 14:20:40 -0500 (EST) > > > > > From: Masami

Re: [PATCH net-next v4 0/6] net: tcp: sctp: dccp: Replace jprobe usage with trace events

On Thu, 21 Dec 2017 11:36:57 +0900 Masami Hiramatsu wrote: > On Wed, 20 Dec 2017 14:24:24 -0500 (EST) > David Miller wrote: > > > From: David Miller > > Date: Wed, 20 Dec 2017 14:20:40 -0500 (EST) > > > > > From: Masami Hiramatsu > > > Date: Wed, 20 Dec 2017 13:14:11 +0900 > > > > > >>

Re: hw: Fix permissions for OCRDMA_RESET_STATS

On Tue, Aug 08, 2017 at 06:56:37PM +0300, Anton Vasilyev wrote: > Debugfs file reset_stats is created with S_IRUSR permissions, > but ocrdma_dbgfs_ops_read() doesn't support OCRDMA_RESET_STATS, > whereas ocrdma_dbgfs_ops_write() supports only OCRDMA_RESET_STATS. > > The patch fixes misstype with

Re: hw: Fix permissions for OCRDMA_RESET_STATS

On Tue, Aug 08, 2017 at 06:56:37PM +0300, Anton Vasilyev wrote: > Debugfs file reset_stats is created with S_IRUSR permissions, > but ocrdma_dbgfs_ops_read() doesn't support OCRDMA_RESET_STATS, > whereas ocrdma_dbgfs_ops_write() supports only OCRDMA_RESET_STATS. > > The patch fixes misstype with

[PATCH/RFC] NFS: add nostatflush mount option.

When an i_op->getattr() call is made on an NFS file (typically from a 'stat' family system call), NFS will first flush any dirty data to the server. This ensures that the mtime reported is correct and stable, but has a performance penalty. 'stat' is normally thought to be a quick operation, and

[PATCH/RFC] NFS: add nostatflush mount option.

When an i_op->getattr() call is made on an NFS file (typically from a 'stat' family system call), NFS will first flush any dirty data to the server. This ensures that the mtime reported is correct and stable, but has a performance penalty. 'stat' is normally thought to be a quick operation, and

Re: [PATCH linux-next] KVM: x86: don't forget vcpu_put() in kvm_arch_vcpu_ioctl_set_sregs()

On 2017年12月21日 08:30, Paolo Bonzini wrote: > On 21/12/2017 01:24, Eric Biggers wrote: >> From: Eric Biggers >> >> Due to a bad merge resolution between commit f29810335965 ("KVM/x86: >> Check input paging mode when cs.l is set") and commit b4ef9d4e8cb8 >> ("KVM: Move

Re: [PATCH linux-next] KVM: x86: don't forget vcpu_put() in kvm_arch_vcpu_ioctl_set_sregs()

On 2017年12月21日 08:30, Paolo Bonzini wrote: > On 21/12/2017 01:24, Eric Biggers wrote: >> From: Eric Biggers >> >> Due to a bad merge resolution between commit f29810335965 ("KVM/x86: >> Check input paging mode when cs.l is set") and commit b4ef9d4e8cb8 >> ("KVM: Move vcpu_load to arch-specific

Re: [PATCH v2 2/3] dt-bindings: media: Add Allwinner V3s Camera Sensor Interface (CSI)

Hi, On Tue, 19 Dec 2017 13:53:28 +0200 Sakari Ailus wrote: > Hi Yong, > > On Thu, Jul 27, 2017 at 01:01:36PM +0800, Yong Deng wrote: > > Add binding documentation for Allwinner V3s CSI. > > > > Signed-off-by: Yong Deng > > DT bindings should

Re: [PATCH v2 2/3] dt-bindings: media: Add Allwinner V3s Camera Sensor Interface (CSI)

Hi, On Tue, 19 Dec 2017 13:53:28 +0200 Sakari Ailus wrote: > Hi Yong, > > On Thu, Jul 27, 2017 at 01:01:36PM +0800, Yong Deng wrote: > > Add binding documentation for Allwinner V3s CSI. > > > > Signed-off-by: Yong Deng > > DT bindings should precede the driver. OK. > > > --- > >

Re: [PATCH v20 0/7] Virtio-balloon Enhancement

On 12/21/2017 01:10 AM, Matthew Wilcox wrote: On Wed, Dec 20, 2017 at 04:13:16PM +, Wang, Wei W wrote: On Wednesday, December 20, 2017 8:26 PM, Matthew Wilcox wrote: unsigned long bit; xb_preload(GFP_KERNEL); xb_set_bit(xb, 700); xb_preload_end();

Re: [PATCH v20 0/7] Virtio-balloon Enhancement

On 12/21/2017 01:10 AM, Matthew Wilcox wrote: On Wed, Dec 20, 2017 at 04:13:16PM +, Wang, Wei W wrote: On Wednesday, December 20, 2017 8:26 PM, Matthew Wilcox wrote: unsigned long bit; xb_preload(GFP_KERNEL); xb_set_bit(xb, 700); xb_preload_end();

[PATCH v20 3/7 RESEND] xbitmap: add more operations

This patch adds support to find next 1 or 0 bit in a xbmitmap range and clear a range of bits. More possible optimizations to add in the future: 1) xb_set_bit_range: set a range of bits. 2) when searching a bit, if the bit is not found in the slot, move on to the next slot directly. 3) add tags

[PATCH v20 3/7 RESEND] xbitmap: add more operations

This patch adds support to find next 1 or 0 bit in a xbmitmap range and clear a range of bits. More possible optimizations to add in the future: 1) xb_set_bit_range: set a range of bits. 2) when searching a bit, if the bit is not found in the slot, move on to the next slot directly. 3) add tags

Re: [PATCH V3 net-next 00/17] add some features and fix some bugs for HNS3 driver

On 2017/12/21 10:27, lipeng (Y) wrote: > > > On 2017/12/21 3:28, David Miller wrote: >> From: Lipeng >> Date: Wed, 20 Dec 2017 16:43:02 +0800 >> >>> This patchset adds some new feature support and fixes some bugs: >>> [Patch 1/17 - 5/17] add the support to modify/query the

Re: [PATCH V3 net-next 00/17] add some features and fix some bugs for HNS3 driver

On 2017/12/21 10:27, lipeng (Y) wrote: > > > On 2017/12/21 3:28, David Miller wrote: >> From: Lipeng >> Date: Wed, 20 Dec 2017 16:43:02 +0800 >> >>> This patchset adds some new feature support and fixes some bugs: >>> [Patch 1/17 - 5/17] add the support to modify/query the tqp number >>>

Re: [PATCH v2 3/3] media: MAINTAINERS: add entries for Allwinner V3s CSI

On Tue, 19 Dec 2017 13:48:03 +0200 Sakari Ailus wrote: > On Thu, Jul 27, 2017 at 01:01:37PM +0800, Yong Deng wrote: > > Signed-off-by: Yong Deng > > --- > > MAINTAINERS | 8 > > 1 file changed, 8 insertions(+) > > > > diff --git

Re: [PATCH v2 3/3] media: MAINTAINERS: add entries for Allwinner V3s CSI

On Tue, 19 Dec 2017 13:48:03 +0200 Sakari Ailus wrote: > On Thu, Jul 27, 2017 at 01:01:37PM +0800, Yong Deng wrote: > > Signed-off-by: Yong Deng > > --- > > MAINTAINERS | 8 > > 1 file changed, 8 insertions(+) > > > > diff --git a/MAINTAINERS b/MAINTAINERS > > index 9826a91..b91fa27

Re: [linux-sunxi] [PATCH v3 1/3] media: V3s: Add support for Allwinner CSI.

Hi, On Tue, 19 Dec 2017 18:35:49 +0800 Chen-Yu Tsai wrote: > On Mon, Nov 13, 2017 at 3:30 PM, Yong Deng wrote: > > Allwinner V3s SoC have two CSI module. CSI0 is used for MIPI interface > > and CSI1 is used for parallel interface. This is not documented

Re: [linux-sunxi] [PATCH v3 1/3] media: V3s: Add support for Allwinner CSI.

Hi, On Tue, 19 Dec 2017 18:35:49 +0800 Chen-Yu Tsai wrote: > On Mon, Nov 13, 2017 at 3:30 PM, Yong Deng wrote: > > Allwinner V3s SoC have two CSI module. CSI0 is used for MIPI interface > > and CSI1 is used for parallel interface. This is not documented in > > datasheet but by testing and

Re: [PATCH 1/2 v3] scsi: ufs: introduce static sysfs entries

>> For future patch series submissions, please include a cover letter >> that explains the purpose of the patch series and please also >> document the changes between the different versions of the patch >> series in the cover letter. > > Yup, I'll be aware of it. Thank you for the advice. These

Re: [PATCH 1/2 v3] scsi: ufs: introduce static sysfs entries

>> For future patch series submissions, please include a cover letter >> that explains the purpose of the patch series and please also >> document the changes between the different versions of the patch >> series in the cover letter. > > Yup, I'll be aware of it. Thank you for the advice. These

Re: [PATCH net-next v4 0/6] net: tcp: sctp: dccp: Replace jprobe usage with trace events

On Wed, 20 Dec 2017 14:24:24 -0500 (EST) David Miller wrote: > From: David Miller > Date: Wed, 20 Dec 2017 14:20:40 -0500 (EST) > > > From: Masami Hiramatsu > > Date: Wed, 20 Dec 2017 13:14:11 +0900 > > > >> This series is v4 of

Re: [PATCH net-next v4 0/6] net: tcp: sctp: dccp: Replace jprobe usage with trace events

On Wed, 20 Dec 2017 14:24:24 -0500 (EST) David Miller wrote: > From: David Miller > Date: Wed, 20 Dec 2017 14:20:40 -0500 (EST) > > > From: Masami Hiramatsu > > Date: Wed, 20 Dec 2017 13:14:11 +0900 > > > >> This series is v4 of the replacement of jprobe usage with trace > >> events. This

Re: [PATCH V3 net-next 00/17] add some features and fix some bugs for HNS3 driver

On 2017/12/21 3:28, David Miller wrote: From: Lipeng Date: Wed, 20 Dec 2017 16:43:02 +0800 This patchset adds some new feature support and fixes some bugs: [Patch 1/17 - 5/17] add the support to modify/query the tqp number through ethtool -L/l command, and also fix

Re: [PATCH V3 net-next 00/17] add some features and fix some bugs for HNS3 driver

On 2017/12/21 3:28, David Miller wrote: From: Lipeng Date: Wed, 20 Dec 2017 16:43:02 +0800 This patchset adds some new feature support and fixes some bugs: [Patch 1/17 - 5/17] add the support to modify/query the tqp number through ethtool -L/l command, and also fix some related bugs for

Re: [PATCH] scsi: storvsc: Fix scsi_cmd error assignments in storvsc_handle_error

Cathy, > When an I/O is returned with an srb_status of SRB_STATUS_INVALID_LUN > which has zero good_bytes it must be assigned an error. Otherwise the > I/O will be continuously requeued and will cause a deadlock in the > case where disks are being hot added and removed. sd_probe_async will >

Re: [PATCH] scsi: storvsc: Fix scsi_cmd error assignments in storvsc_handle_error

Cathy, > When an I/O is returned with an srb_status of SRB_STATUS_INVALID_LUN > which has zero good_bytes it must be assigned an error. Otherwise the > I/O will be continuously requeued and will cause a deadlock in the > case where disks are being hot added and removed. sd_probe_async will >

Re: linux-next: Signed-off-by missing for commit in the scsi tree

chenxiang, > John is on vacation. I have checked it and please add a > "Signed-off-by: Xiang Chen " or let me know > if want us to re-send this patch again . I fixed it up. Thanks! -- Martin K. Petersen Oracle Linux Engineering

Re: linux-next: Signed-off-by missing for commit in the scsi tree

chenxiang, > John is on vacation. I have checked it and please add a > "Signed-off-by: Xiang Chen " or let me know > if want us to re-send this patch again . I fixed it up. Thanks! -- Martin K. Petersen Oracle Linux Engineering

Re: [PATCH -V4 -mm] mm, swap: Fix race between swapoff and some swap operations

On Wed, Dec 20, 2017 at 09:26:32AM +0800, Huang, Ying wrote: > From: Huang Ying > > When the swapin is performed, after getting the swap entry information > from the page table, system will swap in the swap entry, without any > lock held to prevent the swap device from

Re: [PATCH -V4 -mm] mm, swap: Fix race between swapoff and some swap operations

On Wed, Dec 20, 2017 at 09:26:32AM +0800, Huang, Ying wrote: > From: Huang Ying > > When the swapin is performed, after getting the swap entry information > from the page table, system will swap in the swap entry, without any > lock held to prevent the swap device from being swapoff. This may >

Re: [PATCH v3 1/6] media: rc: update sunxi-ir driver to get base clock frequency from devicetree

Hi Philipp, On Tue, Dec 19, 2017 at 09:07:42AM +0100, Philipp Rossak wrote: > This patch updates the sunxi-ir driver to set the base clock frequency from > devicetree. > > This is necessary since there are different ir receivers on the > market, that operate with different frequencies. So this

Re: [PATCH v3 1/6] media: rc: update sunxi-ir driver to get base clock frequency from devicetree

Hi Philipp, On Tue, Dec 19, 2017 at 09:07:42AM +0100, Philipp Rossak wrote: > This patch updates the sunxi-ir driver to set the base clock frequency from > devicetree. > > This is necessary since there are different ir receivers on the > market, that operate with different frequencies. So this

Re: [PATCH v2 0/2] PCI: mediatek: Fixups for the IRQ handle routine and MT7622's class code

On Thu, 2017-12-21 at 10:08 +0800, honghui.zh...@mediatek.com wrote: > From: Honghui Zhang > > Two fixups for mediatek's host bridge: > The first patch fixup the IRQ handle routine to avoid IRQ reentry which > may exist for both MT2712 and MT7622. > The second patch

Re: [PATCH v2 0/2] PCI: mediatek: Fixups for the IRQ handle routine and MT7622's class code

On Thu, 2017-12-21 at 10:08 +0800, honghui.zh...@mediatek.com wrote: > From: Honghui Zhang > > Two fixups for mediatek's host bridge: > The first patch fixup the IRQ handle routine to avoid IRQ reentry which > may exist for both MT2712 and MT7622. > The second patch fixup class type for MT7622.

[PATCH v2 2/2] PCI: mediatek: Fixup class type for MT7622

From: Honghui Zhang The host bridge of MT7622 has hardware code the class code to an arbitrary, meaningless value, fix that. Signed-off-by: Honghui Zhang --- drivers/pci/host/pcie-mediatek.c | 12 1 file changed, 12

[PATCH v2 0/2] PCI: mediatek: Fixups for the IRQ handle routine and MT7622's class code

From: Honghui Zhang Two fixups for mediatek's host bridge: The first patch fixup the IRQ handle routine to avoid IRQ reentry which may exist for both MT2712 and MT7622. The second patch fixup class type for MT7622. Change Since v1: - Add the second patch. - Make

[PATCH v2 1/2] PCI: mediatek: Clear IRQ status after IRQ dispatched to avoid reentry

From: Honghui Zhang There maybe a same IRQ reentry scenario after IRQ received in current IRQ handle flow: EP device PCIe host driverEP driver 1. issue an IRQ 2. received IRQ 3. clear IRQ

[PATCH v2 0/2] PCI: mediatek: Fixups for the IRQ handle routine and MT7622's class code

From: Honghui Zhang Two fixups for mediatek's host bridge: The first patch fixup the IRQ handle routine to avoid IRQ reentry which may exist for both MT2712 and MT7622. The second patch fixup class type for MT7622. Change Since v1: - Add the second patch. - Make the first patch's commit

[PATCH v2 1/2] PCI: mediatek: Clear IRQ status after IRQ dispatched to avoid reentry

From: Honghui Zhang There maybe a same IRQ reentry scenario after IRQ received in current IRQ handle flow: EP device PCIe host driverEP driver 1. issue an IRQ 2. received IRQ 3. clear IRQ status

[PATCH v2 2/2] PCI: mediatek: Fixup class type for MT7622

From: Honghui Zhang The host bridge of MT7622 has hardware code the class code to an arbitrary, meaningless value, fix that. Signed-off-by: Honghui Zhang --- drivers/pci/host/pcie-mediatek.c | 12 1 file changed, 12 insertions(+) diff --git a/drivers/pci/host/pcie-mediatek.c

[PATCH v2 0/2] PCI: mediatek: Fixups for the IRQ handle routine and MT7622's class code

From: Honghui Zhang Two fixups for mediatek's host bridge: The first patch fixup the IRQ handle routine to avoid IRQ reentry which may exist for both MT2712 and MT7622. The second patch fixup class type for MT7622. Change Since v1: - Add the second patch. - Make

[PATCH v2 0/2] PCI: mediatek: Fixups for the IRQ handle routine and MT7622's class code

From: Honghui Zhang Two fixups for mediatek's host bridge: The first patch fixup the IRQ handle routine to avoid IRQ reentry which may exist for both MT2712 and MT7622. The second patch fixup class type for MT7622. Change Since v1: - Add the second patch. - Make the first patch's commit

[PATCH v2 2/2] PCI: mediatek: Fixup class type for MT7622

From: Honghui Zhang The host bridge of MT7622 has hardware code the class code to an arbitrary, meaningless value, fix that. Signed-off-by: Honghui Zhang --- drivers/pci/host/pcie-mediatek.c | 12 1 file changed, 12

[PATCH v2 2/2] PCI: mediatek: Fixup class type for MT7622

From: Honghui Zhang The host bridge of MT7622 has hardware code the class code to an arbitrary, meaningless value, fix that. Signed-off-by: Honghui Zhang --- drivers/pci/host/pcie-mediatek.c | 12 1 file changed, 12 insertions(+) diff --git a/drivers/pci/host/pcie-mediatek.c

<    1   2   3   4   5   6   7   8   9   10   >