Not every arch has io or DMA memory.
So, unbreak the build by fixing the dependencies.
Signed-off-by: Richard Weinberger
---
drivers/scsi/hisi_sas/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/scsi/hisi_sas/Kconfig b/drivers/scsi/hisi_sas/Kconfig
index 37a0c71..f9157f4
Am 26.01.2016 um 11:15 schrieb John Garry:
> On 25/01/2016 22:24, Richard Weinberger wrote:
>> Not every arch has io or DMA memory.
>> So, unbreak the build by fixing the dependencies.
>>
>> Signed-off-by: Richard Weinberger
>> ---
>> drivers/scsi/hisi_s
On Thu, Nov 21, 2013 at 9:34 AM, Paul Bolle wrote:
> (Eddie was added as maintainer a few months ago, so Eddie receives this
> message too.)
>
> On Wed, 2012-06-27 at 21:26 +0200, Paul Bolle wrote:
>> During each suspend and resume cycle a mysterious message is added to
>> the logs:
>> CPU 1 o
On Fri, Jan 17, 2014 at 2:37 PM, Dorau, Lukasz wrote:
> Hi
>
> My story is very simply...
> I applied the following patch:
>
> diff --git a/drivers/scsi/isci/init.c b/drivers/scsi/isci/init.c
> --- a/drivers/scsi/isci/init.c
> +++ b/drivers/scsi/isci/init.c
> @@ -698,8 +698,11 @@ static int isci_p
On Wed, Jul 9, 2014 at 8:51 PM, KY Srinivasan wrote:
>
>
>> -Original Message-
>> From: Christoph Hellwig [mailto:h...@infradead.org]
>> Sent: Wednesday, July 9, 2014 1:44 AM
>> To: KY Srinivasan
>> Cc: linux-ker...@vger.kernel.org; de...@linuxdriverproject.org;
>> oher...@suse.com; jbotto
On Thu, Jul 10, 2014 at 12:33 PM, Richard Weinberger
wrote:
> On Wed, Jul 9, 2014 at 8:51 PM, KY Srinivasan wrote:
>>
>>
>>> -Original Message-
>>> From: Christoph Hellwig [mailto:h...@infradead.org]
>>> Sent: Wednesday, July 9, 2014 1:44
On Sat, Mar 31, 2018 at 3:59 AM, Wakko Warner wrote:
> I reported this before but noone responded.
Because you're sending only to LKML.
CC'ing storage folks.
> I have an iscsi target setup with /dev/sr[012] using pscsi. On the
> initiator, I mount only 1 disc. Then I issue find -type f | xargs
Hi!
I can reliably trigger the following warning by physically detaching my disk
array after
stopping md1.
---cut---
[ 149.780554] md: md1 stopped.
[ 149.780559] md: unbind
[ 149.782025] md: export_rdev(sdh1)
[ 149.782039] md: unbind
[ 149.786026] md: export_rdev(sdg1)
[ 149.786038] md: u
On Sat, Nov 29, 2014 at 11:52 AM, Simon Danner wrote:
> Hello,
> i get the following crash after i try to copy files from a broken
> external hdd to another external hdd.
> It happens after a few minutes, with latest git and 3.17.4 from Arch.
> Attached screenshot is from latest mainline git.
>
>
berman wrote:
>> I need more of the stack if you have it, the screenshot is not attached.
>> Thanks
>> Laurence
>>
>> On Sun, Nov 30, 2014 at 6:11 AM, Richard Weinberger
>> wrote:
>>> On Sat, Nov 29, 2014 at 11:52 AM, Simon Danner
>>> wrote
Michal,
Am 05.04.2017 um 13:31 schrieb Michal Hocko:
> On Wed 05-04-17 09:47:00, Vlastimil Babka wrote:
>> Nandsim has own functions set_memalloc() and clear_memalloc() for robust
>> setting and clearing of PF_MEMALLOC. Replace them by the new generic helpers.
>> No functional change.
>
> This on
Pavel,
On Mon, May 8, 2017 at 11:28 AM, Pavel Machek wrote:
> Are you sure you have it right in JFFS2? Do you journal block erases?
> Apparently, that was pretty much non-issue on older flashes.
This is what the website says, yes. Do you have hardware where you can
trigger it?
If so, I'd love to
On Mon, May 8, 2017 at 12:49 PM, Pavel Machek wrote:
> Aha, nice, so it looks like ubifs is a step back here.
>
> 'clean marker' is a good idea... empty pages have plenty of space.
If UBI (not UBIFS) faces an empty block, it also re-erases it.
The EC header is uses as clean marker.
> How do you
Boris,
Am 08.05.2017 um 13:48 schrieb Boris Brezillon:
>>> How do you handle the issue during regular write? Always ignore last
>>> successfully written block?
>
> I guess UBIFS can know what was written last, because of the log-based
> approach + the seqnum stored along with FS nodes, but I'm
14 matches
Mail list logo
